story-builder

name	story-builder
description	Use this skill when the user asks to "build a story", "pitch an idea", "structure a narrative", "get buy-in", "sell a strategy", "frame a proposal", "build a case for", "write an elevator pitch", "present to leadership", or needs to construct a compelling narrative to gain alignment, approval, or resources for a product initiative.
version	1.0.0

Story Builder

Construct a structured product narrative that drives buy-in, alignment, and action. Transforms a PM's idea, strategy, or initiative into a story with a clear structure (who's affected, what's the problem, what's the outcome, how we get there, what we need) and compelling supporting content.

When to Use

• After the PRD: The PM knows what to build — now they need to sell it
• Before a leadership review: Need to pitch for resources, approval, or strategic alignment
• To align a cross-functional team: Need the team to understand and care about the mission
• To unlock a dependency: Need another team to prioritize your request
• Strategy pitches: Proposing a new direction, product line, or way of working

Why Stories Matter for PMs

PMs tell stories about things that haven't happened yet. Unlike a retrospective narrative, a PM story needs to make a future outcome feel real, inevitable, and worth investing in. This changes the structure: the desired result comes before the action plan, because your audience needs to be bought into where you're going before they'll care about how you plan to get there.

A PM story also has two protagonists: the user and the business. Both must have a clear problem and a clear outcome. A story that only serves the customer but has no business case won't get funded. A story that only serves the business but has no customer value won't survive contact with reality.

Process

Step 1: Check Story Readiness

Before building the story, validate three prerequisites. If any fails, the story will be dead on arrival — no amount of narrative craft will save it.

Also ask: Output format: What format for the final document? (docx, md, or pdf). Default: docx.

1. Is it in the interest of both the customer and the business?

Ask the PM:

