Story prototypes let you test how an audience experiences a narrative before you spend time building final scripts, interfaces, sets, or software. With paper, cards, and a few clear rules, you can explore structure, choice, pacing, and character information in a single afternoon.
What a paper story prototype is
A paper story prototype is a physical model of a narrative experience. It does not need polished dialogue, artwork, or a complete plot. Instead, it represents the decisions, information, events, and consequences that shape the audience’s journey.
Depending on your project, the prototype might represent:
- An interactive fiction game
- A branching film or web experience
- A transmedia campaign
- A participatory theatre piece
- A tabletop narrative
- A documentary with multiple viewing paths
- A story-driven educational experience
The goal is not to prove that the final project will look beautiful. The goal is to discover whether the experience makes sense, creates meaningful choices, and moves people through the story in the intended way.
A useful prototype answers practical questions such as:
- Do participants understand what they can do?
- Are the choices genuinely different, or merely different wordings of the same action?
- Does each decision produce an understandable consequence?
- Is the audience receiving information too early or too late?
- Can the story continue if a participant ignores the expected path?
- Where do people become confused, bored, or overburdened by information?
Define the experience before making cards
Start with a one-page description of the experience. Keep it short enough to read aloud in under a minute.
Write down:
- Audience: Who is experiencing the story?
- Role: Who do they play or represent?
- Objective: What are they trying to accomplish?
- Core action: What do they repeatedly do—choose, investigate, negotiate, arrange, ask, explore, or interpret?
- Story promise: What kind of experience should the project deliver?
- Ending condition: How does the experience conclude?
For example:
The participant plays a journalist investigating a disappearing coastal town. They gather testimony, choose whom to trust, and publish a final account. The experience should create tension between factual accuracy and protecting vulnerable residents.
This description prevents the prototype from becoming a collection of disconnected scenes. It also gives you a standard for judging decisions. If a card does not support the audience’s role, objective, or core action, remove it or revise it.
Next, choose a small slice of the story. Do not prototype the entire project immediately. Select an opening sequence, one major decision, or a complete five- to fifteen-minute experience. A small slice is easier to explain and produces clearer feedback.
Gather simple materials
Use materials that are quick to change. The prototype should feel temporary.
Recommended supplies include:
- Index cards or cut-up sheets of paper
- Sticky notes in several colors
- Pens and thick markers
- A large sheet of paper or a whiteboard
- Paper clips or small tokens
- Dice, coins, or a simple spinner
- Envelopes for hidden information
- A timer
- A notebook for observations
- Removable tape
Avoid spending time on visual design at this stage. Use large, readable handwriting and consistent labels. If you need an image, draw a rough symbol. If you need a sound cue, write “storm begins” on a card. If you need a video, describe its content in one sentence.
A practical color system can make the prototype easier to operate:
- Yellow cards: locations or scenes
- Blue cards: characters or sources
- Red cards: problems, conflicts, or hazards
- Green cards: actions or resources
- White cards: endings or outcome states
The colors do not matter by themselves. Consistency does. Write a small legend on the table so participants know what the colors mean.
Build the card system
Create cards for the parts of the story that may change, move, or be selected. Begin with five categories.
Scene cards
A scene card identifies where the participant is and what situation is active. Include only the information needed to make a decision.
A scene card might contain:
- Scene name
- Immediate situation
- Available actions
- Information revealed here
- Conditions for leaving
Example:
Closed Ferry Terminal
The last ferry has left, but a maintenance worker is still inside. You can search the office, question the worker, or follow footprints toward the docks.
Character cards
Character cards describe what a person wants, knows, hides, and can offer. Separate public information from information that should be revealed later.
Useful fields include:
- Name and role
- Public goal
- Private motivation
- Relevant knowledge
- Trust level
- Possible response to pressure
Do not write an entire biography. The card should help the facilitator portray the character and help the designer test the interaction.
Choice cards
Choice cards represent actions available to the participant. A useful choice should alter information, relationships, resources, timing, or the route through the story.
Avoid choices such as “be brave” and “be cautious” unless the prototype defines exactly how each changes the experience. Replace vague choices with observable actions:
- Publish the anonymous testimony
- Hide the evidence from the mayor
- Return to question the witness
- Trade the recording for safe passage
Event cards
Event cards introduce changes that are not fully controlled by the participant. They may reveal information, create pressure, or force a new decision.
Examples include:
- A storm cuts off the road.
- A witness changes their story.
- A recording is partially damaged.
- Another character discovers what the participant has done.
Use event cards carefully. Too many random events can make the story feel arbitrary. Each event should test a theme, complicate an objective, or expose a consequence.
Outcome cards
Outcome cards describe the state reached after an important decision. They do not need to be final endings. They can represent temporary states such as “the witness trusts you,” “the town is alerted,” or “the evidence is incomplete.”
Write outcomes in concrete terms. A participant should be able to see what changed and what options are now available.
Map the story on the table
Before running the prototype, lay out the main route using scene cards. Put the opening card on the left and possible endings on the right. Place decision cards between them.
A simple structure might look like this:
Opening → Investigation → Trust decision → Evidence state → Final account
↘ Conflict route ↗Then add cards for information and consequences. Use arrows, paper clips, or strings to show connections. If a path cannot be explained in one sentence, simplify it.
A compact planning table can help you check whether each choice has a useful function:
| Story element | Participant action | Immediate result | Longer consequence |
|---|---|---|---|
| Witness interview | Ask about the missing boat | Learn two conflicting facts | Witness may refuse later questions |
| Damaged recording | Repair or publish it | Gain evidence or create doubt | Changes credibility of final account |
| Mayor’s offer | Accept protection or refuse | Gain access or remain independent | Determines available ending |
| Storm warning | Leave now or continue searching | Preserve safety or find another clue | Alters time and evidence available |
Do not map every possible branch at first. Map the main route, then add only the branches needed to test your central question. A prototype with twenty meaningful cards is often more useful than one with one hundred cards and unclear relationships.
Add rules for information and choice
The cards need operating rules. Keep them visible and simple.
Decide:
- Who controls the cards—the participant, facilitator, or both?
- When can new cards be drawn or revealed?
- Can a participant revisit a previous scene?
- What limits actions: time, trust, evidence, money, safety, or another resource?
- How does the participant know when the story has ended?
- What happens when an action is not represented by a card?
Use tokens for resources that change during play. For instance, a participant might begin with three time tokens, two trust tokens, and one evidence token. Searching a restricted room could cost one time token. Publishing a claim without corroboration could reduce trust.
Resources should clarify the story rather than turn it into an unrelated game. If counting tokens distracts from the narrative, replace the system with a visible status card or a facilitator note.
Write a short facilitator script containing:
- The opening explanation
- The rules participants must know immediately
- The rules that can be learned during play
- Prompts for moments of confusion
- Conditions for ending the session
Do not explain every hidden consequence in advance. If the experience depends on discovery, the facilitator should know the system without revealing it.
Run the first test
Invite one person who is not deeply familiar with the project. A friend can help, but someone outside the design process will expose assumptions more quickly.
Start by explaining the participant’s role and objective. Avoid summarizing the entire plot. Give only the information the participant should reasonably have at the beginning.
During the session, observe without rescuing the participant too quickly. Record:
- The exact point where they ask what to do
- Cards they ignore
- Choices they describe as equivalent
- Rules they interpret differently from your intention
- Moments of excitement or hesitation
- Information they forget
- Places where the facilitator must invent an explanation
When possible, ask the participant to think aloud, but do not interrupt every decision. If thinking aloud changes the experience, observe silently and ask questions afterward.
Useful follow-up questions include:
- What did you think your options were?
- Which choice felt most important?
- What did you believe would happen next?
- Was any information difficult to use?
- Did the consequences feel connected to your action?
- When did you feel most involved?
- What would you remove or combine?
Do not ask whether the participant “liked” the story as your only measure. A confusing experience may still contain a powerful idea, while a pleasant session may hide a weak structure.
Revise the prototype systematically
After each test, separate observations from interpretations. “The participant returned to the first card three times” is an observation. “The opening is boring” is an interpretation that needs investigation.
Sort notes into four groups:
- Comprehension: The participant did not understand a rule, card, or objective.
- Agency: A choice did not feel meaningful or lacked a visible effect.
- Pacing: The story moved too slowly, too quickly, or became repetitive.
- Emotion and theme: The experience did or did not create the intended tension, curiosity, empathy, or uncertainty.
Revise one layer at a time. First fix rules and confusing card language. Then address the structure. Only afterward tune dialogue, flavor text, or visual presentation.
When a branch is rarely chosen, do not automatically delete it. Ask why it exists. It may represent an important theme, provide an alternative for a different audience, or reveal that the preceding choice is not working. Sometimes the correct fix is to make the branch more attractive; sometimes it is to combine it with another route.
Keep old versions in separate envelopes or photograph the layout before changing it. A discarded card can reveal a pattern later, and version tracking prevents you from repeating an unsuccessful approach.
Troubleshooting common problems
Participants ask for instructions constantly. The rules may be too abstract, or the first decision may arrive before the participant understands their objective. Rewrite the opening in concrete language and demonstrate one neutral action.
Every choice leads to the same result. Add consequences that affect later information, relationships, access, or risk. If the outcomes cannot differ because the plot is fixed, make the choice expressive rather than pretending it changes the story.
The prototype becomes a role-playing performance. This is useful if performance is part of the final experience, but it can hide structural problems. Run a second test with less acting and more direct card manipulation.
The story branches uncontrollably. Reduce the number of decision points and use converging branches. Two routes can produce different experiences while returning to a shared later scene.
Randomness feels unfair. Give participants ways to prepare for, mitigate, or interpret random events. Replace a dice roll with a visible choice if the result is meant to reflect judgment rather than luck.
The facilitator explains too much. Mark the exact information the facilitator is allowed to provide. If a rule repeatedly requires verbal rescue, put that information on a card or redesign the interaction.
The session takes too long. Identify which cards create repeated actions without new information. Combine similar scenes, remove low-value searches, or introduce a clear time limit.
Know the limits of paper prototyping
Paper is excellent for testing structure, choice, information flow, and facilitator workload. It is less reliable for evaluating final visual design, sound, performance quality, technical latency, accessibility of a finished interface, or the emotional impact of polished media.
A paper prototype can also make interactions seem easier than they will be in the final product. A facilitator may silently correct errors that software cannot. Participants may tolerate awkward card handling because they understand it is a test. For this reason, follow a paper test with a more realistic prototype when the basic structure is stable.
Test different aspects with different levels of fidelity:
- Paper cards for narrative structure and branching
- A clickable wireframe for interface flow
- Rough audio or video for timing and tone
- A physical rehearsal for spatial or participatory experiences
- A working build for technical constraints and accessibility
Move forward when participants understand the objective, make choices without constant assistance, recognize consequences, and reach an ending that reflects the project’s intended question or theme. At that point, the cards have done their job: they have turned an uncertain story idea into an experience you can examine, discuss, and improve.