Another company's AI success story won't transfer to yours
DORA research shows AI returns vary widely between organizations using the same tools. The variance is the signal: measure your own baseline and your own bottlenecks before copying a playbook.
Written by
-
Benedikt Stemmildt Founder & Co-CEO
Published: 4 March 2026 Updated: 1 min read
Your competitor’s AI success story is useless to you. The data shows why.
The data shows wide variance
DORA’s research describes AI as an amplifier: it magnifies the strengths of high-performing organizations and the dysfunctions of struggling ones (opens in a new tab).
Same tools. Same models. Wildly different outcomes.
Why the outcomes differ
- “Just turn it on” creates confusion. Developers use AI differently. Code quality varies wildly. Security gaps appear randomly.
- Culture eats tools for breakfast. Organizations that punish AI-assisted “mistakes” see developers hide their usage entirely.
- No shared context, no shared results. Without structured conventions and documentation, every developer reinvents the wheel.
- Copy-pasting someone else’s playbook ignores your specific bottlenecks, codebase, and team dynamics.
The variance is the signal
What worked for Spotify won’t automatically work for you. Their culture, codebase, and challenges are different. The variance is the signal.
AI adoption is not a technology rollout. It’s a change management initiative, the same as Agile 20 years ago: the same resistance, the same organizational dynamics, the same need for structured enablement.
What actually helps
- Measure your own baseline first. You can’t improve what you don’t measure.
- Run controlled experiments: one team, one codebase, real data.
- Identify your bottlenecks. Not the industry’s. Yours.
- Build your own enablement programs: shared context, shared conventions, shared results.
The companies closing the variance gap have one thing in common: they stopped copying and started measuring.
Further reading
Written by
-
Benedikt Stemmildt · Founder & Co-CEO
More on Measuring AI impact
- Morgan Stanley saved 280,000 hours by reading old code Most teams point AI at code generation. Morgan Stanley pointed it at code understanding, the step where developer time actually went.
- The highest AI returns come from automation, not time savings Data from more than 2,500 self-reported use cases shows time savings as the most common goal and the most modest return. Risk reduction, agentic automation and broad adoption pay off more.
- GenAI creates more work before it creates less A German study of IT leaders finds 73% still have the trough of the J-curve ahead of them. Its authors call the next 18 months decisive.
Test the constraint in your system
The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.
Training on this topic: Agentic Engineering for Engineering and Product LeadersWant to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check