Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Micromanages Upward
Transcript
- Lucas: Luna, I want to talk about a management pattern that doesn't get a lot of airtime but quietly drains a ton of energy — micromanaging upward. Luna: Micromanaging upward? You mean when the employee is the one doing the hovering? Lucas: Exactly. It's the senior developer who sends a 'just confirming' email after every decision. The marketing coordinator who asks for approval on a font choice that's clearly within their scope. It's not malicious — it's usually driven by anxiety or a lack of clear boundaries. Luna: I've definitely seen that. And as a manager, it's exhausting because you feel like you're doing their job for them, but you also don't want to squash their diligence. Lucas: Right. So let me walk through a real case. I was talking to a former engineering manager at a mid-size SaaS company — let's call it CloudBoard, not the real name. She had a senior developer named Priya who was technically excellent but would ping her on Slack three or four times a day with questions like 'Do you think we should use the blue button or the green button?' or 'I'm about to push this commit, can you glance at it?' Luna: Three or four times a day — that's a lot. And Priya was senior. So what was going on? Lucas: The manager initially assumed it was a confidence issue. But when she dug deeper in their one-on-one, Priya said something revealing: 'I don't want to make a mistake that wastes the team's time, so I'd rather just check with you first.' Luna: So she was trying to be responsible, but it was actually creating a bottleneck. Lucas: Exactly. And the fix wasn't to tell her 'just be more confident.' That's too vague. The manager used a framework she'd picked up from a training at Airbnb, where they explicitly define what they call 'decision latitude.' Luna: Decision latitude — I like that. Break that down. Lucas: Sure. It's a simple spectrum. Level one: you decide and you don't need to inform me. Level two: you decide and inform me after. Level three: you decide but check with me first if it's over a certain cost or risk. Level four: we decide together. Level five: I decide and you execute. Luna: So the manager mapped out which decisions fell into which level for Priya. Lucas: Yes. In their next one-on-one, they went through a list of ten typical decisions Priya faced — button color, commit timing, which library to use for a new feature, how to name a variable. For maybe half of them, the manager said 'This is a level one for me. You decide, don't tell me. I trust your judgment.' For three of them, it was level two — decide and just shoot me a quick summary. For two, level three — run it by me if it involves more than two engineering days. And one was level four. Luna: That's so concrete. Priya suddenly had a map instead of a vague sense of 'should I ask?' Lucas: That's exactly the idea. The manager also set up a 15-minute weekly check-in for the level-three decisions, so Priya knew she'd have a dedicated moment to escalate. That way, she didn't feel the need to ping randomly. Luna: Did it work? Lucas: Within two weeks, the Slack pings dropped from three or four a day to maybe one every other day. And Priya's confidence actually grew because she started making those level-one calls and realising they were fine. The manager told me it freed up about three hours of her week. Luna: Three hours. That's huge. And it's not like Priya was a bad employee — she was just operating without a clear decision map. Lucas: Right. And I think that's the key insight here: micromanaging upward is almost always a symptom of unclear autonomy boundaries. The employee isn't trying to be difficult — they're trying to be safe. But safety-seeking behaviour, when it goes unchecked, becomes a tax on both people's time. Luna: So what's the first step for a manager who recognises this pattern? Say you have a Priya on your team starting tomorrow. Lucas: First, name the pattern without blame. In your one-on-one, say something like: 'I've noticed you check in with me quite a bit before making decisions. I appreciate your thoroughness, and I also think there's an opportunity to give you more ownership. Let's talk about where you feel uncertain.' Luna: That's a great opener — it's not 'you're asking too many questions,' it's 'let's give you more ownership.' Lucas: Exactly. Then, together, map out those decision latitudes. List the five to ten recurring decisions and agree which level each one is. Write it down. Send a follow-up email so there's a record. Luna: And then you need to follow through. If you say 'you decide and inform me,' you can't then nitpick the decision. That breaks trust. Lucas: Absolutely. That's the hardest part for managers who are control-oriented themselves. If you delegate latitude but then override the decision, you've effectively told the employee 'level one doesn't actually exist.' And they'll go right back to checking. Luna: So it's a two-way street. The employee needs to trust that the latitude is real, and the manager needs to trust that the employee can handle it. Lucas: One other tactic I've seen work well is the 'ticket to escalate.' Some teams use a shared document where the employee can write down a decision they're stuck on, and the manager reviews it once a day. That way, the employee doesn't feel abandoned, but the manager isn't interrupted constantly. Luna: That's a nice async approach. And it also builds a record — after a few weeks, you can look back and see which decisions kept coming up, which tells you where the employee still needs more clarity. Lucas: Exactly. And for the really sticky cases — where the employee still checks in even after you've set the latitude — you might need to explore whether there's a deeper anxiety at play. Maybe they've been burned before by a previous manager who punished mistakes. Or maybe they're in a perfectionist spiral. Luna: That's where coaching becomes more psychological. But the latitude framework is a good first diagnostic — it's concrete, it's collaborative, and it gives both sides something to point to. Lucas: Yeah. And I think it scales beyond just one employee. If you see a pattern across your team, you might have an organisational problem — maybe your company's culture rewards excessive checking, or your performance reviews penalise mistakes so heavily that people are afraid to act. Luna: That's a bigger fix, but it starts with noticing the pattern. So for a listener who's dealing with an upward micromanager right now: next one-on-one, try the latitude map. It's low risk, high return. Lucas: Before we wrap — and this actually ties in — a quick honest thing. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many episodes. We don't run ads, so listener support keeps it going. Luna: Yeah, it's a small group, but it makes a big difference. If this show has helped you navigate a tricky management moment, that's where you can keep it alive. Lucas: So if that feels right, no pressure. Now, back to the latitude framework — one more nuance I want to add. When you first set it up, check in after a week. Ask: 'How did it feel making those level-one calls? Anything surprising?' That follow-up reinforces the new behaviour and lets you adjust if something isn't working. Luna: Good point. And I'd add: celebrate a good decision they made independently. Not with a big song and dance, but a simple 'hey, I saw you handled that X situation — nice call.' That builds the muscle. Lucas: Exactly. Positive reinforcement is underrated. So to sum up: name the pattern, define the decision latitude together, set a review cadence, and reinforce trust. That's the playbook for converting micromanaging upward into real ownership. Luna: And it's a win-win — your team member grows, and you get back hours in your week. I'll take that. Lucas: Same. That's it for Manager Mondays. See you next week.