How Spoiling the Ending Improves UX

Ben Moss By Ben Moss  |  Oct. 23, 2017

Storytelling is about the unknown becoming known. But designers aren’t storytellers, and the destinations they design should always be clear to the user. By inserting small spoilers into our UI designs, and spoiling the surprise, we design for much improved user experiences.

It has often been asserted by fans of pop-wisdom that there are only two distinct plots in the whole of western culture: a person goes on a journey, and a stranger comes to town.

A brief flick through your bookcase will disprove the rule—unless you permit metaphorical journeys, in which everything fits—but the frequency with which the idea is repeated, and the sense it seems to make, speaks volumes about the centrality of the unknown in western ideas of narrative.

In both plots, a person is introduced to something new and unexpected, the only variation is the point of view from which the narrative speaks; in both cases, the story arc is the unknown becoming the known. When Clint Eastwood rides into a broken down town in 1800s Idaho, our curiosity about his identity is what drives our engagement. When we read Tolkien’s Lord of the Rings trilogy, we’re never in any doubt that Frodo will eventually make it to Mt Doom, the interest is in what happens along the way.

The key to story-telling is that there is an unknown, and that the unknown will become known.


Designers Aren’t Story-Tellers

Numerous designers have referred to themselves as story-tellers, but this is simply a kitsch way of referring to communication. To tell a story, we have to foster the unknown in preparation for a big reveal, and the major obstacle to this approach is that web experiences—and I would argue most encounters with design—are non-linear and open-ended.

Design is in fact far closer to poetry. Poetry typically exists in bite-sized chunks, and in which themes are explored that are open to interpretation.

Far from constructing a story, a designer’s job is to clarify as unintrusively as possible.


Using Spoilers in Microinteractions

What’s the most engaging element in Jaws? Is it Brody arguing with the mayor? Is it Quint telling the story of the Indianapolis? Is it Hooper’s affair with Ellen Brody (yes really, read the book!)? No. It’s the music. As soon as that shark starts playing the cello we know it’s coming, its arrival is literally heralded. [Incidentally, Jaws is an interesting example of a film in which both a stranger (the shark) comes to town, and then a man goes on a journey (to sea).]

We can create engagement in design by continually dropping spoilers, hinting at what’s coming, with cello music of our own. To do so, we use microinteractions—simple UI components, featuring a trigger and feedback. The feedback portion of the microinteraction is the place to insert your spoiler.

It works by previewing data that would, in a linear experience, be introduced at a later stage. The key is to bring data forward.


Let’s start with something familiar: the classic example of bringing information forward is the thumbnail. A thumbnail is a preview of a larger element, a visual guide to what to expect on the other end of a link.

Jacky Winter is a talent agency for artists, illustrators, and animators. With a diverse range of talent, the best way to browse work is with traditional thumbnails.


Thumbnails don’t have to be traditional. Alexandre Nacache is an art director and interactive designer whose site uses previews of project elements, rather than reproductions of a design in miniature.


Bao is a Taiwanese restaurant with three locations in London. Their location illustrations act like thumbnails, suggesting not just a look for the restaurant, but a possible experience.


A Day Out is a Glasgow-based design studio. The thumbnails on their site form a major component of the art direction and establishes their own brand aesthetic.


The 5 Minute Read

Back in the day, the only way to know how long reading an article like this would take, was to check the time, read the article, and check the time again.

Based on its uptake, one of the most successful UI elements of recent years is the helpful little indicator that tells us how long an article will take to read. Popularised by sites like Medium, there’s no eye tracking involved, or reading speed calculated, the “5 minute read” estimate is based on word count—125 words is expected to be read in 30 seconds or thereabouts. But even this grossly generalized data is sufficient to allow users to make informed decisions about their commitment to a site, article, or product.

The monotone of Australian Design Radio is broken only by the contrasting red used for hover states. The only element that employs the red without interaction? The playhead that features position, and total length.


Sequoia is a California-based venture capital firm. Profiles of tech companies occupies their landing page. Each profile features a numbered position, and the slider’s animated timer draws your attention to exactly where you are in the process.


Vimeo features some of the best videos on the web. They could have displayed any information they wished—producer, subject, title—when hovering over their thumbnails. They chose duration.


Cinelli is Italy’s coolest bike brand. Their product slider features numbered ‘next’ and ‘previous’ buttons. Arrows alone would be enough to convey meaning, but the designers brought data forward with a simple addition to the buttons.


Qualifying Data

One of the simplest ways of enhancing an interface, is to qualify data with a meaningful context. The key to this is not deliver too much information, just a simple summary that can be read at a glance.

Help Scout is a customer service SaaS. Their dashboard displays key metrics like total conversations, which would be meaningless without the addition of an arrow and a percentage indicating whether that’s an improvement, or a setback.


Booking a ticket from Lyon to Bordeaux is made simpler when Trainline displays a bar beneath the journey time, to give a visual indication of both duration, and the number of changes.


Maps and Reassurance

When we anticipate journeys, especially a journey into the unknown, we often demystify the experience with a map. In the real world, a map is very much like a thumbnail of a destination. In user interface design, the maps we use clarify information architecture.

Labels are one of the most complex areas of information architecture because they tend towards jargon, often company-exclusive jargon. Adding jargon-free microcopy previews the destination for users, and helps them find their way to the right information.

Lattice is a performance management SaaS, but their products are very company-centric. They solve this problem by signalling the key feature of each product in their menu.


Thriva helps you track your health with blood tests you can take at home. They have three levels of product that are clearly explained in their menu.


Financial transactions are technically complex. Plaid offers a variety of API products for developers. Their menu not only explains the key feature of each product, but previews two potential solutions based on product combinations.



The Key to Effective UI Design Is Spoilers

Telling stories is the antithesis of effective design, because stories by their nature, pander to the unknown elements in an experience. Design, by contrast, seeks to eliminate the unknown by clarifying.

When we bring data forward in a design, we typically do so in a simple fashion. A single piece of well selected data can clarify an entire process. Microinteractions are the ideal way to insert these ‘spoilers’, which empower users to create their own experience, whilst always knowing precisely where they are within the wider context.

 By revealing more than a linear story would, we engage users far more effectively, and design experiences that are robust, and enjoyable to use.