Managing Up and Across

Earlier parts of this book looked mostly downward — at leading the people who report to you, running your team, and turning a group and a goal into reliable outcomes. But here is an uncomfortable truth that surfaces the moment you try to get anything real done: most of the outcomes you own depend on people you don’t control. Your boss sets your priorities. A peer team owns the thing your project is blocked on. A stakeholder three floors away can quietly kill your work by withholding a decision. None of them report to you. You can’t tell any of them what to do.

This part is about that world — the sideways and upward world where you have responsibility but no authority. The good news is that this is a skill, not a personality trait, and not a dark art. Anyone at any level can practice it: a new nurse who needs the pharmacy to move faster, a warehouse shift lead who needs the day crew to hand off cleanly, a junior developer who needs a decision from a product manager. This page frames the core problem and gives you a roadmap for the rest of the part.

The core problem: responsibility without control

Draw the line honestly and it is almost always longer than your authority. You are accountable for a launch, a patient’s discharge, a delivery, a report. But the inputs to that outcome are scattered across people who don’t work for you. This gap — between what you’re on the hook for and what you can command — is the permanent condition of almost every job above the very bottom, and of plenty at the bottom too.

There are only two ways to close that gap. One is authority: someone can be told. The other is influence: someone chooses to help because it makes sense to them, because they trust you, and because working with you is easy rather than costly. Managing up and across is the deliberate practice of the second one.

              WHAT YOU CONTROL          WHAT YOU DEPEND ON
              ----------------          -------------------
              your own work             your boss's priorities
              your own time             a peer team's roadmap
              your team (if any)        a stakeholder's sign-off
                                        another department's data
                                        a vendor's timeline

   The outcomes you own almost always sit in the RIGHT column.

Managing down vs. managing up and across

It helps to name the difference plainly, because the tools are not the same.

• Managing down runs on authority. When someone reports to you, you can assign work, set priorities, and hold them to account. Authority is real and useful — but it’s also the smallest lever most people have, because most people don’t have many reports, and some have none.
• Managing up is influencing the people above you — your boss, your boss’s boss, a senior sponsor. You can’t direct them; you earn their trust and shape their decisions by being reliable and by making their job easier.
• Managing across is influencing your peers and other teams — people at your level or in other departments who owe you nothing. Here you have the least formal power of all, so credibility and goodwill do all the work.

Note what “managing up” does not mean. It is not flattery, not office politics, not angling for promotion. It means taking active responsibility for the relationship with your manager instead of passively waiting to be managed — so that you both get better outcomes.

The reason this matters more than most people expect is that authority is a shrinking share of how work gets done. Organizations have flattened, work has become more cross-functional, and almost nothing important is delivered by a single team acting alone. A hospital discharge needs the ward, pharmacy, social work, and transport to line up. A product launch needs engineering, marketing, legal, and support. In that world, the person who can only operate through the people who report to them is nearly powerless. The person who can enlist people sideways and upward gets things done. That is why the center of gravity of real-world influence has moved off the org chart’s downward arrows and onto the sideways and upward ones.

In practice — the blocked cafe manager

Priya manages a cafe. Head office controls the menu, the supplier contracts, and the point-of-sale software; the landlord controls the opening hours; the neighboring tenant controls the shared bin area. Priya is accountable for the cafe’s numbers, yet almost every lever that moves those numbers sits with someone she can’t command. The manager who succeeds here isn’t the one who complains that “my hands are tied.” It’s the one who builds a good enough relationship with the head-office buyer to get a menu tweak approved, and who makes the landlord’s life easy enough that the hours request gets a yes. Same job, same lack of authority — completely different results, entirely from managing up and across.

The common trap — waiting to be managed

The most common mistake is treating your boss as the weather: something that happens to you. You wait for direction, guess at priorities, and hope your work is what they wanted. Then you’re surprised when it wasn’t. Managing up flips this. You don’t wait to be told what matters — you find out, confirm it, and keep the relationship current. The boss who has to chase you for updates trusts you less; the one who never has to wonder where things stand trusts you more.

The throughline: remove surprises, reduce friction

If you take one idea from this entire part, take this: reliable influence comes from removing surprises and reducing friction — not from politics.

• Removing surprises means the people who depend on you are never blindsided. They know what you’re doing, where it stands, what’s at risk, and when something changes — early, not at the last minute. A boss who is never surprised by your work will give you room. A peer team that is never surprised by your dependency on them will prioritize you.
• Reducing friction means working with you is easy. Your requests are clear, your updates are short and useful, your asks come with context and options rather than raw problems. People spend a finite amount of goodwill on the colleagues who make them work hard to help; they refill it endlessly for the ones who make it simple.

Almost everything in the pages ahead is a specific application of these two moves. Notice that neither one requires charm, seniority, or maneuvering. They require care and consistency — which is exactly why anyone can practice them.

