Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / Why New Managers Fail At Strategic Delegation
Transcript
- Lucas: I want to talk about the one thing that keeps new managers awake at two in the morning, which isn't really about the work itself. It's the terrifying realization that if they step away from their desk for even an hour, the entire operation might stall because they never actually figured out how to let go. Most people think delegation is just a productivity hack, a way to clear your calendar so you can do more important stuff. But it's actually a leadership test, a measure of whether you trust your team's judgment as much as your own. Luna: Right, because we all know the feeling. You pick a project, you know exactly how it should be done, and the urge to jump in and fix it before someone else messes up is overwhelming. So what's the actual mechanism for breaking that habit? Lucas: The mechanism starts with realizing that delegation isn't just about dumping tasks; it's about transferring decision rights. When you assign a task, you're saying do this. When you delegate authority, you're saying decide how this gets done and tell me when you need help. The problem is that most new managers confuse these two concepts and end up micromanaging the outcome while pretending they gave ownership. They say I trust you with this project, but then they check every email draft and correct every font size. Luna: That sounds like classic impostor syndrome leaking into management style. They feel like if they aren't doing the work, they aren't adding value. Lucas: Exactly. And it creates a bottleneck where the manager becomes the single point of failure for everything. I've seen this happen repeatedly with promotions from individual contributor roles. Someone was great at coding or selling, so they get promoted to manage those functions. But now they spend forty percent of their week answering questions their team could easily solve themselves. That's not leadership; that's just being a senior player who also happens to hold the keys. Luna: So how do you distinguish between a question that needs your input versus one where the team has enough context to proceed? Where's the line? Lucas: The line is defined by risk tolerance and clarity of outcomes. Before you hand off a responsibility, you need to define what success looks like in concrete terms. Not vague goals like improve engagement, but specific metrics like increase response time by fifteen percent within six weeks. Once those boundaries are set, the team owns the path to get there. Your job shifts from directing the steps to reviewing the results against those pre-agreed standards. Luna: But doesn't that require a level of upfront communication that feels exhausting at first? Like spending hours aligning on details before they even start? Lucas: It does initially, yes. But it pays back exponentially over time. Think of it as an investment in friction reduction. If you spend three days clearly outlining the constraints, the resources, and the expected deliverables, you save thirty hours of back and forth corrections later. The cost of miscommunication is always higher than the cost of alignment. Most managers skip the alignment phase because they're in a rush, and then they pay for it in constant firefighting mode. Luna: So the mistake isn't giving them too much freedom; it's failing to give them enough structure to use that freedom effectively. Lucas: Precisely. Autonomy without context is chaos. Context without autonomy is suffocation. You need both. And here's the tricky part that trips up so many new leaders: you have to be willing to watch them make small mistakes. If you intervene the moment something goes slightly off track, you signal that you don't actually trust their capability. You reset the cycle of dependency. Luna: That's hard to sit with. Watching someone struggle through a process you know is inefficient feels painful. How do you resist the urge to jump in? Lucas: You reframe the struggle as data. Every time they hit a snag, it tells you where their knowledge gap is or where your instructions were unclear. Instead of fixing it yourself, ask them what they think the next best move is. Force them to articulate their reasoning. This builds their problem-solving muscle while keeping you in the coach role rather than the player role. You're not abandoning them; you're scaffolding their independence. Luna: I love that framing. It turns frustration into a learning opportunity for both sides. But what about when the stakes are actually high? When a mistake could cost the company serious money or reputation? Lucas: Then you adjust the risk parameters. High-stakes decisions require higher levels of consultation and sometimes veto power for the manager. But even then, the goal is shared understanding, not unilateral control. You can say I'll review this final draft before it goes out, but you still write the first version. You don't take the keyboard away; you just become the final checkpoint. That preserves their creative agency while protecting the organization from catastrophic error. Luna: So it's a spectrum, not a binary switch. You calibrate your involvement based on the potential impact of the outcome. Lucas: Correct. And this calibration requires honest self-assessment about your own team's maturity. A seasoned team can handle broad autonomy with minimal oversight. A newer team needs tighter loops and more frequent check-ins. The mistake new managers make is applying the same delegation model to everyone regardless of experience level. They either micromanage the experts who are bored stiff or laissez-faire the novices who are drowning. Luna: That makes sense. Tailoring the approach to the individual seems like a core management skill that doesn't get taught enough in those quick promotion trainings. Lucas: It absolutely doesn't. Those trainings usually focus on administrative tasks like setting up calendars or running meetings. They rarely touch on the psychological heavy lifting of managing human potential. Which brings us to another critical piece: feedback loops. Delegation fails when there's no mechanism for course correction mid-stream. Luna: So you're saying you can't just dump the project and disappear until the deadline? You need regular touchpoints? Lucas: Regular touchpoints are non-negotiable, but they shouldn't be status updates. Status updates are for reporting progress. Touchpoints should be for removing blockers and refining strategy. If you're asking Did you finish section two? you're treating them like a robot. If you're asking What obstacles did you encounter today and how can I help clear them? you're treating them like a partner. The language shift changes the dynamic entirely. Luna: I think that's the key. It moves the relationship from supervisor-subordinate to collaborator-collaborator. Even though the power dynamic still exists, the day-to-day interaction feels more equitable. Lucas: Equitable doesn't mean equal in responsibility, but it means equal in respect for their professional judgment. When you validate their insights during those touchpoints, you reinforce their confidence. Confidence leads to faster decision-making. Faster decision-making reduces your workload. It's a virtuous cycle that scales beautifully. Luna: And if the cycle breaks? If someone consistently misses the mark despite clear guidance and support? Lucas: Then you have a performance issue, not a delegation issue. Don't confuse incompetence with poor delegation structures. Sometimes people genuinely aren't suited for certain types of work, and that's okay. Recognizing that early saves everyone time. You might need to reassign the task or provide intensive training. But you shouldn't assume that because someone struggled once, you need to take the reins forever. One bad attempt doesn't disqualify them from future autonomy. Luna: That's a crucial distinction. We often generalize from a single failure. Taking it one step further, how do you celebrate the wins when the team member executes perfectly? Lucas: Public recognition is vital. Make sure credit flows to the person who did the work, not the manager who facilitated it. This reinforces the behavior you want to see. It shows the rest of the team that autonomy leads to visibility and reward. If you hoard the praise, you kill motivation faster than anything else. Let them shine. Your glow comes from having a team that operates independently, not from being the center of attention. Luna: It feels counterintuitive to some ego-driven managers, but it's the only sustainable way to build a legacy. You're building systems, not just delivering projects. Lucas: Exactly. Legacy is about what happens when you're not in the room. If your absence causes chaos, you haven't built a system; you've built a crutch. And speaking of systems, I want to pause briefly to talk about how this show stays online. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. — and that's literally what funds making this many of these episodes possible. No ads, just community support keeping the lights on. Luna: Yeah, it's amazing how much that direct support allows us to dive deeper into topics like this without worrying about sponsor constraints. It keeps the conversation focused on what actually helps you. Lucas: Back to the topic, though. One last thing on delegation: documenting the process. When someone successfully handles a complex task, capture that knowledge. Create a simple checklist or a guide. This prevents reinventing the wheel and gives future hires a roadmap. It transforms personal expertise into organizational assets. Luna: Knowledge transfer is huge. It stops the bus factor problem where only one person knows how things work. Making that knowledge accessible empowers everyone else to step up. Lucas: It does. And it reduces the pressure on high performers who are currently carrying that hidden knowledge load. Giving them permission to document and share takes some weight off their shoulders. They can focus on strategic thinking instead of being the sole repository for tactical details. Luna: So ultimately, good delegation is about distributing intelligence across the team, not just distributing labor. You're leveraging collective brainpower. Lucas: That's the right way to look at it. Labor is cheap; intelligence and judgment are expensive. Protecting and developing that judgment in your team members is the highest ROI activity a manager can engage in. It takes patience, it requires vulnerability, but the payoff is a resilient, agile organization that doesn't collapse under pressure. Luna: Resilience through distributed competence. I think that's the mantra for any leader looking to scale their impact beyond their own bandwidth. Lucas: Agreed. So the next time you feel that itch to jump in and fix something, take a breath. Ask yourself if you're preventing a mistake or preventing a learning moment. Because sometimes the mistake is the teacher.