Latest / The Difficult Boss Podcast with Fexingo: Managing Up, Toxic Managers, and Workplace Survival / How to Manage a Boss Who Holds All the Context
Transcript
- Lucas: So, have you ever been in a meeting where your boss gives you a task, and you nod along, and then you leave thinking, wait, why are we doing this at all? Like, what's the actual point? Luna: Oh, constantly. It's like a game of telephone where you get the final message but none of the backstory. Lucas: Right. And that's what we're diving into today: managing a boss who holds all the context. Not a micromanager, not someone who takes credit, but someone who, for whatever reason, keeps the why, the history, the constraints, all locked up in their head and only hands you the what. Luna: And that can be just as paralyzing, honestly. Because you can't do good work if you're always guessing at the real goal. Lucas: Exactly. And I want to be clear, this isn't about malicious info-hoarding. I think more often than not, it's a habit left over from when they were an individual contributor. They were promoted because they were the expert, they knew all the details, and now they're a manager, but they haven't switched to sharing that context with their team. Luna: So it's almost like they don't even realize they're doing it. They think they're giving you everything you need, but they're giving you the CliffsNotes version of a five-hundred-page novel. Lucas: Exactly. And the problem is, when you don't have the context, you fill in the gaps yourself. You make assumptions. And those assumptions are often wrong, which leads to rework, missed deadlines, and that creeping feeling that you're just not performing up to par, even though the real issue is a communication gap, not a competence gap. Luna: And that can really mess with your confidence over time. I've seen people start doubting their own abilities when the real problem is they're working blind. Lucas: Yeah. And I think the first step in dealing with this is to stop trying to read your boss's mind and start becoming a context detective. Which sounds like a fun job title, but I mean it practically. You need to figure out what specific pieces of context are missing and why they're missing them. Luna: Before we go down that path, though, I have to say something. This episode is exactly why we love making this show, and honestly, it's the kind of thing that keeps us going. Lucas: And if it's helped you navigate a tricky boss or even just feel less alone in the break room, a couple of dollars a month over at buy me a coffee dot com slash fexingo genuinely makes a difference. It keeps these episodes ad-free and on the air. Luna: Yeah. No pressure, but if you've gotten something out of it, it's a small way to give back. Lucas: Alright, so back to the context detective. The first thing you want to do is map out the decisions you're making and the tasks you're working on. For each one, ask yourself: what do I not know that would change how I approach this? Luna: So, like, for a report you're writing, you might be missing the real audience. Is it for your boss's boss, or for a client? That changes everything. Lucas: Exactly. And once you have that list, you can start to see patterns. Maybe it's always the same types of context that go missing: the budget constraints, the political landscape, the historical reasons why things are the way they are. Luna: And then you can address those specific gaps instead of just vaguely asking for 'more information.' Lucas: Right. And the next step is to ask for the context in a way that doesn't sound like you're challenging your boss's intelligence. The key is to frame it around shared goals. So instead of asking 'why are we doing this?' which can sound like you're questioning the work, you say something like, 'I want to make sure I'm prioritizing correctly. What's the key outcome we're driving toward with this project?' Luna: Oh, that's good. It's not asking for justification, it's asking for alignment. Lucas: Exactly. And another powerful question is, 'Is there any context or background that would help me make better decisions here?' This is almost like a magic question, because it gives your boss an open door to share the stuff they might not think to mention. Luna: But what if they say no? Like, 'no, you have everything you need'? What then? Lucas: That's a great question, and it's where you have to be a little more strategic. If your boss insists you have everything you need, but you're still missing pieces, you can start to test your assumptions in your work. Present your plan, and explicitly state the context you're assuming. Like, 'I'm assuming this is for the board presentation, so I'm leaning into the high-level numbers. Is that right?' Luna: So you're forcing the context to the surface by putting it out there yourself. Lucas: Exactly. And sometimes that's the only way. But I also want to mention, there's a chance your boss doesn't have the context either. They might be just as in the dark as you are, and they're making it up as they go. Luna: Oh, that's a whole other level of fun. So how do you tell if it's a knowledge-holding problem or an improv problem? Lucas: One sign is if your boss gets defensive or vague when you ask for context. If they consistently can't explain the 'why' behind a decision, they might not know it themselves. Another sign is if the context they do give you changes from week to week. Luna: Right. Like, one week it's 'we're doing this to increase market share,' and the next week it's 'we're doing this to cut costs.' Lucas: Exactly. In that case, you're not just managing a difficult boss, you're managing a chaotic one. And the strategy shifts from pulling context out to creating stability yourself. You can propose a brief, one-page summary of your understanding of the project's goals and ask them to confirm or correct. That can help anchor them. Luna: That's a really practical move. And I imagine it also makes you look proactive and organized, which never hurts. Lucas: No, it definitely doesn't. Now, one more thing I want to hit on is making context capture a habit. Don't wait for big projects to try to extract context. Use your regular one-on-ones to build a picture over time. Luna: So, like, asking 'what's the most important thing for me to know about this quarter?' every time? Lucas: Exactly. And you can keep a running document where you jot down what you learn. Over a few months, you'll have a much richer understanding of your boss's priorities, their pressures, and the hidden rules of your workplace. And that's the kind of context that makes you invaluable, not just a task-taker. Luna: It's like building your own internal Wikipedia for how your organization actually works. Lucas: That's a great analogy. And it takes the mystery out of your day-to-day. You stop guessing and start knowing. Luna: I love that. So, to wrap up, if you're dealing with a context-hoarding boss, the move is to become a detective, ask targeted questions, and build your own context over time. And if your boss is just as lost as you, create your own structure to anchor the work. Lucas: Exactly. And remember, you're not trying to score points or prove your boss wrong. You're trying to get the information you need to do your best work. That's a goal you and your boss share, even if they don't always act like it. Luna: So, next time you leave a meeting feeling confused, instead of nodding along, try asking one of those questions. It might just change the whole trajectory of your project. Lucas: And your career. Alright, that's our take on managing a boss who holds all the context. We'll be back next week with another episode on navigating the tricky world of work. Until then, keep asking the right questions.