The evidence — trust is built in small, repeated moments

Researchers who study workplace trust generally find it accrues the way a bank balance does: through many small, reliable interactions rather than a few grand gestures. Each time you do what you said you’d do, flag a risk early, or deliver a clean handoff, the balance ticks up. Each surprise or dropped ball draws it down. The practical upshot is that influence isn’t won in the dramatic meeting — it’s won in the dozens of ordinary moments before it, most of which are about removing surprises and reducing friction.

Case study — the 1986 Challenger launch

On January 28, 1986, the space shuttle Challenger broke apart shortly after launch, killing all seven aboard. The subsequent Rogers Commission found that engineers at a contractor had raised concerns the night before about the O-ring seals in cold weather — but the concern did not travel clearly up the chain to the people making the launch decision. The exact chain of who knew what is debated, and the technical picture was genuinely complex, so hold the specifics loosely. The durable lesson is about managing up: a warning that stays in the room where it was first spoken protects no one. Getting a critical concern heard by the person who can act on it — early, clearly, and in a form they can use — is not optional politeness. Sometimes it is the whole job. Later pages on status updates and escalation are, in part, about never letting a Challenger-shaped concern die quietly one level below where it needed to land.

A roadmap for this part

Each page in this part answers one concrete question about the people around you. Read them in order — they build — but this table is your map.

#	Page	The question it answers
2	Managing Your Boss	What does my boss actually need from me, and how do I give it to them?
3	Mapping Your Stakeholders	Who else has a stake in my work, and how much do they care and influence?
4	Setting and Managing Expectations	How do I agree on what “done” and “on time” mean before I’m judged against them?
5	Status Updates That Actually Inform	How do I keep people current without wasting their time or hiding the truth?
6	Influence Without Authority	How do I get people who don’t report to me to help — willingly?
7	Negotiation Basics	How do I resolve competing needs so both sides can live with the result?
8	Escalation Done Right	When something’s stuck, how do I raise it up the chain without burning bridges?
900	Part Recap	What were the load-bearing ideas, in one place?

The thread

Here’s how the pages connect, so you can hold the shape in your head. You start by understanding the single most important relationship you don’t control — your boss (page 2) — then widen the lens to see everyone who has a stake in your work (page 3, stakeholders). With the map drawn, the next three pages are the day-to-day mechanics of keeping those relationships healthy: setting expectations up front (page 4) so you’re judged fairly, giving status updates that inform rather than perform (page 5), and influencing without authority (page 6) when you need someone to act. The last two pages handle the hard cases — negotiating when needs collide (page 7) and escalating when you’re genuinely stuck (page 8). Every one of them is the same two moves in a different costume: remove surprises, reduce friction.

How it connects

This part sits between leading a team and communicating clearly. The stakeholder map (page 3) reappears whenever you plan a project or a change. The expectations and status update habits (pages 4–5) are the backbone of good project communication. And influence without authority (page 6) is the engine behind almost every cross-team effort you’ll ever run — it’s the skill that lets responsibility exceed your authority without the work falling apart.

Try this

Before reading the next page, spend fifteen minutes drawing your own dependency picture. On the left, list what you fully control. On the right, list every person or team whose action or decision an outcome you own currently depends on — your boss, peer teams, a specific stakeholder, a vendor. Then circle the one relationship on the right that, if it went quiet on you for two weeks, would hurt the most. That circle is where this part will pay off first.

Reflect

1. Name an outcome you’re responsible for right now. How much of it do you actually control, and how much sits with people you don’t?
2. Do you tend to wait to be managed by your boss, or do you actively manage the relationship? What does the passive version cost you?
3. Think of a colleague others love to work with. How much of that is charm, and how much is that they remove surprises and reduce friction?
4. When was the last time someone was surprised by your work — a missed date, a change they didn’t see coming? What would have prevented it?
5. Which of the seven upcoming questions in the roadmap feels most urgent for your current situation, and why?

Show reflections

1. Most people find the controlled fraction is smaller than they assumed. The point isn’t to feel helpless — it’s to see clearly where influence, not authority, has to do the work, so you invest effort there.
2. The passive version usually costs you in redone work and lost trust: you build the wrong thing, or your boss learns to double-check you. Naming that cost is what motivates the shift to active managing up in the next page.
3. Almost always it’s less charm than you’d guess. The colleagues everyone wants on their project are the ones whose updates are clear, whose asks are easy, and who never blindside you. That’s learnable; charm mostly isn’t.
4. Trace it back to the earliest moment the surprise became foreseeable. That gap — between when you could have flagged it and when you did — is exactly the muscle the “status updates” and “expectations” pages train.
5. There’s no wrong answer, but notice whether your instinct points up (boss), sideways (peers), or at a specific stuck situation (escalation). That tells you which page to read most carefully — and probably names the relationship you circled in Try this.