Answer 20 of 50

Integrating Storytelling Techniques Into Web Design and User Journeys

8 min read

Storytelling in web design is an ordering decision: what the visitor sees first, which problem the page names, what evidence answers it, and where the page asks for action. A story-led page puts the visitor’s situation before your product and lets the scroll move from problem to resolution. The techniques below cover page structure, characters, visuals, scroll, and data, and each one comes with the condition under which it helps or gets in the way.

Map the story arc onto the page sections

Classical stories have a beginning, a middle, and an end. A page can follow the same order, section by section:

Story stage Page section What it does What goes wrong
Setup Hero and first screen Names the visitor's situation and what the page offers A slogan that names neither the problem nor the offer
Tension Problem and stakes Says what the current situation costs the visitor Urgency the visitor does not feel
Turning point How it works Shows the change: the product, service, or method A feature list with no link back to the problem
Evidence Proof Customer stories, data, or a demo showing the change happened Proof unrelated to the problem named at the top
Resolution Call to action The next step and what happens after it An ask bigger than the story has earned

The reason to use this order is practical rather than proven: it gives each section one job and makes gaps visible. A page with a strong hero and a call to action but no evidence section has skipped the middle of its own story. Whether a story-led page outperforms a conventional one for your audience is a question for testing, covered at the end.

Make the visitor the hero and the brand the guide

Nancy Duarte applied this idea to presentations. Her company’s page for the book Resonate says it “upends the usual paradigm by making the audience the hero and the presenter the mentor”. On a website, the same move means the visitor faces the problem and your brand supplies the plan or the tool. In practice:

  • The hero headline describes the visitor’s goal or problem, not the company’s history.
  • The product enters as the means of change, after the problem is named.
  • Origin stories and founder journeys move to the about page, where visitors who want them can find them.

Customer stories make the hero concrete. They work when a reader can recognize the starting point: the same role, the same constraint, the same problem. A customer story that reports results is also a testimonial, and testimonials carry disclosure and substantiation duties; those are covered in where to place social proof and what it must prove.

Let images and video carry part of the story

A sequence of images can tell a story without text: before and after, step by step, problem to result. Photography sets the emotional register, and illustration can show what a camera cannot, such as a process, a data flow, or an internal state.

Video compresses a story into a few minutes, and it has to work for people who cannot hear it. W3C’s Captions (Prerecorded) criterion is Level A: “Captions are provided for all prerecorded audio content in synchronized media,” with an exception for media that is a clearly labeled alternative to text. W3C adds that captions also “identify who is speaking and include non-speech information conveyed through sound, including meaningful sound effects.” For a brand video whose mood depends on music or sound, that last part decides whether a caption-only viewer gets the story.

Pace the story with the scroll, and leave control with the reader

Scrolling can work like turning a page. Sections can reveal one idea at a time, and whitespace between them can act as a pause. Two techniques need limits.

Motion effects. Scroll-triggered animation and parallax can make a page feel like it unfolds. They can also make some people ill. W3C’s explanation of Animation from Interactions states: “Another animation that is often non-essential is parallax scrolling.” The prefers-reduced-motion media feature, in MDN’s words, detects “if a user has enabled a setting on their device to minimize the amount of non-essential motion.” One way to build with it is to make the static page the default and add motion only for people who have not asked for less:

.reveal { opacity: 1; }

@media (prefers-reduced-motion: no-preference) {
  .js .reveal { opacity: 0; transform: translateY(24px); transition: opacity 0.6s, transform 0.6s; }
  .js .reveal.is-visible { opacity: 1; transform: none; }
}

The is-visible class has to come from a script. MDN describes the Intersection Observer API as a way to “asynchronously observe changes in the intersection of a target element” with the viewport, which is what tells the page a section has scrolled into view:

document.documentElement.classList.add('js');

const observer = new IntersectionObserver((entries, observer) => {
  entries.forEach((entry) => {
    if (entry.isIntersecting) {
      entry.target.classList.add('is-visible');
      observer.unobserve(entry.target);
    }
  });
});

document.querySelectorAll('.reveal').forEach((section) => observer.observe(section));

Because the same script adds the js class that the hidden state depends on, sections stay visible if the script never runs.

