after we build · part nine
The Portfolio
The view across features and products. Technical debt as accumulated chain gaps. The financial translation. Client trust as the ultimate signal. When to stop.
Reading across the portfolio
The model update closes the loop for one feature. The portfolio view asks a different question: across all the features, all the products, all the cycles — where is the team's chain strongest and where is it weakest?
The data exists in the bug tracker. Over months, the chain-aware root-cause labels accumulate into a pattern.
- If 40% of high-severity bugs are
scenario-gap, the amigos practice needs attention — not a lecture, a structural change to the template or the preparation discipline. - If 25% are
observation-mismatch, the briefs are thinner than they need to be — the discovery sessions need to go deeper or longer.
The portfolio view is not a report. It is a diagnostic tool that tells the team where to invest in the chain itself.
DORA — the four system signals
The platform signals from Volume IV — lead time, change failure rate, deploy frequency, time to restore — are known in the industry as the DORA metrics (from the DevOps Research and Assessment program). They measure the health of the delivery machinery itself.
| Metric | Reads as |
|---|---|
| Lead time | How thick the chain is. Long lead time means a bottleneck somewhere. |
| Change failure rate | How often the chain ships something that has to be rolled back. |
| Deploy frequency | How often the chain is willing to commit. Low frequency hides problems. |
| Time to restore (MTTR) | How quickly the chain recovers when it breaks. |
A team that tracks DORA alongside the chain-aware root causes has a complete picture: how well does the chain carry meaning (root causes) and how well does the machinery run (DORA). Both matter. Neither alone is sufficient.
Technical debt as accumulated chain gaps
Technical debt is usually described as shortcuts in the code — quick fixes, missing tests, hardcoded values. Technical debt is not bad code. It is unresolved decisions in the chain — the accumulated cost of gaps that were not closed when they were found.
- A story pulled with a named gap that was never backfilled.
- A flag that was never cleaned up.
- An ADR that drifted but was never corrected.
Each one is a small amount of debt. Together, they are why the system is harder to change than it should be.
The treatment is the same as financial debt: name it, size it, pay it down deliberately. A team that spends 100% of its capacity on new features and 0% on debt is a team whose chain will degrade until new features take twice as long — because every change has to work around the accumulated gaps.
The financial translation
Every cycle produces a prediction with a value attached — grading time from 47 to 15 minutes, billing reconciliation from manual to automatic, pickup-line wait from 5 minutes to 30 seconds. These are not abstract improvements. They translate to hours recovered, errors prevented, trust built.
The Value Realization Index (VRI) is the percentage of the predicted value that actually reached the person.
- A VRI of 0.8 means 80% of the intended change happened.
- A VRI of 0.3 means the team delivered 30% of what it promised — and invoiced for 100%.
VRI is not a tool for billing disputes. It is the chain's financial conscience. A team that tracks VRI across cycles knows whether it is getting better at delivering value — not just shipping features, delivering the change the features were meant to produce.