This page explains how work is organised inside a DEP 3 DAO. It is the heart of what is new in this cohort. Templates you can fill in — the Launch Kit, the All-DAOs Sync agenda — live on their own pages; this page explains the model they serve.

 

Why Lanes

Across earlier cohorts, a pattern kept appearing. Some members would become quiet — not because they didn't care, but because they weren't sure what to do, or how, and waiting felt safer than guessing. 

Looking closely, low ownership usually comes from one of three things:

•   “It's not really mine.” Someone else — the DAO lead, a working-group lead — seems to be the one really responsible, so I wait to be told.
•   “Waiting is safer than acting.” If I act on my own and get it wrong, that's on me; if I wait for direction, no one can fault me. Waiting is the rational choice.
•   “I can't see where my work goes.” I finish a task and don't see where it leads, so the next step feels like something to be assigned rather than something I carry.

The Owned Lanes model is built to address them directly — by changing what they are given to hold.

 

Three Choices, Aimed at the Three Causes

The model isn't one idea; it's three deliberate design choices, each aimed at one of the causes above. They're described in full in the sections that follow — here is the logic that ties them together.

•   Real ownership boundaries, not assigned tasks. Instead of a lead handing out tasks, each pair owns an area with real edges. It's yours, you decide within it without asking, and your name is on the result. Ownership doesn't grow by encouragement — it grows when something genuinely belongs to someone. This answers “it's not really mine.” The one condition: the DAO lead has to actually let the area go. Override it once, and the model breaks.
•   Pairs, not individuals or large groups. An individual who goes quiet is invisible; in a large group, responsibility dissolves and “someone else will do it.” A pair is the strongest unit of ownership — small enough that no one can hide, companioned enough that no one is alone. It takes the peer buddy idea from Cohort 2 and promotes it from support to shared ownership. This answers “waiting is safer than acting” and the invisibility of going quiet.
•   Self-set public commitments, not top-down targets. Not a KPI handed down by Kambria. Each pair declares to the whole cohort what they'll do this month, and afterwards tells what they did, what came of it, and where they're stuck. Ownership comes from the promise being your own and witnessed — not from being measured. This answers “I can't see where my work goes” by making each pair's arc visible, in their own words.

Everything below is these three choices, in detail.

 

What a Lane Is

A lane is a real, continuing area of a DAO's work that belongs to the people who run it. Not a task passed down, but a stream of work with edges — something a member can point to and say “this part is mine.”

A DAO is organised into lanes, grouped under a few broad scopes. Each lane lives for the length of the cohort, has clear boundaries, and carries the names of the pair who own it. Within its boundaries, the pair who own a lane decide what happens next — they don't wait to be told.

A lane is not the same as a task, and not the same as a working group:

A task	A lane
Is handed to you	Belongs to you
Ends when it's done	Continues through the cohort
Someone else decides what's next	You decide what's next, within your boundaries
Is anonymous once complete	Carries your name
Waiting for the next one is safe	Waiting means your lane stalls

 A lane is also different from a Cohort 2 working group. Working groups were organised by stage of work — one group gathered material, another turned it into outputs, another archived it — so each group depended on the one before it, and a slow handoff stalled everyone. Lanes are organised by ownership instead: each lane is a stream someone runs end to end, so progress depends on the owners, not on a chain of handoffs.

 

Lanes Are Held in Pairs

Each lane is owned by two people, not one. This is not mainly about splitting the work — it is about resilience and momentum.

•   No single point of failure. A lane owned by one person stops the moment that person gets busy, travels, or loses steam. A pair keeps the lane alive through the normal ups and downs of people's lives.
•   Nobody vanishes, nobody is alone. It is easy to quietly disappear when you're one of fifteen. It is much harder — and much less lonely — when one other person is holding the same lane with you.

Pairs are formed deliberately, so that each lane is likely to have at least one person actively moving it at any given time. The pair decides between themselves how to divide the work inside their lane — the model doesn't prescribe it.

 

Every Lane Comes With a Launch Kit

The earlier cohorts taught us that people freeze at the start — not throughout. Once someone is moving, they can steer; it's the blank first week that stalls them. So every lane comes with a Launch Kit: enough to get moving, and no more.

