Last week, driving through Germany, I was grateful for our navigation system. We knew where we wanted to go. Getting there was another matter.
Without it, who knows where we might have ended up? Somewhere beautiful, probably. Just nowhere near where we intended.
We entered our destination, and the system created a route. Which roads to take. How far to travel on each one. Where to turn. How long the trip should take.
But what caught my attention was what happened when we went off course. It recognized the gap and adjusted the route. It didn’t wait until we were miles in the wrong direction. It gave us the next turn.
I’ve been thinking about how often organizations approach execution with a destination in mind and too little thought about the route. Deliver sooner. Improve quality. Reduce costs. Build a stronger engineering team.
Those are worthwhile goals. They look good on a strategy slide, too. But when Monday morning arrives, what changes? Who does what? Which dependencies need to be resolved? What evidence supports the delivery date?
Stephen Covey’s principle of beginning with the end in mind gives us an essential starting point.
We need to know where we’re headed and what value we intend to deliver. Then we need to plan how to get there.
A goal names the destination.
A plan gives the team its next turn.
A navigation system connects our current position with our intended destination. It breaks the journey into manageable segments, estimates the time required, and accounts for constraints along the way.
Engineering plans need that same honesty.
What capacity do we actually have? Which assumptions have we validated? Where are the technical uncertainties? What must happen before the next team can begin? A date on a slide doesn’t answer those questions. Neither does calling the schedule “aggressive but achievable.”
If the route only works when every light is green, we should probably revisit the arrival time.
A credible plan makes the work, ownership, dependencies, and uncertainty visible. It gives people enough clarity to act and enough evidence to make commitments responsibly. Then we need to pay attention.
That was the other lesson from Germany. The navigation system kept comparing our actual location with the route.
How often do our teams do that?
A dependency slips. An assumption proves wrong. Rework consumes the capacity we expected to use for the next milestone. The original delivery date stays on the slide while the evidence supporting it quietly disappears. Meanwhile, everyone is busy.
Activity tells us people are working. Evidence tells us whether we’re on course.
That distinction matters for Speed-to-Value. Teams need to know whether their work is producing the intended outcome, what remains uncertain, and where a decision or intervention could prevent delay. They also need a culture where people can surface a gap early and expect help addressing it.
When reality changes, leaders have work to do: understand the impact, evaluate the options, adjust the plan, and renegotiate affected commitments while others still have time to respond.
Culture of Commitment
That is how commitment reliability becomes a practiced behavior. People make commitments with evidence, monitor progress, and communicate when the route changes. We don’t need to wait for the next planning cycle to check our position.
Choose one outcome your team has committed to deliver. Where are you today? What evidence supports your expected arrival? Who owns the next turn? When will you check again?
Excellence is a choice. Make it visible in the plan—and in how you respond when reality changes.
Next Steps
Contact us or visit www.exceptionaldifference.com to learn more about our offerings and how we can help you and your team. Our Commitment Fundamentals workshop, Commitment Deep Dive, and the Exceptional Engineering Experience are just a few examples of our offerings that will help you reliably make commitments you can meet or beat.
Follow us on LinkedIn and check out our website to stay connected and learn about our upcoming offerings.