Build the story before the slides
Create a source-to-story outline before constructing a customer presentation.
Customer-centered presentation story spine
Finish with an artifact another professional can review, challenge, and act on.
When to use this
Create a source-to-story outline before constructing a customer presentation. Use it when the decision matters enough that source authority, uncertainty, and human review must stay visible.
Match the depth to the consequence
Quick
Produce the minimum useful customer-centered presentation story spine from the controlling sources and flag gaps.
Working
Compare sources, classify evidence, produce the customer-centered presentation story spine, and run the task-specific checks.
Thorough
Add a countercase, conflict review, stakeholder challenge, and explicit validation plan before action.
Bring only what the task needs
- The decision this work must support
- Current, approved source material
- Known constraints and open questions
Boundary: Approved customer information in an employer-approved environment; otherwise use public or fictional material.
Do not add credentials, unnecessary personal information, private security details, unapproved pricing, contracts, or customer material.
Work sequence
- State the decision the customer-centered presentation story spine must support.
- Select the controlling sources and record their date, owner, and authority.
- Separate customer evidence from seller interpretation before asking AI to synthesize.
- Build the customer-centered presentation story spine and label Known, Inferred, Assumed, and Unknown.
- Challenge the result with contrary evidence and complete the verification checks.
Build the story before the slides
GOAL Develop a presentation narrative tied to the audience, decision, and approved evidence. CONTEXT The account, audience, decision, and current sales stage are [CONTEXT]. CONTROLLING SOURCES Use only [APPROVED SOURCES]. Identify the source behind every material fact. TASK State one governing message, then organize customer context, change, meaning, evidence, options, tradeoffs, and the next decision. Map every claim to a source. CONSTRAINTS Do not invent customer intent, authority, dates, budgets, pricing, commitments, product capabilities, legal conclusions, or missing facts. REQUIRED OUTPUT Customer-centered presentation story spine UNCERTAINTY BEHAVIOR Separate Known, Inferred, Assumed, and Unknown. Show conflicts instead of resolving them without evidence. Turn important unknowns into questions. VERIFICATION REQUEST List the claims, calculations, names, dates, owners, commitments, and source conflicts a human must verify before acting. Construct the strongest evidence-based case against the proposed conclusion.
Northstar example
Northstar’s story begins with cross-environment operating friction and ends with a vendor-neutral assessment, not a predetermined single-platform claim.
Task-specific checks
Why this works
The sequence starts with the decision and source authority, so fluent output cannot quietly replace evidence. The countercase turns uncertainty into focused customer questions.
A weak AI request
“Create a polished customer-centered presentation story spine and make it persuasive.”
This request has no controlling sources, evidence boundary, uncertainty behavior, or verification step. It rewards confident prose instead of dependable work.
Practice safely
Find and repair the unsupported claim in the Northstar customer presentation.
Open Northstar exercises