There’s a slide in every Inspect & Adapt that nobody looks forward to. Objectives committed: 31. Objectives delivered: 20. Say-do ratio: 65%. A roomful of capable engineers stares at a number that says, politely but publicly, you didn’t do what you said you’d do.
It stings — partly because the team worked hard for every one of those twenty objectives, and partly because the number is accurate. But here’s what the say-do ratio doesn’t tell you: when you lost the other 35%. Or why. Or which piece of it you could have renegotiated in week four, when there was still time to do something about it.
A number that deserves more respect than it gets
The say-do ratio is simple on purpose: what a team delivered, divided by what it committed to. In SAFe shops it travels alongside program predictability; everywhere else it just goes by “did we do what we said.” Either way, the “say” half deserves defending. It wasn’t a guess. It came out of PI planning, where the team held a fist-of-five confidence vote on objectives they had scoped against a real throughput window, a real capacity calendar, and a scope list they had argued over line by line. That vote is expert engineering judgment — the considered opinion of the people closest to the work — and the say-do ratio honors it by taking the commitment seriously enough to score it.
The problem isn’t the metric. It’s the timing.
Say-do is a trailing indicator. By definition, it can only be computed after the boundary has passed — after the PI ends, after the release ships or doesn’t. It’s a post-mortem: precise, honest, and delivered to a patient who is already on the table. Worse, it arrives unattributed. A 65% say-do doesn’t distinguish between a commitment that was wrong on day one and a commitment that was right on day one and eroded quietly for ten weeks. Those are different problems, and they have different cures.
Where the missing percent actually goes
The gap between say and do rarely shows up as one dramatic failure. It leaks in through the three things that quietly erode a committed release date: scope added after the vote, one “small” item at a time; dependencies that surface in week seven instead of week one; and capacity that changes when someone is borrowed, sick, or gone. Each one moves the real finish line a few days at a time — and none of them, individually, feels big enough to reopen the plan. Ten weeks later they’ve compounded into the 35% you’re staring at on the slide.
Keep the commitment live instead
A confidence vote is a snapshot. It was correct on the evidence the team validated the day it was taken. The question is what happens to it afterward. Release Management for Jira (Divim’s release planning app, formerly Advanced Release Planning) keeps that snapshot current: your committed date carries a live confidence band — 50/85/95% — recalculated at Monte Carlo scale on the same assumptions the team voted on. The team still owns those assumptions: which throughput window reflects reality, whose capacity counts, what’s actually in scope. The app just does the arithmetic continuously instead of once.
When something moves, you see it as erosion against the committed date, in days, attributed to its driver: this scope addition cost four days; that late dependency, six; the capacity change, three. Choosing what confidence level to commit at is still the team’s call — and now defending it is too, in week four, with options on the table, instead of in the Inspect & Adapt with none.
Say-do as an outcome, not a scoreboard
No team ever improved its say-do ratio by being scolded with it. The ratio improves upstream, when erosion is caught and renegotiated while the commitment is still alive — a smaller scope delivered on the date, or an honestly moved date agreed before it slipped. Do that all PI long and the say-do slide stops being a quarterly surprise. It becomes what it should have been all along: confirmation that your commitments mean something.
Your next confidence vote deserves to stay right. Run it, commit the date — and keep the vote live in Release Management for Jira, free for 30 days. For a closer look at how live commitment health works, see the documentation.
Leave a Reply
Your email is safe with us.