Using WOOP to enhance Managing Up

What each one is actually for

WOOP

WOOP takes a wish that's currently just floating around in your head, get a raise, finally push back on scope creep, and forces it through four short steps. Wish: state it in one plain sentence. Outcome: spend a minute actually picturing, in detail, what it would feel like if you got it. Obstacle: this is the step that does the real work, and it has to be internal, not 'my manager is too busy' but something like 'I always soften a direct ask into an apology before I've even finished the sentence.' Plan: turn that exact obstacle into an if-then statement, if I notice myself starting to apologize for asking, then I will finish the sentence with the actual number and stop talking, so the response is already decided before the moment arrives and doesn't have to be invented under pressure.

Managing Up

Behind most wishes about work there is a sentence you have not yet said to your manager. Managing up is the practice of treating that channel as yours to run: you find out what your manager is really measured on, you learn the form in which they take information in, and you put what they need in front of them ahead of being asked for it. Asking is part of the practice, not an exception to it. The raise, the scope you want dropped, the extra person, the deadline you need moved: each is a specific request to a specific human being who has particular pressures sitting on them that week. Managing up says the request lands better when it is timed against their calendar rather than your nerve, framed in terms of what they are accountable for rather than what you deserve, and preceded by several months in which they have never once had to chase you for anything. Which means most of the work happens well before the sentence is spoken, and the sentence itself, when it finally arrives, is usually short, plain and unhedged.

What you get out of pairing them

WOOP buys you a plan that's already been tested against the actual obstacle, which means the hard moment doesn't require you to invent a response from scratch while you're also nervous, distracted, or annoyed; the response is pre-loaded. Managing up buys you something a talented person without it often lacks: a manager who doesn't have to spend effort guessing what you're doing or translating your updates into what they actually need to know, which is frequently the real difference between someone who gets stretch assignments and someone equally capable who doesn't, not raw output.

What WOOP rests on

• Implementation intention closes intention action gap randomised trials
  Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
• Contrasting future and reality increases commitment randomised trials
  Vividly imagining a desired outcome against the present obstacle blocking it increases motivational commitment when success seems attainable.
• Obstacle identification focuses effort plausible mechanism
  Naming the specific internal obstacle between wish and outcome focuses effort on the actual barrier rather than the goal itself.

What Managing Up rests on

• Perspective taking expands frame randomised trials
  Deliberately adopting a vantage point other than one's own default view widens the range of interpretations or options available for a situation.
• Adapting to anothers style improves collaboration observational studies
  Matching communication frequency and format to a manager's stated preferences produces smoother collaboration than expecting them to adapt to yours.
• Proactive disclosure builds trust observational studies
  Volunteering relevant information and progress updates before being asked builds a manager's trust and reduces their need to monitor closely.

Where they actually meet

WOOP's obstacle step and managing up's whole premise are doing the same thing to two different targets. WOOP won't let you name an external obstacle, the traffic, your manager's busy calendar, as the reason a wish stalls; it forces you to find the internal one, the specific habit or fear actually driving your behavior. Managing up won't let you treat your own view of a situation, what you think is important, how you'd naturally prefer to communicate, as the only relevant one; it forces you to find your manager's actual priorities and working style instead. Both are refusing the same shortcut: acting from whatever view is closest at hand, rather than the one that's actually accurate.

The principle underneath both

Deliberately looking from a vantage point other than your own default one, the honest internal obstacle instead of the convenient external excuse, or your manager's actual priorities instead of your own agenda, surfaces information that view was otherwise hiding, and that surfaced information is what makes the plan you build afterward actually hold up when the moment arrives.

What that makes the real goal

The real target in both cases is acting on what's actually true about a situation, the specific internal habit standing between you and a wish, or the real misalignment between what you want to say and what your manager needs to hear, rather than on your own comfortable, self-centered default account of it.

Other practices that serve the same goal

The premortem, a technique from decision researcher Gary Klein, pursues the same objective as WOOP's obstacle step by asking a team to imagine a project has already failed and work backward to name why, surfacing real obstacles before they've had a chance to hide behind optimism, and it has observational support in organizational decision-making. Stakeholder mapping, a project-management practice of explicitly listing each person's priorities and concerns before a decision is made, pursues managing up's objective at a wider scale, across a whole group rather than one manager, with mostly practitioner and case-study support rather than controlled trials. The empty-chair technique from Gestalt therapy, where a person speaks as if they were someone else in their life, is an older, more literal route to the same perspective-taking managing up asks for, developed for personal relationships rather than the workplace.

A tradition that already does this

