Perfectionism looks like high standards from the outside. Inside a growing business, it feels more like delay, hesitation, second-guessing, and leaders holding onto work longer than they should. Teams wait for approval. Decisions take too long. Capable people stay underused because the business is still orbiting one person's comfort level. I don’t say all of this from some academic, ivory tower perspective, wagging a finger at leaders who struggle with this. The reality is, I’ve had to overcome this very issue in my own leadership, and still find myself battling those demons from time to time.

I also see this pattern a lot in companies I’ve worked with that want to grow with more intention. Quality matters, and most leaders who struggle with perfectionism know that. The problem shows up when the need to get everything exactly right starts creating friction across the organization. What sounds responsible can become a structural drag, especially when the leader is still reviewing, refining, and reworking tasks that should already be moving forward.

I’ve found that this matters even more in distributed teams. Remote work asks leaders to be clearer, trust faster, and build systems that let people execute without constant intervention. When perfectionism sits underneath leadership behavior, those systems struggle to take hold. Progress ends up depending on the leader's personal reassurance.

My conversation with Todd Greider on Lead Smarter gave me a bit more language for all of this. Todd is a leadership coach, a facilitator, and a self-described recovering perfectionist, and what follows draws heavily on what he surfaced in that episode.

Perfectionism Is Fear in Disguise

One of the most useful things Todd said in our conversation was this: perfectionism is rarely about excellence alone. More often, it is about risk. It is the internal belief that every important decision, message, hire, or deliverable has to go exactly to plan, with no deviation and no room for visible mistakes. In practice, that mindset creates slower leadership.

Todd was describing a truth about the human psyche. We convince ourselves that holding back is discipline when it is often self-protection, lowering the credibility of the message sent to the team. When people learn that work is never quite ready, they stop taking ownership with confidence. They wait for the leader's signal. Over time, that weakens initiative and trains the organization to escalate decisions upward instead of solving problems where they happen.

At a certain stage, perfectionism stops being a personal productivity issue and becomes an organizational design issue. If the founder or operator cannot let good work move without another round of edits, the team never becomes fully self-sufficient. If every detail still comes back to the top, growth gets more expensive and more fragile than it needs to be.

Why Shipping at 70% Creates Better Leadership

The phrase "ship at 70%" can sound reckless without context. It is a discipline, and it comes with conditions. Leaders learn by moving, teams learn by doing, and organizations improve through feedback. Endless internal polishing produces none of that.

For leaders, shipping at 70% means releasing work when it is strong enough to create learning. That might mean launching a process before it feels complete, delegating a responsibility before you would do it exactly the same way yourself, or making a decision with the information you have. The remaining 30% comes through iteration.

I have already applied this principle in my own business, including in how this very blog gets produced. What I like about the mindset is that it separates quality from anxiety. Strong leaders still care about outcomes. They still define what good looks like. They also understand that movement produces data. Once a team starts executing, you can see where the process breaks, where expectations are unclear, and where support is needed. Waiting for everything to feel finished delays the very learning that would improve the result.

There is a condition attached, and Todd was clear about it. Shipping at 70% works as long as you have defined what good enough means, protected the non-negotiables like accuracy and clarity, and decided in advance what you are willing to let be imperfect. Without those pieces in place, it becomes an excuse. With them, it becomes an operating advantage.

Guardrails Protect Quality Without Creating Dependency

If leaders are going to move faster and delegate more, they need a way to protect quality without becoming the center of every workflow. That is where guardrails come in. Guardrails give people a clear standard, a boundary, and a decision framework. Constant checking does the opposite. It keeps authority vague, pulls execution back to the leader, and forces people to ask for permission more often than they should.

Good guardrails are concrete. They define decision rights, quality thresholds, timelines, escalation points, and what success looks like. They make it possible for someone to contribute within days because the environment is structured for performance. This is also why I believe team building goes well beyond placement. If you want people to stick, contribute, and grow, they need the surrounding framework as much as they need the role itself.

In practice, this means leaders should spend less time hovering over output and more time building the conditions for good output. Clarify the objective. Define what must be reviewed and what does not. Set a cadence for feedback and give people enough room to think and act. Leaders who do this well make quality repeatable across the team. Leaders who skip it keep quality trapped in one person's head.

Executive Presence Starts With Emotional Control

Perfectionism is more than an execution problem. It is a leadership signal. Teams pay attention to how leaders react when something is incomplete or uncertain. If every deviation from the plan creates visible stress, people become cautious. If every mistake feels high stakes, they become defensive and less creative.

Todd described executive presence as the ability to communicate clarity under pressure and make calculated, informed decisions when everything around you is a mess, without letting what you cannot control define how you move forward. That framing puts presence within reach of every leader, including the ones who will never light up a room. Composure can be practiced. Charisma is harder to schedule.

There is a practical side to this. Leaders who react from fear tend to overcorrect through control. Leaders who react from confidence ask better questions. They coach. They look for where a system failed before assuming a person failed. That difference shapes culture quickly, especially in small and mid-sized businesses where the leader's behavior sets the tone every day.

For founders and operators, this is one of the harder shifts to make because it asks for both discipline and self-awareness. You have to notice when caring about quality is becoming discomfort with letting go. The more clearly you can separate those two things, the more likely you are to build a team that can carry real responsibility. That, to me, is the whole point of scaling. It means building a business that does not depend on your personal tension to function.

If you are working through this in your own business and want to build a remote team that can operate with less founder dependency, that is exactly the kind of work we help clients with at Unbottleneck. We connect growing businesses with vetted global talent and support the onboarding, structure, and culture needed to help distributed teams perform. If that resonates, you can book a call with me here: https://cal.com/david-kent/meeting-with-david-kent-unbottleneck 

Ship at 70% when the work is strong enough to create learning. Put guardrails in place so quality is protected without constant intervention. And pay attention to the emotional side of leadership, because teams respond less to what a leader says and more to how that leader behaves when things are still imperfect.