← All posts

8 July 2026 · 4 min read

How we run a cohort, and why it is 12 weeks

A technical scenario on screen during a session

People ask why our cohorts run for twelve weeks and not, say, a weekend intensive. The short answer is that speaking under pressure improves with repetition spread over time, not with a burst you forget a week later. Twelve weekly sessions give you eleven chances to notice a habit and one more to have fixed it.

A fixed group of eight to ten

The group does not change week to week. That matters more than it sounds. By week three you know the people, so you stop performing and start talking. The room feels safe enough to take a risk and get it wrong, which is the only way anyone gets better at speaking.

One real scenario per week

Every session is a situation you meet at work: a design review, an incident postmortem, a stakeholder update. You get the brief in advance and prepare a position. Then you argue it, live, with the group. Roles rotate, so over the programme you practise leading the discussion, challenging it, and reporting on it.

The error log is the point

After each session we pull your recurring mistakes from the recording and add them to your personal log, most frequent first, with a timestamp so you can hear yourself make them. Not a wall of corrections. The three or four patterns that actually hold you back. Watching that list shrink over twelve weeks is the clearest picture of progress we know how to give.

Practise this with a cohort of engineers at your level.

View upcoming cohorts