Testing What Users Really Understand
Content design aims to reduce confusion and improve clarity, but pinpointing exactly where users stumble is often difficult. User feedback tends to be vague — "it looks fine" — while the actual comprehension gap remains hidden. Simple, structured testing techniques can reveal how users truly perceive your content, whether it’s a paragraph, a flow, or a full dashboard.
Banana Testing for Mental Models
Banana testing checks whether your interface matches the user’s mental model. Replace every key action label with the word "Banana," then ask participants what they think each action does. This exposes whether actions are understood immediately, whether they sit in the right place, whether icons are meaningful, and whether interactive elements actually read as clickable.
Content Heatmapping for Clarity Patterns
Content heatmapping offers a dependable method for evaluating text. Give participants a task, then ask them to highlight what is clear or confusing. You can define additional lenses — for example, marking phrases that increase or decrease confidence. After collecting the highlights, map them onto a heatmap to spot patterns and trends.
The session can run in person with print-outs or remotely in tools like Figjam or Miro, as long as a highlighter feature is available.
Moderated Sessions Surface Missing Needs
Heatmapping and banana testing uncover existing problems, but they don’t reveal what content is missing, nor the doubts and concerns users carry. Those insights rarely emerge in unmoderated tests. When users call a page "clear and well-organized," follow-up questions often show their understanding is quite different from what the design intended.
Observing behavior and asking questions on the spot — in person or remotely — is more effective for surfacing those gaps.
Test Concepts, Not Wording
Define your learning goals before testing. Write a plan covering objectives, target customers, questions, and a script. Avoid focusing on isolated wording changes — broader concept testing yields better insight. During sessions, do not read text aloud, since that’s not how users normally consume content. Ask a question, then wait silently for the participant to respond.
After the task, request that the user explain the product, flow, or concepts back to you. Avoid asking what they like or prefer. Also, steer clear of the word "content" — users interpret it differently than designers do.
Selecting the Right Test Method
Different questions call for different techniques:
- Do users understand the text? Try interviews, highlighting, or a Cloze test.
- Does the design match the mental model? Use banana testing or a Cloze test.
- Which wording works best? Card sorting, A/B testing, or tree testing.
- Why is something failing? Conduct interviews, highlighting tasks, or walkthroughs.
- Do we actually know user needs? Competitive testing and process mapping are helpful.
Other options include reaction cards — where users pick emotions from a deck — or having users explain competitors’ pages in competitive testing.
The Weight of Words on Key Pages
Few tasks have more impact than the careful selection of words on a page. Beyond the words themselves, the voice and tone used to communicate matter equally. The techniques above measure how content is understood, but they also help you evaluate the end-to-end experience users have on your site.
A single misapplied phrase on a critical page can derail an otherwise strong product. If a user is blocked at a key step, they are gone quickly — no matter how well the rest of the experience performs.
Further Reading
- Practical Guide To Content Testing, by Intuit
- How To Test Content With Users, by Kate Moran
- Five Fun Ways To Test Words, by John Saito
- A Simple Technique For Evaluating Content, by Pete Gale
