The Cohort Arc

Communal Projects.

Not learning by simulation. Building something real, together, accountable to a cohort, bound to a fixed timeline, working for a stakeholder who will actually use what you make.

01 Mentorship 02 Conferences 03 Projects 04 Publication
In Formation
What this is

Building something real, together.

A hackathon compresses work into 48 hours of excitement and then disappears. What gets built is almost never used. Communal Projects are different: a 12–16 week structured programme in which a cohort of young people build something with a real stakeholder, held genuinely accountable to the people in the room with them.

Cohort members enter the project stage with two things already in place: a mentor relationship built during the first stage, and a conference encounter where their work was sharpened by peers and practitioners. The project is where those relationships stop being background support and become active guidance on something that is actually being built.

The harder skill is learning to build with other people. The cohort makes that unavoidable. It holds you accountable in ways no instructor or deadline can.

What gets built is real. A product used by real people. A research report submitted somewhere it will be read.

How it works

The structure of a real project.

Cohort

6–12 people, selected carefully.

Each cohort is small enough that no one can hide, and diverse enough for productive friction. Selection weighs individual capability against what the full cohort can do together. The team is part of the design.

Scope

A product, study, or initiative.

Projects span technology, research, policy, design, and community work. The common denominator is a real stakeholder: an organisation that needs what the cohort is building, and will use it when it is done. The project is not invented for the programme. The programme exists to get the project built.

Timeline

12–16 weeks, structured.

Weekly check-ins and milestone reviews at weeks four, eight, and twelve build toward a final presentation to the stakeholder and a broader Kronogon audience. The timeline is a commitment device: it makes abandonment harder than delivery.

Output

Something that gets used.

The output belongs to the cohort and the stakeholder. It does not go into a portfolio or to a professor. It goes directly to the stakeholder who asked for it, because that is who it was built for.

On community
"The community is the curriculum. You cannot learn to build with people except by building with people and being accountable to them when it gets hard."

The conviction behind Communal Projects.

Join the cohort arc

The first cohort is being formed.

If you are ready for the full arc (mentorship through to publication) or know someone who is, apply or nominate.

Apply to the arc Nominate someone →