Decisive Execution · Feature
Decisive Execution: Keep Swinging, Stay Frosty, Get It Done
Plans break. Markets turn. Even great hitters strike out most of the time. Decisive execution is what a leader does next, and how calmly they do it.
Key takeaways
- How you endure a setback matters more than the setback. Your team takes its cue from your reaction.
- Decisions are rarely made in the meeting. Do the groundwork one on one first, so the meeting can confirm and move.
- When the plan breaks, confirm what really matters, then find the next alternative. You control you.
- Resolve and agility aren’t opposites. Hold firm on the goal and stay flexible on the path.
The year always wins a few rounds
Engineers like problems with answers. You define the system, state your assumptions, run the numbers, and the answer is the answer. Execution in a real business doesn’t work that way. You make a good plan, and then the year shows up and starts knocking holes in it.
I’ve come to think of decisive execution as what a leader does in the gap between the plan and reality. It has three parts, and they pull against each other. You have to be resolute about the goal. You have to drive toward measurable results. And you have to be agile enough to change the path when the facts change. Lean too hard on any one of them and you get into trouble.
This article isn’t a theory of execution. It’s a handful of habits I’ve picked up, mostly by getting them wrong first.
Keep swinging
There’s a stretch in every career when nothing seems to go your way. In 2023 I wrote a daily letter to my children, and one spring day I put down a line I still come back to: “Even the top hitters averaging like 400 either strike out or get put out 60% of the time. We’ll keep swinging.”
That’s the heart of being resolute. It isn’t pretending the strikeouts don’t happen. It’s refusing to let them decide whether you step back up to the plate.
One of my favorite lines on this comes from Dean Acheson: “the manner in which one endures is more important than the thing that must be endured.” As a leader, that’s not just a personal philosophy. Your team is watching how you endure. On the Resolute page, I tell the story of arriving at a refinery in the middle of a crisis, where my job was to create urgency without panic. The crisis itself was mostly out of my hands. The manner in which I carried it was entirely in them.
There’s even an upside to hard times, if you look for it. As I wrote to my children that November, “If everything was great, what would you work on to make things better? It is what it is. Deal with it. Then resolve to make it better.”
““There’s always a way to win if you’re resolute enough to stay in the game. If you quit, you’re done.””
— Brent Beason
The meeting is not where the decision happens
A lot of engineers think decisions are made in meetings. You bring your proposal, make your case, and the room decides. Experienced leaders know better.
Meetings aren’t where decisions happen. They’re where decisions get confirmed. The real work happens beforehand, one on one: walking each key person through the idea, hearing their concerns while there’s still time to address them, and adjusting the plan so it reflects what you learned. It’s slower at the start and much faster at the finish. When you finally get everyone in the room, nobody is surprised, and the meeting can do what it should, which is commit and move.
The other lesson that took me too long to learn is that great work doesn’t speak for itself. Engineers especially tend to believe that if the analysis is right, people will see it. They often won’t, not because they’re careless, but because they’re busy. Driving results includes making sure the right people understand what was done and why it matters. That isn’t bragging. It’s part of finishing the job.
Bill Malloy, who has made about 170 investments, sees the same thing from the investor’s side. He tells teams to lay out the plan in layers, from three to five years down to the quarter, and then to accept that very few companies hit their quarterly plan. So they huddle every week and keep adjusting. The plan gives you direction. The weekly rhythm is what gets you to the result.
Both habits come back to the same discipline. Results don’t come from having the best plan. They come from getting the people who have to carry the plan to understand it, believe it and act on it.
““That prioritization and that focus is really what I think will separate the highly successful companies from the ones that fail or that are just kind of mediocre.””
— Bill Malloy
Stay frosty
One Easter weekend, my flight home from a business trip was cancelled, and the only way to make my family’s trip the next morning was a nine-hour drive. I tell that story on the Optimism page as a lesson in attitude. It’s also a lesson in agility. That night I wrote down the approach I try to take whenever a plan falls apart: “Evaluate the next alternative, find a way to the next plan… Just get on with it, roll with it and stay frosty.”
You control you. You don’t control the airline, the market, the supplier who just missed a delivery or the competitor who just cut prices. You do control how quickly you stop arguing with what happened and start working on what’s next.
When something feels like a disaster, I run through a short mental checklist before I react, and it starts with confirming what really matters. Once I’ve done that, the problem usually shrinks to its real size. Then I can work on it with a clear head instead of a racing pulse. Agility isn’t speed for its own sake. It’s the ability to change direction without losing your footing.
Ed Rose, who shares his story on the Agile page, has a rule I wish I’d heard as a young engineer. He tells his organizations he wants about 70 percent of the data, and then he wants to move. Not 95 percent, unless it relates to safety or compliance. For engineers trained to get it right, that feels risky. But waiting for certainty is a decision too, and usually a worse one.
““It’s not really what happens, it’s how you respond.””
— Ed Rose
Hold the goal, flex the path
People sometimes ask me how a leader can be both resolute and agile. Doesn’t one cancel the other? I don’t think so. The trick is to be clear about which thing you’re holding firm on.
Hold firm on the goal and on your values. Stay flexible about the route. A leader who changes the goal every time the wind shifts wears the team out. A leader who refuses to change the route when the bridge is out drives the team into the river. Drive Results keeps both honest by tying everything back to outcomes you can measure.
If you’re an engineer stepping into leadership, start small. Pick one decision you’ve been delaying while you wait for more data, and make it. Do the groundwork one on one before your next big meeting. And the next time something blows up, run the checklist before you react.
Go deeper
RESOLUTE
Brent Beason on running a company as a college student, and my own test of creating urgency without panic.
DRIVE RESULTS
Bill Malloy’s pattern from some 170 investments, and why you have to know your numbers cold.
AGILE
Ed Rose on moving with 70 percent of the data and setting a quota for failure, plus my case for just starting.
Decisive execution isn’t about never striking out. It’s about how you carry the strikeouts, how well you prepare the people who have to act, and how quickly you find the next plan. Visit the Decisive Execution pillar page, then dig into whichever constant you need most right now.



