Someone senior is going to try to hijack the next meeting.

What to do when someone senior is going to hijack your meeting

January two thousand and six. Bob Iger has been chief executive of the Walt Disney Company for less than four months.

Disney's animation pipeline is in trouble. The previous decade of theatrical releases has thinned. The films audiences want are coming from one place — Pixar — and the deal that lets Disney distribute them runs out after one more title. Steve Jobs, who owns Pixar, has publicly walked away. Iger's predecessor and Jobs had a personal relationship that broke in the press. The industry consensus is that Disney has lost Pixar.

The meeting Iger walks into in Emeryville is, on the public reading, the meeting where Disney either renews a deal that has already been refused, or watches the next Toy Story go to a competitor.

The meeting Iger holds is a different meeting.

He proposes that Disney buy Pixar outright. Not a renewed distribution deal — the whole company. Jobs becomes Disney's largest individual shareholder. John Lasseter and Ed Catmull take charge of Disney Animation. The terms aren't a renegotiation; they are a structural reshaping of who is the creative leadership for both organisations.

The meeting Jobs had prepared for — the one where he was going to tell Disney no — never happens. The room is set up for a different conversation entirely. Jobs accepts.

Iger does it again three years later with Ike Perlmutter at Marvel, walking in alone, having read every Marvel Knights title Perlmutter built the modern company around. He does it again three years after that with George Lucas, opening with a commitment that the creative direction of Star Wars stays with Lucasfilm rather than being absorbed into Disney's machinery.

Three meetings. Three counter-parties whose seniority and history could have hijacked the room. None did. The meeting wasn't where Iger had let the fight be located.

So let's go to the office and work through it.

"Someone senior is going to try to hijack the next meeting."

The feeling is outgunned.

You know who it'll be. You know roughly what they'll say. The agenda is set. The decisions in the room are the ones the project depends on. And one person is going to walk in with enough seniority that neither the chair nor anyone else is going to interrupt them.

First decide whether to contain them or neutralise them

Two choices. They look identical when you walk in. They need different first moves.

When the pushback is a foregone conclusion

Choice one: containment. They're going to push back no matter what you do, and the only question is how much of the meeting they eat. Assign them the formal role of challenger at the top of the agenda. Not as a trap. As a job title. Two things happen at once. The room hears that objections are welcome, which makes any single objection less powerful. And the senior person now has a structure they have to stay inside. Disruption will still come; it'll come when you're ready for it.

When they shift position to whoever spoke last

Choice two: neutralisation. They're the kind of person who changes their position to whoever they spoke to last. Open the meeting by asking them to remind the room why they originally approved the project. A public restatement of an earlier commitment is hard to contradict five minutes later — the contradiction is visible to everyone. You're not stopping them changing their mind. You're making the cost of changing it slightly higher than it was going to be.

Containment, or neutralisation. Same room, two different first sentences.

Win the meeting before it starts

Three tools. They're all about doing the relationship work before the meeting, not during it.

The first is

Find who actually decides, not who the chart says

Stakeholder Mapping.

Aubrey Mendelow wrote up Stakeholder Mapping in a nineteen ninety-one conference paper at Kent State, sitting on R. Edward Freeman's stakeholder theory from nineteen eighty-four. The form most managers know — a two-by-two grid, power against interest — is Mendelow's version.

The reason the tool exists is that project teams write down the formal sponsors, the formal reviewers, the formal stakeholders — and routinely miss the informal ones who actually decide whether the project survives.

The unique insight is that the map is a discipline of honesty about who actually has power. The senior person who keeps hijacking your meetings is almost always already on this map. They're sitting in a position the team has been working without — high power, high interest, no one managing the relationship — and the hijack is the visible symptom of that absent management.

What you get is a picture of who you actually need on side. Not who the org chart says is in charge. Who actually decides.

So. How to run it.

List. Everyone who can affect or be affected by the project, formal and informal. Write the names down. Don't filter — you can't draw the map if you've already excluded the awkward ones.

Plot. Two axes. Power, high to low. Interest, high to low. Place each name. Argue inside the team about placements. The argument is the diagnostic.

Gap. Look at the high-power, high-interest quadrant. For each name there, when did you last speak to them alone, about this project? If the answer for any of them is I haven't, that's where the hijack is going to come from.

The map isn't a deliverable. It's a working document for the project team — kept current, revisited every couple of weeks, the names move.

The second is

Pre-brief the powerful so there's nothing to ambush

Communication Planning.

PMI codified the modern shape of Communication Planning through its standards work in the early two-thousands, sitting on much older programme-management practice — defence, construction, large-systems engineering — places that have been managing senior stakeholders for decades and had to write down what worked. The lineage is shared rather than singular.

The reason the tool exists is to fix what looks like a personality problem.

