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 you give someone a task, and their first response is — can you give me more context? And then you give them more context, and they ask for background on the context, and suddenly you're three emails deep and the thing still hasn't been started. Luna: I've been that manager. It's like they can't move until they understand the entire history of the universe around the project. Lucas: Right. And the tricky part is — it often comes from a sincere place. They want to do a good job, they want to fully understand before acting. But at some point, it becomes a drag on speed, and it can actually undermine their own decision-making. Luna: When does curiosity become a liability? Lucas: That's exactly the question. I want to talk about a specific case from a mid-size SaaS company I know. A VP of Engineering had a product manager who was brilliant — fantastic at synthesizing information — but every assignment turned into a research project. Before writing a single user story, she'd want the competitive landscape, the customer interview transcripts, the last six months of sales call notes, the board deck from the previous quarter. Luna: That actually sounds thorough, not dysfunctional. At least on the surface. Lucas: It does. And the VP initially thought, great, she's diligent. But then he noticed a pattern. Her team would miss sprint commitments because she was still "gathering context" on day three of a one-week sprint. And when she finally did produce something, the extra information rarely changed her output. It was protective, not productive. Luna: So how did he approach it? Lucas: He introduced something from a Harvard Business Review article called the 'context threshold.' The idea is that there's a point beyond which additional information stops improving the quality of a decision and actually degrades it — because you're delaying action, overfitting to noise, or exhausting your stakeholders. Luna: Is there a way to measure that threshold, or is it more of a judgment call? Lucas: It's more of a heuristic. But the VP made it concrete. He told her: for any task I give you, you have one page of background — that's the constraint. And you have 48 hours to make a decision or produce a draft. After that, the context is what it is. Luna: One page. That's pretty extreme for someone used to consuming 50 pages. Lucas: It felt extreme to her too. She pushed back — said she needed more to avoid making a bad call. And the VP said, 'If you hit the 48-hour mark and you genuinely don't have enough information to proceed, then come to me with exactly one question. Not a list. One question. And I'll answer it within the hour.' Luna: That's a really smart constraint. It forces prioritization. Lucas: Exactly. It reframes the problem from 'get all the context' to 'what is the single most critical unknown.' And most of the time, once you force someone to articulate that one question, they realize they already know enough to act. Luna: Did it work for her? Lucas: It took about three sprints for the habit to stick. The first sprint she still tried to gather context on the side, but the constraint forced her to ship something by the deadline. And she saw that her decisions weren't worse — in fact, they were faster and more confident. The VP told me her velocity increased by about 40 percent over the next quarter. Luna: I wonder how much of this is a management failure versus an employee flaw. Because if someone is asking for context, maybe it's because they don't trust that they have the full picture — and maybe that's on the manager for not setting clear boundaries upfront. Lucas: That's a fair point. There's definitely a spectrum. On one end, you have managers who under-communicate and leave employees guessing — that's a failure of clarity. On the other end, you have employees who use context-seeking as a way to avoid making a wrong call, or to postpone accountability. The key is distinguishing between the two. Luna: So how do you tell the difference as a manager? Lucas: I like a simple diagnostic. Ask yourself: does this person produce excellent work once they have the context, or do they keep asking for more even after a reasonable amount has been given? If it's the former, you probably need to give clearer initial briefs. If it's the latter, you have a context threshold problem. Luna: And the fix for the latter is what you described — constraining the container. Lucas: Right. Another technique I've seen work is the 'three-question drill.' Before starting any project, the employee has to answer: what am I trying to achieve, what is the single most important piece of information I need, and what am I comfortable not knowing. Luna: That third question is the hardest. Most people hate admitting they don't know something. Lucas: Exactly. But it's the one that actually builds confidence. Because once you name what you're okay not knowing, you realize you can still make progress without it. And that's a muscle you have to train. Luna: So for a manager dealing with this right now — maybe a first-time manager — what's the one thing you'd say? Lucas: Don't frame it as 'stop asking questions.' Frame it as 'let's make your questions count.' Give them a container — one page, 48 hours, one question — and see what happens. Most of the time, the employee just needs permission to act on imperfect information. Luna: We talk a lot on this show about the practical side of management, and I think that's exactly why people listen. We don't run ads, we don't sell anything — it's just the two of us trying to help managers get better at the hard stuff. Lucas: Yeah, and that's only possible because of the listeners who choose to support the show. If you've ever gotten something useful from an episode, and you want to help keep it ad-free and independent, you can find us at buy me a coffee dot com slash fexingo. It's a simple way to support the work we do. Luna: And it genuinely makes a difference. Every contribution helps us keep making episodes exactly the way we want to. Lucas: Alright, back to the context threshold — because I want to talk about the follow-up. What happens once the employee starts operating within the container? Do you eventually expand it? Luna: I'd assume yes, over time, as they build trust and speed. Lucas: Exactly. The VP I mentioned — after about six weeks, he started loosening the constraint. He gave her two pages of context, then three. But always with the 48-hour decision deadline. And she started self-regulating. She'd say, 'I only need one page for this.' She internalized the threshold. Luna: That's the ideal outcome — they manage their own context intake. Lucas: Right. And that's really the goal of this whole approach: not to micromanage how much information someone consumes, but to give them a framework so they can make that judgment call themselves. It's a coaching move, not a control move. Luna: I also think it's important to acknowledge that some roles genuinely require more context. A product manager making strategic decisions probably needs more background than a customer support rep handling a ticket. Lucas: Absolutely. The threshold isn't a universal number. But the principle is universal: every role has a point of diminishing returns on information. The trick is finding it, and then building the discipline to stop just before it. Luna: So if I'm a manager listening to this, and I have an employee who always asks for more context, what's my first move tomorrow morning? Lucas: I'd sit down with them for 15 minutes. Don't accuse. Just say, 'I've noticed you like to be really thorough before you start, which I appreciate. Let's experiment with a tighter timeline so we can move faster and learn from the outcomes. For the next two weeks, every task comes with a one-page brief and a 48-hour deadline. If you need more, you get one question. Let's see how it goes.' Luna: And if they resist? Lucas: Then you dig into the fear. Ask them: what's the worst that could happen if you made a decision with less context? Usually the answer reveals a deeper anxiety — about failure, about looking bad, about getting blamed. And that's a different conversation entirely. Luna: Yeah, sometimes the context-seeking is a symptom of a trust issue, not a process issue. Lucas: Exactly. And that's why the one-question rule is so useful. It surfaces whether the employee genuinely lacks information or whether they're avoiding accountability. Because if they can't even articulate one question, they're probably stalling. Luna: Alright, so to recap: set a clear context threshold, use constraints like one page and 48 hours, and have them boil it down to one question. And if that doesn't work, look for the trust issue underneath. Lucas: That's the playbook. And if you try it, let us know how it goes. We'd love to hear what works and what doesn't. Luna: Absolutely. Thanks for listening, and we'll see you next time on Manager Mondays.