beginner 3 min answer Multiple choice

Four minutes into a twenty-minute architecture slot a stakeholder asks a question that belongs on slide 14 and the discussion runs for eight minutes. You now have eight minutes and fourteen slides. What do you do?

presentationtime managementdecisionaudienceasks
Pick one
Show the full answer Hide the answer

What the eight minutes are actually for

A slot is a budget for the audience's attention, not for your material. Twenty minutes holds roughly eight to ten slides that each carry a point worth saying, and at most two or three decisions. You have eight minutes, so the honest capacity is one decision.

The eight minutes already spent were not wasted. A question arriving at minute four is the cheapest signal you will get about what this room actually cares about, and it usually tells you that your slides 5 to 13 are answering a question nobody asked.

The move

Say, roughly: "We have eight minutes. The decision I need today is X. Two things make the case: A and B. Everything else is in the deck." Then stop talking and take questions. It takes 90 seconds and it gets you the one thing the meeting exists for.

The trade is explicit. You give up your sequence, which is the thing you spent two days building, and you buy the ask. The sequence was instrumental; the ask was the point. A presentation that lands every slide and never states what it needs has produced nothing, and the follow-up will be scheduled for three weeks later.

Why the other options fail

  • Speeding up. Retention falls faster than pace rises, and the questions get cut, which is where agreement is actually formed. Worse, the ask lives on the last slide, and the slot ends before it. This is the most common version of the failure and it feels like diligence.
  • Stopping and rescheduling. Reasonable when the stakeholder's question genuinely invalidates the proposal, and wrong here. You have the room now; senior calendars mean the follow-up is weeks away, and the second meeting starts by re-establishing context you have already paid for.
  • Jumping to the appendix. The appendix exists to be read, not presented. Detailed diagrams need more setup than eight minutes allows, and the room will spend the time decoding notation.
  • Sharing the deck to be read in the room. Reading in the room can work, and it works when it is designed for, as a pre-read at the start of a longer meeting. Dropped in at minute twelve it fragments the audience: half read, half wait, and nobody decides.

The structural fix

Build the deck so its order can survive being abandoned. Title each slide with the question it answers, so you can jump to one and the room follows, because a self-labelled slide lets the audience re-orient without you narrating the detour. Put the ask on slide two, not slide fifteen. Keep a visible parking list so deferring a question reads as sequencing rather than dismissal.

The decision rule for the interruption itself: answer it now only if its answer changes the decision you are asking for, and say which of the two it is. When not to compress at all: if the question revealed that your proposal rests on something the room believes is false, the ask fails anyway, so spend the eight minutes on that instead and take the reschedule.

Common weak answers

  • "Ask for more time." Occasionally granted, and it competes with everything else on the agenda, so plan as though it will not be.
  • "Never let the audience interrupt." This protects the deck and loses the room, and it makes the objection arrive after the meeting instead of inside it.