You set expectations without micromanaging by agreeing in writing on what finished looks like, when you will hear from each other, and what counts as off track. Settle that once and you stop needing to ask. The asking is the part that reads as micromanagement.
Micromanaging is usually a symptom rather than a personality. The person requesting an update every afternoon is often someone who never wrote down what they wanted and is now trying to reconstruct it one message at a time, which feels to them like diligence and to everyone else like being followed around.
Why vague briefs turn into hovering
Hovering fills the gap left by an unwritten standard.
If nobody said what good looks like, the only way to find out is to look at the work while it is happening. So you look. Then you look again two days later.
From the outside that reads as distrust. From the inside it feels like doing your job. Both readings are honest, which is why arguing about micromanagement in the abstract never gets anywhere.
Telling yourself to trust harder does nothing. Trust is not a message you can send. What works is making the information arrive on a schedule, so nobody has to go and fetch it.
Write what done looks like, not the route
An expectation describes the finished thing and the real limits around it, and says nothing about the steps.
Steps are where micromanagement lives, because a list of steps is a claim that your way of working is the correct one. It also moves the thinking back to you. If the route is yours, every problem on it is yours too.
What belongs in a written expectation:
- The outcome, described so someone else could tell you when it has been reached.
- A date that is an actual date, not "end of the month-ish".
- The limits that are real, like the budget, the tools you already have, or a review it has to pass.
- The quality bar, written as an example rather than an adjective.
People skip the last one. "Make it polished" means nothing, because polished lives in your head and nowhere else. "As clean as the onboarding doc we already have" means something, because it points at an object both of you can open and argue about.
Set the rhythm so nobody has to ask
Agree when you will hear from each other, in writing, and the unscheduled "any update?" message stops being necessary.
A rhythm has to be specific enough to check. Thursday morning, in the channel, three lines. That is a rhythm. "Keep me posted" is a wish.
Two things keep it alive. The update has to be short enough that writing it never competes with doing the work, and it has to land in one place you have both agreed to read. If it takes half an hour to produce, it will be late, then you will chase it, and you are back where you started. A short written update does this better than a standing call, because it leaves something you can point at later.
The rule I hold myself to: if I want a status before the agreed time, I have to say why in the same message. "I am asking early because the client call moved" is a reason. "Just checking in" is me being nervous and making it somebody else's problem.
Name what off track looks like
An expectation is incomplete until both of you can tell, without a meeting, whether the work is behind.
Projects rarely fail on the deadline. They fail quietly, days earlier, at the moment somebody knew and said nothing. Give that moment a definition and it gets said out loud.
Off track is easier to define than people expect:
- The next step has not moved for two working days.
- The work now depends on a person who has not agreed to it yet.
- The answer to "will this land on the date" changed from yes to probably.
- The task turned out to be a different task.
Then write the sentence that makes the list usable: raising any of these early is the job, and it will never be held against you. Say that and then react badly the first time somebody uses it, and you have taught the opposite lesson permanently. No amount of process undoes a bad reaction.
Name the parts you are staying out of
Write down the parts you are staying out of, because silence about them reads as a review that could arrive at any time.
People overwork the areas where they cannot see your position. They polish the internal doc nobody opens, because nobody told them it would not be read.
"I will read the summary and the numbers, and I am not going to review the wording" takes a few seconds to type and removes a week of invisible caution. Do the same for decisions. Name the calls that are theirs outright, so the ones that reach you arrive as decisions to make rather than permission slips to sign.
The tells that you crossed into hovering
You have crossed into micromanaging when your messages ask for information you already agreed would arrive later.
- You ask for an update before the agreed check-in, twice in one week.
- You rewrite the work instead of saying what is wrong with it.
- You ask how they plan to do it when you only need to know whether it lands on the date.
- You add a new reporting habit after a mistake instead of talking about the mistake.
- You read a draft you were not sent.
That last one is worse than it looks. Reacting to work in progress teaches people to hide their progress until it is safe to show, so you get surprises, so you check more, so the hiding gets better. I have been on both ends of that loop and it never announces itself while it is happening.
When it slips, renegotiate out loud
When something slips, reopen the agreement in plain words instead of quietly adding surveillance.
The instinct after a miss is to tighten. More updates, shorter loops, a call on Monday. That treats attention as the missing ingredient, and attention is almost never the missing ingredient. What is usually missing is a realistic estimate, or a standard nobody ever wrote down. Sometimes it is a person who got handed four of these and could only finish one.
So ask which part was wrong. Fix that part, say so in a message, and leave the rest of the agreement where it stands. Naming the problem plainly costs less than building a process on top of it.
Wording carries more weight here than it should, because an agreement that reads as a threat gets obeyed rather than understood, and obeyed work is the shallow kind. When my first draft of one of these comes out clipped, I take the Warm rewrite in Unvent and send the version that still holds the line without sounding like a warning.
The sign that the agreement is working is boring. The update lands on Thursday, you read it, you have nothing to add, and both of you go back to work. Weeks like that look, from outside, like nothing is being managed at all. Nobody has ever thanked me for one.
Say the standard without sounding like a warning
Unvent rewrites what you are typing, in place, in the tone you choose. The agreement you send stays clear about the date and the bar, and still sounds like a person wrote it.
Add Unvent to Chrome