• What does the customer get out of this? (Frame from the customer's perspective, not the PM's or the team's.)
• What does the business get out of this? Think in terms of opportunity, not just internal efficiency.

Red flags:

• The PM describes benefits for their team but can't articulate the customer impact
• The PM describes a customer problem but can't connect it to a business outcome
• The story is about solving an internal annoyance rather than creating value

2. Is it aligned with company strategy and goals?

Ask the PM:

• What is the company's current strategy or product strategy?
• What are the key metrics leadership is tracking?
• How does this initiative move the company closer to those goals?

If the PM can't articulate the strategy, help them figure it out: ask what their manager or leadership team is trying to accomplish, what metrics they report on, how progress is tracked.

Red flags:

• The initiative goes against the current strategic direction
• The PM can't explain how it connects to any company goal
• It requires the company to change its strategy to make sense

3. Is it possible?

Gut-check:

• Does the PM see a path to success, even if it's hard?
• Does the technology exist or can it be built?
• Is it financially viable (not cost-prohibitive)?
• Is it within the company's brand and customer base?

If any of the three checks fails, flag it clearly. Help the PM either reframe the story to address the gap or acknowledge that this isn't the right story to tell right now.

Step 2: Evaluate Timing

Even a great story can fail if the timing is wrong. Help the PM assess their company's current context across five dimensions:

Business performance: Is leadership hitting or missing targets? Missing targets → higher scrutiny on long-term bets, need to show near-term impact. Exceeding targets → more appetite for bigger, longer-term investments.

Business maturity: Early stage → focus on product-market fit, short iterative projects. Mature stage → focus on retention, margin, diversification, new product lines.

Competitive landscape: High competition → leadership is risk-averse, favor experience improvements and closing gaps. Low competition → more space to innovate and try new things.

Financial position: Cash-constrained → break big investments into milestones with interim ROI. Cash-rich → more room for larger bets with longer time horizons.

Team trust: Low trust → leadership is risk-averse, want to see quick wins first. High trust → more openness to bold proposals and experimentation.

Help the PM read the room. If the context is unfavorable, help them either adapt the story (smaller scope, faster payoff, lower risk) or decide to wait.

Step 3: Build the Story Structure

The PM story has 5 components, in this specific order. This order is intentional — result comes before action because the audience must want the outcome before they'll evaluate the plan.

1. The Main Character (Who)

The main character should always be a person, never an abstraction like "the business" or "the organization." Human characters create connection and empathy.

Types of main characters:

• End users or customers (most common for strategy stories)
• Internal customers — employees affected by a process or tool (common for process stories)
• Channel partners
• A specific persona with a name, role, and context

Help the PM define their main character with enough specificity that the audience can picture a real human being.

2. The Problem (Why)

Two problems, always:

• The character's problem: What pain, frustration, or unmet need does the main character experience? Ground it in concrete, specific reality — not abstractions.
• The business problem: What opportunity or risk does this represent for the company? Frame as opportunity cost, revenue at risk, market position, or strategic gap.

Both problems must be real and substantiated. If the PM has interview data, User Value Map, or research, weave that evidence in.

3. The Result (Where)

What does the world look like after the story succeeds? Again, two results:

• For the character: How does their experience improve? What can they do that they couldn't before?
• For the business: What metric moves? What strategic goal is advanced? What's the expected impact (quantified where possible)?

The result must connect directly to company goals. If leadership is tracking revenue, show how this impacts revenue. If they're tracking retention, show the retention impact.

4. The Action (How)

The high-level plan for making the result happen. This is NOT the full execution plan — it's the narrative-level description of what the team will do.

Keep it concise. The audience should already be bought into the result by this point. The action just needs to feel credible and achievable, not exhaustively detailed.

Include: key phases or milestones, timeline, what resources are needed, and any critical dependencies.

5. The Ask (What you need)

Be explicit about what you need from the audience:

• Approval to proceed?
• Headcount or budget?
• Alignment on direction?
• A dependency unlocked?
• Support or advocacy from a specific leader?

Quantify the ask where possible. "We need 2 engineers for 6 weeks" is better than "we need engineering support." "We need $50K for a pilot" is better than "we need some budget."

Step 4: Identify the Story Archetype

Help the PM identify which archetype fits their story, because it clarifies the main character choice and how to frame the business opportunity:

Strategy story: Aligning people around a product direction. Main character is typically the end customer. Business opportunity framed by market opportunity (new customers, new market, new monetization).

Process story: Changing how people work. Main character is typically an internal customer (the person affected by the process). Business opportunity measured in efficiency, reduced friction, or experience improvement.

Adoption story: Getting people to use something. Main character can be end users or internal customers. Business opportunity measured in usage, engagement, retention — and the upstream metrics they drive.

Budget / cost savings story: Changing how money is spent. Main character is almost always internal. Business opportunity measured in dollars saved or reallocated.

Step 5: Develop Supporting Content

The story structure is the skeleton. Content brings it to life. Every story needs to score well on four dimensions:

1. Make it Tangible

Take the abstract and make it concrete. The audience should be able to see the future you're describing. Visual content is the most effective because people picture different things in their heads — visuals ensure everyone is imagining the same outcome.

Options by fidelity:

• Low fidelity: whiteboard sketch, before/after comparison, workflow diagram, annotated screenshot
• Medium fidelity: wireframe, mockup, journey map, competitive screenshot comparison
• High fidelity: prototype, video walkthrough, interactive demo

Match fidelity to the stage. Early discovery → low fidelity. Pre-launch → high fidelity. Don't over-invest in visuals before the direction is validated.

2. Tap into Emotion

The audience should feel something — either the pain of the current state or the delight of the future state. Human connection is what makes stories stick.

Best sources:

• Direct customer quotes from interviews (especially emotional ones — frustration, embarrassment, excitement)
• Customer journey maps showing pain and delight moments
• Video clips of real users describing their experience
• Concrete stories of individual users and their struggles

The interview debrief artifacts are gold here. If the PM has done user research, help them find the most emotionally resonant evidence.

3. Be Clear

The audience should immediately understand why this story matters to them. Don't make them work to find the connection.

Techniques:

• Connect to company strategy and goals explicitly — show the strategic priority this story serves
• Use familiar language and terms (match the vocabulary leadership and the team already use)
• Quantify the ask so it's concrete
• Call out assumptions transparently — this builds trust

4. Make it Believable

The audience needs to believe this is not just possible but probable. Your job is to reduce their perceived risk.

Evidence types:

• Market research and sizing
• Experiment outcomes or pilot results
• Product analytics showing the problem's scale
• Financial models projecting ROI
• Technical architecture proving feasibility
• Cost estimations
• Examples of other companies that succeeded with a similar approach (use carefully — show what's possible, not what you plan to copy)
• Concept testing or survey results
• A concrete next-steps action plan

Step 6: Build the Elevator Pitch

Distill the full story into a 30-second version that covers all 5 components in 3-4 sentences. This is the version the PM should be able to deliver in any meeting, hallway conversation, or Slack thread.

Format:

[Main character] is struggling with [problem], which is costing [business] [business impact]. If we [action at high level], we can [result for character] and [result for business]. To make this happen, we need [ask].

This elevator pitch is also the backbone for reactive storytelling — when the PM gets asked "What's your team working on?" in an unexpected moment.

Step 7: Simulate Audience Reaction

After building the story, simulate how the key decision-maker will receive it. This is different from the generic Q&A prep — it's personalized to a specific person.

Ask the PM: "Who is the primary decision-maker that needs to say yes? Tell me about them — their role, what they care about, their communication style, and any known concerns or biases."

Then simulate that person's reaction:

1. First impression: What's the first thing this person will think when they hear the elevator pitch? What grabs them? What makes them skeptical?

2. Top 3 objections: Based on what we know about this person's priorities and concerns, what are the three most likely pushbacks? For each:

• The objection, phrased in the decision-maker's voice
• Why they'd raise it (what underlying concern it reflects)
• How to address it within the story (not as a defensive answer, but by strengthening the narrative itself)

3. What they need to hear to say yes: What specific evidence, framing, or commitment would tip this person from "interesting" to "approved"? This might be a metric, a risk mitigation, a timeline, or connecting to something they've publicly championed.

4. What to avoid: Language, framing, or asks that would trigger a negative reaction from this specific person. (e.g., "Don't use the word 'experiment' with this VP — they interpret it as 'we don't know what we're doing'. Use 'structured validation' instead.")

After presenting the simulation, ask the PM: "Does this match your read of this person? Anything to adjust?" Then refine the story structure and Q&A based on the simulation.

If the PM has multiple key decision-makers, run a brief simulation for each (top 2 objections per person, not the full framework).

Step 8: Generate the Story Document

Produce the document in the user's chosen format (default: docx). If docx, use the docx skill. If pdf, use the pdf skill. If md, write as markdown. Use the following structure:

# Story: [Initiative Name]
Date: [date]
Story type: [strategy / process / adoption / budget]
Author: [PM name]

## Elevator Pitch
[30-second version — all 5 components in 3-4 sentences]

## Story Readiness
- Customer interest: [✓/✗] [brief justification]
- Business interest: [✓/✗] [brief justification]
- Strategic alignment: [✓/✗] [which strategy/goal it connects to]
- Feasibility: [✓/✗] [brief justification]
- Timing: [assessment of current business context]

## The Story

### Main Character
[Who is the protagonist? Make them human and specific.]
[Context: their role, situation, what their world looks like today]

### The Problem
**For [character name/type]:**
[Their pain, frustration, unmet need — grounded in evidence]

**For the business:**
[The opportunity or risk — connected to company goals, quantified where possible]

### The Result
**For [character name/type]:**
[How their experience improves — concrete and visual]

**For the business:**
[What metric moves, by how much, connected to which goal]

### The Action
[High-level plan — phases, timeline, key milestones]
[What makes this approach credible]

### The Ask
[Exactly what you need — quantified, specific, actionable]

## Supporting Content Inventory

### Tangible (making it real)
- [ ] [visual asset — prototype, mockup, diagram, before/after, etc.]

### Emotional (making them feel)
- [ ] [customer quote, journey map, video clip, user story]

### Clear (making it obvious)
- [ ] [strategy connection, familiar metrics, quantified ask]

### Believable (reducing risk)
- [ ] [data, research, experiment results, financial model, competitive examples]

## Audience Simulation
### Primary decision-maker: [name / role]
- First impression: [what grabs them, what makes them skeptical]
- Top objections:
  1. [objection in their voice] → [how the story addresses it]
  2. [objection in their voice] → [how the story addresses it]
  3. [objection in their voice] → [how the story addresses it]
- What they need to hear to say yes: [specific evidence or framing]
- What to avoid: [language or framing that would trigger a negative reaction]

## Q&A Prep
[Anticipate the 5-7 toughest questions — informed by the audience simulation above]

1. **[Question]** → [Answer]
2. **[Question]** → [Answer]
3. **[Question]** → [Answer]

Common Mistakes

1. Pitching without a story: Jumping straight to "here's what we want to build" without establishing who cares and why. Even a great product idea needs narrative context.

2. Forgetting the business half: A story that only talks about the user's problem without connecting to business impact won't get funded. Always show both sides.

3. Result after action: If you explain the plan before the audience is bought into the destination, they'll poke holes in the plan instead of aligning on the goal. Result first, plan second.

4. Abstract characters: "The user" or "the business" as main characters creates zero emotional connection. Use a specific person with a name, role, and context.

5. Opinion-based content: Leadership decisions are based on evidence, not conviction. Every claim in the story should be backed by data, research, or concrete examples — not the PM's opinion.

6. Vague asks: "We need support" means nothing. "We need 2 engineers for Q3 and $30K for a research study" is actionable.

7. Ignoring context: Pitching a moonshot when the company is missing targets and cutting costs. Read the room and adapt the story's scope and framing.

8. No preparation for questions: If the PM can't answer "Why now?", "What's the ROI?", or "What did you consider instead?", the story loses credibility instantly.

9. One-size-fits-all: The same story told the same way to leadership, the team, and dependent stakeholders will underperform for all three. Build the story once, but adapt it (see comms-plan skill).

Key Principle

The best product stories don't feel like pitches — they feel like inevitabilities. When the problem is clear, the result is compelling, and the evidence is strong, the audience arrives at "yes, obviously we should do this" before you even make the ask. Build toward that moment.