Build Rfc Presentation Deck Faster — PowerPoint Prompt Library (Develop RFC Presentatio...

Compare this approach with the default playbook most teams use to build a rfc presentation deck: a templated cover slide, a recycled agenda layout, and a closing slide imported from the last similar deck. That approach optimizes for speed but sacrifices argument integrity. This template inverts that trade-off — it accepts a slightly slower first-draft cycle in exchange for architecture decision record that survives review, trade-off vector that satisfies skeptical scrutiny, and technical-debt amortization that converts viewers into decision participants. Before: a one-line brief saying 'cover proposal.' After: a structured rfc presentation deck that turns proposal into a sequence of decision-grade slides. Structural cadence: CONTEXT → ARGUMENT → EVIDENCE → DECISION-ASK — sequenced to drive rfc narrative. For engineering leads and platform architects, the comparative math is straightforward: one slow draft beats four fast ones that all get rejected. Operators typically chain this template with "Build Tech Debt Pitch Deck" and "Create Technical Roadmap Deck" to cover the full motion. This is not a beginner template — it assumes the operator already understands their audience's decision criteria and wants structural leverage rather than starter scaffolding.

The Core Blueprint

Software Environment: PowerPoint (Enterprise AI: Copilot, ChatGPT, Claude, etc.)
Role Focus: Engineering
Execution Complexity: Advanced Logic
Taxonomy Tag: #RFC

PROMPT TEMPLATE

"Build an RFC deck for [PROPOSAL] covering motivation, design, alternatives, trade-offs, open questions, and a clear request for feedback."

4.1k RUNS

Strategic Use Cases

This presentation construct acts as a strict narrative architect. Rather than generating bloated text, it forces the AI to output discrete slide structures specifically tailored for Engineering:

Replacing ad-hoc high-stakes rfc presentation deck cycle decks with a architecture decision record-disciplined template across engineering leads and platform architects.

Equipping engineering leads and platform architects with a reusable rfc presentation deck when recurring rfc narrative meetings cycles compress.

Execution Workflow

Translate this raw prompt into a functional pitch deck using this sequence:

1
Stage your supporting research, data exports, and prior decks in a single working folder before invoking the prompt.
2
Activate your PowerPoint AI assistant directly inside the deck file you intend to ship — not a scratch file.
3
At this point, sanity-check that the deck still reads as a 'RFC Presentation Deck' and has not drifted into an adjacent template's shape.
4
Inject the template, substituting placeholders with concrete inputs (for example, the bracketed primary variable with proposal).
5
Critique the AI-generated outline against a architecture decision record checklist; reject any slide that fails the rfc narrative test.
6
Iterate on the body slides individually, asking the AI to expand each one with audience-grade detail and technical-debt amortization discipline.
7
Finalize speaker notes for the high-stakes slides so the verbal layer reinforces — not duplicates — the visual layer.

Advanced Optimization

Elevate the rhetorical quality of your deck by appending these presentation-specific constraints:

Slide Economy Constraint
"...Cap any single slide at 7 visual elements. Beyond that, ask the AI to split the slide into two — never compress further."
Decision Slide Mandate
"...The final body slide must propose a single, named decision with a named owner and a named timeline. Tie this back to your team's trade-off vector standard."
Enforcing Headline Discipline
"...Every slide title must be a complete claim, not a topic label. Reject any title under 6 words or any that ends in a noun phrase without a verb. This is non-negotiable for engineering leads operating at rfc narrative scale."
Audience Vector Lock
"...Open the prompt with a one-line audience description. The AI is forbidden from drifting into a different audience's vocabulary."
Evidence Anchoring
"...Each claim slide must cite a specific source, dashboard, or interview. Vague evidence is rejected and regenerated. Tie this back to your team's reliability posture standard."