How to design a leadership cohort that completes.
Ownership, calendar architecture, make-up rules, holds, and escalation. People ghost after session two. This is not engagement tips.
A leadership cohort that completes is an operating system: named ownership, calendar architecture, make-up rules, holds, and escalation. You already chose a cohort. People ghost after session two. Completion is an ownership and calendar problem, not a better icebreaker.
If you are still choosing the container, stop and use workshop vs cohort vs 1:1. If you do not yet have a named group, you do not have a completion problem. You have a design problem.
Session two is where the calendar tells the truth. Session one is where the invite did.
You already chose a cohort.
GROW is a cohort layer once the container is chosen. See GROW. This page will not sell a kickoff, a community hour, or a warmer opening round. TOGETHER is a team room for a working team, not a completion feature. TOGETHER is the wrong door if your problem is a named development group that thins out.
An emerging-leaders bench still needs this OS if you put them in a cohort. Design the bench first, then keep them finishing here.
Why they ghost after session two.
Operator pattern, not a cited sample. Session one has a sponsor and novelty. Session two lands on a week that already had a forecast. Nobody owns the miss. There is no make-up that fits. The between-session work was a worksheet. We do not publish a drop-off percentage. Treat the pattern as a diagnosis.
A finished workshop export is not enablement. We already said that in why a completed manager-workshop export is not enablement. An offsite commitments slide is not a plan either (that post). A cohort that does not complete is the same failure with better snacks.
Named ownership.
| Work | Accountable |
|---|---|
| Look at who missed and write the next action | Named cohort operator |
| Run the live room | Facilitator |
| Protect the hold on the team calendar | The person's manager |
| Show up at kickoff and midpoint | Sponsor |
Staff the operator hours on how to staff an internal coaching program manager. A facilitator who also "owns completion" in leftover minutes will not escalate.
Calendar architecture and holds.
Owner
One person looks at attendance every week and names the miss. Not a shared inbox. Hours for this seat are on the program-manager page.
Calendar
Every live block is on the work calendar before anyone applies. Adding dates after kickoff is how session three dies.
Make-up
A path inside a set number of days. After that, the seat is in question. Soft make-up is a polite goodbye.
Holds
The work between sessions has a hold (a 1:1, a practice, a manager conversation). Homework without a hold is a PDF.
Escalation
Second unexplained miss goes to the person's manager, then to the sponsor if the manager shrugs. Silence is how ghosting becomes culture.
If the week cannot hold a 90-minute block, you do not have an engagement problem. You have time poverty. Redesign the block on coaching for manager time poverty. Then come back to the OS.
No icebreaker rescue. If you are tempted to add energy, a Slack channel, or a nicer opening round, you are on the wrong diagnosis. Cut that idea. Fix the owner and the calendar.
Make-up rules and escalation.
Recommendation: first miss gets a make-up inside seven days. Second miss gets the manager. Third miss is a conversation about leaving the cohort so the remaining group stays a group. Write this before kickoff so it is not personal later.
Holds between sessions can be 1:1 coaching. That loop is the same 90-day discipline as the adoption playbook, applied to a named wave. The cohort is not finished because the live blocks were attended. It is finished because the between-work happened and the last block still had the same people.
Put the completion OS on this wave.
Bring the dates you already picked and who has ghosted. We will write owner, make-up, and escalation. No icebreakers.
Book a strategy callFrequently asked questions
How do you design a leadership cohort that people actually complete?
Name an owner, put every live block on the work calendar before kickoff, write a make-up rule, place holds for the work between sessions, and escalate after the second miss. Completion is an ownership and calendar problem. It is not a warmer opening exercise.
Why do people ghost a leadership cohort after session two?
Session one is social and sponsored. Session two is a Tuesday that already had a customer call. Without a make-up rule and an owner who notices, the group becomes optional. The content is rarely the reason.
What is a make-up rule for a cohort?
A written path when someone misses: a recorded artifact plus a 20-minute catch-up, or a hold with the facilitator, inside a set number of days. "Watch the video when you can" is how the cohort ends.
Who owns cohort completion?
One named operator. Facilitators run the room. Managers protect the calendar. The sponsor shows up twice. If completion is "everyone's job," it is nobody's.
Is this the same as choosing workshop vs cohort vs 1:1?
No. That page is whether a cohort is the right container. This page assumes you already chose a cohort and people are disappearing after session two.