By Andreas Pettersson, Founder, Leaders ADAPT
The task came back. Not finished, not wrong, just back on your desk with a question you'd already answered. So you opened the doc "to have a look," and forty minutes later you'd rewritten half of it.
That's the loop. Everyone searching how to stop micromanaging is stuck in some version of it, and the usual advice, trust more, let go, names a feeling instead of a mechanism. The Delegation Protocol in my 5-Minute Leader system replaces the feeling with a number: check in at 25 percent done, not 5.
Micromanaging is checking the process of delegated work so often that the person doing it no longer owns it.
Quick answer: To stop micromanaging, delegate the outcome instead of the task, state the person's decision authority out loud, and replace ad hoc checking with one scheduled check-in at the 25 percent mark of the work. At that check-in, ask about blockers rather than asking to see the work. Then judge the result against a 70 percent quality bar, not against how you would have done it.
Why do I micromanage? Because you delegated the task and kept the outcome
Most managers who hover aren't control freaks. They handed over a to-do item and kept the result, and when you own the result while someone else owns the steps, watching the steps is the only way to protect it. Hovering is the rational response to a bad handoff.
I said this on a coaching call about a CEO who was in every document: "She's micromanaging, but she's not delegating outcomes." Underneath it was fear, not ego. She was afraid of failing, so she kept the thing that could fail.
Here's the line I give founders, and I mean it literally. If you delegate outcomes, you are by definition not micromanaging. An outcome comes with a success criterion, a deadline, and an owner. Once those exist, the steps belong to the other person.
Outcomes vs tasks is the whole distinction. "Send the monthly report to the board" is a task. "Make sure the board has complete visibility into our performance and feels confident about our trajectory" is an outcome.
One creates a waiter taking your order. The other creates an owner.
Perfectionism gets blamed a lot here, and it's a symptom. Perfectionism about the process only shows up when the process is the thing you kept.
How do you know if you are micromanaging? Six signs you can check this week
The signs you are micromanaging aren't about your personality. They're about your calendar and your inbox. (The published surveys sit in the micromanagement statistics roundup.)
- You're copied on everything. People are asking permission, not making decisions.
- Work comes back before it's finished. "Just checking I'm on the right track" is a team that has learned you'll change it anyway. That boomerang has a name and a script: reverse delegation and how to send the task home.
- Your 1:1s are status updates. If the meeting opens with "give me an update," it's a reporting session.
- You can name the steps but not the success criterion. If "done" is a list of activities, you delegated tasks.
- You reopen finished work. It was fine at 80 percent of your standard and you took it to 95.
- Nobody asks you questions. Silence in a handoff means they've stopped expecting any autonomy.
Three or more of these and you don't have a trust problem. You have a delegation problem. Good news: delegation is a skill with a protocol, and trust is a feeling you can't schedule.
For the employee's view, read what it looks like from the other side of a micromanager.
How do you stop micromanaging without losing control? Make the control explicit
Nobody wants to lose control of the outcome, and you shouldn't. The mistake is keeping it by controlling the process. Say the authority level out loud in the handoff instead.
The Delegation Protocol uses three levels, and the handoff isn't done until one is named:
- Level 1. Decide and inform me after.
- Level 2. Decide, but tell me before you implement.
- Level 3. Recommend options and I'll decide.
Ambiguous authority kills ownership. Name no level and the other person assumes Level 3, comes back for approval on everything, and you read obedience as incompetence. The Level 1 line is short: "You own it. Update me weekly for visibility, not approval."
This is where I got it wrong at Arcules. We hired 30 people in the first three months and passed 150 at the peak, and I was fine handing out responsibility. What I couldn't hand out was the decision. As I put it on a call recently: I'm okay delegating responsibility, I struggle to delegate the authority.
A role with responsibility and no authority is a role in name only. The fix wasn't a personality change. It was slicing off a little more authority each quarter. My week went from 60 hours to 45 while the headcount kept climbing.
So the answer to how to stop micromanaging without losing control is to pick the level deliberately. Level 3 on a new hire's first big project isn't micromanaging. Level 3 on your head of operations after three years is.
How often should a manager check in on delegated work? The 25% Rule
The 25% Rule is a check-in timing rule: check in when delegated work is about 25 percent done, ask about blockers rather than asking to see the work, and do not check in earlier unless the person asks.
The schedule falls out of the rule:
- A one week task means a check-in on Wednesday.
- A two week project means day three or four.
- A month long project means one check-in after week one.
The reasoning sits on both edges. At 5 percent the person has barely started, so your check-in can only be about the plan, which means you're editing their process. That's micromanagement. At 90 percent a wrong direction has already been paid for. At 25 percent a wrong turn is still cheap to correct, and the conversation is about their work, not your preferences.
The script is support, not oversight. Three questions, in this order:
- How's it going?
- Any blockers I can remove?
- Anything you need from me?
Not on the list: "Can I see what you've got so far?" Ask that and the check-in becomes an inspection.
And setting expectations isn't hovering. If your expectation is a text within an hour when something breaks, say so in the handoff. Standards are what let you stop checking.
Delegate. Trust, but verify. The 25 percent mark is the verify.
Is checking in micromanaging? Status check vs calibration check
Checking in is only micromanaging when it's about the process. The 1:1 Protocol draws the line with two words: a status update asks what are you doing, a calibration asks how are you really. Most managers run the first and call it the second.
| Status check | Calibration check | |
|---|---|---|
| What you ask | "Where are we on the launch?" "Can I see the draft?" | "What's on your mind?" "On a scale of 1 to 10, what's your energy level right now?" "What are you struggling with that you haven't told me about?" |
| What you're allowed to change | The work itself: steps, sequence, wording | The conditions around it: blockers, priorities, the authority level |
| How long it takes | Often the whole 30 minute 1:1 | About 40 percent of a 30 minute 1:1, roughly 12 minutes, inside a 40/40/20 structure |
| What it produces | An updated task list and a person who reports "fine" | A number to track week to week, feedback both ways, an early warning |
The status check isn't evil. But when it's the only check-in you run, it trains people to perform "fine" instead of telling you the truth. The one-on-one status update trap and the calibration 1:1 pages show both versions.
Checking in without micromanaging is a two part fix. Move status to writing. Spend the meeting on the person.
What is the 70 percent rule in delegation? The bar that stops you taking work back
The 70% Test does two jobs. The second one cures micromanaging.
The 70% Test is a delegation rule: if someone else can do a piece of work at 70 percent of your quality, delegate it; if not, keep it or develop someone until they can.
Job one is picking what to hand over. Open last week's calendar and ask of every block: could someone else do this at 70 percent of my quality? Seventy, not 90.
Job two is accepting what comes back. If the outcome is achieved at 70 percent plus quality, you succeeded, even if you would have done it differently. Systems minded leaders hate this part. It's the part that matters.
Polish a 75 percent result to 95 and you teach the person that finished means "the boss will fix it." Their way at 70, delivered by them, beats your way at 100, delivered by you at 11pm.
If your team fails the 70% Test on work inside their role, that's a capability gap, not a delegation problem. The fix is training or a management coach for the manager who is struggling, not a tighter leash. The rest of the method sits in our delegation training guide.
How to avoid micromanaging on the next handoff: the four moves
Knowing how to avoid micromanaging beats recovering from it. Build the next handoff right.
- Frame it as an outcome, not a task. Situation, complication, question, then the delegation. Most leaders skip straight to "can you handle this."
- Name the authority level. One of the three, out loud, before they leave the room.
- Book the 25 percent check-in on the calendar. Right there, in the handoff. A scheduled check-in kills the urge for a dozen unscheduled ones.
- Verify it landed. Can you repeat back what I asked, why does this matter, are you fully committed? "I think I can do that" is a no.
Three minutes of that up front saves three weeks of checking later. Run it on one low risk handoff this week and count how often you open the doc before the check-in date. One honest note: these numbers come from the managers I coach and my own years, not a survey.
For the survey side, the delegation statistics page lists every published figure with its year and sample. The check-in rule itself sits inside a longer sequence, laid out step by step in how to delegate.
How to stop micromanaging FAQ
Why do managers micromanage?
Managers usually micromanage because they delegated a task while keeping ownership of the outcome, which leaves them responsible for a result they no longer control. Fear of visible failure, unclear authority levels, and habits from doing the work themselves reinforce the pattern. Personality matters less than the structure of the handoff: once the outcome, the deadline, and the decision rights are stated, the reason to hover mostly disappears.
Is checking in on an employee micromanaging?
Checking in is not micromanaging by itself. A check-in becomes micromanaging when it is unscheduled, frequent, and focused on the process of the work rather than on blockers and conditions. One scheduled check-in at about 25 percent of the work, asking how it is going and what the person needs, is support. Asking to see the work in progress, or checking daily on a one week task, is oversight.
How often should a manager check in on delegated work?
Under the 25% Rule, a manager checks in once when the work is about a quarter done, then at any milestones agreed in the handoff. For a one week task that means midweek; for a month long project it means after the first week. Earlier check-ins tend to become process edits, and later ones arrive after a wrong direction has already cost time. The person can always ask for more contact.
What is the 70 percent rule in delegation?
The 70 percent rule, or 70% Test, says that if someone else can do a piece of work at about 70 percent of your quality, you should delegate it, and if they cannot, you keep it or develop them until they can. It also sets the acceptance bar: a delegated outcome achieved at 70 percent or better counts as a success, even when the manager would have done it differently.
How to stop micromanaging without losing control?
The method is to keep control of the outcome and give up control of the process. That means stating the success criterion and deadline, naming one of three authority levels (decide and inform, decide but tell me first, or recommend and I decide), and scheduling one check-in at 25 percent of the work. Control lives in the criteria and the level, not in watching the steps.
The check-in is the cure, not the disease
Micromanaging isn't a character trait you have to apologize for. It's what an unfinished handoff looks like from the outside. You kept the outcome, so you watched the steps. Give the outcome away properly, with a criterion, a level, and a date, and the watching stops on its own.
That's why the fix is a schedule, not a personality transplant. One check-in at 25 percent, a 70 percent bar on the way back, status in writing, calibration in the room. And people tell the truth to a manager who isn't about to rewrite their paragraph.
The task that came back last week? Send it home with an outcome and a Wednesday on the calendar. Then leave the doc closed until Wednesday.
The system I built after I stopped being the bottleneck
The 25% Rule is one piece of the Delegation Protocol, the first of four protocols in The 5-Minute Leader. I wrote the system down after scaling a company past 150 people as one of Canon's youngest CEOs and learning to hand over the authority and not just the work.
The book gives you the 3-Minute Delegation Conversation, the three authority levels, the 25% Rule with its script, and the 1:1 Protocol that moves status out of your meetings and puts calibration in. There's also a Friday review with a pass mark for what stayed delegated versus what boomeranged, which is how you know how to stop micromanaging actually took, in numbers rather than feelings. Five minutes a day. It was the only leadership I could sustain at 150 people, and it's the only kind I'd ask of you.
