role · product owner

Product Owner

The chain's spine. The PO names the change, predicts what will happen, runs the check, and writes the model update so the next cycle inherits a sharper version of the understanding.

What good looks like

A competent PO produces three artefacts every cycle, all of them readable by someone who wasn't in the room:

1. A Feature Brief that begins with a named person's day, contains a five-field prediction, and is signed by the trio.
2. A signal reading — five lines, written next to the brief, on the date the brief said it would be written.
3. A model update — assumptions closed, new ones added, at least one template or checklist sharpened.

A PO who produces these three artefacts every cycle has the chain working. A PO who produces one or two has work to do; a PO who produces none has not yet learned the role.

The PO's stance

The PO is responsible for	The PO is not responsible for
What the team is solving	What the team builds
The prediction	The implementation
The relationship with the named person	The relationship with the codebase
The brief, the signal reading, the model update	The ADR, the runbook, the deploy
Killing the initiative when needed	Coding around the initiative being wrong

The PO holds the chain by holding the artefacts that span it.

Three artefacts to read first

These three pages, read in order, give you the centre of the role:

1. Volume II · Part 7 — Feature Brief
2. Volume II · Part 9 — Prediction Writing
3. Volume V · Part 6 — The Model Update

First 30 days

A six-step gated track for a new PO. Each step has an output someone else can verify.

Day 1–3 — Read the canon

Read Volume II Introduction → Part 9 in order. Read Volume V Parts 1, 2, 5, 6. Stop reading when the corpus's voice becomes familiar — typically by the end of week 1.

Output: in your own words, three sentences explaining what Volume II hands to Volume III.

Day 4–7 — Sit next to a named person

Find one of the named people the team is currently building for. Schedule 90 minutes. Sit next to them. Use the observation note format. Do not interview during.

Output: an observation note, time-stamped, with at least one workaround the person has stopped noticing.

Day 8–14 — Write a Feature Brief

Pick one moment from the observation note. Write the brief. Use the corpus's Feature Brief shape. Get the trio to sign.

Output: a signed Feature Brief with a five-field prediction.

Day 15–18 — Hold amigos

Pull the first story. Hold a 45-minute amigos session with the developer and QA. Produce three Gherkin scenarios, including a negative case.

Output: signed Gherkin set linked from the story.

Day 19–25 — Watch the first 48h

When the flag enables, you watch the dashboards (not support tickets) for the first 48 hours. Take notes; do not act on first-hour noise.

Output: a one-page note of what you observed, with a clear distinction between first-contact noise and signals worth following up on.

Day 26–30 — Run the check, write the model update

On the date in the brief, run the check. Write the signal reading. Hold the retro. Write the model update.

Output: signal reading next to the brief, retro change committed, model update with at least one template adjustment.

By day 30 you have run one full cycle. The full curriculum continues at PO foundations.

Deepening — self-rate yourself

Once you've run a few cycles, deepen across these dimensions. Rate yourself 1–5 honestly. Below 3 in any dimension means that's the next thing to invest in.

Discovery

• I can identify, in 10 minutes with a stakeholder, whether we have witnessed the problem or only described it.
• I can run an observation session that produces a useful note even when the named person is in a regulated environment I can't enter.
• I can detect when a brief is being written from a solution backwards, before any signatures are on it.

Skill paths to deepen here: PO foundations (steps 2–4) · PO practitioner — Discovery (planned).

Brief discipline

• I can write a Feature Brief in 90 minutes that the trio signs without rewrite.
• I can identify, in three sentences, the difference between a Feature Brief and a Technical Design Brief on the same topic.
• I can refuse to sign my own brief when one of the five prediction fields is weak.

Read: Feature Brief · Initiative Brief.

Prediction & signal

• The check runs on the date in the brief, every cycle.
• My signal reading has a gap line that names one specific thing.
• I can convert a signal reading into a model update in under an hour.

Skill path to deepen here: PO foundations · steps 4, 8, 9.

Portfolio sense

• I can recommend killing an initiative without it being a personal moment.
• I read DORA + VRI quarterly and can name what changed.
• I can defend a do nothing option in a Solution Options conversation.

Read: Volume V · The Portfolio · Volume I · Portfolio Direction.

Client cadence

• The weekly client update goes out every Friday before 4pm in 200 words.
• The bi-weekly sync runs the corpus's fixed agenda; feature requests stay in the backlog process.
• I can hold the SLA review as a contract conversation, not a sales conversation.

Read: Volume V · The Ongoing Relationship.

Stuck if…

The anti-symptom catalogue. Senior practitioners catch themselves here. Each item points at the chain level it traces to.

…your prediction has all five fields and reality still surprises you

You probably have a brief that didn't witness. Check the baseline — was it captured by query or by sitting next to the person? Read Clinic — A brief that didn't witness. The fix is in Volume II · Observation, not in the prediction shape.

…your retros keep producing the same change

The change isn't owned, isn't dated, or isn't testable. Re-read Volume V · Retrospective. The discipline is one change. owned. dated. testable. Lists do not compound.

…you have ten initiatives in flight and the team feels exhausted

Concentration limit broken. Re-read Volume V · The Portfolio. The chain default is no more than half the team's capacity on first-cycle initiatives. Cut.

…the client surprises you in the bi-weekly sync

The weekly written update isn't doing its job. Either it isn't going out, or it isn't shaped right (shipped / in progress / blocked). The sync should never be where the client first hears something — that's the no-surprises rule from Volume V · Postmortems generalised.

…your team has stopped pushing back on briefs

Most likely cause: amigos has decayed into rubber-stamping, or the trio has lost trust that resistance produces a better brief rather than a delayed cycle. Re-read Volume III · Amigos & Gherkin. Resistance handled well produces a smaller, more honest brief.

…you cannot remember the named person mid-cycle

The brief began with a category, not a person. Either the brief never had a real named person, or the person decayed into a persona during scope. Re-read Volume II · Person & Moment. The brief's experience snapshot should be re-read at every Epic kickoff.

…leadership is briefed by you in meetings, not by reading artefacts

The chain artefacts have become illegible to leadership — or they've never tried to read them. Quarterly portfolio review with the three-artefact agenda fixes the second problem. The first is a structural fix to the briefs themselves.

…an initiative you're proud of has been alive for two cycles with no signal moving

Strong candidate for kill. Read Volume V · The Portfolio · When to stop. Killing is the chain's most disciplined act. Continuing because you're proud is the failure mode.

See also

• Skill path — PO foundations
• Canon — Volume II · Volume V
• Practice — Writing predictions
• Clinic — A brief that didn't witness