{"id":21172,"date":"2026-07-07T13:57:04","date_gmt":"2026-07-07T18:57:04","guid":{"rendered":"https:\/\/securedb.io\/kb\/?p=21172"},"modified":"2026-07-07T13:57:04","modified_gmt":"2026-07-07T18:57:04","slug":"leadership-compass-admin-setup-checklist","status":"publish","type":"post","link":"https:\/\/securedb.io\/kb\/?p=21172","title":{"rendered":"Leadership Compass Admin Setup Checklist"},"content":{"rendered":"\n<p>Use this checklist when preparing Leadership Compass for a new organization, cohort, or participant group.<\/p>\n\n\n\n<p>A clean setup helps participants start smoothly, helps Leaders and Facilitators support the right people, and helps Champions manage progress without confusion.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who should use this checklist?<\/h2>\n\n\n\n<p>This checklist is for users responsible for setting up or managing Leadership Compass.<\/p>\n\n\n\n<p>That may include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Admins<\/li>\n\n\n\n<li>Champions<\/li>\n\n\n\n<li>implementation leads<\/li>\n\n\n\n<li>HR or learning and development owners<\/li>\n\n\n\n<li>program coordinators<\/li>\n\n\n\n<li>internal support contacts<\/li>\n\n\n\n<li>external implementation partners<\/li>\n<\/ul>\n\n\n\n<p>Participants, Leaders, and Facilitators may not need every setup step, but understanding the setup process can help with troubleshooting.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Setup overview<\/h2>\n\n\n\n<p>Before launching a cohort, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Leadership Compass is enabled<\/li>\n\n\n\n<li>the organization is correct<\/li>\n\n\n\n<li>the cohort is created<\/li>\n\n\n\n<li>the cohort name is clear<\/li>\n\n\n\n<li>the correct pillars are enabled<\/li>\n\n\n\n<li>participant access is ready<\/li>\n\n\n\n<li>Leaders are assigned<\/li>\n\n\n\n<li>Facilitators are assigned, if used<\/li>\n\n\n\n<li>pricing or unlock settings are correct<\/li>\n\n\n\n<li>notifications are understood<\/li>\n\n\n\n<li>support contacts are ready<\/li>\n\n\n\n<li>launch timing is intentional<\/li>\n<\/ul>\n\n\n\n<p>Most problems after launch come from missing assignments, unclear roles, duplicate accounts, or incorrect cohort settings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Confirm Leadership Compass is enabled<\/h2>\n\n\n\n<p>Before creating a cohort, confirm that Leadership Compass is enabled for the organization.<\/p>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the correct organization or client account is selected<\/li>\n\n\n\n<li>Leadership Compass access is active<\/li>\n\n\n\n<li>the organization has the correct package or permissions<\/li>\n\n\n\n<li>the right users can access setup tools<\/li>\n\n\n\n<li>any required feature flags or unlocks are active<\/li>\n<\/ul>\n\n\n\n<p>If Leadership Compass does not appear, resolve access before building the cohort.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Confirm organization context<\/h2>\n\n\n\n<p>Make sure you are working in the correct organization.<\/p>\n\n\n\n<p>This is especially important if you support multiple companies, business units, or client accounts.<\/p>\n\n\n\n<p>Before continuing, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>organization name<\/li>\n\n\n\n<li>account or workspace<\/li>\n\n\n\n<li>program owner<\/li>\n\n\n\n<li>launch contact<\/li>\n\n\n\n<li>support contact<\/li>\n\n\n\n<li>expected participant group<\/li>\n<\/ul>\n\n\n\n<p>Do not create a cohort in a test or wrong organization unless that is intentional.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Define the cohort<\/h2>\n\n\n\n<p>Create or review the cohort.<\/p>\n\n\n\n<p>A clear cohort setup should include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>cohort name<\/li>\n\n\n\n<li>cohort purpose<\/li>\n\n\n\n<li>participant group<\/li>\n\n\n\n<li>launch timing<\/li>\n\n\n\n<li>expected completion timing<\/li>\n\n\n\n<li>assigned Champion or owner<\/li>\n\n\n\n<li>enabled pillars<\/li>\n\n\n\n<li>Facilitator plan<\/li>\n\n\n\n<li>Leader assignment plan<\/li>\n<\/ul>\n\n\n\n<p>Use a name that will make sense later.<\/p>\n\n\n\n<p>For example:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>2026 Leadership Compass &#8211; Executive Team<\/li>\n\n\n\n<li>Spring Manager Cohort<\/li>\n\n\n\n<li>New Leader Development Group<\/li>\n\n\n\n<li>Leadership Compass Pilot Cohort<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Select enabled pillars<\/h2>\n\n\n\n<p>Confirm which pillars should be available for the cohort.<\/p>\n\n\n\n<p>Leadership Compass may be configured for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pillar 1 only<\/li>\n\n\n\n<li>Pillars 1\u20133<\/li>\n\n\n\n<li>all five pillars<\/li>\n\n\n\n<li>another available package or configuration<\/li>\n<\/ul>\n\n\n\n<p>Before launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>which pillars are included<\/li>\n\n\n\n<li>whether the selected package supports them<\/li>\n\n\n\n<li>whether the client expects all five pillars<\/li>\n\n\n\n<li>whether disabled pillars should stay hidden<\/li>\n\n\n\n<li>whether completion logic matches enabled pillars<\/li>\n<\/ul>\n\n\n\n<p>Disabled pillars should not count against participant progress.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Confirm pricing or unlock settings<\/h2>\n\n\n\n<p>Some cohorts may depend on pricing, package, or unlock settings.<\/p>\n\n\n\n<p>Before launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the correct package is selected<\/li>\n\n\n\n<li>the right pillars are unlocked<\/li>\n\n\n\n<li>paid or premium features are available<\/li>\n\n\n\n<li>guide generation is included if expected<\/li>\n\n\n\n<li>Facilitator tools are available if needed<\/li>\n\n\n\n<li>post-program features are available if expected<\/li>\n<\/ul>\n\n\n\n<p>If a participant cannot see a pillar or feature, package or unlock settings may be the reason.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Add participants<\/h2>\n\n\n\n<p>Add the participants who should complete Leadership Compass.<\/p>\n\n\n\n<p>Before launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>participant names<\/li>\n\n\n\n<li>email addresses<\/li>\n\n\n\n<li>organization membership<\/li>\n\n\n\n<li>account status<\/li>\n\n\n\n<li>duplicate accounts<\/li>\n\n\n\n<li>correct cohort assignment<\/li>\n\n\n\n<li>participant role access<\/li>\n<\/ul>\n\n\n\n<p>Email accuracy matters. A user invited with one email may not see the cohort if they log in with a different email.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Review duplicate users<\/h2>\n\n\n\n<p>Duplicate accounts can create confusion.<\/p>\n\n\n\n<p>Watch for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the same person listed twice<\/li>\n\n\n\n<li>personal and work email versions of the same user<\/li>\n\n\n\n<li>spelling differences<\/li>\n\n\n\n<li>old inactive accounts<\/li>\n\n\n\n<li>manually created users who were later invited again<\/li>\n<\/ul>\n\n\n\n<p>Before launch, decide which account should be used.<\/p>\n\n\n\n<p>If possible, clean up duplicates before participants begin.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 8: Assign Leaders<\/h2>\n\n\n\n<p>If Leaders will support participants, assign them before launch.<\/p>\n\n\n\n<p>Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>which Leaders need access<\/li>\n\n\n\n<li>which participants belong to each Leader<\/li>\n\n\n\n<li>whether Leaders are also Participants<\/li>\n\n\n\n<li>whether Leaders should see only assigned participants<\/li>\n\n\n\n<li>whether Leader access is scoped correctly<\/li>\n<\/ul>\n\n\n\n<p>Leader assignments affect dashboard visibility.<\/p>\n\n\n\n<p>If a Leader cannot see a participant, assignment is the first thing to check.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 9: Assign Facilitators<\/h2>\n\n\n\n<p>If the cohort uses Facilitators, assign them before launch.<\/p>\n\n\n\n<p>Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>whether the cohort has Facilitators<\/li>\n\n\n\n<li>whether Facilitators are internal or external<\/li>\n\n\n\n<li>whether Facilitators support the whole cohort or selected participants<\/li>\n\n\n\n<li>whether Facilitators need participant reflection access<\/li>\n\n\n\n<li>whether feedback tools are enabled<\/li>\n\n\n\n<li>whether check-ins or messaging are enabled<\/li>\n<\/ul>\n\n\n\n<p>Facilitator assignment affects reflection review, feedback, messages, and check-ins.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 10: Review external or virtual users<\/h2>\n\n\n\n<p>Some programs may include external Facilitators, consultants, or virtual users.<\/p>\n\n\n\n<p>Before launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>whether external users need access<\/li>\n\n\n\n<li>whether they have the correct email<\/li>\n\n\n\n<li>whether they belong to the right organization context<\/li>\n\n\n\n<li>whether they have the correct role<\/li>\n\n\n\n<li>whether their access should be limited<\/li>\n\n\n\n<li>whether they can see only what they need<\/li>\n<\/ul>\n\n\n\n<p>External access should be intentional and scoped carefully.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 11: Review privacy expectations<\/h2>\n\n\n\n<p>Before participants begin, make sure privacy expectations are clear.<\/p>\n\n\n\n<p>Participants should understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>who can see progress<\/li>\n\n\n\n<li>who can see reflection cards<\/li>\n\n\n\n<li>whether Facilitators can provide feedback<\/li>\n\n\n\n<li>what Leaders can see<\/li>\n\n\n\n<li>what Champions can manage<\/li>\n\n\n\n<li>how guide sharing works<\/li>\n\n\n\n<li>what content is private unless shared<\/li>\n<\/ul>\n\n\n\n<p>Clear privacy expectations help participants reflect more honestly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 12: Prepare launch communication<\/h2>\n\n\n\n<p>Do not rely only on automated notifications.<\/p>\n\n\n\n<p>Before launch, prepare a message that explains:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>what Leadership Compass is<\/li>\n\n\n\n<li>why the participant is included<\/li>\n\n\n\n<li>when to begin<\/li>\n\n\n\n<li>what the expected timeline is<\/li>\n\n\n\n<li>who to contact for help<\/li>\n\n\n\n<li>what support is available<\/li>\n\n\n\n<li>whether guide sharing is expected<\/li>\n\n\n\n<li>what Leaders or Facilitators will do<\/li>\n<\/ul>\n\n\n\n<p>A clear launch message reduces support questions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 13: Confirm notifications<\/h2>\n\n\n\n<p>Before launching, confirm what notifications may be sent.<\/p>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>cohort launch emails<\/li>\n\n\n\n<li>participant invitations<\/li>\n\n\n\n<li>reminder expectations<\/li>\n\n\n\n<li>Facilitator notifications<\/li>\n\n\n\n<li>Leader notifications<\/li>\n\n\n\n<li>guide sharing invitations<\/li>\n\n\n\n<li>message or check-in notifications<\/li>\n<\/ul>\n\n\n\n<p>Also confirm whether the organization\u2019s email system may block automated emails.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 14: Launch the cohort<\/h2>\n\n\n\n<p>Launch only after setup is reviewed.<\/p>\n\n\n\n<p>Before clicking launch or making the cohort active, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the cohort name is correct<\/li>\n\n\n\n<li>participants are correct<\/li>\n\n\n\n<li>enabled pillars are correct<\/li>\n\n\n\n<li>Leaders are assigned<\/li>\n\n\n\n<li>Facilitators are assigned<\/li>\n\n\n\n<li>package or unlock settings are correct<\/li>\n\n\n\n<li>support contacts are ready<\/li>\n\n\n\n<li>timing is appropriate<\/li>\n<\/ul>\n\n\n\n<p>After launch, verify that at least one participant can access the cohort successfully.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 15: Monitor early activity<\/h2>\n\n\n\n<p>The first few days after launch are important.<\/p>\n\n\n\n<p>Watch for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>participants who cannot log in<\/li>\n\n\n\n<li>participants who do not see the cohort<\/li>\n\n\n\n<li>duplicate account issues<\/li>\n\n\n\n<li>missing Leader assignments<\/li>\n\n\n\n<li>missing Facilitator assignments<\/li>\n\n\n\n<li>notification problems<\/li>\n\n\n\n<li>participants who have not started<\/li>\n\n\n\n<li>questions about privacy or expectations<\/li>\n<\/ul>\n\n\n\n<p>Early support prevents small issues from becoming larger problems.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 16: Review progress during the cohort<\/h2>\n\n\n\n<p>As the cohort progresses, review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>participant start status<\/li>\n\n\n\n<li>pillar completion<\/li>\n\n\n\n<li>reflection card acceptance<\/li>\n\n\n\n<li>guide readiness<\/li>\n\n\n\n<li>guide completion<\/li>\n\n\n\n<li>Facilitator feedback activity<\/li>\n\n\n\n<li>Leader follow-up needs<\/li>\n\n\n\n<li>participants who may be stuck<\/li>\n<\/ul>\n\n\n\n<p>Use progress data to support people, not pressure them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 17: Prepare for guide completion<\/h2>\n\n\n\n<p>As participants finish enabled pillars, confirm that the guide workflow is ready.<\/p>\n\n\n\n<p>Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>reflection cards are accepted<\/li>\n\n\n\n<li>guide generation is available<\/li>\n\n\n\n<li>guide editing expectations are clear<\/li>\n\n\n\n<li>signing expectations are clear<\/li>\n\n\n\n<li>sharing options are understood<\/li>\n\n\n\n<li>Facilitators are ready to support review, if needed<\/li>\n<\/ul>\n\n\n\n<p>Participants may need reminders that guide quality depends on accepted reflection cards.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 18: Plan post-program support<\/h2>\n\n\n\n<p>Leadership Compass should continue to support leadership practice after the active cohort work is complete.<\/p>\n\n\n\n<p>Plan for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>post-program dashboard use<\/li>\n\n\n\n<li>alignment moments<\/li>\n\n\n\n<li>guide review conversations<\/li>\n\n\n\n<li>Leader support<\/li>\n\n\n\n<li>Facilitator check-ins<\/li>\n\n\n\n<li>recommitment conversations<\/li>\n\n\n\n<li>follow-up reminders<\/li>\n\n\n\n<li>future cohort planning<\/li>\n<\/ul>\n\n\n\n<p>The end of the cohort should lead into continued use.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 19: Close or archive the cohort<\/h2>\n\n\n\n<p>When the cohort is complete, decide whether it should remain active, move into post-program use, or be archived.<\/p>\n\n\n\n<p>Before closing or archiving, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>participants completed expected work<\/li>\n\n\n\n<li>guides are generated or signed, if required<\/li>\n\n\n\n<li>sharing expectations are complete<\/li>\n\n\n\n<li>progress has been reviewed<\/li>\n\n\n\n<li>unresolved access issues are closed<\/li>\n\n\n\n<li>follow-up plans are documented<\/li>\n<\/ul>\n\n\n\n<p>Do not archive a cohort too early if participants still need access.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common setup mistakes<\/h2>\n\n\n\n<p>Common setup mistakes include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>creating the cohort in the wrong organization<\/li>\n\n\n\n<li>adding participants with the wrong email<\/li>\n\n\n\n<li>forgetting to assign Leaders<\/li>\n\n\n\n<li>forgetting to assign Facilitators<\/li>\n\n\n\n<li>enabling the wrong pillars<\/li>\n\n\n\n<li>missing unlock or package settings<\/li>\n\n\n\n<li>launching before communication is ready<\/li>\n\n\n\n<li>not checking for duplicate accounts<\/li>\n\n\n\n<li>assuming notifications were received<\/li>\n\n\n\n<li>unclear privacy expectations<\/li>\n\n\n\n<li>unclear completion expectations<\/li>\n<\/ul>\n\n\n\n<p>Most of these can be prevented with a pre-launch review.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pre-launch checklist<\/h2>\n\n\n\n<p>Before launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Leadership Compass is enabled.<\/li>\n\n\n\n<li>The correct organization is selected.<\/li>\n\n\n\n<li>The cohort name is clear.<\/li>\n\n\n\n<li>The enabled pillars are correct.<\/li>\n\n\n\n<li>Pricing or unlock settings are correct.<\/li>\n\n\n\n<li>Participants are added.<\/li>\n\n\n\n<li>Duplicate users have been reviewed.<\/li>\n\n\n\n<li>Leaders are assigned.<\/li>\n\n\n\n<li>Facilitators are assigned, if needed.<\/li>\n\n\n\n<li>External users are scoped correctly.<\/li>\n\n\n\n<li>Notifications are understood.<\/li>\n\n\n\n<li>Launch communication is ready.<\/li>\n\n\n\n<li>Support contacts are ready.<\/li>\n\n\n\n<li>Privacy expectations are clear.<\/li>\n\n\n\n<li>The cohort timing is intentional.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Post-launch checklist<\/h2>\n\n\n\n<p>After launch, confirm:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>participants can access the cohort<\/li>\n\n\n\n<li>launch notifications were received or alternative communication was sent<\/li>\n\n\n\n<li>participants are beginning work<\/li>\n\n\n\n<li>Leaders can see assigned participants<\/li>\n\n\n\n<li>Facilitators can see assigned participants<\/li>\n\n\n\n<li>support questions are being answered<\/li>\n\n\n\n<li>progress is updating<\/li>\n\n\n\n<li>reminders are sent thoughtfully<\/li>\n\n\n\n<li>completion expectations remain clear<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Common questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can I change the enabled pillars after launch?<\/h3>\n\n\n\n<p>This depends on your setup. Be careful changing pillars after participants have started, because it may affect progress and completion expectations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I add participants after launch?<\/h3>\n\n\n\n<p>Usually yes, if the workflow allows it. Confirm that late-added participants receive the right instructions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I change Leader assignments after launch?<\/h3>\n\n\n\n<p>This may be possible. After changing assignments, confirm that the Leader can see the correct participants.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I change Facilitator assignments after launch?<\/h3>\n\n\n\n<p>This may be possible. Confirm that reflection review, messages, and check-ins still make sense after the change.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I launch before assigning Leaders and Facilitators?<\/h3>\n\n\n\n<p>Usually no. Assign support roles first unless the cohort is intentionally self-guided.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should I test the workflow before inviting everyone?<\/h3>\n\n\n\n<p>Yes. Testing with one or two users can help confirm access, notifications, and role visibility.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting setup issues<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Participants cannot see the cohort.<\/h3>\n\n\n\n<p>Check organization, email address, account, cohort assignment, cohort status, and duplicate users.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Leaders cannot see participants.<\/h3>\n\n\n\n<p>Check Leader role assignment and participant assignment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Facilitators cannot see reflection cards.<\/h3>\n\n\n\n<p>Check Facilitator assignment and whether facilitator feedback tools are enabled.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Pillars are missing.<\/h3>\n\n\n\n<p>Check enabled pillars, package settings, and unlock settings.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Progress is not updating.<\/h3>\n\n\n\n<p>Check whether required reflection cards have been accepted and whether the participant has refreshed the dashboard.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Notifications are not received.<\/h3>\n\n\n\n<p>Check email address, launch status, spam or junk folders, organization email filtering, and whether notifications are enabled.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Best practices<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build the cohort before announcing it.<\/li>\n\n\n\n<li>Review the full setup before launch.<\/li>\n\n\n\n<li>Use clear cohort names.<\/li>\n\n\n\n<li>Confirm email addresses.<\/li>\n\n\n\n<li>Assign Leaders and Facilitators intentionally.<\/li>\n\n\n\n<li>Keep privacy expectations clear.<\/li>\n\n\n\n<li>Test access before broad launch.<\/li>\n\n\n\n<li>Monitor early activity.<\/li>\n\n\n\n<li>Use progress data to support people.<\/li>\n\n\n\n<li>Document lessons learned for future cohorts.<\/li>\n<\/ul>\n\n\n\n<p>A thoughtful setup creates a smoother Leadership Compass experience for everyone involved.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Use this checklist when preparing Leadership Compass for a new organization, cohort, or participant group. A clean setup helps participants start smoothly, helps Leaders and Facilitators support the right people, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":21173,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_helpful_status":1,"footnotes":""},"categories":[202],"tags":[211,203],"class_list":["post-21172","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-leadership-compass","tag-admins","tag-leadership-compass"],"wps_subtitle":"Use this checklist when preparing Leadership Compass for a new organization, cohort, or participant group.","_links":{"self":[{"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/posts\/21172","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=21172"}],"version-history":[{"count":2,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/posts\/21172\/revisions"}],"predecessor-version":[{"id":21175,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/posts\/21172\/revisions\/21175"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=\/wp\/v2\/media\/21173"}],"wp:attachment":[{"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=21172"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=21172"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/securedb.io\/kb\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=21172"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}