how we work · practice
Practice
Operational guides anchored to the canon. Each Practice page derives from a Volume section, takes 10–25 minutes, and tells you how to do the thing — with the failure modes named.
The Volumes are the canon. Practice pages are projections of the canon at the cognitive load you need when you're about to do the thing. Every Practice page declares derives_from: — the Volume anchor that owns the truth — so when the canon updates, the practice doesn't drift.
Shape
Every Practice page follows the same shape:
| Section | What it is |
|---|---|
| TL;DR | One paragraph. The thing in its smallest defensible form. |
| What it is | Definition. The artefact or activity. |
| Why it matters | What breaks without it. |
| How to do it | Step-by-step. Templates and checklists embedded or linked. |
| Evidence | What we know about this from our cycles or external research. |
| Anti-patterns | Common ways this goes wrong. Often pointed at a Clinic. |
| Further reading | The Volume part it derives from + adjacent Practice pages. |
Browse
Briefs & Discovery
- Writing predictions — the five-field discipline that makes a brief a brief.
Coming next
The corpus is being filled. Planned shape:
- Briefs & Discovery — Initiative briefs · Feature briefs · Technical Design briefs · Observation sessions · The Five Stations
- Stories & Scope — Epic kickoff · Story writing · Amigos · Story mapping · Walking skeleton
- Releases — Release gate · Gradual rollout · CS handoff · Release brief
- Checks & Signal — Check sessions · Signal reading · The model update
- Incidents & Postmortems — Containment · Postmortem session · Runbook authoring
- Operations — Daily triage · Weekly client update · Quarterly portfolio review
Clinics
Clinics are the corpus's anti-pattern teachers — corrupt artifacts with diagnoses. Each Practice page links to the Clinics that show its failure modes.