role · leadership

Leadership

Leadership holds the chain at altitude. The vision sets what every cycle is for. The portfolio decides which cycles run. The kill decision is the most disciplined act of the role. Leadership's job is not to lead the cycles — it is to make the cycles answerable to something.

What good looks like

Competent Leadership produces three artefacts every quarter:

1. A portfolio review — every initiative reads against its bet. Kept, sharpened, or killed. Signed and dated.
2. A goal set — fewer than five. Each one with a metric, a check date, and a named owner. No goal without a method.
3. A read of the chain artefacts — leadership reads briefs, signal readings, and postmortems directly. Not summarised in meetings. The corpus is the medium.

A leader who produces these three is governing the chain. A leader who governs by meeting has the chain learning to perform rather than to report.

Leadership's stance

Leadership is responsible for	Leadership is not responsible for
The bet above any single cycle	Running the cycle
The portfolio's concentration	The story's slice
Killing initiatives that aren't moving	Killing initiatives faster than the cycle can answer
Reading the chain artefacts directly	Editing the artefacts
Holding no surprises in both directions	Being the team's first responder

Leadership holds the chain by making the cycle answerable to something larger than itself, and by not collapsing that altitude into operational meddling.

Three artefacts to read first

1. Vision & Mission
2. Portfolio Direction
3. The Portfolio (Did We Serve?)

First 30 days

Day 1–3 — Read the canon

Read Why We Build in full. Read Did We Serve? Parts 3, 4 (The Portfolio, Adoption). Read After We Build Part 6 (The Model Update).

Output: in five sentences, the bet 200apps is running this quarter — in your own words, not in the language of the existing slides.

Day 4–7 — Read every active brief

Open the active Feature Briefs across the studio. For each: is the person named, is the prediction five-field, is the check dated.

Output: a one-page note on the briefs you would not have signed.

Day 8–14 — Walk the portfolio

Sit with each PO. For each initiative: when did the signal last move, what is the next check date, what would it take to kill.

Output: a portfolio note — kept · sharpened · killed — with rationale per row.

Day 15–18 — Hold the first portfolio review

Run the quarterly portfolio review with the corpus's three-artefact agenda. Sign or refuse to sign each row.

Output: signed portfolio with kill decisions and rationale published.

Day 19–25 — Read a signal reading and a postmortem

Pick one cycle's signal reading and one recent postmortem. Read them, not the summary. Surface one chain-level observation back to the team.

Output: a written observation — not a directive — that the team can answer.

Day 26–30 — Set quarterly goals

Fewer than five. Each has metric, check date, owner. Each ties to the bet. Each has a method the team can run.

Output: signed goal set, published, anchored in the corpus.

Deepening — self-rate yourself

Bet discipline

• I can say in five sentences what 200apps is betting on this quarter.
• The bet has changed in response to evidence at least once in the last year.
• I can defend do nothing as a strategic move in a portfolio review.

Portfolio sense

• Concentration is honest — no more than half the studio's capacity is in first-cycle initiatives.
• I have killed an initiative without it being a personal moment.
• I read DORA and VRI quarterly and can name what changed.

Goal craft

• Every goal has a method.
• The check date holds, even when the goal is failing.
• I have killed a goal that no longer served the bet.

Reading the artefacts

• I read briefs, signal readings, and postmortems directly.
• I have changed a decision based on a chain artefact in the last quarter.
• I never use a meeting where a written artefact would do.

No surprises

• The client never learns something from the cycle for the first time in a meeting.
• The team never learns a leadership decision for the first time at the all-hands.
• I have stopped a release calmly, without it being a personal moment.

Stuck if…

…the studio is running ten initiatives and the team is exhausted

Concentration limit broken. Re-read The Portfolio · concentration limits. The chain default is half the team's capacity in first-cycle work. Cut.

…every cycle ends with leadership being surprised

You are not reading the briefs or the signal readings directly. The summary is filtering. Pick up the artefacts; the corpus is designed to be read.

…you can't say what is being killed this quarter

If nothing is being killed, the portfolio is accumulating. Re-read The Portfolio · When to stop.

…goals from last quarter weren't checked on their dates

A goal without a check date that holds is a wish. Hold the check date even when the goal is failing — that is the discipline.

…the client surprised you in a quarterly review

The PO's weekly client update isn't doing its job, or you aren't reading it. The no-surprises rule holds in both directions.

…a brief reached production with no named person

Stop signing briefs without a person. Re-read Person & Moment. This is a Level 2 chain failure; the structural fix is at the brief, not at the bug.

See also

• Skill path — Leadership foundations
• Canon — Why We Build · Did We Serve?
• Practice — Quarterly portfolio review · Kill criterion · SLA review · Weekly client update (read directly, not summarised)
• Templates — Portfolio review · Initiative Brief
• Checklists — Portfolio review · agenda · SLA review · agenda
• Clinics — An SLA review that became sales · An initiative without a goal
• Areas — 1 · Strategy & Direction · 12 · Team & Organisational
• Map — The Map · Owner → craft index