They had improved the system. They couldn't prove it.
A major Canadian bank had been running a large DevOps program. Teams had made real changes. Then leadership asked a simple question: what has actually improved?
Nobody could answer confidently because no useful baseline had been established before the work began.
So we started by making the system visible. We created a common way to track work across teams and focused measurement on what would help us decide what to improve next. Then we worked through a series of constraints: deployment friction, team access, environment and resource setup, and other problems surfaced by the teams.
There wasn't one magic fix. There was a sequence: understand the constraint, make an intervention, measure the result, learn, and move to the next one.
Over roughly a year, average cycle time across the teams we measured dropped from 20 weeks to 1 week.




