How it works
Every Hand-Off Is A Compression Event
What is the 8 Ways Context Disappears diagnostic?
Your developers already have AI.
What your agents do not have is your institution.
The credit policy behind a rule, the decision behind an architecture pattern, the incident behind a regression test. Every SDLC hand-off, from demand to requirement, requirement to design, design to code and code to test, compresses that knowledge. Experienced people used to fill the gaps from memory. Agents cannot. They produce code that works and fails at the same time: technically correct, operationally or regulatorily wrong.
We only see anonymous usage statistics, and a summary of your results if you choose to contact us.
- 01ScoreRate each of the eight patterns: 0 if you rarely see it, 1 if it happens sometimes, 2 if it happens often.
- 02TotalAdd up a score out of 16 that places your delivery in one of three bands.
- 03StartSee your highest-scoring patterns, what closes each one, and a report to share.
Why it matters now
- 90%of technology professionals now use AI at work.Google DORA, 2025
- 66%of developers are frustrated by AI output that is “almost right, but not quite.”Stack Overflow Developer Survey, 2025
- −7.2%estimated delivery stability associated with a 25% rise in AI adoption.Google DORA, 2024
How to score each pattern
- Rarely (0)
- You rarely see this pattern in your delivery.
- Sometimes (1)
- It happens on some journeys, teams or releases.
- Often (2)
- It happens often enough that people expect it.
Few leaders see every hand-off. Requirements, architecture, development, test and release often sit with different teams and partners.
Loop in a colleague for the stages you do not own. Send them this diagnostic, and their scores fill in the patterns you have left blank.