It's 11:40pm and you're rewriting a proposal someone else spent two days on. Not all of it. Just the opening, the pricing language, and the paragraph that sounds a little too casual for this client. In the morning you'll send it back with your edits and a note that says "small tweaks." Your team will read it the way they've read the last forty: next time, why finish it? It'll get rewritten anyway.
You've said you want more ownership. You've said it in meetings, in one-on-ones, maybe in a job posting. You've told people, more than once, "you don't need to run everything by me." And still, every decision seems to find its way back to your desk.
There's a possibility worth sitting with. Your team may not be short on initiative. They may simply have learned, through experience, what happens to it.
How the pattern shows up
Needing to approve everything rarely looks like control from the inside. It looks like care. It looks like high standards. It looks like being the person who catches what everyone else missed.
From the outside, it looks more like this. You're copied on every client email. "Just run it by me first" has become the team's unofficial policy. A $150 software subscription, the kind anyone on your team could sign off on, waits three days for your approval. You weigh in on the font in a slide deck. You ask to see the draft before the draft, and then the final before it goes out. Even the work you've handed off stays half-open in your head, because you already know you'll be back in it later.
Every one of these makes sense on its own. Together, they teach a team to wait.
Nobody calls a meeting to decide it. People just adjust. They stop finishing things, because finished work gets rewritten. They stop making calls, because calls get reversed. They start waiting, because waiting has never once gotten anyone in trouble. One "small tweak" at a time, the team becomes exactly what you've been frustrated by: people who won't decide without you.
I know this pattern from the other side. I once worked for a boss who redid everything I handed them, until it sounded like them instead of me. So I started leaving things in draft. Why polish something that was going to be rewritten anyway?
Why "just delegate more" doesn't stick
If you've noticed this pattern, you've probably tried to fix it. Maybe you read a book on delegation, or drew up a chart of who owns what, or made a rule that you'd only review final versions. For a few weeks it worked. Then a client spotted a mistake, or a deadline got tight, and by Friday you were back to checking everything.
That isn't a failure of discipline. Delegation systems ask you to override the urge to step in, and an urge you have to override every single day will win eventually. If letting go felt genuinely safe, you wouldn't need a framework to make yourself do it. The pull to check is coming from somewhere deeper than your workflow.
Where it can come from
For some people, getting things right was never just a preference. It was protection.
Maybe you grew up in a home where mistakes had real consequences, where a bad grade or a broken dish set off something much bigger than the moment called for. Maybe approval arrived when the work was flawless and went missing when it wasn't. Maybe you were the one expected to have it handled, from an age when most kids weren't expected to handle much at all.
A child in that kind of environment learns something genuinely smart: check everything, then check it again, and you stay safe. That lesson works. It probably carried you through school, through your early career, through the first hard years of building a business. It may be a big part of why you're good at what you do.
This isn't about blame. It's about noticing that an alarm was set a long time ago, and it's still going off in rooms where the stakes are completely different. A typo in a proposal isn't dangerous. The person who made it is a capable adult. But your nervous system doesn't always know that, so the old alarm fires anyway, and you step back in.
What it's costing
The cost rarely arrives as one big moment. It builds as a slow drag you get used to, until it starts to feel like the normal price of running a business.
It costs speed. Projects sit at 90 percent for days, waiting on your review, and clients often feel the delay before you do.
It costs your best people. Capable people want room to own something. When every call gets checked, the ones with options eventually start using them.
It costs the people who stay. They stop offering ideas and start offering drafts, because a draft is safer to have rewritten than a decision is to have reversed.
It costs you. The late-night edits, the vacation spent answering "quick questions," the constant low hum of knowing nothing moves unless you push it.
And it caps your growth. A business that can't move without you can't grow beyond you. Your bandwidth becomes its ceiling, whether you meant it to or not.
What changes when the pattern settles
Resolving this doesn't mean lowering your standards. You can care deeply about quality and still let other people produce it. What changes is the alarm. A mistake stops registering as a threat you personally have to prevent, and starts registering as information: something to learn from, fix, and move past.
From there, a few things tend to shift. You can review work without rewriting it. You can say "this is good, send it" and mean it. Decisions start getting made without you, and most of them turn out fine. The ones that don't become something the team learns from, instead of proof that you should have checked.
There's another shift people often don't expect. Your team's nervous systems respond to yours. When your reviews come with a sigh, a long pause, or a tight jaw, people register it before they've read a single comment, and they tense up for the next round. When your reviews come from a steadier place, the people around you settle too. They take more chances. They finish things, instead of leaving them 80 percent done for you to fix. Calm spreads through a team the same way tension does.
What a review can sound like instead
Part of the shift shows up in the words you use. A review that teaches a team to wait tends to sound like a rewrite with a polite note on top. A review that builds ownership sounds more like this:
"What were you going for here?" Asking first, before editing, tells the person their thinking matters.
"This is ready. One thing I'd consider is..." Leading with "ready" makes your input a suggestion rather than a verdict.
"Your call." Two words that hand the decision back to the person who owns it, and mean it.
None of these will feel natural while the old alarm is still loud. That's normal. They get easier as the pattern underneath them settles.
A small experiment for this week
Pick one decision you'd normally weigh in on, something low-stakes, and leave it entirely with the person who owns it. Don't ask to see it first. Don't check it after.
Then notice what happens in you. The urge to ask how it's going. The tightness when you don't know. The story your mind starts telling about what could go wrong. That urge is the pattern, showing itself. You don't have to act on it, and you don't have to fight it. Just notice it. Noticing is where changing it starts.
Where to start
I'm Anita Govender, an emotional intelligence coach, and this is the kind of pattern I work with privately, with founders and business owners who are ready to step back without everything falling apart. If you're curious how much of your week goes into holding everything together, the Presence Under Pressure Score will show you where you stand. It takes three minutes → kyraca.com/pups
