LinkedIn·Tuesday, 25 August 2026·1d ago
One question completely changed the way I think about delivery commitments. How much risk are you willing to take? When someone asks "when…
Sonya Siderova
Founder & CEO at Nave | Helping enterprise agile coaches prove transformation value with metrics executives trust
One question completely changed the way I think about delivery commitments.
How much risk are you willing to take?
When someone asks "when can you deliver this?" we usually respond with a date. But a date on its own leaves out an important part of that decision: the risk we’re taking when we commit to it.
Here is what I mean by that. Imagine your historical delivery data gives you three options and the probabilities that come with each of them:
10 days, with 70% confidence.
15 days, with 85% confidence.
20 days, with 95% confidence.
Which one would you go for? Well, it depends on how much risk you're willing to take.
If the work is easy, you've done this before and you don't expect challenges along the way, 70% is perfectly acceptable. If the scope is big and there are a lot of unknowns around it, perhaps the 95th or even 98th percentile is the more reliable answer.
The rule of thumb is simple: the higher the uncertainty, the higher the percentile you should work with.
That's the part I think we miss when we talk about forecasting. We spend so much time trying to find the date.
But the more important question is, how much certainty do we need to make this promise? And the great thing is, we can actually put a number, a percentage on that certainty.
Because not every commitment deserves the same level of certainty. The consequence of being wrong should determine how much confidence you need before you commit.
That's what turns forecasting from predicting dates into managing risk. That’s what makes it a business decision.
A reliable commitment isn’t just a date. It’s a date with a level of risk you’ve consciously chosen.
If you'd like to go deeper into how probabilistic forecasting works and how to apply the concept in your own context, send me a DM and I'll share the guide with you.
#NavigateYourFlow #FlowMetrics #Predictability #AgileLeadership #DataDrivenDecisions
♥ 7💬 1
View on LinkedIn Cross-referenced
Related on the wire
Francine Milke noticed something unusual in her team's Cumulative Flow Diagram. The QA band was getting wider. Developers were moving work…
919 days. That’s how long this team’s work had spent sitting in Ready for Deployment. 241 items, waiting after the work was already ready.…
I think we’ve made predictability too much about the date. Can we tell the customer when this will be done? Can we give leadership a…
I used to think that if I could prove there was a better way of doing something, people would naturally want to change. I don’t think that…
I used to spend hours in meetings answering questions our board should have answered in seconds. What’s everyone working on? Where is this…
Leadership asks whether the transformation is working. And you realize it's surprisingly difficult to answer. You've changed the team…