Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / Why New Managers Fail at Context Setting
Transcript
- Lucas: I want to talk about a specific failure mode I see every day in the office. It is not laziness. It is not incompetence. It is what I call the Context Gap. A new manager gets promoted because they were excellent at executing tasks. They know how to build the widget or write the code. So when they become a manager, they assume their job is to tell people exactly what to do. And they do it with extreme precision. Luna: But precision without context is just noise, right? The team knows the what, but they have no idea why it matters. Lucas: Exactly. And here is the concrete example. Last month, I spoke with a director at a mid-sized software company. She had just taken over a team of eight engineers. Her first big initiative was to migrate their legacy database. She sent an email listing ten technical requirements. Every single one was accurate. But two weeks later, half the team was still arguing over which library to use for the migration script. She had given them the destination, but she hadn't drawn the map. Luna: That sounds like classic micromanagement in reverse. She controlled the details so tightly that she left no room for judgment. Lucas: It is worse than micromanagement because she thought she was being helpful. She thought she was removing ambiguity. But by not explaining the business reason for the migration, she didn't remove ambiguity. She just shifted it from the goal to the method. Now the engineers are debating methods because they don't know which constraint is hard and which is soft. One engineer spent four days optimizing a query that turned out to be irrelevant because the business priority shifted. Luna: So the cost wasn't just wasted time. It was wasted trust. The team probably felt confused and then frustrated when their work didn't align with the shifting priorities. Lucas: Precisely. And this happens constantly. We think that if we write the instruction clearly enough, the recipient will automatically understand the intent. But human beings are not computers. We fill in the blanks with our own assumptions. And those assumptions are usually wrong. When you promote a high performer to management, you have to teach them something completely different. You have to teach them how to set context, not just assign tasks. Luna: So what does good context setting actually look like? Is there a framework? Lucas: There is a simple structure that works remarkably well. It is the Why, What, and How. Most managers skip the Why entirely. They jump straight to the What. The How is optional, depending on the seniority of the team member. Let me break down the Why. This is the business rationale. Why are we doing this now? What problem are we solving? Who is affected? If you can explain the Why, you give your team the ability to make decisions when you aren't in the room. Luna: And the What is the deliverable. The specific outcome you need. But the How is where most new managers choke. They want to dictate the process. Lucas: Right. The How is the flexibility zone. For a junior employee, you might need to specify the How. For a senior engineer, you should never specify the How unless asked. By giving them the Why and the What, you empower them to choose the best How. This speeds up execution because they don't have to wait for approval on every step. They just have to ensure the result meets the criteria you set. Luna: It shifts the dynamic from compliance to ownership. That changes the entire energy of the team. Lucas: It does. And it solves the problem of the shifting priority I mentioned earlier. If the director had explained that the migration was driven by a security audit coming in six weeks, the engineers would have prioritized speed over optimization. They wouldn't have spent four days on a query that didn't matter. They would have built the minimum viable solution to pass the audit. The context of the deadline changed the technical decision. Luna: So the lesson is that context includes constraints. Deadlines, budgets, risks. Without those, the team is flying blind. Lucas: Yes. Constraints are part of the context. In fact, they are often more important than the goal itself. If I tell you to run a mile, but I don't tell you that you have a sprained ankle, you might try to sprint. You need to know the boundaries. As a manager, you hold the map of the constraints. Your job is to share that map so your team doesn't walk off a cliff. Luna: This feels like a lot of work upfront. Isn't it faster to just tell someone what to do? Lucas: It is faster in the moment. That is the trap. Taking five minutes to explain the Why saves five hours of rework next week. But new managers are under pressure. They feel like they need to show immediate output. So they cut corners on communication. They think they are being efficient. But they are actually creating debt. Technical debt is bad. Communication debt is worse because it compounds over time. Luna: Because once the team learns that instructions are vague, they stop trusting them. They start asking for clarification constantly. Lucas: Exactly. You create a cycle of dependency. The team comes back to you for every little decision because they don't trust their own judgment. They think you will correct them if they guess wrong. So you end up doing their job for them. You become the bottleneck. And you burn out because you are carrying the cognitive load of the entire team. Luna: Which brings us back to the original point. Managing former peers is hard. But managing them effectively requires this shift in communication style. Lucas: It makes it even harder. Because when you were their peer, you talked as equals. You shared context informally. Now you are their boss. You have to formalize that context. You have to sit them down and say, here is the business goal, here is the constraint, here is the expected outcome. It feels awkward at first. It feels like you are lecturing them. But it is necessary. Luna: And it establishes your authority not through title, but through clarity. People respect leaders who make things clear. Lucas: They do. Ambiguity breeds anxiety. Clarity breeds confidence. When your team knows exactly what success looks like, they can relax. They can focus on the work. They don't have to spend energy guessing what you want. That is a gift you give them. It reduces their stress. It increases their performance. Luna: So how do you practice this? Do you write it all down? Or is it verbal? Lucas: It should be both. Start with a verbal conversation. Sit down with the team member. Explain the Why. Discuss the constraints. Let them ask questions. Then, follow up with a brief written summary. This serves as a reference. It prevents the 'I forgot what you said' excuse. But the magic happens in the verbal exchange. That is where you gauge understanding. You can see if they are nodding along or if they are confused. Written text has no tone. It has no feedback loop. Luna: So the email is just the receipt. The meeting is the transaction. Lucas: Perfect way to put it. The email confirms the agreement. The meeting builds the alignment. If you skip the meeting, you have an agreement without alignment. And that leads to the kind of friction we saw with the database migration. Luna: I think a lot of new managers also fear that if they explain too much, they will lose control. Like they are giving away power. Lucas: That is a common fear. But sharing context is not losing control. It is distributing control. You are empowering others to execute within your framework. You are not giving up the steering wheel. You are just letting them drive. You still decide the destination. You still watch the road signs. But you let them handle the gear shift. Luna: That reframes it nicely. It turns management into enablement rather than enforcement. Lucas: Exactly. Enablement. That is the keyword. Your job is to enable your team to do their best work. And the best way to do that is to remove obstacles. Vague instructions are an obstacle. Context clears the path. It allows flow state. It allows creativity. When people know the boundaries, they can play inside them. Luna: So for listeners who are new managers, the takeaway is to slow down the initial instruction phase. Spend more time on the Why. Lucas: Yes. And check for understanding. Don't just ask if they have questions. Ask them to repeat back the goal in their own words. If they can articulate the Why, you know they are ready. If they cannot, you haven't finished your job yet. Go back and clarify. Luna: It seems like such a simple thing. But it requires discipline to resist the urge to just send the ticket. Lucas: It does. It requires resisting the quick fix. The quick fix always costs more in the long run. Investing in context is investing in speed. It sounds counterintuitive. But slower is smoother. Smoother is faster. Luna: I love that. Slower is smoother. It reminds me of the saying about haste making waste. Lucas: Old wisdom, new application. But it holds true in the modern workplace. We are so obsessed with velocity that we forget about direction. Direction requires context. Velocity requires execution. You need both. Luna: So before we go, I want to mention that this show is listener-supported. We deliberately don't run ads on these episodes because we want to keep the content clean and focused on value. If you've found this conversation useful, you can support us directly at buy me a coffee dot com slash fexingo. It helps us keep producing these deep dives without corporate interference. Lucas: We appreciate any support. It allows us to continue exploring these topics thoroughly. Back to the topic. Think about your last team meeting. Did you provide enough context? Or did you just assign tasks? Try adding the Why next time. See how it changes the quality of the work. Luna: Try it. I bet you will see a difference in engagement almost immediately. Lucas: It is worth the effort. Clear direction is the foundation of great leadership. Without it, everything else falls apart.