The unique insight is that the senior person hijacking your meeting is often the senior person who is finding out about the project in your meeting. The meeting is the first time they're being asked to react. From their position, that isn't a hijack — it's an ambush they're defending against.

What you get is a briefing pattern that moves the difficult conversation out of the meeting and into a twenty-minute one-on-one two days before. The hijack stops looking like a hijack because there is nothing left to hijack.

So. How to run it.

Audience. Who needs to know what, when, in what form? Map it from the stakeholder map. Different people get different briefings — high-interest names get detail; high-power-low-interest names get a one-paragraph note that respects their time.

Pre-brief. The high-power, high-interest names from the stakeholder map get a private briefing. Twenty minutes is usually enough. Two days before the meeting works — long enough that they've absorbed it, short enough that nothing has moved underneath. Not for sign-off. For forewarning. So they walk into the meeting already knowing what's going to be said.

Cadence. Make it standing. Same names, same rhythm. Not just before the difficult meeting — before every material meeting where they have a stake. The pre-brief works because it's expected, not because it's a special intervention.

The twenty-minute pre-brief is, structurally, the difference between a meeting that goes well and the one you're worrying about.

The third is

Three real-time moves to buy the room time

Facilitation Techniques.

Facilitation Techniques have a long lineage. Kurt Lewin's group dynamics work in the nineteen-forties; the T-groups that grew out of it; the National Training Laboratories. The named moves managers use today were codified by the International Association of Facilitators in the nineteen-nineties.

The reason this tool exists is for when the relationship work hasn't held. Despite the stakeholder map, despite the pre-brief, the senior person walks in and tries to take the room. You need moves that work in real time, that don't require seniority of your own, and that don't escalate the fight.

The unique insight is that the named facilitation moves don't stop the hijack. They buy time. The aim isn't to win the exchange. The aim is to keep the meeting on its agenda for long enough that the rest of the room can do its work.

What you get is a small repertoire — three moves, repeatable — that fits any meeting and doesn't depend on you being the most senior person in the room.

So. How to run it.

Park. "That's interesting. Let's park it on the wall and come back to it." Names the objection. Doesn't argue with it. Buys the meeting thirty seconds and the next agenda item.

Bridge. "And specifically on the question we're on, what does the team need to decide?" Returns the room to its agenda without saying no to the objection. The objection still exists; it isn't what the room is doing right now.

Question. When the senior person makes a flat claim — this won't work — ask them what would have to be true for the claim to be wrong. Forces them off assertion onto reasoning. A reasoning conversation is a different conversation from an assertion conversation; you'll usually find the room has more to contribute to the first.

Three moves. None of them stops the hijack. All of them buy the meeting thirty more seconds, which is usually enough.

That's the toolkit. One more story before we close.

The Iger story we opened with is about reshaping what the meeting is before walking in. The story we close with is one move further — the recognition that the right answer is sometimes not to walk in at all.

A precedent: refusing the room and making the refusal the move

February two thousand and seventeen. Susan Fowler has just published Reflecting On One Very, Very Strange Year At Uber — the post that begins the unraveling of Travis Kalanick's Uber.

Two weeks later, Uber offers Black Girls Code a hundred and twenty-five thousand dollars.

Black Girls Code is the organisation Kimberly Bryant founded in two thousand and eleven, in her San Francisco apartment, as an evening programme teaching young Black girls to code. By two thousand and seventeen it is one of the visible institutions in the conversation about who tech is built by and for. The donation, structured as a joint announcement, is positioned as Uber's institutional response to Fowler's account — a public rejoinder, with Black Girls Code as the centrepiece.

Bryant declines. Publicly. On Black Girls Code's own channels. She names the offer for what it is — reputation laundering. She explains the reasoning: accepting the money would have implicated the organisation in Uber's narrative recovery. The post goes up; the press cover the rejection rather than the donation; and within twenty-four hours independent donors have crowdfunded the equivalent sum from people who read the rejection and wanted to replace the money.

The meeting Bryant was being asked to walk into was not literal. It was a press announcement. But it was a meeting in every editorial sense — a room where her presence would have been used. Her move was to refuse the room, and to make the refusal the thing the room remembered.

So.

Iger reshaped the meeting before walking in. Bryant refused to walk in and made the refusal the move. Both treat the meeting itself as a piece of equipment — something someone built, with assumptions inside it, that you can redesign before you arrive or decline before you start.

The meeting is rarely a force of nature. It's a room someone designed. When the design favours a hijack, the move is on the design, not on the dialogue inside it.

The three tools — Stakeholder Mapping, Communication Planning, Facilitation Techniques — are all moves on the design. The relationship work that happens before the meeting is the meeting that will happen later.

So. Your Next Move from this playbook.

Who has informal veto power over your project that isn't on any org chart — and when did you last spend any time managing that relationship?