Design a 6-Week Cohort Curriculum From Your 1:1 Framework

1:1 to group already covered the transition and the tech. Course covers a product. Group tools cover the stack. This is teaching design: six weeks, one outcome, live vs async. The overtalker post is how you hold the room once it exists. A think-about-it follow-up is how you fill it. Do not remake the changeover.

Week	Live (60–75 min)	Async	Artifact
1	Contract + map	Intro + working agreement	One-sentence outcome
2	Diagnosis of the default	One experiment	Done / skipped
3	Hot seat (2)	Pair check	Mid-score
4	Pattern harvest	Reshape experiment	Keep / reshape
5	Hot seat (2)	Draft the next 30 days	Public commit
6	Close + next container	Case / testimonial ask	Completion or continue

Why Copying 1:1 Fails

You cannot paste twelve private hours into six group calls. People will sit back and wait for their turn to be the client. That’s a queue, not a cohort.

The fix: one outcome for the whole room. Individual experiments. Peer air. You referee.

Live vs Async

Live is for the thing that needs a room: contract, hot seat, harvest, close. Async is for the thing that needs a Tuesday: the experiment, a short prompt, a score.

If you lecture live, you stole their coaching minutes. Put teaching in a 8-minute async. If they won’t watch 8 minutes, they won’t do a 12-week course either.

The Week Map Rule

Each week has one live job. If week 3 tries hot seats and a teaching and a guest, you get none. Cut until the table above still fits on one page.

Protect week 6. Completion is a curriculum outcome, not a fade.

What Most Coaches Get Wrong

They design from their favorite modules, not from the 90-day outcome. Then week 4 is a random workshop.

They also under-spec async and then complain the group “isn’t engaged.” Engagement is a designed Tuesday, not a personality.

They skip the overtalker rule in the working agreement. Then week 2 is a podcast.

Turning a 1:1 Framework Into Weeks

Take the five things you always do in 1:1. Those are not six lectures. They are six jobs:

1. Contract the outcome
2. Diagnose the default
3. Run a live test
4. Harvest the pattern
5. Run a harder test
6. Close or continue

Each job gets a live hour and an async Tuesday. If your 1:1 framework has twelve stages, you have a course, not a cohort. Cut to six jobs or extend the container. Don’t smuggle twelve into six and call it intensive.

Enrollment Copy for This Map

The page should say the outcome, the six jobs, the live dates, and what async means. It should not say “community.” Community is a hope. The map is the product.

Attendance and Makeup

Write it in week 0: miss one live call, use the async + a 10-minute pair with another member. Miss two, we talk about completing. Do not offer private makeup sessions as a default. That turns the cohort back into 1:1 with extra steps.

If the room is chronically thin, you have an enrollment problem or a date problem. You do not have a “content” problem. Do not add a seventh week of teaching to rescue week 3.

Facilitator Notes (steal)

Week 1: you talk 30%. Week 3 and 5: you talk 15% — you are the clock. Week 6: you talk 25% and you close. If your talk-ratio climbs, you are lonely, not leading.

Week 0 is a letter, not a call: outcome, dates, async rule, attendance, how we interrupt. If they won’t read one page, they will not do Tuesday. Refund them before week 1. A full room of readers beats a full room of spectators.

Keep a kill list: modules you love that do not serve the six jobs. Review it after every cohort. If a favorite module didn’t change a Tuesday, it does not come back. Sentiment is how curricula bloat. After week 6, kill one thing before you add one thing. Never both.

When DIY Isn’t Enough

When enrollment, attendance, and async live in three tools, the map dies. A cohort rail (Scale) can hold the weeks. You still have to pick one live job per call.

---

Want a six-week map that doesn’t depend on you being the hero every Tuesday? Let’s talk.