A Launch Kit starts with two things:

•   A guideline. The principles of the lane and, crucially, its decision boundaries — what the pair can decide on their own, and where the edges are.
•   A starter plan. A concrete plan for just the first two to three weeks — enough to carry the pair across the blank-page moment and into motion.

Notice what isn't in the kit by default: worked examples and detailed samples. This is deliberate. Handing a pair a finished example on day one invites them to copy it, and copying is the opposite of ownership. Instead, pairs are asked to think it through and try it themselves first — and samples and further guidance are provided when a pair genuinely needs them, not before.

This is a little slower than giving everything upfront, and that trade is intentional: the slower path builds real ownership, where the faster one builds dependence. It does ask something of Kambria in return — to observe closely enough to offer help at the right moment, so that a pair who is genuinely stuck gets support quickly rather than being left to struggle. The aim is neither to abandon nor to spoon-feed, but to let people find their own footing with a hand ready when they reach for it.

The Launch Kit is a runway, not a blueprint. It exists to get the pair moving, after which the lane is genuinely theirs.

 

Decision Boundaries: Where Ownership Actually Lives

Ownership is real only if decisions are real. Each Launch Kit states plainly what the pair can decide without asking — the channel to use, the theme to choose, the price to set within a range, who to invite. Inside those boundaries, the DAO lead does not override.

This is the hardest part of the model, and it is a matter of culture, not mechanism. In earlier cohorts the DAO lead was the person who assigned tasks and approved outputs. This model asks something different of them.

The shift the model asks of the DAO lead is from assigning and approving to connecting and stepping back. That shift is the real experiment in ownership.

Kambria's role does not change here. As in earlier cohorts, Kambria facilitates from outside — it does not execute, assign tasks, or override a lane. 

Boundaries protect both sides. They tell the pair where they are free, and they tell the lead where a decision genuinely belongs to the whole DAO — cross-lane choices, budget above a line, anything that commits everyone. Everything inside the line belongs to the pair.

 

What a Lane Commits To: Lane OKRs

Owning a lane means owning an outcome, not just an activity — so each lane sets its own goal. The DAO has an overall objective for the cohort; each lane defines the Key Results that express its part of it: concrete, checkable outcomes the pair commits to.

These key results are the pair's to set, not handed down. That is what makes them drive ownership rather than compliance — a goal you set yourself is one you carry, where a target imposed on you is one you meet and no more. Setting a lane's key results is one of the real decisions that lives inside a lane's boundaries.

Lane OKRs also give the All-DAOs Sync something concrete to be about: each pair speaks to its key results — what moved, what didn't, what they'll commit to next. How the cohort measures impact overall — and how lane key results roll up into a DAO's objective — is described on the Measuring What Matters page.

 

Every DAO Has an Onboarding Lane

In earlier cohorts, “inactive members” was a problem that belonged to no one in particular — and so it went unsolved. In DEP 3, every DAO has a pair whose work is exactly this: welcoming new people and turning sign-ups into active contributors — whether that is a lane of its own or the onboarding scope of the DAO.

By making it a lane with named owners, the thing earlier cohorts struggled with becomes a stream a pair is actually responsible for and steering — not a vague gap everyone notices and no one holds. Whatever else a DAO's lanes are, one of them always carries this.

 

Rhythms and Alignment

The cohort runs on two rhythms that do different jobs, plus a way of aligning lanes when they need to move together.

The weekly check-in. Each week the DAO meets briefly, facilitated by Kambria. This is the operational rhythm: each lane updates on how it's moving, who is stuck, what needs adjusting. It is short and practical, and it is how the cohort keeps a close enough eye on itself to catch a stalling lane early rather than a month too late — which matters especially in a first run of this model.

The All-DAOs Sync. About once a month, at each phase of the cohort, all the DAOs gather together — the whole cohort in one room. Each pair speaks to its key results: what its lane will focus on next, and the story of the period just gone — what they did, what came of it, and where they're stuck. This is the ownership rhythm, and it is more deliberate than the weekly check-in. It is also where the DAOs see each other's work, so the cohort moves as one and not as separate silos. The first All-DAOs Sync is the Kickoff that opens the cohort; the last is the Showcase that closes it.