The wider motion and contrast checklist sits in designing for color blindness and visual impairments.

Scrolljacking. Nielsen Norman Group’s Scrolljacking 101, by Sara Paul (2023), defines it as “a design pattern that changes the speed and, sometimes, the direction of scrolling on a web page.” The article reports from NN/g’s usability testing: “The majority of our study participants were at least mildly disoriented by scrolljacking.” If a stakeholder still wants it, the article’s best practices narrow its use: reserve it for critical information, test the scroll rate, do not change the scroll direction, keep important text out of it, avoid it on mobile, and place it below the fold. The same testing found that a navigation bar that stayed visible gave participants a way out of a confusing scrolljack.

Give scanners a story in the headings

Some visitors read every word; others scan headings and land mid-page from search or a shared link. Each section should make sense on its own, and the headings together should carry the arc. For example, imagine an accounting software page. Headings like “Features,” “Benefits,” and “Pricing” tell no story. Headings like “Month-end close takes your team a week,” “Reconciliation runs while you work,” and “Close in two days, or your next month free” carry problem, change, and offer, but the last one is a promise, and any promise in a heading has to be one the business makes.

Tell the story in the data without changing the claim

A number becomes a story when it is put in the reader’s terms. The rule is that the reframed sentence must make the same claim, with the same unit and the same comparison. For example, imagine three claims from a product page:

Raw claim Same claim in the reader's terms Reframing that changes the claim
Support tickets fell 47% after the redesign Customers now send about half as many support tickets as before Nearly half of our customers no longer need support
5 million users in 18 months Five million users within a year and a half of launch Five million users in an industry where most startups fail
Page load time dropped from 4.0 to 2.0 seconds Pages now load in half the time Our site is twice as fast as competitors'

The first distortion swaps tickets for customers. The second adds a comparison with no source behind it. The third invents a competitor benchmark. Charts follow the same rule: if a bar chart’s axis does not start at zero, show the break, so a small change does not look like a large one.

Keep brand stories and product stories in different places

Brand stories explain why the company exists: origin, mission, the people behind it. Product stories explain what the product does for a specific person. A visitor comparing options on a landing page should get the product story first; the brand story earns attention on the about page and in a short line near the top. Storytelling, about pages, and case studies sit in the zone where a site can take more creative risk without blocking a task, as set out in balancing convention and creativity.

B2B: one case study, several readers

A business purchase has several readers, and each one reads the case study for a different story: the technical lead for implementation, the budget holder for cost and return, the daily user for what changes in their week. A case study that serves all three follows a fixed order:

  1. The customer and their starting situation, in one paragraph.
  2. The problem and what it was costing them.
  3. The options they considered.
  4. What they implemented and how long it took.
  5. The result, with a measure, a time frame, and how it was measured.
  6. A quote from a named person in a named role.

Step 5 carries the weight: a result without a time frame or a baseline cannot be compared with anything.

Measure the story against a control

Engagement metrics are ambiguous. Longer time on page can mean a reader is absorbed, or that they cannot find what they came for. Scroll depth has the same problem. To learn whether storytelling helps, compare a story-led version of a page with a conventional version of the same page, and read conversion and task completion alongside engagement. Add a short survey or a few user interviews asking what visitors remember and what they would do next; recall and intent are what a story is meant to change.

Questions teams ask

Our product is technical and dry. Can storytelling still work?

The product may be technical, but the problem it solves belongs to a person: a delay, a risk, a manual task. Start the story there and bring in technical detail as the evidence section.

Visitors want quick answers. Does a story slow them down?

Put the answer first and let the story support it. A hero that states the offer plainly, followed by sections that each work alone, serves the scanner and the reader who wants depth.

Is video worth the cost?

It depends on what the video has to show. Video earns its cost when the thing being sold is easier to understand in motion, such as a physical device or a multi-step workflow. Start with a short, captioned video on one page and compare it with the same page without it.

Our competitors do not use storytelling. Will we look unprofessional?

Story structure is a way of ordering content, not a tone of voice. A sober page can still move from problem to proof to next step. Judge it by how your visitors respond in testing, not by what competitors publish.

Keep a story element only if removing it would cost the reader something: the problem, the proof, or the next step. Anything that adds only motion or length is the first thing to cut.