Post-program coaching as aftercare: so the class is not the intervention.
Use a short coaching burst after a leadership program so the class is not the intervention.
The last live block is on the calendar. The room will empty on a Thursday. Friday, a sponsor asks what happens in the three months after. You own the leadership program. If the answer is a recap deck and a Slack channel, the class was the intervention.
Stay on aftercare. The job is a short coaching burst so the program transfers. This is not a second catalog. It is not a platform go-live. People already finished the class.
If the program ends when the room empties, you ran an event.
The empty room after the last block.
Operator pattern, not a cited sample. L&D just closed a leadership program. Attendance looked fine. The sponsor liked the energy. Nobody can name a conversation that changed the following Monday. The request that shows up next is a three-month window to reinforce and extend that learning, not a new menu.
An offsite commitments slide is not a plan (the offsite commitments slide is not a plan). The class gave people language. Aftercare is the hold where they use it on a live week, then stop.
A window, not a second catalog.
The class already ran
People sat in the room. They have language. Aftercare does not reteach the deck. It holds the week they try the thing the deck named.
The window has a stop date
A common operator pattern is about three months after the last live block, used to reinforce and extend that program, not to open general growth. If you cannot name the stop, you bought a quiet second program.
The work is transfer
One conversation they delayed. One standard they will say in a 1:1. One meeting they will run differently. If you cannot name the transfer, you are extending the class.
Training is the classroom. Coaching is the week (leadership development vs leadership training). A program that lists both and only staffs the room is already a training program (management development program guide). How you designed the whole thing still lives on how to build a leadership development program. This page is the burst you attach after.
Dose honesty.
Recommendation, not a trial. We do not have a session-count RCT for aftercare. Anyone who sells you one is guessing. What operators actually say in the room: two sessions are too few for some cohorts, four are too many for others. The number is a fit question. It is not a proof point.
Fit means the hold can survive the week, the coach can see a live attempt, and you will look at transfer before the stop date. More sessions are not kinder if the job was a burst and you quietly started a year.
No invented dose math. Do not publish a magic session count, a completion multiple, or an unused-seat story about the burst. If you cannot defend the number to the people in the cohort, you do not have a dose. You have a leftover budget.
What this is not.
| If you are actually deciding | Go here instead |
|---|---|
| First 90 days after a coaching platform buy goes live | The 90-day coaching adoption playbook |
| People ghost a cohort after they signed up | How to design a leadership cohort that completes |
| Optional coaching inside a program collapsed | Coaching as expectation, not an add-on |
| Workshop vs cohort vs 1:1 as the container | Workshop vs cohort vs 1:1 |
Platform go-live is the 90-day adoption playbook. Ghosting after signup is a cohort that completes. Opt-in inside the program is coaching as expectation, not opt-in. Container choice is workshop vs cohort vs 1:1. Come back here when the class finished and you still owe transfer.
Do not rebuild a workshop, then practice, then 1:1 sandwich and call it aftercare. That architecture is a different design argument. This page is a burst after a program you already ran. Coaching vs training (coaching vs training) is the category split. Aftercare is the calendar after the split.
What the burst actually holds.
Name two or three live attempts the class already pointed at. Put holds on the same calendar you used for the live blocks. GROW can stay the cohort you just ran. SCALE is the 1:1 burst after, matched to the person, not a public lab that reteaches the deck.
Look at transfer before the stop date: a conversation that happened, a standard that got said, a meeting they no longer run as a status dump. If the only evidence is that people liked the coach, you extended the event.
What good looks like. Recommendation, not a benchmark: the next sponsor can repeat the window, the stop date, and one behavior you will look at. If they still think aftercare is "more leadership content," you have not designed transfer. You have hoped the class would stick.
Put a burst after the class, or admit the class was the intervention.
Bring the program you just ran and the three-month window you actually have. We will write a short aftercare burst, or tell you this is still just an event.
Book a strategy callFrequently asked questions
How do you use coaching after a leadership program so the class is not the intervention?
Put a short, dated coaching burst on the calendar after the last live block. The class names the work. The sessions are where someone tries it on a live week. If the program ends when the room empties, the class was the intervention.
What is post-program coaching aftercare?
Aftercare is a bounded coaching window after a leadership program, used to reinforce and extend what the class already taught. It is not general growth for whoever is free. It is not a second catalog. It is transfer with a stop date.
Is this the same as a 90-day coaching adoption playbook?
No. The 90-day playbook is what you run after a coaching platform buy goes live: time-to-session, sponsor check-ins, course-corrects. This page assumes the leadership program already happened. The job is transfer after class, not adoption of a new platform.
Is this the same as designing a cohort that completes?
No. A cohort that completes is about ghosting after signup: ownership, holds, make-up rules. This page starts after people finished the class. Completion already happened. Transfer has not.