Nancy Duarte's Sparkline

The Sparkline is a presentation structure that creates persuasive momentum by repeatedly contrasting what is (the current reality) with what could be (the better future). Coined by Nancy Duarte after analyzing the structure of great speeches — Martin Luther King Jr.'s "I Have a Dream," Steve Jobs's iPhone launch, and others — the Sparkline reveals that the most persuasive presentations are not linear lists of facts but oscillating waves of tension and resolution. Each oscillation pulls the audience closer to the speaker's "new bliss" — the call to action.

Duarte Sparkline: oscillating between what is and what could be, climaxing at the new bliss

Origin

Nancy Duarte is the founder of Duarte Inc., the design firm behind Al Gore's An Inconvenient Truth presentation. After years of building presentations at the highest level of consequence, Duarte set out to reverse-engineer what made some presentations historically transformative and others forgettable.

She analyzed dozens of famous speeches and product launches and discovered a consistent shape: the speaker repeatedly returns to "what is" (the unsatisfactory present) and contrasts it with "what could be" (the desirable future). This pattern — visualized as a wave-like sparkline — became the central insight of her 2010 book Resonate. The framework has since become a staple in TED Talk coaching, executive presentation training, and product launch design.

The Framework

The Three Acts

The Sparkline is a three-act structure:

Act 1 - Beginning:       Establish "what is"
                         The audience's current reality

Act 1 - Inciting Moment: Introduce the contrast
                         "It doesn't have to be this way"

Act 2 - Middle:          Oscillate between "what is" and "what could be"
                         Each oscillation builds tension toward the desired future

Act 3 - End:             Land at the new bliss
                         The transformed state, with call to action

The Oscillation

The signature feature is the back-and-forth between two states:

WHAT IS              vs.        WHAT COULD BE
---------                       --------------
Current reality                 Desired future
The pain                        The relief
The status quo                  The transformation
What's broken                   What's possible
The cost of inaction            The reward of action

Each oscillation in the middle deepens both poles — the present feels worse, the future feels better, the gap between them feels more urgent.

Visualizing the Sparkline

Duarte literally diagrams this as a line that rises and falls:

          ↑
         /  \    /\    /\        New Bliss
        /    \  /  \  /  \        ↗
WHAT   /      \/    \/    \      /
COULD /                    \    /
BE   /                      \  /
    /                        \/
   ╱─────────────────────────────────
WHAT IS

   Beginning   Middle (oscillating)    End

The audience travels with the speaker. Each peak of "what could be" lifts them; each valley of "what is" reminds them why change is needed. The end resolves at a higher point — the new normal.

The Components in Detail

1. The Beginning:
   - Establish common ground
   - Show that you understand the audience's reality
   - "We are here today because..."

2. The Inciting Moment:
   - The first glimpse of what could be
   - Often a story, statistic, or insight that
     opens the door to a new possibility
   - "But what if..."

3. The Middle (3-5 oscillations):
   - For each oscillation:
     a. State a current pain or limitation
     b. Contrast with the future possibility
     c. Provide evidence (data, story, demo)
   - Each cycle escalates urgency

4. The Call to Action / New Bliss:
   - The transformed future, made concrete
   - The action the audience must take
   - The reward of taking it

How to Use It

Building a Sparkline

1. Define the New Bliss.
   What's the transformation you want the audience to embrace?
   Be specific. Not "a better future" but "every customer onboarding
   in under 5 minutes."

2. Define the Current State.
   Where are they now? What's the pain, the cost, the limitation?
   Concrete and visceral.

3. Identify the Gap.
   What's blocking them from the new bliss? This is the tension
   the rest of the talk explores.

4. Generate Contrast Points (3-5).
   For each contrast:
   - What's a specific aspect of "what is" that hurts?
   - What's the corresponding "what could be" that resolves it?
   - What evidence makes the contrast vivid?

5. Sequence for Escalation.
   Easier contrasts first; the most consequential last.
   Each oscillation should feel like a step closer to the
   inevitability of the new bliss.

6. Land the Call to Action.
   What must the audience do, decide, or believe by the end?

The S.T.A.R. Moments

Duarte also coined "S.T.A.R. moments" — Something They'll Always Remember. These are the moments of high contrast where the gap between "what is" and "what could be" becomes undeniable.

Common S.T.A.R. moment formats:
- A surprising statistic, dramatically delivered
- A repeatable phrase or sound bite
- An evocative visual
- A personal story with high emotional stakes
- A live demo that makes the future tangible
- A prop or physical object that anchors the message

