Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How Managers Lose Context When They Delegate
Transcript
- Lucas: We spend a lot of time talking about delegation as if it’s a simple transfer of labor. Hand off the task, get the result, move on. But here’s the thing that keeps tripping up good managers in October twenty twenty six: they delegate the what, but they forget to delegate the why. Luna: Right, because without the why, the employee is just guessing at the constraints. They end up asking ten clarification questions or, worse, making a confident but misaligned decision. Lucas: Exactly. I call this the Context Gap. It’s not that your team members are incapable of execution. It’s that you’ve handed them a map with the legend missing. You give them the destination, but not the terrain, the weather, or the reason we’re going there in the first place. Luna: So it’s less about trust and more about information asymmetry. The manager holds all the institutional knowledge, and then suddenly drops it on someone who doesn’t have access to those emails or hallway conversations. Lucas: Precisely. And in a hybrid or fully remote environment, that asymmetry gets wider. If you used to tap someone on the shoulder and explain the political nuance of a client request, now you’re dropping a Jira ticket or a Slack message. The nuance evaporates. Luna: I see this all the time with new hires. They’ll deliver exactly what was asked for, but miss the unstated requirement because no one took five minutes to set the stage. Lucas: Let’s look at a concrete example. Imagine a marketing manager asks a junior analyst to build a report on customer churn. The instruction is clear: pull data from Q three, compare it to Q two, and send it by Friday. Luna: Simple enough. What goes wrong? Lucas: The analyst builds a beautiful chart. But she doesn’t know that the CEO is currently obsessed with retention rates in the enterprise segment, not SMB. Or that there’s a product outage last month that skewed the numbers artificially. She presents raw data, and the meeting feels awkward because the insights don’t match the executive’s current anxiety. Luna: That’s frustrating for everyone. The analyst did her job, but the output was useless to the stakeholder. So the manager looks like he didn’t provide direction, and the analyst feels criticized even though she followed instructions. Lucas: It’s a lose-lose. And the fix isn’t to micromanage the analysis. It’s to bake the context into the initial ask. We need a framework for what I call the Briefing Layer. Luna: Tell me about this layer. Is it just a checklist of things to include? Lucas: It’s three specific components. First is the Decision History. Why are we doing this now? What previous attempts failed? Second is the Constraint Set. Who needs to approve this? What’s the budget cap? What tools can you use? Third is the Success Criteria beyond the deliverable. What does winning look like for the stakeholder? Luna: So instead of saying build the report, you’d say build the report so the VP can defend the budget cut to the board, using only Salesforce data, because HR data is locked down. Lucas: Spot on. That third point changes everything. Now the analyst knows to focus on clarity and defensibility, not just accuracy. She might even suggest a different visualization that highlights the trend line rather than individual monthly spikes. Luna: That shifts the cognitive load. Instead of figuring out the politics, she can focus on the craft. It actually makes the work more engaging for her. Lucas: It does. And it frees you up. You’re not checking every step because you aligned on the destination and the rules of the road upfront. You’re just reviewing the final output against those pre-agreed criteria. Luna: But doesn’t this take longer initially? Writing out the decision history and constraints seems like extra admin work. Lucas: It takes five minutes extra per assignment. But it saves hours of rework later. Think about the cost of that one-hour meeting where the manager has to explain why the report is wrong. That’s thirty minutes of lost productivity right there, plus the morale hit. Luna: Yeah, the ROI on those five minutes is massive. Especially when you consider that high performers hate ambiguity. They want to solve hard problems, not guess what the boss wants. Lucas: Agreed. High performers will thrive in a high-context environment. They’ll feel trusted because you’re giving them the full picture. Low performers might try to use the lack of context as an excuse for poor results, but that’s a different problem. Luna: True. If someone refuses to engage with the context you provide, that’s a performance issue, not a management failure. Lucas: Right. So the manager’s job is to eliminate the noise. Make the signal clear. And that means being deliberate about what you share. Luna: What about sensitive context? Like office politics or confidential restructuring plans? Do you share that too? Lucas: That’s the tricky part. You don’t share gossip. You share structural reality. You don’t say John is difficult. You say John cares deeply about risk mitigation, so frame your proposal around safety margins, not speed. Luna: Ah, so it’s about translating human dynamics into actionable constraints. That’s actually very safe to share. It’s professional intelligence, not drama. Lucas: Exactly. It empowers the employee to navigate the organization effectively. It’s like giving them a compass instead of just coordinates. Luna: I love that. Compass versus coordinates. One tells you where you are relative to north. The other just says go east. Lucas: And in today’s distributed workforce, knowing which way north is crucial. You don’t have the luxury of overheard conversations in the kitchen. Luna: So, practically speaking, how do we embed this into daily workflows? Is there a template? Lucas: You don’t need a complex template. Just a standard structure for your briefs. Start with the context paragraph. Then list the constraints. Then define success. Keep it tight. Luna: Can you give us a quick example of that structure? Something listeners could copy tomorrow. Lucas: Sure. Context: We’re pitching the new software suite to the logistics division next week. They rejected the pilot last year due to integration concerns. Constraints: Use only existing API docs. Budget is fixed at fifty thousand dollars. Success: They sign a letter of intent by Friday. Luna: That’s incredibly clear. The person taking this on knows exactly what the obstacle was, what the limits are, and what the goal is. No guessing required. Lucas: No guessing. And notice how much faster that conversation moves. You skip the first round of clarifying emails. You jump straight to execution. Luna: It also reduces your own anxiety. You’re not hovering because you know the parameters are set. Lucas: It does. Delegation becomes scalable. You can hand off bigger projects because you’ve trained your team to think within the context you provide. Luna: Before we wrap this up, I want to pause for a second. This show is completely ad-free. We don’t run banners, we don’t read sponsorships, and we don’t push affiliate links. We just make the content we believe is useful for people managing teams and careers. Lucas: If we’ve helped you think through a career move or a management challenge this week, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. It’s the only way we keep the lights on. Luna: Thanks for keeping this independent. Now, back to the work. How do you handle pushback when a team member says they don’t need all that context? Lucas: That’s a great question. Sometimes senior staff say, just tell me what to do, don’t waste my time with background. My response is usually, I’m trusting your expertise to navigate the nuance. If I leave it out, you’re flying blind. Luna: Reframing it as trust rather than bureaucracy. That works. It makes the context sharing feel like respect for their skill level. Lucas: Exactly. You’re treating them like partners, not order-takers. And that changes the dynamic entirely. Luna: So the takeaway is simple. Stop delegating tasks. Start delegating context. Give them the map, the compass, and the destination. Lucas: Give them the whole picture. Because once they have it, they won’t just execute. They’ll excel.