Fictional example · DeliveryShorter waits between development and release.
Teams complete changes quickly, but a shared release process leaves work waiting.
The architectural insight
Deployment dependencies and shared ownership create more delay than development itself.
A possible intervention
Separate one frequently changed capability, define compatibility checks and clarify release ownership.
Approved change to production20 → 12 days
Illustrative before → after. Comparable changes across two eight-week periods; median lead time.
Track recovery time and change failure rate alongside speed.
Fictional example · AI evaluationAnswers that take less effort to verify.
An assistant prepares architecture summaries, but reviewers spend too long checking its claims.
The architectural insight
Fluent answers conceal the cost of verification.
A possible intervention
Require source evidence, test missing-information handling and use a fixed review rubric.
Outputs with unsupported claims18 → 6
Illustrative before → after. The same 100 synthetic evaluation tasks; outputs with at least one unsupported factual claim.
Investigate remaining errors before wider adoption.
Fictional example · AlignmentProgramme decisions made sooner.
Teams repeatedly revisit design choices because competing requirements remain unresolved.
The architectural insight
Clear ownership and escalation are missing.
A possible intervention
Create a shared dependency view, assign decision owners and define escalation points.
Decision turnaround15 → 6 days
Illustrative before → after. Comparable twelve-week periods; median working days per decision.
Account for differences in decision scope and complexity.