In this article
- What Is Transformation Milestone Achievement?
- What Is Agile Velocity and What Is It Good For?
- What Are the Key Differences Between Milestones and Velocity?
- When Should You Use Milestones, and When Should You Use Velocity?
- How Do You Build a Balanced Transformation Dashboard?
- Frequently Asked Questions
- About the Author
What Is Transformation Milestone Achievement?
Transformation Milestone Achievement is the share of critical transformation milestones reached on or ahead of schedule. A true milestone is a strategic inflection point, not a project deliverable: it changes capability or market position in a way that is hard to reverse, and it carries a measurable value that can be verified after the fact.
Good milestones share four traits. They are hard for competitors to copy. They represent step changes in capability, such as moving from six-week to two-week development cycles. They shift market position. And they have quantifiable impact, because “improve customer experience” is not a milestone.
I structure milestones on four horizons: thirty-day quick wins to build credibility, ninety-day foundations, 180-day breakthroughs and 365-day positions. Scoring is binary. A milestone is achieved or not, which kills the “80 percent complete” syndrome.
What Is Agile Velocity and What Is It Good For?
Agile velocity is the amount of work a team completes in a sprint, usually counted in story points. It is a planning tool that helps a stable team forecast remaining work from its own recent history. It is team-specific, so it is not meant for comparing teams or judging strategic progress.
Used properly, velocity is valuable. It shows a team its capacity, flags when estimates are drifting and helps spot bottlenecks before they derail a release.
It breaks down when organizations treat it as a performance measure. Teams inflate estimates to show rising velocity. High velocity on low-value features looks productive while wasting resources. Teams optimize their own throughput at the expense of the whole system. None of that tells you whether the business is transforming. I go further in the cult of agile.
A sprint scoreboard tells you how fast the team is running. It does not tell you whether it is running in the right direction.
Free from Todd
Symptoms tell you something’s wrong. The cause is usually deeper. My free Stagnation Genome worksheet walks you through five genes and 25 indicators, so you can see what’s actually driving your team.
What Are the Key Differences Between Milestones and Velocity?
Milestones measure strategic outcomes on a calendar; velocity measures team output per sprint. Milestones are binary and tied to verified value; velocity is relative and tied to estimates. Milestones show whether the business is changing position. Velocity shows whether a team delivers predictably. Use one to steer, the other to plan.
- Unit: strategic inflection points versus story points.
- Audience: the board and leadership versus the delivery team.
- Gaming risk: milestones can be defined too softly; velocity can be inflated with estimates.
- Time horizon: thirty to 365 days versus two to four weeks.
There is also a lag problem with most dashboards. As I put it in 10-Minute Transformation (forthcoming, Koehler Books, February 2027): “The metrics most operators trust are lagging indicators of a state that has already changed.” For a shorter list of the numbers that do matter on the floor, see 12 manufacturing KPIs that matter.
When Should You Use Milestones, and When Should You Use Velocity?
Use milestones to govern the transformation and report progress to leadership. Use velocity inside software or product teams to plan sprints. Problems start when velocity is promoted to a strategic metric, or when milestones are set so far apart that nobody can tell whether the work is on track until it is too late.
The Refrigeration division showed what happens without real milestones. A new product launch took eighteen months from concept to first shipment. Everyone was busy the whole time. Activity was high, and the market moved on.
The fix was shorter cycles with binary outcomes. Every improvement ran through the 3-A Method in six weeks, with victory conditions written in advance: 85 percent or more of projects completed within six weeks and 90 percent or more still working at ninety days. That is a milestone system at the project level. The method is in the 3-A Method.
How Do You Build a Balanced Transformation Dashboard?
Put three to five transformation milestones at the top, each binary, dated and tied to verified value. Underneath, track the leading indicators that predict them, such as decision speed and project completion rates. Keep velocity at the team level for planning. Review weekly, and treat any milestone at risk as a decision to make now.
- Top line: the current thirty, ninety, 180 and 365-day milestones, achieved or not.
- Leading indicators: decision cycle time, six-week project completion rate, and improvements still working at ninety days.
- Team level: velocity and sprint health, used for forecasting, not for judgment.
Decision speed belongs on that list because it moves everything else. When we measured it in Refrigeration and then pushed decisions to the lowest competent level using the 70% Rule, average decision time dropped 73 percent.
If you are not sure the turnaround is working, my checklist on how to tell if a turnaround is working pairs well with this dashboard.
A milestone that cannot fail is not a milestone. If it is never missed, it was set too low.
Frequently Asked Questions
What is the main difference between transformation milestones and agile velocity?
Milestones measure strategic progress against dated, binary outcomes. Velocity measures how much work a team completes per sprint and is mainly a planning tool.
Can agile velocity measure transformation success?
Not on its own. It can show a team is delivering at a steady pace, but not whether the business is changing its competitive position.
How should transformation milestones be scored?
Binary: achieved on time or not. Partial credit hides risk and creates the “80 percent complete” problem.
How often should milestones be reviewed?
Weekly at the leadership level, with any milestone at risk treated as a decision to make immediately rather than a status update.
Busy is not the same as transforming. I show leadership teams how to set milestones that tell the truth and run improvement in six-week cycles. Book me to speak to your team, or get the 3-A Method in full in Stagnation Assassin.
Free from Todd
If this was useful, read Chapter 1 of Stagnation Assassin free. You’ll get the five stagnation genes, the Ten Warning Signs assessment and the 90-Day Question.
About the Author
Todd Hagopian is a business transformation author and VP of Product Strategy and Marketing. Known as The Stagnation Assassin, he has led turnarounds across his corporate career, including roles at Berkshire Hathaway, Illinois Tool Works and Whirlpool, and his transformation work has created $3B+ shareholder value across five turnarounds. He is the author of Stagnation Assassin. Invite him to your event through his speaking page or connect on LinkedIn.