Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / Managing the Employee Who Always Says I Need More Context
Transcript
- Lucas: So Luna, we've covered a lot of ground on employee types over the past few weeks. But there's one I keep hearing from managers, and it's a bit different from the usual suspects. Luna: What's that? Lucas: The employee who always says, 'I just need more context.' It sounds reasonable, even thoughtful. But when it happens on every single task, it can become a real drag on momentum. Luna: Oh, I know that one. It's like they're asking for the backstory before they'll even consider moving forward. Lucas: Exactly. And it's tricky because you don't want to discourage curiosity. But there's a line between wanting to understand the 'why' and using context as a way to avoid starting. Luna: So how do you tell the difference? That feels like the core question here. Lucas: Let's get into that. I actually came across a case study from a mid-sized SaaS company, about 200 employees, where a product manager had this exact issue with one of her reports. Every new project, the employee would ask for more background, more customer interviews, more data. She was spending hours just briefing him. Luna: What was the breaking point? Lucas: They had a feature release that got delayed by three weeks because he kept asking for more competitor research. She realized this wasn't just about being thorough. It was a pattern. Luna: So what did she do? Lucas: She started tracking his questions for two weeks. Every time he asked for more context, she wrote it down. Then she categorized them. About half were legitimate—needed to make good decisions. The other half were things he could have found in the company wiki or by talking to a teammate. Luna: That's smart. It turns a vague feeling into something concrete. Lucas: Right. And it gave her a way to have a conversation without accusing him of being lazy. She showed him the list and said, 'Here's what I'm noticing. Let's figure out what you actually need to move forward.' Luna: Did that work? Did he change? Lucas: It did, but not overnight. They set up a 'context threshold' together. Basically, they agreed on the minimum information needed before starting a task. For example, for a new feature, he needed the target user, the problem it solved, and the success metric. Anything else he could research as he went. Luna: So they defined what 'enough' looks like. That's a great framework. Lucas: Yeah. The key was that she didn't just say 'stop asking questions.' She helped him build a filter for what questions were worth asking. Luna: But what if the employee resists that? Like, they feel you're cutting off their ability to do good work? Lucas: That's a real risk. That's why the conversation has to be collaborative. You're not saying 'stop asking.' You're saying, 'Let's figure out what you truly need versus what you think you need.' Luna: And maybe there's a deeper issue. Like, they're afraid of making a mistake without all the info. Lucas: Exactly. Often, the need for context is a symptom of anxiety or perfectionism. They want to avoid the discomfort of ambiguity. So as a manager, you need to create psychological safety for them to start without all the answers. Luna: That sounds like a coaching opportunity, not just a task assignment. Lucas: Yeah. You can say, 'I know this feels incomplete, but we're going to learn as we go. Your job is to flag what you're missing, not to have everything upfront.' Luna: And then you have to follow through. If they flag a missing piece, you need to either fill it or explicitly say, 'Let's proceed without it.' Lucas: Absolutely. Consistency is what builds trust. If you say 'start anyway' but then get annoyed when they ask a question later, you've just reinforced their fear. Luna: Speaking of trust, this reminds me of something from our own experience. We've been doing this show for a while, and we've never run a single ad. That's a choice we've made because we want you to get the information without any distractions. Lucas: Yeah, we've kept it clean. And if you find value in what we do, and you want to support that ad-free mission, there's a simple way to do it. It's at buy me a coffee dot com slash fexingo. Luna: That's a low-key way to help us keep doing this. No pressure, but it does make a difference. Lucas: Yeah, we appreciate anyone who does. But let's get back to the topic. We were talking about the context threshold. I think there's another layer to this. Luna: What's that? Lucas: Sometimes, asking for context isn't about anxiety at all. It can be a sophisticated way to stall or even to assert control. If an employee feels insecure about their role, they might use questions as a power move. Luna: Really? How does that play out? Lucas: They ask for 'the bigger picture' or 'the strategic rationale' in a way that subtly challenges your authority. It's like they're saying, 'I'm not sure YOU know what you're doing, so give me a reason to trust you.' Luna: That sounds exhausting to deal with. Lucas: It is. But here's the thing: if you assume good intent and treat it as a genuine request, you can disarm it. You say, 'Great question. Here's the context. Now let's move.' Luna: And if they keep pushing? Lucas: Then you name it directly. You say, 'I notice we keep going back to the 'why' here. Is there something about the direction you're uncomfortable with?' That opens a real conversation. Luna: That's a bold move, but probably necessary. Lucas: Yeah. Because if you let it slide, you end up with a dynamic where the employee is essentially setting the pace and the agenda. Luna: And that's not good for anyone. Lucas: No. So the key is to be aware of the different motivations. If you can diagnose whether it's anxiety, a genuine need, or a power play, you can respond appropriately. Luna: What about the opposite? An employee who never asks for context? They just run with it and sometimes crash? Lucas: That's a different problem. But in a way, it's the same root issue: a mismatch between the information they have and the information they need. For the chronic asker, you're trying to get them to move with less. For the runner, you're trying to get them to slow down and ask. Luna: So it's all about calibration. Lucas: Exactly. And as a manager, you're the one who has to set the baseline. You need to be explicit about what level of context you expect for different types of tasks. Luna: Can you give an example? Lucas: Sure. For a routine task like updating a report, the expectation might be 'just do it.' For a project with cross-team impact, you'd want them to come to you with a plan and a few clarifying questions first. Defining these expectations prevents a lot of back and forth. Luna: That makes sense. It's like you're giving them a map for when to ask and when to proceed. Lucas: Right. And you have to be consistent with it. If you say 'just do it' but then get upset when they miss a detail, you're sending mixed signals. Luna: So it's about building a shared understanding. Lucas: Exactly. And that takes time and practice. But once you have it, the team runs much more smoothly. Luna: I like that we're giving managers a practical tool. The context threshold is something you can literally implement tomorrow. Lucas: Yeah. And if you try it, let us know how it goes. We love hearing from listeners. Luna: Absolutely. And on that note, I think we've given people a lot to chew on. Lucas: We have. So next time an employee asks for more context, think about whether they need it to move or if they're using it to stay still. And then coach them accordingly. Luna: That's a good takeaway. Thanks for listening, everyone. Lucas: See you next week.