Skip to content

Portfolio Direction

Which initiatives to fund, continue, or kill — the strategic decision the portfolio makes every quarter.

The portfolio is the set of initiatives the organisation is currently funding. This part of the volume describes the strategic side of the portfolio — what funding decisions to make, on what evidence. The operational side — DORA, VRI, kill mechanics — is in Volume V Part 9.

The portfolio is not a backlog. A backlog accumulates by default. A portfolio is curated by decision.

Three states, every initiative

At every portfolio review, every initiative is in one of three states.

StateMeaningWhat it produces
FundThis initiative is open and resourced for the next quarterCycle plans, briefs, predictions
ContinueThis initiative is in flight and on track; carry forwardContinued cadence, no new commitment
KillThis initiative will not continue; resources are releasedA kill brief, a model update, a portfolio note

There is no fourth state. Pause is one of the most common forms of organisational dishonesty — initiatives that are paused indefinitely consume attention without producing decisions. The corpus pattern: paused initiatives are renamed killed after one full quarter of inaction, with the option to re-fund as a new initiative if conditions change.

What the portfolio is for

Three jobs.

  1. Concentrate attention. A team can run a finite number of cycles in flight at once. The portfolio names the limit honestly.
  2. Surface conflicts early. Two initiatives that depend on the same scarce resource — the senior developer, the design system, the client's review time — are surfaced before the cycle runs, not during.
  3. Hold the chain to the goals. Every initiative maps upward to a goal. Initiatives that don't are surfaced and either re-justified or killed.

A portfolio review that does not produce at least one kill or re-justify in any given quarter is one where the discipline has decayed.

How to read an initiative at portfolio level

Three artifacts on the table per initiative.

  • The latest signal reading — what reality answered most recently.
  • The current V and the assumption status — what we said we would deliver and what we know about the path.
  • The chain-level rework distribution — where this initiative is producing rework, and at what level.

The portfolio reads these and asks the same three questions of every initiative.

  1. Is the prediction holding?
  2. Is the path still credible?
  3. Is the goal it serves still the goal we hold?

Three yes-es and the initiative continues. Any no and the conversation is open.

Concentration limits

The corpus default: no more than half the team's capacity is spent on initiatives whose first signal reading has not yet happened. This is the chain's anti-overcommitment rule. A team that has only first-cycle initiatives is a team running on hope, not on signal.

A second rule: no initiative should consume more than 40% of the team's quarter without an explicit portfolio acknowledgement. Concentration is sometimes warranted. It is always named, never accidental.

Kill culture

The hardest cultural fact the chain asks of leadership: killing is not failure. It is the chain's most disciplined act. The portfolio that never kills is one that has confused continuation with progress.

The corpus produces an artifact for every kill — a kill brief — that names what was learned, why the initiative is stopping, and what the next initiative inherits from this one's learning. The kill is the seed of the next decision, not the end of a story.

A team can be measured on its kills the way it is measured on its launches. A team that kills three initiatives in a year, each with a kill brief that joined the corpus, is healthier than a team that has never killed one.

What this volume produces, in one sentence

The chain runs because direction was named. Initiatives serve goals; goals serve a vision; the portfolio is curated, not accumulated; killing is part of the discipline; the financial chain is honest.

Back to the volume cover → · Volume II — Discovery & Brief →

200apps · How We Work · NWIRE