Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Build Decision Frameworks
Transcript
- Lucas: If we've helped you think through a career move or decision, it really comes down to the small things listeners do to keep this ad-free. Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Thanks for supporting us, Lucas. It keeps the signal clear. Lucas: Let's jump into today's friction point. You know the one. A new manager gets promoted from within, and suddenly their inbox is a graveyard of questions. Every email feels like an emergency. They start answering everything because they want to prove they're helpful, but what they actually do is become the bottleneck. Luna: Right, and they burn out in three months because they're doing the work instead of enabling the work. Lucas: Exactly. And the root cause isn't laziness or poor time management. It's a lack of a decision framework. Most new managers don't realize that leadership isn't about making more decisions; it's about deciding who makes which decisions. Without a map, every request looks like a mountain. Luna: So how do we build that map? Is there a concrete model that works outside of big tech? Lucas: The best starting point is what Amazon calls the two-way door principle. It's simple. You categorize every decision your team brings you into two buckets: reversible or irreversible. If you can undo the decision without lasting damage, it's a two-way door. The manager should not be involved in those. The team member decides, executes, and learns. Luna: That sounds efficient, but doesn't it create risk? What if they pick the wrong option on a reversible choice? Lucas: It creates learning. That's the trade-off. Let's look at a real example from a recent case study with a mid-sized software company. A senior developer asked their new manager for approval to switch a minor internal tool from one cloud provider to another. It cost five thousand dollars a month. Technically, it was reversible. If the new provider sucked, they could switch back. But the old manager had signed off on it anyway. Luna: And by signing off, the old manager wasted his own time and didn't develop the developer's judgment. Lucas: Precisely. Under a two-way door framework, the new manager would say, 'Run the pilot. Tell me the results in two weeks.' If the metrics are good, great. If they're bad, you switch back. No drama, no lost reputation. The team moves faster because they aren't waiting for permission on low-stakes items. Luna: I love that. It shifts the burden of proof from the manager to the data. But what about the other side? The irreversible decisions? Lucas: Those are one-way doors. Once you walk through, you can't come back. Hiring a key executive, launching a public product, changing the brand identity. These require heavy managerial input. You slow down here. You ask harder questions. You force the team to prepare better briefs because the cost of failure is high. Luna: So the framework acts as a filter. It tells you where to speed up and where to slow down. Lucas: Exactly. And most new managers get this backwards. They treat everything like a one-way door, slowing everything down to avoid risk. Or worse, they abdicate entirely on the one-way doors because they're afraid of being wrong. The balance is the skill. Luna: This reminds me of the concept of decision fatigue. If I'm making fifty small decisions a day, I have no mental energy left for the big ones. Lucas: Spot on. Cognitive load is real. When you micromanage the two-way doors, you drain your own battery. But more importantly, you drain your team's trust. They start looking for cues instead of solutions. They wait for you to nod before they act. That's dependency, not development. Luna: How do you actually communicate this to the team without sounding like you're shirking responsibility? Lucas: You frame it as empowerment. In your first team meeting, you lay out the criteria. You say, 'Here is how I evaluate decisions. Here is what I need from you for each type.' It removes ambiguity. People hate ambiguity. They'd rather have a rigid rule than guess what the boss wants. Luna: Does this work for creative teams? Marketing, design? Those fields often feel less binary. Lucas: It works even better there. Creative work is full of reversible experiments. A new social media campaign, a landing page variant, a color scheme change. These are all two-way doors. If it doesn't resonate, you pivot. Only the annual brand strategy or the major partnership sponsorship should go through the one-way door filter. Luna: So the manager becomes the gatekeeper only for the high-stakes creative risks, not the daily iterations. Lucas: Yes. And this clarifies your role. You're not the editor of every sentence; you're the curator of the final exhibit. That distinction changes how you spend your day. You stop checking spelling errors and start checking strategic alignment. Luna: What happens when a team member insists a two-way door is actually a one-way door? They want your sign-off. Lucas: That's a test. Ask them why. Are they insecure about the decision? Do they lack confidence? Or is there a hidden risk they see that you don't? Sometimes they're right. Maybe switching that cloud provider has legal implications they haven't mentioned. If so, elevate it to a one-way door discussion. Luna: So you use their hesitation as diagnostic data. Interesting. Lucas: Always. Hesitation usually means fear of blame. Your job is to remove the blame for reversible failures. You say, 'If this goes south, we fix it. No performance review hits. Just a post-mortem on what we learned.' That psychological safety is crucial. Luna: That takes the pressure off. But does it make you look lazy? Like you're not managing? Lucas: Only if you define management as activity. Management is outcomes. If your team ships faster and makes fewer catastrophic errors, you're managing well. Silence on the two-way doors is productive silence. It signals trust. Luna: I think many new managers confuse visibility with value. They want to be seen working hard. Lucas: Right. They mistake motion for progress. By stepping back on the small stuff, you free yourself to tackle the one-way doors properly. You give them the attention they deserve. That's where you add real value. Luna: How do you track this? Do you need a formal system? Lucas: Not initially. Start with a shared document or a simple slide. List your top ten recurring decision types. Tag each as one-way or two-way. Review it quarterly. As the team matures, you might shift some one-ways to two-ways if the risk profile changes. It's a living framework. Luna: So it evolves with the team's competence. That makes sense. Lucas: Competence grows. Trust grows. The framework expands. The goal is to eventually have almost nothing on your plate except the truly critical few. Everything else runs itself. Luna: That sounds like the ultimate freedom. But it requires letting go. Lucas: It requires discipline. You have to resist the urge to jump in when you see a mistake coming on a two-way door. Let them stumble. The lesson sticks better than your advice ever would. Luna: Hard to watch, though. Especially if you've been a performer yourself. Lucas: That's the hardest part. Shifting from player to coach. You used to win the game. Now you just set the strategy. It feels slower, quieter. But the wins are bigger because they belong to the team. Luna: Do you recommend sharing this framework with the team immediately? Lucas: Yes. Transparency builds alignment. If they know the rules of engagement, they can self-correct. They'll start asking, 'Is this a two-way door?' before they come to you. That's the goal. Luna: They start thinking like owners. That's the shift. Lucas: Ownership is contagious. One person starts owning their decisions, and others follow. You create a culture of accountability rather than compliance. Luna: Compliance is following orders. Ownership is understanding the why. Big difference. Lucas: Exactly. And it scales. You can't manage a hundred people by approving every email. You need systems. Decision frameworks are those systems. Luna: So the takeaway is: categorize, delegate the reversible, focus on the irreversible. Lucas: Summarized perfectly. It's not about doing less; it's about doing the right things. Stop being the hero of every small plot. Be the architect of the building. Luna: I like that image. Architects plan; heroes fight fires. Lucas: Be the architect. Let your team build the walls. Just make sure the foundation is solid. Luna: Solid foundations take time. But they last. Lucas: They do. And when the storm comes, you'll be glad you built it right. Luna: Here's to building structures that stand. Lucas: Agreed. Now, let's see if we can apply this to our own next steps.