how we work · roles

Roles

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, and a scaffolded path from first day to depth.

Each role hub has four entry points:

• Landing — what this role is for, and what good looks like.
• First 30 days — the gated linear track for new hires. Six steps, one cycle.
• Deepening — a menu of skills with a self-rated maturity matrix.
• You're stuck if… — the anti-symptom catalogue. Senior practitioners catch themselves here.

Roles in the corpus

• Product Owner · the chain's spine — briefs, predictions, signal, model update
• Tech Lead · ADRs, sequence/schema/API, runbooks, postmortem structure (coming)
• Designer · journey, flow, design system, content design (coming)
• Developer · domain language, trunk-based, pair, review (coming)
• QA · amigos, Gherkin, exploratory, accessibility (coming)
• CS Lead · L1/2/3, support-to-bug pipeline, helpdesk metrics (coming)
• On-call · runbooks, incidents, communication during, postmortem (coming)
• Leadership · vision, goals, portfolio, kill decisions (coming)

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).