Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / How to Manage Your Manager Without Making It Obvious
Transcript
- Lucas: There's a moment in every career where you realize your boss isn't going to figure out your best idea on their own. And if you just wait for them to ask, you'll be waiting forever. Luna: Right — so you have to nudge them toward it without making it feel like a nudge. That's the art. Lucas: Exactly. And most people either do nothing and resent their boss for not reading their mind, or they do too much — they pitch hard, they over-explain, they basically hand the boss a finished solution. And the boss's authority reflex kicks in and they push back. Luna: So what's the middle path? Because I think everyone's had that experience where you bring a fully formed plan and your manager picks it apart just because they weren't part of the process. Lucas: Yeah, that's the classic failure mode. The research on this — there's a great study by researchers at Harvard Business School on what they call 'upward influence tactics' — found that the most effective approach isn't persuasion, it's something closer to stagecraft. You don't convince your boss. You arrange the conditions so they convince themselves. Luna: That sounds almost manipulative. But I guess it depends on intent. If the idea genuinely makes the team better, then guiding your boss toward it is just good stewardship. Lucas: Exactly. And there are three specific moves that come out of that research. The first is information shaping. You don't dump all your data on the boss at once. You feed it to them in the order that leads them to the conclusion you've already reached. The second is decision pre-wiring. Before the meeting where a decision gets made, you have one-on-one conversations with the key stakeholders — including your boss — to surface objections early and adjust your framing. And the third is credit framing. You structure the idea so your boss can take partial ownership of it without feeling like you're handing them a script. Luna: Can we unpack those one at a time? Because information shaping sounds like something I've done without knowing it had a name. Lucas: Sure. So take a real example. I was talking to a product engineer at a large industrial automation company — think a firm that makes sensors and control systems for factory floors. She had a proposal to shift one testing protocol from manual to automated. It would save about 200 engineering hours per quarter. But her VP was deeply skeptical of automation because of a failed rollout two years earlier. If she'd walked in and said 'I want to automate testing,' she'd have been shut down. Luna: Because that's the first thing out of her mouth, and it triggers his failure memory. Lucas: Exactly. So instead, over three weeks, she shared data in a specific sequence. First week, she sent him a one-paragraph summary of the manual testing hours for the last two quarters — just the raw numbers, no recommendation. Second week, she forwarded an article from a peer company that had reduced defects by 30 percent after automating a similar process. Third week, she asked him for his thoughts on 'small-scale automation pilots' — his words, not hers. By the time she pitched the actual project, he'd already connected the dots himself. Luna: That's really clever. She let him arrive at the conclusion, so it felt like his idea. But that takes patience — most people want to get to the solution immediately. Lucas: It does. And that's actually the hardest part of managing up. You have to suppress your own urgency. Because your boss has a different set of constraints. They have their own boss, their own political landscape, their own risk tolerance. If you just hand them a solution, you're asking them to adopt your framework. If you guide them through the problem, they adopt their own framework — which happens to end at your solution. Luna: So decision pre-wiring — that's the behind the scenes work. I've seen people do this really poorly. They have one hallway conversation with a colleague and think that's enough. Lucas: Right. The research from the same HBS group — they looked at how successful proposals get adopted inside large organizations — found that the most effective pre-wiring involves talking to at least three people before the decision meeting: someone who will challenge the idea, someone who will champion it, and someone who's neutral but influential. You surface the objections in private, where you can adapt. By the time you're in the room, there are no surprises. Luna: And the boss feels like the decision was reached by consensus, not by a single person pushing an agenda. That's genius. Lucas: Exactly. Then credit framing is the final piece. The mistake people make is they try to get explicit credit. They say 'I came up with this.' That puts the boss in a weird position where they either have to acknowledge your ownership — which diminishes their own — or they have to push you down. Instead, you frame the idea as emerging from the team's work, with the boss as the key enabler. So the boss gets credit for creating the conditions, and you get credit for the execution. Everyone wins. Luna: That aligns with what we talked about in episode 6 about owning others' work, but from the opposite direction. Here you're voluntarily giving away credit to get the idea adopted. Lucas: It's strategic generosity. And it only works if your boss is not a pure credit hog. If they are, you have a different problem. But for most decent managers, this approach builds trust. They start coming to you for input because they know you'll make them look good. Luna: That's a really valuable framework. And honestly, if today's episode helped you think through a tricky relationship with your manager, we'd love to hear about it. But also, if you found it useful and want to support the show staying ad-free, there's a simple way. It's buy me a coffee dot com slash fexingo. No pressure, just a coffee if it was worth it. Lucas: Yeah, we keep the show independent because we think that makes the advice more honest. And listener support is what lets us do that. So thank you to anyone who chips in. Luna: Alright, let's dig into a second dimension of managing up — because I think there's a trap a lot of ambitious people fall into. They manage up so well that they become indispensable to their boss, but invisible to everyone else. Lucas: That's a real risk. The term for it is 'bottleneck status.' You become the person who knows everything about your boss's priorities, who can execute anything, who is the go-to. But you're so focused upward that you neglect lateral relationships. And when your boss gets promoted or leaves, you have no network to advocate for you. Luna: So how do you balance managing up with building visibility across the organization? Lucas: The key is to use your boss as a platform, not a shelter. Instead of being the person who executes quietly, you ask your boss to let you present findings to the broader team. Or you offer to write a summary that goes to the VP level with your name on it. You don't just do the work — you make sure the work is seen by the people who matter beyond your direct reporting line. Luna: So you're essentially asking your boss to sponsor you, not just manage you. That's a different conversation. Lucas: Exactly. And it's one you have to have explicitly. You say something like, 'I'd like to take on more visibility in the quarterly review. Could I present the results from our last project?' Most bosses will say yes because it makes them look good to have a strong team member stepping up. And if they say no, that's a red flag about whether they're invested in your growth. Luna: That's a good litmus test. Let's circle back to the engineer case. Did her automation proposal actually get approved? Lucas: It did. Four months after she started the information shaping, the VP approved a pilot for one production line. That pilot saved 180 hours in the first quarter. Then it got scaled to three lines. She got a promotion six months later — not explicitly because of that project, but because the VP started seeing her as someone who could drive change without creating resistance. Luna: So the meta-lesson is that managing up is really about managing context. You're not managing the person — you're managing the environment around them so they make the decision you want. Lucas: Exactly. And I think that's the core insight that separates effective managing up from the bad advice you see on LinkedIn — the 'always say yes' or 'mirror their body language' stuff. This is structural. It's about information flows, decision timing, and credit architecture. If you get those three things right, you can influence outcomes without ever feeling like you're playing games. Luna: And without triggering your boss's defenses. Because they still feel in control. Lucas: Right. And that's the whole point. The best managing up is invisible. Your boss thinks they're being a great leader. And you're getting your best work adopted. Everybody wins.