Create Compelling Project Presentation Decks

This skill builds project presentation decks that communicate status, insights, and recommendations effectively to different stakeholder audiences. The executive summary framework structures a deck as a title slide, a 3-bullet executive summary (status, achievements, decisions needed), a time-boxed agenda of at most 5 sections, front-loaded key takeaways, and an appendix for backup detail. The SCRAP narrative method structures the core story: Situation (current context), Complication (challenges/blockers), Resolution (proposed solutions), Action (specific next steps with owners), and Payoff (expected outcomes).

Content is tailored by audience: executive slides lead with a status indicator and concise timeline/budget/scope summary, culminating in a specific decision request with investment amount, delay risk, and revenue impact quantified. Technical team slides break down completed components with concrete metrics (uptime, throughput), in-progress work with completion percentage and target metrics, and explicitly flagged blockers with vendor escalation status.

Decision Required
Resource Allocation: Need 2 additional developers for 4 weeks to meet holiday launch
- Investment: $40K
- Risk of delay: 6 weeks, missing peak season
- Revenue impact: $200K opportunity cost

Data visualization best practices cover burndown charts (actual vs. planned with trend projection), a RAG (red/amber/green) status dashboard for at-a-glance health, and milestone timelines by week range. Financial tracking visualizes cost breakdown by category and burn-rate analysis against remaining budget and contingency buffer. Risk communication uses a prioritized matrix (high-impact/high-probability risks get weekly review with a named owner and mitigation; lower-priority risks get monthly review) with impact, probability, and mitigation stated explicitly per risk. Action-oriented slide design covers a structured decision-option-analysis template (pros/cons/cost/timeline per option with an explicit recommendation and rationale) and a next-steps template separating immediate actions (owner and due date), upcoming milestones, and specific support needed from the audience. Presentation flow follows a narrative arc - hook, context, journey, current state, path forward, call to action - with suggested transition phrases connecting sections. A quality assurance checklist covers content (single message per slide, sourced current data, defined acronyms, owned action items), design (consistent styling, max 6 bullets, readable charts, backup slides), and audience preparation (pre-read materials sent in advance, stakeholders briefed on sensitive topics, tested demos, contingency plans).

Use this skill when building a project status or recommendation presentation for stakeholders - structuring an executive summary and SCRAP narrative, tailoring content by audience (executive vs. technical), visualizing progress/budget/risk data, or building decision and action-item slides.

It is not the right fit for purely informational documentation with no live presentation or decision-driving purpose (a written status report may suffice), or for highly technical deep-dive sessions where a narrative deck structure would compress detail the audience actually needs.

Input: the project's current status, key decisions needed, and the audience (executive, technical, or mixed). Output: a structured presentation deck with an executive summary, a SCRAP-narrative core story, audience-tailored content, progress/budget/risk visualizations, decision-option-analysis slides, and a next-steps/action-items slide, validated against a content/design/audience-prep quality checklist.

The framework and templates are presentation-tool-agnostic, designed to be applied in whatever deck-building tool (PowerPoint, Google Slides, Keynote) the team uses.

Project managers and team leads presenting project status or recommendations to stakeholders - particularly those needing audience-tailored content, clear decision framing, and a structured narrative arc.