Use an If-Then Plan to Actually Manage Up

What each one is actually for

Action Planning

Implementation intentions are a planning format, not a mindset. You take a goal you already have and convert it into a sentence with three parts: a cue, a specific when or where; a trigger, what you'll notice; and an action, exactly what you'll do. When I close my laptop at five on Tuesday, I will write down tomorrow's three priorities is an implementation intention. I should plan better is not. The mechanism is that deciding the when and the what in advance removes two decisions from the actual moment, whether now is the right time and what exactly to do, both of which are exactly the decisions that get skipped when you're tired, busy, or distracted, which is most of the time the behavior was actually needed.

Managing Up

The update that never gets sent is almost never the one you decided against sending. Managing up is the practice of taking charge of what your manager knows: learning what they are actually accountable for, finding out which format they absorb information in, and getting the update, the risk or the request to them before they have to ask for it. Notice that every one of those is a recurring behavior rather than a decision made once. Nobody fails at this because they sat down, considered the matter, and concluded that their manager was better off in the dark. They fail because Friday at four was busy, and then the following Friday was busy too, and somewhere in there the practice quietly stopped being a practice without anyone deciding anything. Which means the hard part is not agreeing with the idea, and it is not knowing what to write. It is attaching each of those small acts to a specific, recurring moment in the week that is reliable enough to fire when you are tired and behind, which describes most of the weeks in which it would have mattered.

What you get out of pairing them

The frustrating part of managing up is that almost nobody disagrees it matters, and almost everybody does it inconsistently anyway, because sending the update or flagging the risk is rarely the most urgent thing on your plate at the moment it should happen, so it gets pushed to tomorrow, and tomorrow has its own more urgent thing. An if-then plan does not require you to want to manage up more, or to remember to want to. It requires you to decide once, in a calm moment, exactly when the update goes out and what it says, so that the following through does not depend on that day's motivation or memory at all. The payoff is not a better relationship with your manager in the abstract. It's specific: fewer surprises for them, fewer moments where you're explaining a problem after it's already become one.

What Action Planning 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.
• If then planning offloads self control plausible mechanism
  Linking a response to a specific situational cue shifts behavior initiation from effortful self-control to automatic cue-triggered action.

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

Implementation intentions refuse to leave a resolution floating in general territory, I should plan better becomes when I close my laptop at five, I will write tomorrow's three priorities, tied to an exact moment. Managing up does the same thing to a different kind of vague aspiration, I should have a better relationship with my manager becomes I will send this specific update, in this specific format, on this specific day, because that's what this particular person actually needs. Both practices treat a good intention that stays abstract as one that has already failed, and both fix it the same way: by pinning it to something concrete enough to actually happen.

The principle underneath both

A resolution that depends on noticing, in the moment, that now is the right time and deciding on the spot what to say, mostly loses to whatever is loudest that day, and this is just as true for a solo habit like flossing as it is for a relational one like keeping your manager informed. What actually survives a busy week is a decision made once, ahead of time, about exactly when something happens and exactly what it looks like, so the behavior fires on its cue instead of waiting to be chosen fresh every single day.

What that makes the real goal

Named plainly, the target is turning a good intention that keeps losing to daily urgency into a specific, cue-triggered action that happens regardless of how busy or distracted you are when the moment arrives, whether that intention is about your own habits or about what you owe someone else in a working relationship.

Other practices that serve the same goal

A few other tools chase the same target from different angles. Calendar-blocking a recurring slot, literally putting a fifteen-minute Friday update on your calendar as an unmovable meeting with yourself, does the cue-and-action pairing implementation intentions describe but through a scheduling tool rather than a mental sentence, and it has reasonable observational support for improving follow-through on recurring tasks. Habit stacking, attaching a new behavior to an existing routine you already do reliably, I'll write the update right after I submit my timesheet, borrows an already-strong cue instead of building a new one from scratch, with modest observational evidence behind it. A written one-pager template for status updates, used by many product and engineering teams, solves a different half of the problem: it removes the in-the-moment decision of what to include, which pairs naturally with an if-then plan that already decided when to send it.

