GuidesOct 8, 20262 min readPageworks editorial

Consulting Presentation Structure: An Answer-First Example

A consulting-style deck needs an argument a client can inspect. Start with the recommendation, give the reasons, and show the evidence and limitations behind each reason. This guide offers an editorial structure; it is not a proprietary McKinsey template or a claim that AI automatically produces a validated consulting analysis.

Decision guide
Question	Practical answer
Recommendation	Pilot the new process in one region
Reason 1	A measurable service gap exists
Reason 2	The pilot can test the proposed mechanism
Reason 3	Exposure is limited by an agreed stopping rule
Decision	Approve scope, owner and evaluation date

Suppose response time is 8 days against a 5-day target. The gap is 3 days, or 60% above target. That supports a claim about performance, not a claim about its cause. If the proposed fix is additional staffing, show why staffing is the suspected constraint and what observation would disprove it. Otherwise the recommendation outruns the evidence.

Write slide titles as claims: “Response time exceeds target by three days” is inspectable; “Operational excellence” is not. Under each title, use one exhibit with the period, unit and source. Keep customer demand, process capacity and staffing explanations separate where the data allow it; do not claim categories are exhaustive simply because they fit three columns.

Build the outline before asking Pageworks for slides. Review every generated action title against the approved evidence. A source list makes the argument auditable; it does not turn an assumption into a finding.

Put the workflow into practice

Start with your approved source in Pageworks. Review the outline, generate the deck and refine the result. Pro supports up to 50 slides and editable PowerPoint export; choose the plan that matches your handoff.