A playbook for program owners
Most cohort programs peak on day three and decline from there.
This isn’t a failure of design or enthusiasm. It’s the default. You bring people together, the energy is real, everyone means it when they say they’ll stay in touch — and then they go back to jobs that immediately reclaim all of their attention. Six weeks later the group chat has gone quiet. Six months later you’re planning the next cohort and quietly hoping this one goes differently.
It can. But the things that determine whether a cohort survives happen before it convenes, and most of them are unglamorous.
Here’s the sequence that works.
Before the cohort convenes
Open the network at registration, not at the event.
The most common mistake is treating the online component as a follow-up. By the time everyone has gone home, the moment has passed — you’re now asking people to adopt something new with no energy behind it.
Instead, invite participants in when they register. Weeks of low-stakes activity before anyone travels does something you can’t buy later: by day one, people already recognize names. The room starts warm.
Seed the first questions yourself.
An empty network stays empty. Someone has to go first, and it shouldn’t be a participant.
Post three or four real questions in the weeks before the event. Why are you coming? What are you working on that you’re stuck on? What would make this worth the time away from your desk? These are genuinely useful to you as a program designer, and they establish the norm that asking is what happens here.
Recruit your Gurus deliberately, and tell them what they’re getting.
You’ll need a core of experienced people willing to answer. Identify fifteen or twenty and ask them directly — past participants, senior members, board members, alumni.
When you ask, don’t pitch it as a favor. Most program owners recruit Gurus as though asking for charity, and it recruits poorly. Be specific about what they get: confirmation that what they spent a career learning is worth something to someone else, a clean and visible bit of good in a job where most wins are ambiguous, a way to serve their field that costs ten minutes instead of a board seat. For people near the end of a career, it’s the difference between their judgment leaving with them and their judgment outliving them.
Then be equally specific about the cost. Not a standing monthly call. Ten minutes, on a phone, whenever they have it. That’s the sentence that converts.
Set the expectation that everyone holds both roles.
Say this out loud at the start, or your cohort will sort itself into teachers and students within a week and stop being a network.
Every participant is an Explorer on the things they haven’t done and a Guru on the things they have. The most senior person in your cohort is an Explorer on what’s changed since they last did the job. The most junior is a Guru on something nobody above them has looked at closely in a decade. Name this early, and name it again when someone says they have nothing to contribute — because the people who say that are usually wrong, and they’re the ones most likely to go quiet.
During
Put it into sessions, not around them.
Have presenters pose a question to the cohort mid-session and pull responses from the room. This does two things at once: it makes the session better, and it converts the platform from something participants were told about into something they’ve used.
Watch what people are actually asking.
The questions are the best programming research you will ever have. You’re seeing what your field is struggling with in real time, in participants’ own words, not filtered through a post-event survey nobody enjoys filling out.
Don’t over-facilitate.
The instinct is to manage the conversation. Resist it. Your job at this stage is to have made asking easy and then to get out of the way. Heavily moderated communities read as staff-run, and people participate less in staff-run spaces.
After — the part that decides everything
The first two weeks matter more than the next six months.
This is where programs lose it. Everyone goes home, work reclaims them, and the window closes quietly.
Have something ready to go out within days. One good question to the full cohort, while the room is still fresh in everyone’s mind. That single prompt, sent at the right moment, is worth more than any amount of activity you try to generate in month four.
Keep a slow, steady cadence.
A meaningful question every couple of weeks. Not a newsletter — a question, which asks for something and therefore creates participation rather than consumption.
Enough to stay present. Not so much that it becomes noise people learn to skip.
Close the loop publicly.
When someone acts on advice they received and something happens, surface it. This is the single most underused move in program management.
It matters for the Explorer, obviously. But it matters more for the Gurus, who almost never find out whether their advice was any good. Most people never report back. Showing a Guru that their ten minutes changed a specific outcome for a specific person is the thing that brings them back for the next twenty questions — and it costs you nothing but attention.
Let the next cohort inherit this one.
Don’t archive a cohort when the program year ends. The value compounds: your second-year participants become Gurus to your first-years, which solves your Guru recruitment problem permanently and gives your alumni a reason to stay connected that isn’t a donation request.
This also fixes the structural weakness of any program with rotating leadership. Institutional memory usually walks out the door every year. A persistent network keeps it.
<h2>What your participants are actually building</h2>
When you report on a cohort, you’ll be tempted to report on content delivered — sessions run, speakers booked, topics covered. That’s the least durable thing your program produces.
The specific advice someone receives in your cohort has a shelf life. The industry shifts, their situation changes, and within a few years most of the particulars are obsolete. What doesn’t expire is the set of habits that repeated, real exchange builds in a person. Those are worth naming explicitly, to participants and to your board, because they’re what justifies running the program at all.
Turning a mess into a question. Problems don’t arrive as questions. They arrive as a fog of half-formed worries and competing pressures. Compressing that into one clear, answerable question is a discipline, and it’s most of the work — participants routinely discover they’ve answered half of it themselves just by sharpening it.
Synthesizing conflicting input. Ask five experienced people the same question and you’ll get five sincere, partly contradictory answers. The instinct is to find the right one and follow it. The skill is recognizing that each person is describing what worked in their circumstances, then building an approach that fits yours. A cohort produces this naturally, because multiple Gurus answer the same question.
Judging credibility. Not titles, not how impressive someone sounds. Relevance to the actual situation, willingness to describe what went badly, a track record you can examine. Telling the difference between authoritative and knowledgeable is learned only through repetition.
Urgency about what matters. Not busyness. Most people move quickly on things that don’t matter while the decision that determines their next five years sits untouched. Cohorts surface this fast, because participants see what their peers are prioritizing.
Follow-up and follow-through. Going back to report what happened. Almost nobody does it, which is exactly why the ones who do get disproportionate attention for the rest of their careers.
Obligation to something larger. The shift from being a person who receives help to a person who owes some. In a cohort where everyone holds both roles, this happens on its own — usually the first time a participant realizes they’re the one with the answer.
None of these come from a curriculum. They come from practice: asking real questions of real people about consequential decisions, repeatedly, and being on the other side often enough to see the exchange from both directions. Your program is one of the few places where that practice is available at all.
What to measure
Attendance and satisfaction scores tell you about the event. They tell you nothing about whether the cohort is alive.
Track instead:
• Questions asked per participant — the real engagement number, and the one that predicts everything else.
• Response rate and time to first response. An unanswered question is the fastest way to kill a network. If something sits for three days, intervene.
• Breadth of participation. If 80% of answers come from five people, you have a help desk, not a network, and those five will burn out by spring.
• Activity at day 30, day 90, day 180. This is the decay curve, and it’s the only number that tells you whether you solved the actual problem.
• Relationships that went one-to-one. Hard to capture and worth asking about directly, because it’s where sponsorship starts.
The thing you’re really building
The reason to do any of this isn’t engagement metrics.
Cohort programs exist because sustained contact between experienced people and people coming up is what changes careers. Not the sessions — the relationships that form around them. And what ultimately moves someone into a senior role isn’t mentorship but sponsorship: a person with standing who knows your work well enough to advocate for you when you aren’t in the room.
Sponsorship can’t be assigned. It grows out of exactly the kind of repeated, substantive, low-stakes contact that a three-day convening starts and then terminates.
Your program already creates the conditions. The playbook above is just about not letting them expire in week six.
**To talk through a launch for your own cohort or program, visit turtlewise.net or email info@turtlewise.net.**