after we build — opening
Opening
As We Build ended with the flag enabled and the feature live. The team now faces the only question that matters: was this actually the thing we thought we were building?
Every previous volume produced a claim. Before We Build's brief witnessed a problem and predicted a change. What We Shape turned that prediction into Epics, stories, scenarios. As We Build ran the prediction through code and into production. Now reality answers. The forty-seven minutes Gal spent grading either fell to ten or they didn't. The brief was either a model that survived contact with the world, or it was a description of something that turned out to be different.
This phase is what the team does in the period when reality is answering. Not the celebration. Not the postmortem alone. The honest, sometimes uncomfortable, comparison between what was predicted and what happened — at every level, from the initiative bet down to the individual scenario. And then the step most teams skip: writing the model update so what was learned survives the conversation.
A cycle is not done when the feature ships. It is done when the prediction has been checked, the gaps named, the model updated, and the next cycle inherits a sharper version of the understanding. The question that runs through every part of this phase: where did meaning break — and did we fix it permanently?
The team that does this consistently is not the team that gets things right more often. It is the team that gets things slightly less wrong each cycle than the last — and the difference compounds.
What this phase covers
Ten parts. The first six close the current cycle. The last four address what every previous volume left in shadow — the team itself, the portfolio, and how to start.
- The First 48 Hours — what to watch, what to act on, what to let settle.
- Signal and the Prediction — running the check. The four outcomes. Why "not checked" is the only one with no value.
- Bugs and Their Roots — the bug taxonomy. Chain-aware root causes that trace every defect to its level.
- Incidents and Postmortems — contain before diagnose. Postmortems that produce structural changes, not feelings.
- The Retrospective — three questions. One change. Compounding rather than listing.
- The Model Update — the step most teams skip. Where learning survives the conversation.
- The Ongoing Relationship — support levels and escalation. The SLA as operational contract. Helpdesk metrics. Client cadence. Where the chain meets the people who pay for it.
- The Team — onboarding, T-shaped people, small teams, psychological safety, what happens when someone leaves.
- The Portfolio — the view across features and products. DORA metrics. Technical debt as chain gaps. VRI. When to stop.
- Adoption — how to start. Which practice first. The first cycle. What resistance looks like. What maturity feels like.
In the operational framework, this phase describes the Reflection phase — the work between the live feature (Execution, As We Build) and the next cycle's discovery (back to Before We Build). The Prediction that was named in Before We Build, kept alive through Scope in What We Shape, and made measurable in As We Build is finally checked here. The chain closes — and reopens — at the model update. These are not sections. They are the steps required for the system to learn.