PlaysbyMoat8
Back to the library
The workflow guideManagement

Build a presentation through outline, research, and review stages

Turn an analytical document into a coherent deck by separating story design, missing-evidence research, assembly, and quality review.

5 implementation stepsIntermediate

How this works

Turn an analytical document into a coherent deck by separating story design, missing-evidence research, assembly, and quality review. Use this when an analytical document needs to become a coherent presentation and its argument contains evidence gaps. Separating outline, research, assembly and review prevents attractive slides from concealing unsupported claims.

Extract the document's argument, design a decision-oriented outline, research only the missing material and maintain provenance. Build slides from the reviewed outline, then inspect both factual accuracy and rendered presentation quality. Keep added evidence distinguishable from the original author's statements.

Before you start

Source document

Obtain the intended version and its supporting references.

Presentation brief

Confirm audience, purpose, length and decision sought.

Research scope

Define which evidence gaps may be investigated and permitted sources.

Prepare the inputs

document
Required

text, tables and source references

Preserve uncertainty and original claim context.

audience_goal
Required

decision, knowledge level and format

Avoid adding an unrelated sales narrative.

evidence_gaps
Required

questions requiring support

Prioritize gaps that affect the main argument.

design_constraints
Required

template, aspect ratio and delivery format

Use available presentation tooling or a structured outline fallback.

Implementation, step by step

  1. Extract the argument

    • Identify the main claim, supporting evidence and limitations.
    • Separate facts, interpretation and recommendations.

    Checkpoint: An argument map preserves the document's meaning.

  2. Design the outline

    • Create a logical sequence of questions and answers for the audience.
    • Assign one clear purpose to each slide and flag unsupported transitions.

    Checkpoint: The outline is reviewable before design.

  3. Research the gaps

    • Find primary evidence for the selected missing claims.
    • Record source, date and applicability; do not force sources to support the preferred story.

    Checkpoint: The evidence ledger resolves or preserves each gap.

  4. Assemble the deck

    • Build slides and charts from the reviewed outline and verified figures.
    • Keep source notes and uncertainty visible where needed.

    Checkpoint: A complete draft exists.

  5. Review the rendered result

    • Check claims, arithmetic, narrative continuity and visual legibility.
    • Inspect exported slides for clipping and missing content before handoff.

    Checkpoint: The deck is ready for owner review.

Decisions along the way

Research contradicts the original argument

Revise the outline or show the disagreement rather than hide it.

Evidence remains unavailable

Narrow or qualify the claim.

Requested length is too short for the evidence

Move detail to notes or an appendix without dropping material caveats.

What you will produce

researched-presentation.pptx

Presentation

A coherent deck based on reviewed evidence.

Include: argument · slides · charts · notes · limitations

presentation-evidence.csv

CSV

A traceability ledger for original and added material.

Include: slide · claim · source · applicability · status

Check the result

  • Trace every material claim to the source document or research ledger.
  • Recalculate chart values and units.
  • Inspect the actual rendered slides for readability.
  • Confirm uncertainty did not disappear during summarization.

When something goes wrong

Source document has unreadable tables

Obtain a better export before charting.

Research source is secondary or unsupported

Find primary evidence or label the limitation.

Export corrupts layout

Repair affected slides and inspect the final artifact again.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Synthetic: turn a process review into six slides.

Inputs

The document reports 20 observed handoffs and hypothesizes that a shared checklist will reduce delays; no test of the checklist exists.

Expected result

Synthetic result: present the observed handoff issues, label the checklist as a proposed intervention and include a pilot slide. Do not portray the proposal as a measured improvement.

Run a small pilot

Start small

Produce one deck from a bounded analytical document.

Record the baseline

Record review rounds and evidence gaps found.

Agree success criteria

Agree factual integrity and audience clarity before repeating the pipeline.

Stop or revise

Stop distribution if a headline claim lacks support or the exported artifact is unreadable.

Keep the scope clear

  • Research and slide design cannot convert hypotheses into verified outcomes.
  • Preparing the deck does not authorize publication or external distribution.

Check before using

The workflow is reported as a participant-built pipeline without a full implementation demonstration. Check added evidence and ensure the outline does not turn uncertainty into confident claims.

Business activities

  • Create and publish content
  • Coordinate meetings and follow-ups

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Analytical document · Intended audience and decision · Permitted research sources

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