Steve Jobs pulling the MacBook Air from a manila envelope
is a S.T.A.R. moment. The envelope is the "what is" (the
audience's mental model of laptop size); the laptop sliding
out is the "what could be."

A great Sparkline presentation usually has one S.T.A.R. moment near the climax of the middle act.

Tech & Company Example

A staff engineer pitches a platform investment to executive leadership:

TOPIC: Why we should invest 6 engineers for 2 quarters in
       a deployment platform.

NEW BLISS:
  Every engineer can deploy a service in under 10 minutes,
  with zero involvement from SRE, with automatic rollback.

CURRENT STATE:
  Deployments take 2-4 hours. SRE is the bottleneck. We've
  had 4 production incidents in the last quarter caused by
  manual deployment errors.

GAP:
  No standardized platform. Every team has invented their
  own deploy tooling. SRE has become the deployment service
  desk.

THE SPARKLINE:

Beginning (What Is):
  "Last quarter, we deployed 247 times. Each one took an
   average of 2.5 hours of engineer time. That's 600 hours
   — three engineer-months — spent on the mechanics of
   deploying, not on shipping value."

Inciting Moment (Glimpse of What Could Be):
  "At Stripe, where I worked before, deploying took 8 minutes.
   The same engineer who wrote the code shipped it. SRE
   focused on resilience, not on being a deploy desk."

Oscillation 1:
  WHAT IS: "Today, when an engineer wants to deploy, they
            file a ticket and wait. Average wait time: 4 hours."
  WHAT COULD BE: "What if deploying was a button click? Like
                  this." [DEMO of internal prototype - S.T.A.R. moment]

Oscillation 2:
  WHAT IS: "When deploys fail, we have no automatic rollback.
            On Feb 14, this caused a 47-minute outage."
  WHAT COULD BE: "Automated canary + automatic rollback would
                  have caught Feb 14 in 90 seconds."

Oscillation 3:
  WHAT IS: "SRE has become a deployment service desk. They
            spend 60% of their week on tickets, not on
            reliability."
  WHAT COULD BE: "Free SRE to focus on reliability. Last quarter,
                  competitors who freed their SREs invested in
                  capacity planning that prevented incidents
                  worth $4M in revenue."

Oscillation 4:
  WHAT IS: "Onboarding a new engineer takes 3 weeks before
            they can deploy independently."
  WHAT COULD BE: "Self-serve platform = day-1 deploy capability.
                  3-week ramp becomes 1-day ramp."

New Bliss (Call to Action):
  "Invest 6 engineers for 2 quarters. The result: every team
   ships faster, SRE focuses on reliability, and we build the
   foundation for the next 5 years of growth.

   Without this, we will continue to lose 600 engineer-hours
   per quarter to deployment toil. With it, we get those
   hours back, plus the compound benefit of an SRE team that
   actually does SRE.

   The decision I need today: green-light the platform team
   for Q3-Q4."

This Sparkline structure is much more persuasive than the equivalent linear pitch ("Here are the problems with deployment, here's our proposal, here's the ROI"). The oscillation creates emotional momentum that a list cannot.

When It Works

High-stakes pitches where you need to shift priorities
Product launches and keynote presentations
Executive sponsorship requests
Internal change initiatives requiring buy-in
Recruiting / inspiring talks
TED-style talks aimed at shifting perspective

When It Does Not Work

Status updates — No transformation to pitch. Use direct reporting.
Technical deep-dives for peers — Audience wants depth, not narrative arc. Use Minto Pyramid or RFC structure.
Time-constrained tactical decisions — A 10-minute "what should we do about X?" doesn't need a Sparkline.
Audience already on board — If they're already convinced, you're wasting their time pretending to persuade.
Audience hostile to emotional appeal — Some technical audiences read the Sparkline as manipulation. Calibrate. Acknowledge structure if needed.

Common Failure Modes

Structural

Missing the Inciting Moment — Going straight from "what is" to "what could be" without the moment of pivot. Audience doesn't feel the shift.
Single Oscillation — Only one back-and-forth in the middle. Insufficient to build momentum.
No New Bliss — Build tension throughout, never deliver resolution. Audience leaves frustrated.
Inverted Sparkline — Starting with "what could be" and dropping to "what is." Demoralizing rather than energizing.

Content

Vague "What Is" — Generic complaints about the current state. Specifics build credibility.
Vague "What Could Be" — Hand-wavy future. Specifics make it real.
No S.T.A.R. Moment — All argument, no anchor. Nothing for the audience to remember.
Manipulation Without Substance — Beautiful Sparkline structure with no real evidence. Audience feels worked over.

Delivery

Even Tone — The structure is oscillation; the delivery should oscillate too. Vocal energy on "what could be," gravity on "what is."
Slide-Bound — Reading bullet points kills the narrative. The Sparkline lives in the speaker, not the slides.
Skipping the Pause — After the inciting moment and after the new bliss, pause. Let it land.

Cultural

Storyteller Suspicion — In some engineering cultures, narrative structure is seen as marketing fluff. Acknowledge the audience: "I'm going to give you the executive version first, then the technical detail."
Over-Performance — Sparkline on a 5-minute team standup feels theatrical. Match scale to context.

Hero's Journey (Campbell) — Single-arc narrative; the Sparkline is its multi-oscillation cousin.
Pixar Story Spine — Simpler narrative template; uses a single arc rather than oscillation.
Monroe's Motivated Sequence — Attention/Need/Satisfaction/Visualization/Action; similar but more linear.
Three-Act Structure — The general dramatic shape; Sparkline is a tighter specification.
Resonance Theory (Nancy Duarte) — Broader framework that includes audience analysis, message design, and presentation aesthetics; Sparkline is the structural component.