Dale Carnegie's How to Win Friends and Influence People, published in 1936, taught a version of managing up's core move decades before the term existed: arouse genuine interest in another person by seeing a situation from their point of view first, rather than starting from what you want them to understand about yours.

Using WOOP to Enhance Managing Up

Before a specific, high-stakes conversation with your manager, a raise, pushing back on an unrealistic deadline, run it through WOOP rather than just rehearsing talking points. Wish: state exactly what you want from this conversation, in one sentence. Outcome: picture the conversation actually going well, specifically, not just 'it goes fine.' Obstacle: this is where managing-up conversations usually go wrong, and the honest answer is rarely 'my manager will say no'; it's something like 'I always start apologizing for asking before I've said what I actually want,' or 'I let the conversation drift into justifying myself instead of stating the ask.' Plan: if I notice myself starting to apologize or over-explain, then I will pause, restate the ask in one plain sentence, and stop talking. The plan targets your own pattern, not your manager's mood, which is the only part of the conversation you actually control.

Using Managing Up to Enhance WOOP

WOOP's obstacle step is only as useful as how honestly you name the obstacle, and for work-related wishes, people often stop at something vague and self-blaming, 'I'm just bad at asking for things,' when the real obstacle is a specific mismatch with how their manager operates. Borrow managing up's discipline of taking the other person's actual perspective and use it to sharpen the obstacle itself: instead of a generic obstacle, ask specifically what your manager's known priorities and communication style predict will actually get in the way, for instance, 'my manager only responds to requests tied to this quarter's numbers, and I've been asking in terms of my own workload instead.' The resulting if-then plan then targets the real interpersonal gap, if I'm about to make this request, then I will frame it in terms of this quarter's priority first, rather than a vague personal willpower problem that was never the actual obstacle.

Rehearsing the flexible-hours conversation on Sunday night before Monday's one-on-one

You want to ask your manager for two remote days a week, and you've rehearsed this conversation in your head four times already this month without ever actually having it. You run WOOP: the wish is the two days, the outcome is pictured specifically, a Tuesday morning with no commute and a clear head for deep work. The obstacle, when you're honest about it, isn't your manager's schedule; it's that you always lead with a long list of reasons before you've said what you actually want, and by the time you get to the ask it sounds like a favor rather than a proposal. You add the managing-up piece: your manager cares most, visibly, about deliverables hitting deadline, not about hours logged. Your plan becomes specific: if I start listing personal reasons before stating the ask, then I will lead instead with 'here's how this keeps my deadlines on track,' say the ask in one sentence, and let the silence sit instead of filling it.

When this is worth reaching for

A single, consequential conversation is coming up with someone whose priorities or working style genuinely differ — a raise ask, pushing back on scope, negotiating a deadline — and the plan so far is just 'talk to them.' That vague a plan has a track record: it turns into avoidance, or into an ask that gets buried under its own justifications before the actual sentence gets said.

Where this does not apply

WOOP assumes the obstacle worth naming is genuinely yours to work with; if what's actually blocking you is a manager who is unreasonable, retaliatory, or simply won't hear certain requests no matter how well-framed, turning that into a self-focused obstacle misplaces responsibility that was never yours, and no if-then plan fixes someone else's bad faith. Managing up carries the identical limit from the other direction: it assumes a manager who is at least reasonably fair-minded and open to being understood better; adapting your communication style to someone actively acting in bad faith isn't managing up, it's absorbing a cost that should sit with them, and that situation calls for a different kind of support, not a better-planned conversation. There's also a simpler case where the combination is just overkill: a routine, low-stakes request, asking to move a recurring meeting by twenty minutes, doesn't need a wish, an outcome, an obstacle, and a plan built around it. Save the full exercise for the conversation you've already avoided more than once, not for every small ask that crosses your desk.

What the evidence does and does not support

Implementation intentions, the if-then plan at the center of WOOP, have one of the stronger evidence bases in behavior-change research, backed by a large meta-analysis of controlled trials across many goal domains. Mental contrasting, the outcome-versus-obstacle comparison, also has randomized-trial support from Oettingen's own research program. On the managing-up side, perspective-taking has broad experimental support from negotiation research showing it improves outcomes, but the specific workplace habits of matching a manager's communication style and volunteering updates rest mostly on workplace surveys and case studies rather than controlled trials. Nobody has run WOOP specifically inside a managing-up conversation and measured whether it outperforms either practice alone; WOOP's own trials cover a wide range of personal and academic goals, not this particular professional application, so treat the combination as a reasonable extension rather than a tested result.