Pointer Strategy

Compete & Messaging

One Pager And Slide Outline

Create concise one-pagers and slide outlines for revenue enablement and product messaging use cases. Use when asked to transform source material into structured narrative artifacts for seller training, launch enablement, stakeholder briefings, or internal rollouts. Route message strategy to value-prop-and-positioning.

One Pager And Slide Outline

Turn messy source input into a clear narrative brief and a slide-ready structure that teams can execute quickly.

Confirm Inputs First

  • If a current revenue-enablement-context exists, use it first for ICP/persona language, stage context, and proof norms.
  • Confirm audience and use context.
  • Confirm single primary objective for the artifact.
  • Confirm source materials and evidence quality.
  • Confirm delivery format preference (one-pager, slides, or both).
  • Confirm whether this is net-new narrative or a rewrite.
  • If inputs are incomplete, ask for only the minimum missing items or proceed with labeled assumptions.

Read The Right Reference

Default Workflow

  1. Define one core thesis and one target action for the audience.
  2. Distill source material into claims, evidence, and implications.
  3. Draft one-pager with a strict narrative arc: context, problem, approach, proof, decision, next actions.
  4. Select audience variant: executive brief, seller enablement, partner package, or launch update.
  5. If one-pager only is needed, run memo-only path and skip slide conversion.
  6. Convert narrative sections into slide headlines using assertion style.
  7. Build slide-level outline: one idea per slide, evidence cue, and speaker note intent.
  8. Add appendix candidates for detail that should stay off core slides.
  9. Route adjacent work: For message strategy, use value-prop-and-positioning. For final visual slide production, use the user's existing presentation tooling outside this repo.

Output Contract

  • One-page narrative brief with concise sectioning.
  • Slide outline with takeaway headline per slide.
  • Audience variant notes and emphasis guidance.
  • Evidence map linked to each core claim.
  • Suggested appendix topics and notes.
  • Assumptions list when source inputs were incomplete.

What To Avoid

  • Mixing multiple objectives into one overloaded narrative.
  • Producing topic-label slides instead of assertion headlines.
  • Reusing one audience voice across exec, seller, partner, and launch contexts.

Quality Bar

  • Narrative has one dominant argument with no competing storyline.
  • Slide headlines are assertions, not topic labels.
  • Evidence supports each major claim.
  • Output is concise enough for rapid stakeholder review.
  • Next actions are explicit and owner-ready.

Open source

This playbook is part of 37 open-source enablement workflows. Read, copy, and adapt — attribution welcome but not required.

enablementskills.md · View source on GitHub

Run this playbook with your team

Pointer's workspace lets you assign playbooks to people, track progress, and pair them with role blueprints and ramp plans.

More from Compete & Messaging

All playbooks →