Managing Up: How Great Operators Make Their Principal More Effective

Takeaway: Managing up is the deliberate work of understanding your principal, agreeing on how the relationship will operate, and supplying the information, judgment, and follow-through they need.

For a chief of staff, managing up isn't a tactic for gaining favor. It is part of the operating model. The role succeeds through a close working relationship with one leader, so assumptions about communication, authority, and escalation become expensive quickly.

Gabarro and Kotter's Managing Your Boss describes a relationship of mutual dependence between two fallible people. Their practical point is that both parties need to understand the other's goals, pressures, strengths, weaknesses, and working style, then build a relationship that fits those realities (HBR).

That work starts with observation, but it shouldn't remain invisible. Small adaptations can happen quietly. Expectations about decision rights, updates, disagreement, and escalation need a direct conversation.

Learn how the principal processes work

Vague labels such as "big-picture thinker" aren't enough. Watch how the principal handles specific kinds of work.

Information

Do they want the recommendation first, followed by supporting detail? Do they think by talking, or need time with a written brief? Which updates trigger useful questions, and which ones create more confusion?

Match the format to the decision. A two-line message may be right for a simple approval. A consequential tradeoff may need a short memo and time to read. The goal isn't to cater to every preference. It is to lower avoidable friction while preserving the information needed for a sound decision.

Attention

Notice where the principal's time produces unique value and where the calendar pulls them into work others can own. Protecting the executive's time means making choices about access, preparation, and delegation, not simply declining more meetings.

One HBR study of senior managers found broad concern about meeting effectiveness and the effect of meetings on other work (Perlow, Hadley & Eun). Use that as a prompt to examine the calendar, not as a reason to remove a meeting without understanding its job.

Pressure

Understand what the principal is accountable for this quarter and which relationships or decisions carry the most risk. Prioritize your work against those pressures. Ask where they want early warning and what must remain confidential.

Strengths and recurring gaps

Every leader has patterns. One may see the strategic choice quickly but leave ownership unclear. Another may hold detail so tightly that decisions stall. Your job isn't to diagnose their personality. It is to build a process that supports execution.

Watkins's work on leadership transitions emphasizes understanding the boss and adapting the working relationship early (Harvard Business Review Press). For a chief of staff, that can mean a decision recap, a tighter one-on-one agenda, or a written preview before a sensitive conversation.

Set the working agreement explicitly

Within the first few weeks, align on five things:

• Update format: what the principal wants daily, weekly, and only by exception
• Decision rights: what you can decide, recommend, or coordinate
• Escalation thresholds: which risks or amounts require immediate attention
• Meeting roles: when you facilitate, speak for the principal, or remain an adviser
• Disagreement: where and how you will raise concerns

Write the agreement down in plain language and revisit it as the role develops. "Use your judgment" is not enough if the two of you haven't discussed where that judgment begins and ends.

Bring framed decisions

An open-ended problem transfers all the thinking to the principal. A framed decision lets them evaluate your judgment.

Use four parts:

1. What changed or what needs a decision?
2. What are the viable options?
3. What do you recommend and why?
4. What happens next after the decision?

For example:

The launch owner needs a date today. Product can hold the current date by reducing scope, or move one week and keep the full release. I recommend the smaller release because the customer commitment is tied to the date. If you agree, I will confirm the revised scope with Product and Support by 3 p.m.

The principal can accept, reject, or refine the recommendation without rebuilding the problem from scratch.

Give a clear line of sight

A short, regular brief can separate three categories:

• What moved and needs no action
• What needs the principal's decision
• What is at risk and when it must be addressed

Keep the brief consistent enough that the principal learns where to look. Link to detail instead of loading the update with every fact. If the principal repeatedly asks the same follow-up question, adjust the format. That is evidence about what the brief is missing.

Surface problems early

An early warning should contain more than bad news. Name what happened, the consequence, what is known, what remains uncertain, and the next decision point.

Don't wait for a complete answer when the principal needs time to react. A short message such as "The vendor has missed the test milestone, Friday's launch is now at risk, and I will have recovery options by noon" is more useful than a polished explanation delivered after the choice has disappeared.

Disagree in a way the decision can use

If you withhold a concern to preserve the moment, the principal loses information they need. Raise disagreement privately when possible, and make it concise:

1. Restate the principal's goal.
2. Name the risk or assumption you see differently.
3. Offer an alternative or a test.
4. Confirm who decides and what you will do next.

For example:

I agree that we need a decision this week. My concern is that announcing the reorganization before the functional leads review ownership will create conflicting messages. I recommend a 24-hour review with those three leaders, then publishing one final version. It is your call, and I can execute either path.

This approach doesn't disguise disagreement as agreement. It makes the concern useful while respecting the principal's authority.

Know which adaptations need consent

You can often adjust the length of an update, prepare a cleaner agenda, or close loops more visibly without asking for a new operating agreement.

Changes to delegated authority, who receives sensitive information, how you represent the principal, or what you withhold from their attention require alignment. So do recurring workarounds created because the principal ignores a process. If the system depends on hiding how it works, the relationship needs a conversation.

Hold the boundary

Managing up should improve decisions and execution. It shouldn't protect the principal from information, turn the chief of staff into an informal enforcer, or require participation in dishonest or abusive behavior.

A micromanaging pattern may respond to clearer plans, visible milestones, and consistent follow-through. A pattern of retaliation, deception, discrimination, or abuse is different. Better formatting won't solve it. Document what is happening, use appropriate internal or professional support, and treat the pattern as information about whether the role is workable.

Frequently asked questions

Is managing up corporate politics?

It can be practiced badly, but the useful version is straightforward: understand the principal, agree on how the relationship works, and provide the information and follow-through needed for better decisions.

What if my principal resists structure?

Start with one visible point of friction, such as decisions getting lost or updates arriving too late. Propose a small experiment and agree on what would make it useful. Don't build a parallel system the principal doesn't understand.

How do I manage a hard-to-reach executive?

Agree on a reliable update channel and escalation threshold. Put the recommendation first, distinguish information from decisions, and send early warning before a risk becomes urgent.

How do I know when to push back?

Raise a concern when the principal may be missing material information, the decision creates avoidable risk, or the request conflicts with commitments or standards. Tie the concern to the goal, offer an alternative, and confirm the decision owner.

Use the free Weekly Executive Priorities Brief to create a repeatable update with decisions, risks, and next steps in one view.