Run a Decision Presentation When People Have Not Read the Pre-Read
Run a Decision Presentation When People Have Not Read the Pre-Read
The meeting begins with a question that nobody in the room can answer: what exactly are we deciding?
You prepared a packet. You sent it Thursday. Two people opened it, one skimmed the executive summary, and three are now looking at you with the calm expectancy of people who assume the slides will carry them. The temptation is to start talking. The stronger move is to establish what the room needs before it can do anything resembling deciding.
A missed pre-read is not one problem. It is at least two. Someone may lack the background that would let them follow the argument. Someone else may have skipped a source the decision actually depends on. These look identical from the front of the room, and they call for opposite responses. The first is a context gap a compact orientation can close. The second is a missing load-bearing input that no amount of clear presenting can substitute for.
Restore the common decision context without replaying the whole document
The opening job is orientation, not summary. Replaying the packet slide by slide punishes the people who read it and bores the people who didn't, and neither group ends up better positioned to judge the proposal.
State four things, in this order:
- The choice in front of the room, in one sentence.
- The viable alternatives that were considered, including doing nothing if that is genuinely live.
- The consequence of each option, as concretely as you can manage.
- The evidence on which the recommended decision rests.
This gives prepared and unprepared participants the same starting question. It also forces you to notice whether the recommendation actually depends on the evidence you just named, or whether you are gesturing at a deck you happen to have built.
Notice what this opening does not do. It does not assign blame. It does not narrate the reading history of the room. It does not say "as you'll recall from page fourteen." It restores a shared floor and then stands on it.
Before you begin, confirm two things you cannot infer from the guest list. Who holds the decision authority for this choice, and which reviews or approvals are required by the organization's actual process. Attendance is not authority. A senior person in the room may be there to listen. A quiet person may be the one whose sign-off is required. If you don't know, say so and find out rather than presenting into a vacuum.
Find out which part of the missing preparation matters
Here is where most presentations go wrong. They treat every unread participant as the same kind of unprepared, and they respond with a single remedy: explain more.
A useful distinction:
A context gap means the person doesn't have the background to follow the discussion. They may not know the prior decision, the constraint, the customer segment, or the history of the failed attempt two quarters ago. A concise orientation closes this.
A missing review means the person has not examined something the decision depends on. The cost model. The legal opinion. The user research. The security assessment. No summary substitutes for their own reading, because their judgment is the thing the decision requires.
An unfinished required review is a variant of the second. Someone was supposed to weigh in, sign off, or flag concerns before the meeting, and that hasn't happened. This is not a preparation failure in the ordinary sense. It may be a process stop.
The way to find out which situation you're facing is to ask a bounded question rather than issuing a general invitation. "Before we go further, is there anything you need in order to assess this responsibly?" tends to produce vague reassurance. "Does the cost assumption in section three hold up for you, or do you need to look at the underlying model?" tends to produce information.
One caution: disagreement with the proposal is not evidence that someone failed to read it. A person who read the packet carefully and still thinks your recommendation is wrong has done exactly what you asked. Treating substantive objection as a reading problem is the fastest way to make sure you never hear another one.
Choose orientation, focused review, or deferral
Three routes. They are not ranked. The right one depends on what's actually missing.
Orientation suits a background gap. Take five minutes. Lay out the choice, alternatives, consequence, and evidence. Then proceed. Do not apologize for the orientation, and do not pad it into a lecture. The test is whether the unprepared participant can now follow the substantive discussion, not whether they feel caught up.
Focused review suits a bounded factual question that can be examined in the room. Open the relevant source. Walk through the specific calculation, the specific clause, the specific finding. This works when the question is narrow and the source is short enough to examine together. It does not work as a substitute for someone reading a fifty-page document, and pretending otherwise produces false confidence.
Deferral or narrowing suits a missing required review, absent authority, or insufficient time to examine material that genuinely needs examining. Narrowing means reducing the scope of what's being decided: approving a pilot instead of a full rollout, funding an investigation instead of a commitment, deciding the framing question now and the operational question after the review lands. Deferral means the decision waits.
Each route has limits worth naming out loud. Orientation cannot manufacture the judgment that comes from having read a source. Focused review cannot cover material that needs sustained attention. Deferral costs time and can be used as avoidance, which is why the reason should be specific and recorded.
What none of these routes should be is "push through the agenda because the meeting was scheduled." Finishing the slides is not the criterion for a sound decision. Neither is a room that has gone quiet. Quiet after a compressed presentation can mean comprehension, fatigue, deference, or unspoken objection, and you cannot tell which by looking.
Record what was decided and what remains open
The decision record is where the whole meeting either holds together or comes apart later.
If the group decided, record the decision, the option chosen, and the reason. If the group narrowed, record the narrowed question and the reason for narrowing. If the group deferred, record the deferral, the specific material or review that is needed before the decision can be made, and a confirmed owner for producing it.
Keep objections visible. An objection that was raised and not resolved belongs in the record as open, not as addressed. An objection that was raised and answered belongs in the record with the answer.
This is the point at which a room that seems to agree can later turn out not to have agreed at all. Someone nodded through a summary of a source they had not read, and three weeks later, when the thing they were supposed to have reviewed turns out to contain a problem, the record offers no protection because it never recorded what was actually examined. A record that says "approved" is not the same as a record that says what was approved, on what basis, and what remained unexamined.
A worked example: two meetings, same room, different failure
The following is invented to show the mechanism. No real meeting occurred, no organization's review requirements are depicted, and no facilitation outcome has been measured. It is a paper construction.
The setup. A five-person product group is scheduled to decide whether to replace a legacy scheduling module with a commercial vendor's system. The proposal is to sign a two-year contract. A pre-read was sent Thursday: a twelve-page packet with the choice, two alternatives (rebuild in-house, or extend the current system for a year), cost comparison, and a security assessment commissioned from an outside firm. Three people read it. Two did not. The comparison changes one condition: whether the person responsible for confirming the vendor's data-handling terms has completed that review.
Meeting one: the context gap closes.
In this version, the two who did not read the packet are missing background, not a required source. Neither of them holds a review responsibility for this decision. One is new to the group and doesn't know why the current module has become a problem. The other has been focused on a different workstream and hasn't tracked the vendor evaluation.
The presenter opens by stating the choice, the two alternatives, the consequence of each, and the evidence. Five minutes. The new member asks why extending the current system was rejected. The presenter explains the maintenance burden and names the specific failure that prompted the evaluation. The other participant asks about the cost comparison. The presenter opens the cost page and works through the numbers.
The discussion proceeds. The person responsible for the data-handling review has read the packet and the security assessment, and confirms the vendor's terms meet the requirements. The group chooses the vendor contract. The record states: the decision, the option chosen, the reason, and the fact that the data-handling review was completed and confirmed by the responsible person.
Meeting two: the load-bearing review hasn't happened.
In this version, the same two people have not read the packet, but the situation is different. The person responsible for the data-handling review has not examined the vendor's terms. This is not a background gap. It is a required input that is missing.
The presenter opens with the same orientation: choice, alternatives, consequence, evidence. It takes five minutes and lands well. The room is now caught up on background.
But the decision depends on whether the vendor's data-handling terms meet the organization's requirements, and that examination has not happened. The presenter can summarize the security assessment. The presenter cannot perform the responsible person's review. The room cannot responsibly approve the contract on the strength of a summary of a source nobody with review responsibility has examined.
The presenter names the situation. The group narrows: it approves a ninety-day pilot with the vendor, contingent on the data-handling review being completed and confirmed, with the full contract decision deferred to a meeting scheduled after the review.
The record states: the narrowed decision (pilot approval), the condition (data-handling review completed and confirmed by the named responsible person), the deferral of the full contract decision, the date of the follow-up meeting, and the owner of the review. It also records an objection raised by one participant about the pilot's cost, with the response that the cost will be reassessed at the follow-up meeting once the review is complete.
The difference. Same group, same proposal, same number of unprepared participants. Meeting one reached a final decision. Meeting two narrowed and deferred. The distinguishing factor was whether the required reviewer had examined the material, not how many people had opened the packet.
Where this leaves you
Before treating the room as ready, separate attendance, consultation and approval. Knowing who is present does not establish whose review has been completed or who can make the decision.
Two superficially similar preparation failures can require different actions. In the first fictional meeting, orientation is sufficient because the gap is background and every required review and authority is present. In the second, orientation cannot replace the data-handling review. The pilot stays contingent: it cannot begin until that review is completed and confirmed. The record must preserve the difference between a conditional choice and permission to act now.
Frequently asked questions
What is the first job when people have not read the pre-read?
Restore a common decision context, not replay the whole document. State the choice in one sentence, the viable alternatives including doing nothing if that is genuinely live, the consequence of each option, and the evidence the recommendation rests on. This gives prepared and unprepared participants the same starting question. It should not assign blame or narrate the room's reading history.
How do you distinguish a context gap from a missing review?
A context gap means someone lacks background to follow the discussion; a concise orientation can close it. A missing review means someone has not examined a source the decision depends on, such as a cost model, legal opinion, user research, or security assessment. No summary substitutes for their own reading. An unfinished required review is a variant and may be a process stop.
How should you ask what is missing?
Ask a bounded question rather than a general invitation. 'Is there anything you need?' tends to produce vague reassurance. 'Does the cost assumption in section three hold up, or do you need to look at the underlying model?' tends to produce information. Also remember that disagreement with the proposal is not evidence someone failed to read it; a careful reader may still think the recommendation is wrong.
What are the three routes when preparation is incomplete?
Orientation suits a background gap and takes only a few minutes. Focused review suits a bounded factual question that can be examined in the room from the relevant source. Deferral or narrowing suits a missing required review, absent authority, or insufficient time to examine material that genuinely needs examining. Each has limits: orientation cannot manufacture judgment from reading, focused review cannot cover sustained material, and deferral costs time and can be used as avoidance.
What should the decision record contain?
If the group decided, record the decision, the option chosen, and the reason. If it narrowed, record the narrowed question and the reason. If it deferred, record the deferral, the specific material or review needed, and a confirmed owner. Keep objections visible: an unresolved objection belongs in the record as open, not as addressed. A record that says 'approved' is not enough; it should say what was approved, on what basis, and what remained unexamined.