Early in my career, I believed that strong leadership meant staying close to the work.
Not just directionally close. Literally close. Connected to the decisions, the process, the daily shape of how things were getting done. I thought that presence meant protection. That if I was paying attention, things wouldn’t go sideways. And if they did, I’d catch it early enough to course-correct.
What I was actually doing was confusing attention with control.
The belief had real costs, and it took longer than I’d like to admit to see them clearly. By the time I did, I’d already watched the pattern cause damage to a team, to a project, and to the working relationships I thought I was protecting by staying involved.
The hardest part of that lesson wasn’t learning that control was an illusion.
It was learning that what I called control wasn’t really about the work at all.
On one project, I found myself increasingly protective of a particular way of doing things, a process I believed in, which had become a proxy for something else: a way of maintaining a sense of influence in a situation that was otherwise moving beyond my direct reach. The team saw it before I did. The friction it created wasn’t about the process. It was about what my insistence on the process communicated: that I didn’t trust their judgment, that my framework mattered more than their experience of the actual work, that the goal was less important than the path I’d already decided on.
That realization landed badly. It should have.
The distinction that finally helped me wasn’t between control and letting go.
It was between ownership and attachment.
Ownership is functional. It describes the appropriate relationship between a leader and a piece of work: being accountable for outcomes, providing direction, staying available when it matters. Ownership can be held and transferred. It moves with the work.
Attachment is different. It’s the ego investment in a particular version of how things should go. It doesn’t transfer. It doesn’t serve the work. It serves the person holding it. The reason it’s hard to see in yourself is that it wears the costume of responsibility. It tells you a convincing story: I care about this work. I know what good looks like. I’m staying involved because the stakes are real.
All of that can be true and still be covering for something else.
One thing that clarified this for me was getting honest about where my energy was actually going. Some things genuinely belong to me: the quality of my thinking, what I communicate, how I show up when things get difficult. Some things I can influence but not control: how a team interprets direction, whether a strategy lands the way I intended. And some things simply need to be accepted, not because they don’t matter, but because fighting them takes energy from the places where I might actually make a difference.
Most leadership energy gets wasted in that last category. Not because leaders are careless, but because the instinct to intervene is often more about managing your own discomfort than improving the outcome.
The question that clarifies it: is this effort serving the work, or is it serving my need to feel like I’m doing something?
Letting go of control doesn’t mean disengaging from responsibility. That conflation makes the lesson harder to apply than it needs to be.
The failure modes I’ve watched tend to run in two directions. Over-involvement: staying in the work past the point where it helps, substituting your judgment for the team’s in moments that should belong to them. Premature withdrawal: treating delegation as an excuse to step back entirely, then being genuinely surprised when things drift. Neither looks like what it is from the inside. Over-involvement feels like diligence. Premature withdrawal feels like trust.
What actually works is something closer to engaged non-attachment: having a strong point of view without requiring that it be the one adopted. Accepting that the people closest to the work often understand it better than you do, and that this isn’t a threat. It’s the point.
The goal was never to be the person with all the right answers. It was to create conditions in which the right answers could surface from whoever was closest to them.
I still catch myself getting attached.
It happens when something I’ve built is being changed by someone else. When I think the better path is obvious and I’m watching a different one get chosen. When I’ve invested enough in an outcome that the distance between what I hoped for and what’s happening starts to feel personal.
The signal I’ve learned to watch for is a particular kind of internal resistance. Not the kind that’s tracking a real problem, but the kind that’s tracking my own discomfort with not being in charge of the result.
Those two things feel similar from the inside. Separating them is the actual work.
The paradox isn’t that control doesn’t work. It’s that the effort to maintain it often tells you more about your own attachment than it does about what the situation actually requires.
Learning to tell the difference is a discipline. Not a technique you master once, but a practice you return to, especially in the moments when it’s hardest to see clearly, which are usually the moments when the stakes feel highest.
That’s when the attachment is most convincing.
And most worth examining.