The Delegation Paradox
How to balance trust, clarity, and accountability
Learning to delegate is a rite of passage for any manager, but fine-tuning this skill has a way of highlighting our own quirks and hangups.
How do you calibrate between micromanagement and absentee leadership? Too much involvement leads to trust issues, but too little produces confusion. Neither approach is conducive to actually getting work done.
I wrote about the Formula for Execution a few months ago, which outlines the cultural values common to high-output teams. This is the management perspective: how to map your own behavior to these values and help your team ship successfully.
Exploring this paradox will not only make you a better leader, it will also teach you more about yourself and help you process the anxiety that comes with mounting responsibility.
Identifying Your Blind Spot
I’m very comfortable defaulting to trust, because I personally value independence. I’m a stubborn persistent, experiential learner with a strong sense of ownership, and I love creative problem-solving. I will happily agree to a reasonable request that makes another person’s life easier, but I do not enjoy being told what to do. This means I have a bias toward assuming others feel the same.
This works really well with highly skilled, self-motivated individuals. It does not work with team members who are inexperienced or unreliable.
When I led a market entry project in a CPG startup, dozens of subject matter experts committed to an ambitious timeline, then delivered stellar work. One person did not: they took ownership of a key deliverable, gave vague excuses about why it was perpetually delayed, and started avoiding me. I had to scramble to find a late-stage workaround because I trusted them to deliver despite clear evidence they wouldn’t.
In another instance, I asked a direct report to take ownership of a specific focus area without clocking that their limited experience meant they were in over their head. As a result, we missed a vendor contract renewal deadline. This created time-consuming rework that impacted several internal stakeholders—all of which we could have avoided if I’d asked a few more questions. I apologized to my direct report, made sure they had a system to prevent this moving forward, and reflected on what I’d learned in my next performance review.
You will probably bring some personal bias into your management style. This is normal. It’s also very common to not realize this until something goes wrong. Accepting that will help you face it head-on without judgment and find ways to address your blind spots. Talking it out with a coach, therapist, or mentor is a great way to work through this.
My own bias means I err on the side of over-trusting and risk leaving my team confused and uncomfortable asking questions. I’ve learned (the hard way!) to actively look for indicators this is happening so I can meet people where they are.
How to Calibrate
Once I recognized this pattern in myself, I had to figure out how to compensate for it without overcorrecting into micromanagement. I’ve found that the balance between control and chaos can be distilled into a delegation framework with three principles:
Trust By Default
Build a Successful Foundation
Hold the Line on Accountability
Let’s talk through what this means.
Trust By Default
I highly recommend making “default to trust” a core pillar of your leadership style—it’s that effective. It’s logical, generous, and surprisingly effective at actually manifesting trustworthiness through peer pressure.
How to do this: start by assuming the people around you are competent, motivated to deliver, and have good intent. When something goes wrong, continue to assume this and give them the benefit of the doubt. They’ll most likely work out the problem or enlist your help working with them.
If the same person consistently trips up in the same way, it’s fair to reassess. Assuming you’ve communicated expectations the first 1-2x the problem happened, this is either a skill problem (they don’t know how to do it) or a will problem (they don’t want to do it).
Keep in mind that you must also be trustworthy to make this work. Don’t make commitments you can’t keep, deliver what you’ve promised, and take accountability for the impact if something changes. Communicate clearly and frequently to encourage transparency.
Why it works: people who are genuinely competent, motivated, and have positive intent will do what they were going to do anyway: deliver. The small minority of folks who aren’t will look bad if they don’t follow suit. This clears a path for the team to work through problems, escalate the ones they can’t, and get to the finish line. In my experience, the number of people who don’t deliver in these circumstances is small enough to address as outliers.
When it’s hard: the leaders I’ve seen struggle with trust typically fall into two camps: they love the work and want to continue doing it, or they’re focused on perception. The first is the founder who’s still reviewing every pixel’s placement at Series B; the second is the manager who’s uncomfortable with criticism and deeply aware their team’s actions reflect on them.
Build a Successful Foundation
Trust won’t automatically produce results if you don’t have a shared understanding of what you’re delivering and the role everyone plays in that outcome.
What it means: take the time to get extremely clear about your plans. Ideally, this happens through a shared ideation process that takes into account company objectives and the work it will take to produce outcomes. Talk to domain experts and incorporate their input into execution plans. Get buy-in and commitments from the actual people doing the work.
Document your plans, ideally along the way as you discuss, and at the level appropriate to your work (e.g., a high-level roadmap if you’re the founder or CPO; a PRD or project charter if you’re a PM; a quarterly goals doc if you’re a people manager). Look for points of contention or confusion, and address them from the perspective of curiosity. Communicate way more than you think you need to, and make sure there’s a well-known source of truth for agreements.
Why it works: the root cause of many execution issues is human—conflict, miscommunication, power struggles. Talking through what you’re doing, why you’re prioritizing it, and negotiating how that will happen is baseline respectful behavior and an insurance policy. You can resolve—and prevent—a lot of confusion, finger-pointing and gaslighting with discussion and documentation.
When it’s hard: leaders who struggle with the foundational work typically either over-estimate skill or assume others intuitively understand their vision. As noted, I fall into this camp—it took me an embarrassingly long time to realize how much I needed to slow down and translate my own thinking to communicate effectively with my team. I also had to understand that, in some cases, others want or need to be given more detailed direction.
Hold the Line on Accountability
The final piece of this trifecta is about having Difficult Conversations, then taking action when that doesn’t produce results.
What it means: use the foundational documentation you created to address execution problems. This should be done privately and from a position of curiosity, and you should be willing to accept your own role in the problem. Figure out whether it’s a skill or will problem, then work together to find a solution. If it’s insurmountable or will take awhile to resolve, communicate that ASAP to others who are impacted.
Ideally, this conversation serves as a simple course correction and the problem is short-lived. In more serious cases where there’s a mismatch between job requirements vs performance, or the person is fully disengaged, it’s critical to take action. Your options will depend on your role, but an internal transfer, coaching, formal training, or termination are typically the answer. If you’re not their direct manager, talk to the person who is, with documentation of the impact and how you’ve attempted to address the issue.
Why it works: as a leader, holding others accountable is key to maintaining trust. When committed team members see their colleagues get away with not delivering, they’ll do one of two things: grow resentful and look for another job, or protect their energy by decreasing their own productivity. Centering accountability means the entire team can be depended on because there are consequences for dropping the ball.
When it’s hard: leaders who struggle to hold others accountable are often uncomfortable with conflict or rely heavily on charisma. Telling another person they’re not hitting the mark is inherently difficult, and it may make them dislike or resent you no matter how nice or reasonable you are.
The Lesson
The better you get at delegation, the more it reveals about your own assumptions, fears, and communication gaps. I’m still working on catching myself before I leave someone floundering. The difference now is that I know what to look for, and I’m willing to admit when I’ve gotten it wrong.
About Me
I spent 15+ years in five Silicon Valley startups ranging from entertainment to SaaS to CPG. I’ve built new functions, tackled budget crises, worked on a regulatory hearing, and created more processes than I can remember. I also have hundreds of hours of training and experience volunteering on crisis hotlines.
I’ve seen the highs and the lows of startup life: the feeling of printing money and impending world domination when your product is in demand… vs the time I pinched pennies by selling a plot of fake grass from the company’s office decor to a guy en route to Burning Man.
I work with startups on short-term, high-stakes engagements like rapid scale-ups, post-layoff chaos, and regulatory scrutiny.