how we work · teams
Teams
A role is a stance, not a title. The hub for each role names what good looks like, the three artefacts a competent practitioner produces, the gated path from first day to depth, and the anti-symptoms that tell a senior they've drifted.
A 200apps team is a trio plus the surfaces around it — Product Owner, Tech Lead, Designer, joined by Developer, QA, CS Lead, On-call, and Leadership. Each role holds part of the chain. The hubs make that explicit.
What every hub contains
Each role hub has four entry points:
- Landing — what this role is for, the stance, the three artefacts of competence.
- First 30 days — a gated six-step track for a new hire. Each step has an output someone else can verify.
- Deepening — a self-rated maturity matrix. Below 3 in any dimension means that's the next thing to invest in.
- Stuck if… — anti-symptom catalogue. Senior practitioners catch themselves here.
The eight roles
- Product Owner · the chain's spine — briefs, predictions, signal, model update
- Tech Lead · ADRs, sequence/schema/API, runbooks, postmortem structure
- Designer · journey, flow, design system, content design
- Developer · domain language in code, trunk-based, pair, review
- QA · amigos, Gherkin, exploratory, pre-merge, accessibility
- CS Lead · L1/L2/L3, support-to-bug pipeline, helpdesk metrics
- On-call · runbooks, incidents, comms during, postmortem
- Leadership · vision, goals, portfolio, kill decisions
The trio
Three roles hold the brief together. They sign it. They sit at amigos. They share the postmortem table. The corpus calls them the trio:
| Role | What they hold |
|---|---|
| Product Owner | The named person, the prediction, the model update |
| Tech Lead | The technical feasibility, the constraint, the ADR |
| Designer | The journey, the moment, the flow |
The trio's signature on a Feature Brief is the corpus's discipline against drift. A brief that goes downstream without all three signatures is unfinished.
Cross-role artefacts
Some artefacts are produced by the trio, not by a single role. The hubs link to the same artefact from each angle:
- The Feature Brief appears in PO (writes), Designer (signs), Tech Lead (signs), QA (reads at amigos).
- The Postmortem appears in Tech Lead (drives), On-call (timeline), PO (chain-level), Leadership (no surprises).
- The Release brief to client appears in PO (writes), CS Lead (handoff), Tech Lead (technical confirmation).
Reading patterns by role
- New hire — start at your role's First 30 days tab. Do not skip steps.
- Returning practitioner — open Deepening and self-rate. Pick the lowest dimension.
- Stuck in a cycle — open Stuck if… and find the symptom. The fix points back to a chain level.
- Hiring or growing into the role — start at Landing. The three artefacts of competence are what a successful first cycle produces.