Organising the Work: Lanes, Roles, OKRs, Workplan

Four tabs turn the DAO's plan into something trackable. The why behind them lives in the Owned Lanes Model and Measuring What Matters pages; these tabs are where you write it down.

Owned Lanes & Roles

This is the DAO's concrete map of who owns what.

1. In the Lanes table, list each lane: its Scope, the Lane name, its two owners (a pair), what the lane owns (its boundary), and the decisions the pair can make without asking. A larger DAO groups several lanes under a few scopes; a smaller one may have a scope per lane.
2. Fill the DAO-level roles: the DAO Lead (connects the lanes) and the Kambria Facilitator (facilitates from outside).
3. Fill the KDF roles — Order Handler, Operator, Organizer. One person may hold more than one.

Every DAO includes an onboarding lane. The names you set here feed the Roster, OKR, Workplan and Contributions tabs, so keep them consistent.

Screenshot: the Owned Lanes & Roles tab. Source: the DAO Workbook template.

OKR

1. Set the DAO Objective on the three impact axes — reach, depth, self-propagation — with a target for each.
2. For each lane, add its Key Results: checkable outcomes that express the lane's part of the Objective. The pair sets these themselves; the "% to target" fills in as the current number is entered.

Screenshot: the OKR tab. Source: the DAO Workbook template.

Workplan

The Workplan is where a lane's work becomes tasks anyone can pick up. For each task, write the lane, a task_id, the task, its Definition of Done (what "qualified" means), the owner, dates, and status. Paid tasks share their task_id with the Pay-Per-Task Scheme tab, so the plan and the payment stay linked. When several lanes push toward one shared goal, name that activity so cross-lane work is visible.

The Workplan is the plan, not the record. It defines each task and its Definition of Done — the standard a deliverable is later checked against. It does not carry the verification itself: whether a specific deliverable actually met its Definition of Done is recorded in the Contributions tab, where each delivered piece of work is logged, linked, reviewed by the three reviewers, and marked verified. Keep the two distinct — the Workplan says what "done" means; Contributions says whether a given deliverable reached it.

Screenshot: the Workplan tab. Source: the DAO Workbook template.

How the planning and delivery sheets work together

These two tabs are two different stages — plan first, then deliver and verify:

1. Plan it — Workplan. Each lane lists the tasks it will do: what the task is, who owns it, and its Definition of Done. This is the plan only; nothing is reviewed here.
2. Do the work. The owner completes the task.
3. Log it — Contributions. The contributor records the finished deliverable with its evidence (a link, file, or screenshot).
4. Verify it — Contributions (the three checks). The lane owner, the DAO Lead, and a DAO Facilitator each confirm the deliverable meets its Definition of Done. When all three confirm, it's Verified — no one verifies their own work.
5. Outcome. A verified paid task becomes payable (it flows into the Pay-Per-Task settlement and the Cashbook), and the contribution is recognised with KAT.

So "who reviews" already lives in Contributions, as the three checks — the Workplan stays a planning sheet.