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.
Boon treats a leadership cohort that completes as an operating system: named ownership, calendar architecture, make-up rules, holds, and escalation. You already chose a cohort. If participation drops in the early sessions, inspect the operating conditions before adding engagement tactics.
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 risk appears after the early sessions.
Operator pattern, not a cited sample. Boon uses session two as a practical inspection point because novelty has faded and ordinary work conflicts are visible. That is not a universal failure point. Check content, access, timing, facilitation, manager support, and the reason for each absence before treating operations as the 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
Boon recommends one accountable person who reviews attendance and follows up on misses. Adapt the role and time commitment to the program.
Calendar
Boon recommends placing live blocks on the work calendar before enrollment so participants and managers can see the commitment.
Make-up
Define a recovery path and a decision point for repeated misses. The exact window and consequence should fit the program and local policy.
Holds
Give between-session work a named place, such as a 1:1, practice block, or manager conversation, instead of relying on an unowned worksheet.
Escalation
Boon operating sequence: an unexplained repeat miss goes to the person's manager, then to the sponsor if ownership stalls. Adapt the sequence to your policies and the reason for absence.
If the week cannot hold a 90-minute block, time poverty is one hypothesis to test alongside content fit, access, facilitation, and manager support. If workload is the constraint, 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?
Boon recommends naming an owner, putting every live block on the work calendar before kickoff, writing a make-up rule, and placing holds for the work between sessions. The second-miss escalation is an operator sequence to adapt, not a universal completion threshold.
Why do people ghost a leadership cohort after session two?
Boon uses the early sessions, often session two, as a practical inspection point because novelty has faded and work conflicts are visible. That is an operator pattern, not a published failure curve. Content, access, timing, manager support, and other causes still need to be checked.
What is a make-up rule for a cohort?
A make-up rule is a written path for recovering missed work within a defined window. A recorded artifact plus a short catch-up, or a hold with the facilitator, are Boon starter options to adapt to the program.
Who owns cohort completion?
Boon recommends one named operator, with facilitators running the room and managers protecting the calendar. Sponsor presence at kickoff and midpoint is an operating default to adapt, not a sourced requirement.
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.