Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Delegate When You Are the Micromanager
Transcript
- Lucas: So I want to start with a confession. My first year as a manager, I was a nightmare delegator. I'd assign a task, then check in an hour later. Then again before lunch. By three PM, the person would just send me their draft to shut me up. Luna: Oh I've been on the receiving end of that. It's exhausting. You end up spending more time proving you're working than actually working. Lucas: Exactly. And the irony is, I thought I was being helpful. I thought I was 'staying close to the work.' But what I was really doing was broadcasting that I didn't trust them. And that kills initiative. Luna: So today's episode is for anyone who suspects they might be the micromanager in their own team. What's the first step? Lucas: Step one: admit that micromanagement is rarely about the other person's competence. It's about your own anxiety. I remember reading a study — I think it was from Harvard Business Review — that found managers micromanage most when they feel insecure about their own role or when they're under pressure from above. Luna: So it's a control reflex, not a performance issue. That reframe alone can help you stop moralising about it. Lucas: Right. Once you accept that, you can address the real problem: your risk tolerance. I worked with a product design team at a mid-size SaaS company a few years ago. The design lead, let's call him Mark, was brilliant but he could not let go of visual details. He would redraw button icons himself. Luna: Oof. That's the classic 'it's faster if I do it' trap. But it's not faster in the long run because you're the bottleneck. Lucas: Exactly. So we sat down and I asked him one question: 'What's the worst thing that could happen if you didn't look at that button?' He paused and said, 'It might be slightly less polished. But the user wouldn't notice.' And that was the breakthrough. Luna: Because the real fear was usually smaller than he thought. So how do you turn that insight into a system? Lucas: I use a framework I call 'delegation with guardrails.' You don't just hand off a task and vanish. You specify three things: the intent, the measurable outcome, and the decision boundary. The intent is the 'why' — the strategic goal. The measurable outcome is the concrete result you expect, like 'a prototype with three user flows.' The decision boundary is where the person can make calls without you. Luna: I like that last part. So for Mark, the decision boundary might be 'you can choose any font, but run the primary colour by me.' Lucas: Exactly. And you write it down. Because when you're anxious, your memory lies. You think you agreed to review everything, but the document says otherwise. Luna: So the guardrail gives the manager something to hold onto. It's like a security blanket that still lets the other person move. Lucas: That's a great way to put it. Now, the second part is harder: you have to actively rebuild trust after you've been hovering. Because your team has learned to wait for your approval. They've stopped taking initiative. Luna: So you've trained them to be dependent. How do you undo that? Lucas: You start small. Pick a low-stakes task — something where failure costs nothing but a few minutes. Delegate it with guardrails, then literally do not ask about it until the deadline. If they come to you early, say 'I trust your judgment on this, show me the final version.' Luna: And if they mess up? Lucas: Then you treat it as a learning moment, not a reason to take back control. Say something like 'Okay, that approach didn't work. What would you do differently next time?' You're coaching, not rescuing. Luna: I think that's the hardest part for most managers — letting someone make a mistake that you could have prevented. But if you prevent every mistake, they never learn. Lucas: And you never break the cycle. I remember a Microsoft study — maybe it was from their manager effectiveness survey — that found teams with high psychological safety had managers who explicitly invited mistakes on low-risk tasks. They'd say 'I want you to try this, and if it fails, we'll debrief.' Luna: That's a specific script. 'I want you to try this, and if it fails, we'll debrief.' I'm stealing that. Lucas: Please do. Now, one more tool: the 'pre-mortem.' Before you delegate, ask yourself 'If this goes wrong, what's the most likely cause?' If the answer is 'they misunderstand the goal,' then your guardrails need to be clearer on intent. If the answer is 'they don't have the skill,' then you shouldn't be delegating yet — you need to train first. Luna: That's a good diagnostic. It separates delegation from dumping. Lucas: Right. And it forces you to be honest about whether you're micromanaging because of your anxiety or because the person genuinely isn't ready. Those are different problems with different solutions. Luna: So we've talked about frameworks and scripts. But what about the emotional side? I've had managers who were micromanagers because they cared too much — they wanted things to be perfect. Lucas: That's the perfectionist trap. And it's hard because their intentions are good. But perfectionism in a manager is a form of selfishness — you're prioritising your own comfort over the team's growth. I've had to tell myself that. Luna: That's a tough mirror to hold up. But I think it's necessary. And speaking of growth, if this episode has helped you think about your own management style, we want to mention something. Lucas: Yeah. This podcast is ad-free and listener-supported. If you've gotten value from our episodes — maybe a framework you've actually used, or a conversation you've had with your team because of something we said — you can support us at buy me a coffee dot com slash fexingo. Luna: It's a small way to keep the show going, and it means a lot. Okay, back to delegation. Lucas, you mentioned rebuilding trust. What's the first conversation you have with a direct report after you realise you've been micromanaging? Lucas: You have to be vulnerable. Say 'I've realised I've been hovering, and that's on me. I want to change that. Here's what I'm going to do differently.' Then ask them 'What's one thing I could stop doing that would help you?' And then actually stop doing it. Luna: That's powerful because it shows you're taking ownership. And it gives them permission to be honest. Lucas: Exactly. And you need to follow up. In your next one-on-one, ask 'How's it been? Am I staying out of your way?' That reinforces that you're serious. Luna: I think the key theme of this whole episode is that micromanagement is a habit, not a character flaw. And habits can be replaced. Lucas: Right. It's a behaviour you can change if you're willing to be uncomfortable for a while. Your team will be better for it, and honestly, you will too. You'll have more time to focus on the strategic work that actually needs you. Luna: So if you're a manager listening and you felt that little twinge of recognition, start tomorrow. Pick one task, write down the intent, outcome, and decision boundary, and let it go. See what happens. Lucas: And if you stumble, that's fine. Just don't use the stumble as an excuse to take back control. Stay the course. Your team's autonomy is worth the risk.