The six-month roadmap is mostly dead. When prototypes can be built in an afternoon, the cost of writing a design doc that imagines what users want often exceeds the cost of just building it and putting it in front of someone.
The new ritual: just-in-time decision making. Plans shift from design docs to discussions inside PRs and prototypes.
Click a state to walk the JIT loop. Green = valid next steps. Dim = invalid jumps.
The default move "go find the person who wrote it" is no longer optimal. The new norm: query Claude first with a specific question, and only escalate to a human when the model's answer hits its limit.
This isn't just a speed win — it reframes what humans should be asked. Stop interrupting senior engineers with questions Claude can answer from the repo. Save their attention for context Claude doesn't have.
Toggle to see how the same investigation ran before and after.
Code review is one of the most expensive engineering rituals. Claude is now a first-pass reviewer that handles the mechanical work — style, linting, common bug patterns, draft PR feedback — leaving humans to focus on the parts where their judgment is irreplaceable.
Use the buttons on each task to route it to Claude or humans. Try to match the team's actual split.
When generating code is no longer the bottleneck, the value of pure "coders" drops and the value of creative builders rises. Roles overlap; the silos thin out.
PMs ship code. Engineers ship copy and design. Designers prototype with working data. Hiring shifts: deemphasize raw coding throughput, emphasize product intuition and systems depth.
Click a role to see which tasks they now own that they didn't before.
The mechanical processes change, but they're held in place by three operating principles. Drop any one of them and the rest stop working.
- Every team member, including managers, drives Claude Code through real work every day.
- "100% Claude-assisted commits" is treated as the floor, not the goal.
- Pain points surface in your own backlog before they reach a customer.
- Managers begin as individual contributors before taking on people leadership.
- They keep enough hands-on time to feel the actual engineering experience.
- Information flows in fewer hops — fewer translations means less signal loss.
- Status meetings, ritualized planning, gatekept reviews — anything is on the table.
- The test: "Is this still serving its purpose? Can we automate it?"
- If the answer is no twice in a row, the process dies — without needing a committee.
Removing the typing bottleneck doesn't remove bottlenecks — it moves them. The new metrics watch where pressure shows up: how fast new hires ship, how long PRs take to merge, and how much of the work has Claude in the loop.
Hit "Measure" to see the relative pressure on each metric in an AI-native org.