Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Team Member Who Always Says I Need More Context
Transcript
- Lucas: You've got a team member who seems sharp. Asks good questions. But every time you assign a task, they come back with the same phrase: 'I just need a bit more context.' Luna: Oh, I've managed that person. It feels diligent at first, and then you realize the context-gathering never stops. Lucas: Right. And by the time they have all the context, the deadline has slipped, or worse — the moment to act has passed. This is Episode 99, and we're going to talk about how to manage the employee who always says 'I need more context.' Lucas: If today's episode helps you think through a tricky management situation, you know what keeps these Monday conversations free and ad-free? Listener support. People who find real value here sometimes toss a few bucks to buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to say this is worth keeping around. And it genuinely lets us keep the focus on the content, not the commercials. Lucas: Exactly. So let's dig into the 'more context' loop. I want to anchor this with a specific study. Harvard Business Review ran a piece in 2024 that looked at decision-making delays in knowledge-work teams. They found that employees who habitually ask for additional context before acting are 31 percent more likely to cause project delays. Luna: Thirty-one percent — that's significant. But doesn't context matter? I mean, making a decision without context is how you get bad outcomes. Lucas: It's a tension, absolutely. The study's key finding wasn't that context is bad — it's that context-seeking can become a substitute for action. The researchers identified two types of context requests: genuine informational gaps and what they called 'procrastinatory diligence'. Luna: Procrastinatory diligence — I love that term. It's the feeling of being productive while actually stalling. Lucas: Exactly. So let me bring in a concrete example. I talked to a product director at a mid-size tech firm — about 400 people. She had a product manager, really smart guy, but every feature assignment came with five follow-ups: 'What's the customer persona here? How does this align with Q3 priorities? Can I see the competitive analysis?' Luna: Sounds reasonable on the surface. But I'm guessing the pattern was that he never moved to execution. Lucas: Correct. A feature that should have taken three weeks to ship took nine. And when she finally sat down to look at it, she realized he'd spent four of those six extra weeks gathering context that already existed in the project brief. He just hadn't read it fully the first time. Luna: So part of the problem might be that the context was already given, but he didn't internalize it. That's a different issue from genuinely needing more information. Lucas: That's the distinction a manager has to make. Is this person asking for something they truly don't have, or are they asking for reassurance before taking a risk? In this case, it was the latter. He was afraid of making a wrong call, so he kept gathering data to feel safe. Luna: And that fear of being wrong is something a lot of us can relate to. Especially early in a career. But as a manager, how do you break that cycle without discouraging thoroughness? Lucas: The product director I spoke with used a framework she learned from a former COO. She called it the 'Three Questions' approach. Before the employee could ask for more context, she'd say: 'Tell me what you already know. Tell me what you're unsure about. And tell me what you're going to do with the answer.' Luna: That third question is the kicker. Because if they can't articulate how the context will change their action, then it's likely procrastinatory. Lucas: Exactly. She told me within two weeks, the product manager started coming to her with his own draft answers to those three questions. He didn't need her to provide context anymore — he just needed to articulate what he already had. Luna: So you're basically teaching the employee to self-diagnose. That's a skill they can carry forward. Lucas: Right. But let's talk about a different flavor of this — the employee who genuinely lacks context because the organization is siloed. That's not procrastination; that's a structural problem. Luna: Good point. If your team member is always asking 'more context' because they literally don't have access to the information, then the fix is different. You can't just give them a framework — you have to fix the information flow. Lucas: So how do you tell the difference? One tell is specificity. The procrastinatory context-seeker asks general questions: 'Can you give me more background on this?' The genuine information-seeker asks pointed questions: 'I see the revenue target for Q3, but I don't have the channel breakdown. Can you point me to that?' Luna: That's a useful diagnostic. The specific question can be answered with a single document or a five-minute conversation. The vague question opens a never-ending loop. Lucas: Another sign is pattern over time. If the employee asks for context on every single task — regardless of complexity — it's probably a habit, not a need. I'd also look at whether they eventually act. Some people gather context and then still don't move. Luna: Yeah, that's the paralysis-by-analysis version. They have all the data but no decision. Lucas: So here's a script for when you hear 'I need more context.' First, validate the instinct — context is good. Then say: 'Great, what's the one piece of context that would let you start? And what can you do with what you have right now?' Luna: That pushes them to prioritize. It also sets an expectation that action doesn't require perfect information. Lucas: Exactly. And if they keep coming back, you might need to set a firmer boundary. Something like: 'I trust you to make this call with the information available. If you're stuck after making a genuine attempt, come back to me with your draft solution.' Luna: That's a nice middle ground — you're not shutting them down, but you're also not letting them offload the decision back to you. Lucas: I want to bring in another angle. There's a concept from the book 'Decisive' by Chip and Dan Heath. They talk about 'narrow framing' — making a decision between two options without considering alternatives. The context-seeker often has narrow framing: they think they need more information to choose between A and B, when really they should be considering C or D. Luna: So the manager's role is to expand the frame. Instead of giving more context about A and B, ask: 'What are other ways we could solve this?' Lucas: Precisely. That can break the loop by showing that the question isn't about context — it's about creativity or problem-solving. And that's a different muscle. Luna: Let me push back a little. In some organizations, especially highly regulated ones like finance or healthcare, context isn't optional. If an employee doesn't ask for context and makes a compliance error, that's a big problem. Lucas: That's a fair counter. In regulated environments, the 'more context' request might be a sign of prudence, not procrastination. The manager has to calibrate based on the stakes. If the cost of acting without context is a regulatory fine, then you actually want the employee to pause and ask. Luna: So the manager's first job is to understand the operating environment. A context-seeker in a startup might be stalling; in a bank, they might be protecting the company. Lucas: Exactly. So let's add a layer: you also need to set a shared definition of 'enough context.' I've seen teams create a 'context checklist' for common tasks. If the employee ticks off the checklist, they have enough to proceed. That removes ambiguity. Luna: That's practical. It also gives the employee a sense of control — they can check the boxes themselves instead of relying on you. Lucas: Right. And it's a good way to onboard new hires who are prone to over-asking because they don't know what's normal yet. Give them the checklist and say: 'Once you have these five things, you're ready to go. If you need more, ask yourself why.' Luna: I like that. It's like training wheels for decision-making. Eventually they internalize it and don't need the list. Lucas: So to sum up our toolkit today: First, diagnose — is this a genuine information gap or procrastinatory diligence? Use specificity and pattern to tell the difference. Second, use the Three Questions framework to help the employee self-diagnose. Third, set a shared definition of 'enough context' through a checklist or expectation-setting conversation. Luna: And fourth, know your environment. The same behavior in a startup versus a bank might need totally different responses. Lucas: Exactly. Context-seeking isn't inherently bad. But when it becomes a default pattern that slows the team down, the manager has to step in — not to punish curiosity, but to redirect it toward action. Luna: What about the manager who is themselves a context-seeker? I've seen leaders who always ask for more context before making a decision, and it demoralizes the team. Lucas: That's a great point for a future episode. But briefly: the same principles apply. If you're a manager who asks for context repeatedly, you're signaling that you don't trust your team's judgment. That's corrosive. You have to model the behavior you want — sometimes make a decision with imperfect information and say, 'We'll learn as we go.' Luna: Yeah, that's leadership. It's about showing that action has value even without perfect clarity. Lucas: So next time a team member says 'I need more context,' don't just give it. Ask them what they already know, what they're unsure about, and how the answer will change their next move. You might be surprised how often they already have enough. Luna: And if they truly don't, then you've got a real information gap to address — which is a much more productive conversation. Lucas: That's it for Episode 99. If you've got a management question you'd like us to tackle, drop us a note. We read every one. See you next Monday.