The All-DAOs Sync is not a performance review. The commitment a pair makes is their own, presented to the wider cohort — and it is the fact that it is theirs, and heard by people they respect, that gives it weight. Being stuck is welcome here; a pair naming a blocker out loud is exactly how the cohort helps, and one DAO's stuck point is often another DAO's solved one.

Aligning lanes around shared activities. Weekly updates keep each lane visible, but visibility alone doesn't make lanes work together. When the DAO takes on something that needs several lanes at once — a campaign, a launch, a community push — an activity plan sets out the shared goal and shows how each lane contributes to it. Each lane still owns its part, but the parts are pointed at one outcome, so the lanes move together rather than in parallel. This is how cross-lane collaboration becomes concrete work rather than a good intention, and the DAO Lead — who keeps track of every lane — is often the one who sees when an activity plan is needed.

Not every week carries a deliverable — the space to absorb and integrate is deliberate, and part of how the cohort sustains its people. But the DAO stays in weekly contact throughout, so that rest is built into the work rather than a gap in it.

 

How Lanes Make Up a DAO

A lane is one pair. A DAO of fifteen people is therefore built from several lanes — and to keep them coherent, the lanes are grouped under a small number of scopes: broad areas of the DAO's work, usually three or four. A scope is a direction; the lanes inside it are the pairs who actually run that direction. One scope might be held by a single pair, another by two or three pairs working different parts of it.

This is the answer to a problem earlier cohorts kept hitting. With around fifteen members and only half active at any time, a DAO organised as one big group leaves most people waiting while a few carry everything. Owned Lanes is not a reason to make the DAO smaller — it is how a DAO of fifteen keeps everyone active: each person is in a pair that owns a real piece of the work, so there is no back row to sit in. The scopes keep those pairs pointed in shared directions rather than scattering.

A DAO defines its own scopes and lanes in its master plan — this is the first real act of ownership in the cohort, the point where the abstract model becomes this DAO's concrete shape. As an illustration, an operator DAO focused on a platform might set its scopes as:

•   Growth — bringing new people in — perhaps two pairs, one on outreach, one on partnerships
•   Activation — turning sign-ups into people actually doing the thing — the onboarding work every DAO has
•   Operations — keeping the platform and its users well served — one or more pairs depending on the load

Every DAO includes onboarding as one of its scopes or lanes — the pair (or pairs) whose work is welcoming new members and turning sign-ups into active contributors. The shape above is an example of the pattern, not a required structure; a healing or creative DAO will divide its work quite differently, and how many pairs sit under each scope depends on how many active members the DAO has.

 

Who Does What: Three Layers

The model works because three layers of people play clearly different roles, and none of them is the old “assign and approve” role.

 

Kambria (facilitator, from outside)

Kambria supports the cohort without running any DAO's work — the same facilitation role it held in earlier cohorts. In this model that includes the structural scaffolding that makes lanes possible:

•   providing each lane's Launch Kit
•   forming the initial pairs and lane assignments, based on members' stated interests and their profiles or interviews at kickoff
•   adjusting people and lanes as the cohort runs — when a lane stalls or a pairing isn't working — since this is a structural intervention, it sits with Kambria
•   facilitating the weekly check-in and the All-DAOs Sync

Kambria does not execute a lane's work or assign its tasks.

 

The DAO Lead (a participant, inside the DAO)

The DAO Lead is not the person who assigns tasks and approves outputs. In the Owned Lanes model the lead is the connective tissue across the lanes:

•   Keeps track. keeping track of where each lane is
•   Aligns and connects. connecting the lanes — making sure each knows what the others are doing, spotting where they could help each other, and flagging a lane that has gone quiet (to the pair, and if needed to Kambria)

The lead holds the whole picture, not structural power: adjusting people and lanes is Kambria's to do, and running the work inside a lane is the pair's. A DAO Lead may also own a lane themselves — in practice most will — but that is optional and separate from the connective role.

 

The pairs (lane owners)

The pairs run the lanes. Within their boundaries they decide what happens and do the work, without waiting to be told, and they carry their lane's story to the All-DAOs Sync. This is where the DAO's work actually happens, and where ownership lives.

How members move between owning a lane and contributing to one is described on the Member Roles & Contribution page.