I've got thirty minutes to run a meeting I haven't prepared for.

What to do when you've got thirty minutes for a meeting you haven't prepared for

Fifteenth of January, two thousand and nine. LaGuardia Airport. Three minutes after takeoff.

A flock of Canada geese crosses the climb path of US Airways Flight One Five Four Nine. Both engines lose thrust. The aircraft is at three thousand feet, climbing. The captain has ninety seconds to decide what to do with one hundred and fifty-five people.

Captain Chesley Sullenberger does not have time to prepare. He has time to execute.

He works through crew resource management protocols with First Officer Jeffrey Skiles. Sentences are short and declarative. Birds. Both engines flamed out. Turning back. Air-traffic control offers Teterboro. Sullenberger reads the speed and altitude, rejects it. Unable. We're going to be in the Hudson.

The aircraft lands on the Hudson River at three thirty-one pm. Everyone walks off.

What looks like ninety seconds of unprepared decision-making is twenty-nine years of preparation for the ninety seconds. Crew resource management is the discipline behind that — a cockpit structure that actively invites the junior to contradict the senior in real time, that strips communication down to facts and questions, that puts coordination over ego. Sullenberger had not prepared for the bird strike. He had been preparing for it.

The thing on screen is the decision. The thing beneath it is the structure that made the decision possible.

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

"I've got thirty minutes to run a meeting I haven't prepared for."

The feeling is improvising.

You have a calendar invite, fourteen people coming, no agenda you trust, and the next half-hour is all you've got. The version of you who would have prepared the room properly is the version who didn't have time.

First read whether the room is guarded or just abstract

Two choices. Both need you to do something inside the first sixty seconds. Both depend on what kind of room you've got.

When the team needs permission to be honest

Choice one: the team is guarded. New to each other, walking into a difficult subject, or both. What they need first is permission to be honest. Pair them up — five minutes — and ask each pair to name the biggest risk their part of the project is carrying. Peer-to-peer feels different from group-to-boss. Risks that wouldn't survive being said to the whole room often survive being said to one other person first. The agenda for the rest of the meeting writes itself from what the pairs bring back.

When the team needs the jargon stripped out

Choice two: the team can talk for hours in corporate abstract nouns without anyone learning anything. What they need first is the jargon stripped out. Ask each person to write down, silently, the selfish reason their department cares about the current project. Not the official reason. The actual one. Most of the time the real drivers are obvious and unspoken; the meeting that names them plainly is faster than the meeting that pretends they aren't there.

Different opening moves. Same underlying question — what does this room need before it can do useful work?

Use structures that turn the room into the agenda

Three tools. The discipline with no prep is to use structures that generate content rather than consume it. The room becomes the agenda.

The first is

Get past what you can't change to what you can start

Fifteen Per Cent Solutions.

Lipmanowicz and McCandless wrote Fifteen Per Cent Solutions into the Liberating Structures collection in two thousand and thirteen, sitting on the older organisational-development insight that almost everyone has more discretion than they admit and less than they want.

The reason the tool exists is that meetings stall on the eighty-five per cent — the part you'd need permission to change, the budget you don't control, the executive sponsor who hasn't replied. The conversation about the eighty-five per cent eats unprepared meetings.

The unique insight is the specificity of the number. Not a hundred per cent. Not fifty. Fifteen. Small enough to be plausible. Large enough to matter. What can you do right now, with the authority and resources you already have, to move things forward.

What you get is the room shifting from this is hard to here's what I can actually start.

So. How to run it.

Name. Each person names one thing they could do this week, inside their existing authority. Silent writing first. Three minutes. The room speaks after.

Round. Round the room. Each person reads what they wrote. No editing, no qualifications. The list goes on the board.

Commit. Each person picks the one they're going to start. Not the most ambitious — the most likely to land. Names go next to actions before anyone leaves the room.

You haven't made the eighty-five per cent any smaller. You've made the fifteen per cent visible.

The second is

Have the room consult each other while you stay quiet

Troika Consulting.

Same source — Lipmanowicz and McCandless, Liberating Structures — drawing on older peer-consulting and group-supervision traditions in coaching practice that go back to the nineteen-eighties.

The reason the tool exists is that most meetings produce one or two voices doing most of the work. The senior people speak. The junior people listen. The middle people negotiate the gap. Thirty minutes of that is thirty minutes of one or two perspectives, slightly dressed up.

The unique insight is the chair-turned-around discipline. Threes. One person poses a challenge — their actual challenge, the thing they don't know what to do about. The other two are the consultants. The client poses, then turns their chair around, faces away, and listens silently while the consultants discuss the problem as if the client weren't there.

The structural move is the silence. The client doesn't defend, qualify, or correct. They listen. The consultants don't perform for them; they think out loud about the problem.

