The healthiest working relationships I’ve seen between an engineer and their manager run on two sentences. Before the work: “I intend to do X.” After it: “I have completed it, and I know it works because it passes these tests.”
A manager receiving that flow all week has no reason to hover. Every question a micromanager would ask has already been answered, unprompted, before it occurred to them to ask it. There is nothing left to micromanage.
Almost everything written about micromanagement treats it as a manager’s defect, full stop. The books, the training courses, and the exit interviews are all addressed to the boss.
Half right. Micromanagement is a contract failure, and the contract has two signatures on it.
The leader’s half
The leader owes the team context, guard rails, and everything they need to move forward without asking. A team can’t volunteer good decisions into a vacuum.
This is old advice that keeps getting rediscovered. Ken Blanchard and Spencer Johnson’s The One Minute Manager is from 1982, and its first secret is one-minute goals: agree up front, in writing, what a good job looks like, so the person doing the work can check their own performance without a supervisor in the room. The second secret is to catch people doing something right. Both halves of that are the manager funding the contract: clarity going in, reinforcement coming back.
Guard rails belong in the same deposit. What can’t this person break while moving fast? Which decisions are theirs, and which ones aren’t? Company values, done properly, carry a lot of this load; I’ve argued before that good ones are compressed decision context, letting someone make the founder’s call without asking the founder.
A leader who has paid this half in full has earned the right to expect the other half.
The team’s half
The team’s half is the one nobody writes books about: make your work visible by pushing information upward before it is asked for.
David Marquet’s Turn the Ship Around! is the best account of this I know, and I recommend it to every leader I work with. Marquet stopped giving orders on a nuclear submarine and had his officers announce “I intend to” instead, moving authority to where the information already lived. The part readers skip is the price the crew paid for that authority: they had to say what they intended out loud, ahead of time, every time. Visibility paid for the autonomy.
The closing report matters as much as the opening one. “I have completed it” is a status update. “I have completed it, and I know it works because it passes these tests” is a closed loop with evidence attached. It tells your manager the work is done, verified, and requires nothing from them. Fifty of those in a row and checking up on you starts to feel absurd, because it is.
Why this disarms even a nervous manager
Andy Grove’s High Output Management supplies the mechanism. His dial for how closely to watch someone is task-relevant maturity: meet weekly with a person who is new to this specific task, every few weeks with a veteran of it, and even at the top of the dial, keep monitoring against agreed objectives. Oversight in Grove’s model never drops to zero; it tracks demonstrated experience with the task in front of you.
Unprompted intent and verified completion is how you turn that dial yourself. Every loop you close in public is evidence of maturity on the task, and the rational monitoring frequency falls. You are feeding the manager’s model the exact data it needs to leave you alone.
Visibility changes the texture of feedback too. Kim Scott’s Radical Candor asks managers to care personally and challenge directly. When you’ve pushed the work up voluntarily, a direct challenge lands as coaching on something you offered. When the same information had to be extracted from you in a status meeting, the same challenge feels like surveillance. Same words, different contract.
Both sides of the fence
If you manage people and feel the urge to check in, audit your half first. Have you written down what good looks like, and what can’t be broken? If yes, and you’re still in the dark, the gap is on the team’s side and you should name it as an expectation, out loud.
If you’re the one being micromanaged, the move that works is the same one I described in unblocking yourself: stop waiting to be asked. Open with intent, close with evidence, and keep doing it. Most managers hover because they’re starved of information, and you control the supply.
And if you’ve run intent and verified completion for a full quarter and the hovering hasn’t budged, the contract is broken on the other side. That is worth knowing too.
If your one-on-ones have collapsed into status extraction, jfsi coaches both halves of this contract.