Tools, Templates, and Checklists

14.2 Deck, Memo, and One-Pager Templates (Editable)

Templates are the muscle memory of governance: once they live in your repository, every new team member can step into a meeting rhythm without inventing format from scratch. The three artifacts below—a progress‑deck skeleton, a six‑page narrative memo, and an ultra‑lean one‑pager—arrive in editable PowerPoint, Word, and Google Docs formats (links in the project knowledge base). Each includes embedded guidance notes that disappear when exported to PDF, so authors see instructions while readers see only polished content.

Progress‑Deck Skeleton (PowerPoint or Google Slides, 16:9)

 The file opens with a “Read Me First” hidden slide explaining version control, accessibility checks, and color‑blind contrast rules. From there the eight‑slide core sequence is pre‑built:

1. Cover & Meeting Objective—title placeholder plus a text box that forces a single‑sentence objective (character‑count limited to 130 to prevent rambling).
2. Overall Status—traffic‑light icons locked to theme colors; data fields mapped to an Excel sheet embedded on Slide 8 for automatic refresh.
3. Key Achievements—three bullet placeholders with a “verb + metric” prompt; a note reminds authors to remove internal acronyms.
4. Upcoming Milestones—timeline smart‑art configured for drag‑and‑drop dates; today’s marker auto‑updates from system clock.
5. Risk & Issue Log—table with probability, impact, owner columns; conditional formatting flips cells to amber or red at > 0.60 risk score.
6. Dependencies & Interlocks—two‑column table and arrow icons; rows expand downward instead of widening to keep mobile‑viewer readability.
7. Resource & Budget Burn‑Down—link to an embedded chart pulling from the same Excel tab; captions pre‑filled with template language for data lineage.
8. Decisions Needed / Actions Required—checkbox icons toggle between “pending” and “closed”; footer automatically stamps deck version and confidentiality label.

Speaker‑note panes contain bullet instructions that vanish in presentation mode, ensuring authors remember alt‑text, font size, and plain‑language rules. A master slide locks the color palette and font to corporate brand to prevent creative drift.

Six‑Page Narrative Memo (Word, Google Docs, Markdown)

 The template launches with a two‑inch margin header for classification (“Confidential – Internal”). A dynamic word‑count indicator sits beside it, updating live so authors keep pages tight. The memo’s body uses cascading Heading styles to preserve accessibility:

• Title & Objective—Heading 1, 14 words maximum.
• Context & Problem Statement—Heading 2, with a sidebar call‑out box for “Why now?”
• State of the Business—Heading 2, includes a three‑column fact table (Metric | Baseline | Current).
• Proposed Solution—Heading 2, lorem‑ipsum paragraph prompts replaced by prose; template enforces active voice via a style rule that highlights passive verbs.
• Alternatives Considered—Heading 3; each alternative subsection capped at 150 words.
• Risks & Mitigations—Heading 2, embedded two‑by‑two risk matrix graphics editable in‑place.
• Call to Action—Heading 2, with a pre‑built resolution block that maps decision to owner and due date.

Footnotes auto‑number as you add sources, keeping citations legal‑ready. The file ends with a locked “Appendix Holder” page: drop long tables or technical schematics here; the main memo stays lean.

Ultra‑Lean One‑Pager (PowerPoint, Google Slides, PDF Form)

 Built on an 8.5 × 11‑inch landscape canvas so it prints cleanly or fits a laptop screen:

• Header Bar—project name, date/time stamp, document owner, next milestone; fields pull from a properties panel to avoid typos.
• RAG Strip—one‑inch ribbon across the page with traffic‑light dot; clicking the dot toggles color and auto‑opens a text box for rationale.
• Three Columns—Done, Doing, Blocked. Each has five bullet placeholders; bullets word‑wrapped at 85 characters to ensure they never spill.
• Footer—single‑line “Decision or FYI?” prompt followed by a checkbox; forces the author to specify whether action is needed. Version and file path appear in 6‑pt text for traceability.

Accessibility features include enforced 12‑pt minimum font, contrast‑checked color swatches, and alt‑text prompts on every icon. The template also embeds a “Convert to PNG” macro so teams can paste status quickly into Slack without re‑formatting.

Template Repository Organization

 All files live in a “Governance‑Templates” folder with sub‑folders for Decks, Memos, and One‑Pagers. Each template filename carries semantic metadata:

<Artifact>_<Version>_<YYYY‑MM‑DD>_<Confidentiality>.pptx
e.g., ProgressDeck_v1.3_2025‑07‑14_Internal.pptx

A “Changelog.md” file records updates—font tweaks, new macros—so teams inherit improvements instead of branching off‑brand copies.

Reader‑to‑Author Instructions Built‑In

 Every template embeds a collapsible “Instructions” layer (or comment pane) that:

• Explains mandatory vs. optional fields.
• Links to color‑contrast check or word‑count macros.
• Notes governance policy (“Do not alter confidentiality footer”).
• Flags reviewer checkpoints (e.g., “Finance controller sign‑off required on Slide 7 chart before distribution”).

When exporting to PDF, the instruction layer is automatically excluded, ensuring the final artifact shows no scaffolding.

Getting the Templates

 A short URL and QR code appear in the book’s margin notes for easy cloning into your own repository. If you need alternative formats—Keynote, LaTeX memo, or Adobe InDesign—email the PMO knowledge‑curation mailbox; conversions are available on request.

By standardizing on these editable templates, teams shift effort from “Which slide goes where?” to “What does the data actually mean?”—the only question that moves projects forward.