What you get is thirty minutes that produces three real consulting conversations and nine people who've been heard.

So. How to run it.

Client. Bring the question. Describe your challenge in two minutes. Specific. Concrete. The thing keeping you up at night, not the thing you think will sound impressive. Then listen.

Listen. No questions back. Only what was heard. Consultants discuss for five minutes — what they notice, what questions they'd ask, what they'd try.

Advise. Speak as if the client weren't in the room. Client takes one minute to name what landed. Then roles rotate.

Each person plays all three roles in a single round — by rotation. Three rounds. Nine minutes of consulting per round. Everyone's a client, everyone's a consultant. You walk out with three perspectives on three real problems instead of fourteen perspectives on one safe one.

The third is

Ask why until the real reason for the work surfaces

Nine Whys.

Nine Whys carries the longest lineage of the three. Sakichi Toyoda at Toyota in the nineteen-thirties — the five whys, the original ask-why-until-you-find-the-cause discipline that became part of the Toyota Production System after the war and was adopted by lean manufacturing everywhere from the nineteen-eighties onwards. Lipmanowicz and McCandless extended it to nine for use in strategy and mission work.

The reason the tool exists is that teams stall when they've drifted from the strategy that named the work. The work continues. The strategy hasn't been re-examined since the work began. The meetings start producing the same outputs because no one's questioned the question.

The unique insight is the patience. Five whys gets to a cause. Nine whys gets past the comfortable stopping point. The first three or four answers are the things you've already told yourself. The next two or three are the things you've thought but not said. The last two are sometimes what the work is actually for — and sometimes what it isn't, any more.

What you get is a diagnosis of whether the work the team is doing still serves the strategy that named it. Or whether the strategy is overdue an update.

So. How to run it.

Pair. The room pairs up. One person is the asker, the other the answerer. Both will swap.

Ask. The asker asks: why is that important to you? The answerer answers. The asker asks again: why is that important? Nine times.

Persist. Past the eye-roll. Past the I've answered this already. Past the I don't know. The answer that comes after I don't know is usually the one that matters.

Nine minutes per direction. Eighteen for the whole room. What surfaces is whether the room is doing the right work — or whether the work has outlasted the reason for it.

So. For the meeting you're about to walk into.

You don't know what the team needs yet. But you have three structures that will generate the agenda from the room itself, in less time than it would take you to write one alone.

That's the toolkit. One more story before we close. The Sullenberger story we opened with is preparation working at a ninety-second time scale. The story we close with is the same move at a thirty-minute time scale.

A precedent: finding the question the position will turn on

Seventh of July, two thousand and nine. Washington DC. Hillary Clinton's office at the State Department.

Nine days earlier, Manuel Zelaya had been removed from the Honduran presidency by the Honduran military in the country's first successful coup since the Cold War. The Obama–Medvedev Moscow summit had ended yesterday. Clinton had spent the previous days on Russia. The State Department's policy on Honduras was, as of this morning, still being worked out. The question of whether Zelaya's restoration was the path back to constitutional order — or whether a negotiated political process was — had not been settled.

Zelaya was now in Washington. He had been received at the State Department. The meeting Clinton was about to walk into was scheduled for thirty minutes.

Her preparation window was closer to a single briefing call than a briefing book. The position she was being asked to take had not been agreed inside the building. What she could not afford was to perform an answer she didn't have. What she could afford was to identify the question her position would ultimately have to turn on, and to run the meeting as the search for that question's answer.

She did. The meeting ran about thirty minutes. The question — restoration first, or negotiated process first — became the working frame for State's posture in the weeks that followed.

Subsequent Honduras policy is contested — the Hard Choices paperback edition cut the original hardcover passage on the episode, an edit that itself became part of the discussion. The scenario lesson holds independent of that judgment.

When you have thirty minutes for a meeting you haven't prepared for, the useful move is rarely to take a position. It's to identify the question the position will turn on. And to run the meeting as the search for an answer to that question.

So.

Sullenberger had ninety seconds and twenty-nine years of preparation. Clinton had nine days, one briefing call, and a question she could ask honestly. Different time scales. Same move.

Both were unprepared for the specific thing in front of them. Both had something underneath the thing in front of them — a discipline, in Sullenberger's case; a question, in Clinton's — that turned the absence of preparation into the structure of the response.

The meeting you haven't prepared for isn't a meeting you have to fake your way through. It's a meeting where the discipline you already have, and the question you can ask honestly, do the work the agenda would have done if you'd had time to write one.

So. Your Next Move from this playbook.

What problem are you stuck on that you've never properly described to anyone outside your own head?

And who could you ask for thirty minutes this week?