Skip to content

Tension-Curve Storyboard

A design artifact — instantiates Tension–Resolution Cycle Design

Lays out the intended arc — baseline, rising beats, peak, release, aftermath — as a panel-by-panel plan before anything is built or run.

A Tension-Curve Storyboard maps the intended shape of a tension–resolution cycle before any of it is built or run: panel by panel, it fixes the baseline the audience starts from, the beats by which tension should rise, where the peak and release fall, what the resolution is meant to be worth, which audience segments get which variant, and how multiple cycles are spaced over time. Its distinguishing idea is that it is a plan on paper, not a performance — it commits the arc's structure and the payoff it aims at while everything is still cheap to move, so the enacting mechanisms have a shape to enact and the rehearsal has a design to test. Nothing about it touches a real audience; that is both its value and its limit.

Example

A drama's writers' room storyboards a ten-episode season as a single tension curve before a word of script is written. They pin the baseline first — what the audience believes and expects about the central relationship at episode one — because tension is only definable against that expectation. They chart the rising beats: the secret surfaces in episode three, the betrayal in six, the confrontation held until nine. They mark what the episode-nine resolution must be worth to justify eight episodes of buildup. They note that the binge-watch audience and the weekly-broadcast audience experience the spacing completely differently, and plan a mid-season beat that lands for both. And they set this arc into the multi-season plan so its peak doesn't collide with the next. The room leaves with a map that any writer can build against and any test screening can be checked against — a shared shape, not yet a show.

How it works

  • Anchor on the baseline expectation. Tension is a departure from what the audience expects, so the storyboard starts by pinning that expectation; without it, "rising tension" has no reference point.
  • Name what the resolution must be worth. The intended payoff is set as a target the whole curve is aimed at, so beats can be judged by whether they earn it.
  • Plan variants by segment. Different audiences or agents start from different baselines and tolerances; the storyboard lays out which variant each gets rather than assuming one curve fits all.
  • Space the cycles. Where there is more than one cycle, it plans their rhythm and separation so they don't blunt or collide with each other.

Tuning parameters

  • Specification granularity — how finely the arc is fixed. A detailed board aligns a large team but over-constrains the people enacting it; a loose board leaves room but risks incoherence.
  • Number of planned beats — how many rises and partial releases the curve carries. More beats shape tension precisely but can over-engineer a simple arc.
  • Segment count — how many audience variants to plan for. More variants fit more people but multiply the design work and can dilute a signature arc.
  • Spacing horizon — how far ahead cycles are planned. A long horizon prevents collisions but bets on conditions that may change.

When it helps, and when it misleads

Its strength is that it makes the arc sharable and inspectable before commitment: a team can argue about the shape, spot a sagging middle or an unearned ending, and align on the payoff while changes are still free. It also forces the baseline to be made explicit — the single most-skipped step, since a buildup means nothing without the expectation it departs from.

Its central failure mode is the map–territory error: the storyboard is a model of how tension should land, not evidence of how it will, and a beautiful board can conceal an arc no real audience feels the way the plan assumes.[1] It is also misused as a straitjacket — treated as a contract that forbids the enacting or rehearsing mechanisms from correcting it when reality disagrees. The discipline that guards against this is to treat the storyboard as a hypothesis to be tested in rehearsal and revised, holding the baseline assumption most suspect of all.

How it implements the components

Tension-Curve Storyboard fills the archetype's up-front design and framing components:

  • baseline_expectation_model — pins the expected state the tension will be measured against.
  • intended_resolution_value — sets the payoff the whole curve is aimed at earning.
  • audience_or_agent_segmentation — plans which variant of the arc each audience or agent receives.
  • cycle_portfolio_and_spacing_plan — arranges multiple cycles' rhythm and separation over time.

It plans but does not run: it does not generate or advance the tension (tension_generator, resolution_move — Progressive Reveal Sequence), test the plan on stand-ins (rehearsal_or_sandbox — Tension-Curve Rehearsal), or read the live run (anticipation_accrual_signal — Real-Time Dropout or Distress Monitor).

Notes

A storyboard's weakest panel is almost always the baseline: it is asserted, not observed. Tension-Curve Rehearsal exists partly to check that the audience actually starts where the board assumes — if they don't, every beat measured against it is off.

References

[1] "The map is not the territory" (Alfred Korzybski) — a representation is not the thing it represents. A tension-curve storyboard is a map of an intended experience; its beats are planned reactions, not real ones, and it is only as good as the fit between the two. ↩