Turning a Vague Resolution to Update Your Manager Into an If-Then Plan

Start with the honest version of what you already know you should be doing, keep my manager in the loop, and turn it into a sentence with an exact cue and an exact action: when it's four forty-five on Friday, I will send my manager a three-bullet message, what shipped, what's blocked, what's next. The specific time matters more than it looks like it should, because a vague when Friday still leaves the actual moment to be chosen in real time, and real time is exactly where the update loses to whatever meeting ran long that day. Once the plan exists as an if-then sentence rather than a standing intention, sending the update stops being a decision you make each week and becomes something that just happens on schedule, the same way a recurring calendar reminder does, except it's a decision you made once instead of a nag you get every time.

Using What You Know About Your Manager to Pick the Right Cue and Content

An if-then plan is only as good as the specific action inside it, and picking the right action for managing up requires actually imagining your manager's side of the week: what do they need to know by Monday morning to feel like nothing is quietly on fire, and how do they actually prefer to receive it. If your manager reads email first thing but rarely opens Slack until midday, the right cue is when I open my inbox Monday morning, not when I close my laptop Friday, because a perfectly good update sent into a channel they don't check on time might as well not exist. Taking the time to picture their actual week before writing the plan is what turns a generic update habit into one that lands exactly when and where it's useful to the one specific person receiving it.

The Bug Count Nobody Mentioned Until Standup

You've watched the open bug count on your module creep from two to seven over ten days, and you keep telling yourself you'll flag it once you have a clearer picture, which somehow never quite arrives. Your manager finds out at Thursday's standup, in front of the team, and asks why nobody said anything sooner. It wasn't that you didn't know. It's that flagging it never had a specific moment attached to it, so it kept losing to the actual work of trying to fix the bugs. The next sprint, you set a real if-then plan: when the open count on this module passes five on any day, I will send my manager a two-line message before I log off, count is at five, here's what I think is driving it. Three weeks later the count hits six on a Wednesday afternoon. You send the message before you've even finished the thought you were having about it, because the decision to send it was already made weeks earlier. Your manager replies with one question and a suggestion, and it's handled before Thursday, quietly, instead of in front of the team.

When this is worth reaching for

You already know, without anyone spelling it out, exactly what your manager needs from you — earlier flags, more frequent updates, a different format — and the gap isn't a wrong guess about their priorities. It's that knowing never quite turns into the habit of actually doing it on schedule, so it surfaces in a meeting instead of a message you sent first.

Where this does not apply

If the actual problem is that you genuinely don't know what your manager wants, wrong guesses about their priorities or their preferred format rather than inconsistent follow-through on a plan you already have right, no if-then sentence fixes a wrong guess, because it will faithfully execute the wrong content on schedule. That calls for a direct conversation about their preferences first. And if the relationship itself is adversarial, a manager who reacts to proactive updates with suspicion or uses them against you, the problem is trust and politics, not a missing habit, and building a more reliable habit of transparency into a relationship like that can do more harm than good.

What the evidence does and does not support

Implementation intentions have one of the stronger evidence bases in behavioral science: a large meta-analysis across dozens of randomized studies found consistent, medium-sized effects on follow-through across everything from medication adherence to exercise to voting. The specific managing-up behaviors here, reading a manager's preferred communication style, disclosing information proactively, come mostly from organizational-behavior research using surveys and observational workplace studies rather than randomized trials, which is a different and generally weaker kind of evidence, though the direction of the findings is fairly consistent across that literature. Nobody has run a study testing whether writing an explicit if-then plan specifically improves managing-up behavior compared to just intending to do it, so this page applies a well-tested general mechanism to a well-studied but differently-evidenced workplace domain, rather than reporting a result anyone has actually measured.