200apps · how we work
Master Areas
Every discipline, craft, and operational practice the chain touches — mapped by where it lives, who owns it, and which volume addresses it.
The volumes describe the chain as a story. The areas describe it as a grid. Both are true. The story tells you what to do this week. The grid tells you whether the practice you are about to start has a home in the chain.
The thirteen sections
| # | Section | Phase | Primary owners | Volumes |
|---|---|---|---|---|
| 1 | Strategy & Direction | Before | Founder, Leadership, PO | I, II |
| 2 | Discovery & Research | Before | PO, Designer | II |
| 3 | Product Definition | Before | PO, Trio | II, III |
| 4 | Design & UX | During | Designer | III, IV |
| 5 | Architecture & Technical Design | During | Tech Lead | III, IV |
| 6 | Development & Code | During | Developer | IV |
| 7 | Quality & Testing | During | QA | III, IV |
| 8 | Pipeline & Operations | During | Tech Lead, DevOps | IV |
| 9 | Release & Communication | Boundary | PO | IV |
| 10 | Post-Release & Learning | After | PO, Tech Lead | V |
| 11 | Ongoing Operations & Client | After | PO, CS Lead | V |
| 12 | Team & Organizational | Continuous | Leadership, PO | V |
| 13 | Adoption & Evolution | Meta | PO, Leadership | V |
How a section is structured
Each section is a list of crafts. Each craft is a page. Every craft page declares:
- What the craft is — a working definition.
- Who owns it — the role(s) that produce or steward the artifact.
- Which volume addresses it — the narrative source of truth.
- Related crafts — adjacent practices that depend on or feed this one.
- Maturity —
gap,seed,draft,stable, orreviewed.
Gaps
A small number of areas exist in the chain — they show up in real teams every week — but are not yet addressed in any volume. They are flagged with maturity: gap. The current gaps:
- Market & competitive awareness
- Competitive analysis (as discovery input)
- Quantitative research (alongside observation)
- User testing / usability (validation before build)
- Pair programming / mobbing
- Infrastructure as code
- Team capacity planning (sustainable pace)
- Hiring for chain fit
- Cross-team coordination
- Artifact lifecycle (deprecation, lightweight track)
- Chain evolution (when to change the chain itself)
These are not omissions of importance — they are areas where the chain has not yet produced a volume's worth of considered practice. Filling them is part of the corpus's job.
How to use this index
- Pick a craft to read its definition and find the volume that addresses it.
- Pick a section to see how a discipline composes — which crafts feed which.
- Use the map to see the cross-graph between Volumes and Areas.