THE CONDITIONS FOR LETTING GO
Written by Jessica Murray
Two weeks later, you’re back in the middle of it. Again.
F***.
Have you ever handed off responsibility and felt like this? Back in the decisions and the approvals you thought you empowered others to take over.
I’ve worked with founders and early-stage teams for over a decade, and I’ve watched this happen many times.
Businesses differ.
Industries vary.
Personalities range.
But a few things are universal.
There are certain inflection points where founders need:
More focus.
To shed a few of their 10+ hats to get that focus.
A team operating with an ownership mindset.
Increased execution velocity.
It all to have happened yesterday!
The instinct from team members or outsiders is to say, “OK, then delegate more.”
The advice isn’t necessarily wrong. But it’s definitely incomplete.
The gap between “delegate more” and actually doing it successfully is where the “stuck” happens. While people may assume this is a control problem, I rarely actually see that being the case.
Founders I’ve collaborated with are eager to relinquish what’s not in their zone of genius. The hard part is the how.
How did we get here?
It’s pretty simple. In the beginning, it’s just the founder. Everything runs through that person, and it’s natural for norms to build up in that one person’s head.
Then, traction hits. The team grows. The market, investors and customers all demand more.
Suddenly, founders face more decisions, more approvals, and still too much that only they can do.
They determine a solution: delegate to another capable set of hands.
The person is identified. Instructions are provided. Handoff happens.
Problem solved. Not so fast.
Scroll back up to the opening of this post.
This “F***” moment happens because a task was thrown over the wall, but the conditions for true ownership didn’t exist.
It’s more than delegation. This challenge is structural: The infrastructure wasn’t designed to support "letting go.”
Structure isn’t solely a process document.
Structure isn’t a quick handoff.
Structure isn’t something your team can build around you completely.
Four things worth doing right
There are ways to push through this ceiling. Whether you're an entrepreneur trying to scale a team or build out AI-assisted workflows, the design requirements are largely the same.
Four foundational steps are generally required:
Get it out of your head. You’ll never let go of something [to a human or machine] that can’t be easily described. Context is key. Get the process organized and documented. This tends to be the toughest step. It requires slowing down first, which is counterintuitive for most founders.
Clearly define ownership. Not solely who completes a task, but also who is accountable for the outcomes. These are different; clarity around the nuance is important.
Map out decision authority. What can this person, or agent, decide on their own? What requires escalation? The clearer this is upfront, the less you get pulled back into decisions that should never have reached you in the first place.
Delegate authority, not only responsibility. Handing over a job without the (responsible) power to see it through isn't delegation. In practice, this looks like a team member who checks in before every decision, not due to lack of capability, but because the boundaries of authority weren’t defined.
None of this is the work that makes it to the highlight reel. But it’s the stuff that helps make those highs possible.
Kicking the can down the road in perpetuity isn't a sustainable solution either. The good news is that this is solvable. The infrastructure can be built. The conditions can be created. It just requires deciding that doing it right is worth the investment.