Skip to main content

Flawless Is The Enemy of Good

When tackling large-scale, complex initiatives, the notion of “flawless execution” sets up leaders and teams for disappointment. Complexity guarantees surprises: dependencies shift, risks emerge, and trade-offs appear late in the game. From my experience leading programs at Amazon, Citrix, Philips and beyond, I’ve learned that the right aspiration isn’t flawless execution, but fearless execution.

Fearless execution doesn’t mean chasing perfection. It means leading with clarity, transparency, and adaptability, while creating an environment where teams feel safe and empowered to do their best work. Or as I like to say: flawless is the enemy of good.


 
Here are five key drivers that consistently define fearless execution:

1. Clear Vision
A compelling north star aligns decision-making. Without it, teams drift. Vision isn’t just a tagline—it’s a narrative that helps individuals understand how their day-to-day work maps to long-term outcomes. Fearless leaders repeat the vision often and tie every milestone to that broader story.

2. Detailed Plans
Planning is a continuous discipline, not a one-time artifact. The best leaders break ambiguity into structured components: clear scopes, aligned dependencies, risk registers, and iterative delivery cadences. And critically—plans must include all teams involved, not just your own. Engineering, product, design, security, operations—when everyone sees the same field, execution accelerates with fewer surprises and more ownership.

3. Risk Mitigation
Hope is not a strategy. Fearless execution requires early identification of failure points—technical, process, organizational—and building real fallback plans. In my team, we paired launch plans with rollback and customer impact scenarios, so we never froze when something failed. Speed is important—but responsible speed is built on risk awareness.

4. Psychological Safety
No team performs at its best in fear. I’ve seen this firsthand: motivated, capable engineers under-deliver when they feel their voice doesn’t matter or mistakes are punished. Fearless leaders create environments where dissent is safe, ideas are welcomed, and failures are treated as learning moments. This isn’t soft—it’s strategy. Engagement, creativity, and ownership all stem from feeling safe and supported.

5. Adaptability
Even the most meticulous plans collide with reality. Fearless leaders prepare teams for this: to reevaluate priorities, shift roadmaps, and reset expectations without panic. What matters is how quickly and thoughtfully we respond—not that we saw everything coming. Adaptability is the muscle that keeps momentum intact.

Closing Thought
Flawless execution is impossible in large-scale programs. But fearless execution—anchored in vision, planning, risk management, psychological safety, and adaptability—turns complexity into impact. In the end, it’s not about control—it’s about creating the conditions for people to succeed, even when everything doesn’t go as planned.

Comments

Popular posts from this blog

14 Essential Software Engineering Concepts for Engineers and Managers

There are many terms and concepts that are important for an engineer to be familiar with, in order to effectively build software. This post includes some of those terms. I will continually add to or update this list. Agile. A flexible and iterative approach to software development that emphasizes collaboration, customer feedback, and adaptive planning. My experience and success with agile development was the inspiration behind starting this blog. DevOps. A set of practices and tools that improve efficiency, speed, and reliability of the product through automation and optimization of the software development and delivery process where operational efficiency is part of the development process. Continuous Integration and Continuous Delivery/Deployment (CI/CD). A set of practices and tools that result in faster and more frequent releases, through automation of building, testing, and deployment of software. A key part of CI/CD is to deliver software to production frequently and using tec...

Forget Onboarding, do Alongboarding!

Alongboarding, an agile onboarding approach Alongboarding: We’re in it together! Organizations hire new people every day. A great first impression can make a tremendous difference in retaining employees. No one gets a second chance to make a great first impression, not even the best companies. An onboarding experience is an essential part of making that first impression on a new employee. Agile has been around for many years and has gained vast acceptance throughout the community. Yet, I find it disappointing that its tenets are not used well in most companies and most onboarding approaches follow a waterfall approach.  Alongboarding is an agile onboarding approach that applies agile tenets to onboarding new employees and makes the experience richer and more fulfilling. When I joined AppFolio as an agile coach, I experienced this approach during my onboarding. It felt like the team owned my success as much as I owned the team's success. It was a welcome change from some of m...

Make onboarding fun with Onboarding Canvas!

The Onboarding Canvas is a tool that can be used for onboarding a new team member . We derived this tool from Spotify's adaptation of the Toyota Kata . I like this tool because no one can tell you precisely how your onboarding should be like in order for you to be effective at your new job. This is a tool for continuous reflection and adaptation. It puts the newcomer in the driver’s seat, makes the onboarding process agile through continuous collaboration with your team. Four quadrants The onboarding canvas has four quadrants: Now: It defines where the team is now, what is going on and how is the new team member adapting to the change? Definition of awesome: With the addition of the new team member, how would the team like itself to be? What would be awesome for the new team member? Next target: In order to move towards "Definition of awesome" what outcomes should be achieved in the next x weeks? Next steps: What are the immediate next steps for the team...