The closing slide is what people carry out of the room. It’s the last thing on the screen when the conversation opens up, the image that sits in short-term memory while the room transitions to their next meeting. The opening slide frames the conversation; the closing slide determines what people do with it.
The Closing Slide Drives Action
The closing slide should accomplish one of two things, depending on where the program stands:
- A clear decision for leadership to make. This applies when the readout has built the case for a specific choice and the room has the authority to make it. The closing slide presents the decision, the options, the recommendation, and the ask. The room leaves having committed to a direction.
- A view of what the team built or what happens next. For milestone readouts and final engagement presentations where the goal is to transfer ownership, the closing slide shows the program’s key outputs (i.e., the roadmap and operating model), attributed to the team that built them, with emphasis on what stays after the consulting team leaves. For mid-engagement readouts where the audience needs forward-looking clarity, the closing slide shows the next milestone, its date, and its owner.
Direction Beats “Questions?”
A slide that says “Questions?” transfers control to the room at the moment when the presenter has the most leverage to shape what people take away. The audience’s questions will be about whatever is most recent in memory, which is often a detail from the last substantive slide rather than the most important theme of the readout. It also signals that the presentation is a delivery, something the presenter brought for inspection. That frame positions the audience as reviewers rather than as decision-makers; it ends the readout passively when the moment calls for direction. The same problem applies to summary slides. A summary tells the audience what they just heard; in a live readout, the audience was in the room for the full presentation. They need direction, not a recap.
Design the Closing Slide First
The practical discipline is to design the closing slide first. The principle of content before slides applies: before the deck is built, the facilitator should answer one question: when the room walks out, what should they be thinking about? The answer is the closing slide. Everything else in the deck builds toward it. In a mid-engagement readout, the closing slide might show trajectory: where the program was at intake and where it will be at the next milestone. The team’s progress is visible, the next target is named, and the owner is identified. In a final readout, the closing slide might show capability transfer: a before-and-after view of what the organization can now do. Before the engagement, cross-functional planning happened ad hoc and data lived in disconnected systems; now there’s an operating model with defined cadences and decision rights, and the unified data platform has an owner and a governance rhythm. In a steering committee update, the closing slide might present the single most important pending decision. The options are laid out, the data has been presented earlier, and the recommendation is clear. The room leaves having made the decision or with a clear timeline for making it. Writing a readout a CFO will actually read means applying this same discipline to the entire deck. Every presentation type benefits from this approach. A workstream status update should end with the next decision or milestone; a risk review should end with the specific mitigation that needs approval. End with what the room needs to do, decide, or carry forward.
