Back
Mobile & Desktop

Revealing what a claim doesn’t tell you

Role
UX Designer
Solo
Deliverables
Persona, empathy map, journey map, wireframes to final screens
Context
Independent project
Mobile & desktop app

Overview

Claims travel faster than the context behind them. [context] is a tool that reveals the missing dimensions of a claim: who was studied, when, how it was measured, what it was compared with, and what it doesn’t tell you, without asking anyone to become a researcher first. Built end-to-end from a single interaction idea through real interviews, a persona, wireframes, and final screens.

10interview participants
7interview questions
5context categories
12final screens

So I ran interviews to work from.

Research synthesis

Know quickly whether a claim is worth acting on or passing along
Feel confident sharing something without getting corrected later
Spend as little extra time as possible double-checking a claim
“If it sounds like something I should worry about, I want to know fast whether I actually should.”
Miles's empathy map, “Says” quadrant

Meet Miles

Miles Ferris

The Overwhelmed Sharer

  • 44
  • School administrator
  • Dayton, OH

Bio

Splits his attention between running a small school office and the family and parent group chats that constantly forward him things. Reads news and posts in short bursts on his phone, between tasks, not at a desk with time to dig. Doesn’t think of himself as especially tech-savvy, and is wary of anything that feels like extra homework.

Personality

AnalyticalCreative
Leans Creative
BusyTime-rich
Leans Busy
MessyOrganized
Leans Organized
PassiveActive
Leans Passive
SafeRisky
Leans Safe

Miles

“If it sounds like something I should worry about, I want to know fast whether I actually should.”
“I usually just share things that sound right. My family's called me out for it before.”
“I don't really know where I'd even start looking for the original source.”
“I don't want something that feels like homework.”

User journey map

Miles’s journey across four stages. Tap one to see his tasks, feelings, and where the experience still falls short.

Tasks
  • Sees a claim forwarded into a family group chat.
  • Skims it quickly between other tasks on his phone.
  • Feels a flicker of doubt about whether to trust it.
Feelings

Starts distracted and mildly skeptical, with a low-grade worry about being fooled, or fooling someone else by passing it on.

Area to improve

Nothing currently signals that context is even available. The claim looks exactly as credible as everything else in the feed.

A tool built to add clarity, not more noise.

What I built

Mobile

Context's Full Context screen in a phone frame, with the [C] mark beside it.

Desktop

Context's desktop Full Context window: Who, When, How, Compared With, and Limitation for the remote-worker productivity claim.

A closer look at the final screens.

Context's Home screen: 'What are you seeing?' with a claim text field and a Check it button.
Context's desktop Home window: the same claim field and Check it button, in a browser-style window.

Home

One field, one button. Nothing else competes for the first tap.

Context's Full Context screen: Who, When, How, Compared With, and Limitation, each spelled out in full.
Context's desktop Full Context window: the same five categories, with room for each info icon's detail alongside instead of a sheet on top.

Breakdown

Five categories, spelled out in full: Compared With and Limitation, never abbreviated.

Context's Result screen for a claim with limited context: a flag reading 'we couldn't find enough published information to break this down with confidence.'
Context's desktop Limited Context window: the same flag, with suggestions to look for the original source or ask whoever shared it.

Limited Context

Honesty about its own limits, styled the same as any other result, not as an error.

Context's Share screen: a preview card with the claim and its context, and Messages/Email/Copy link options.
Context's desktop Share window: the same preview card and Messages/Email/Copy link options.

Share

Every share carries the context with it, never just the bare claim.

Every decision tied back to something in Miles’s research.

What worked

Treating every UI decision as answering one question: does this help someone interpret a claim, or work against it.

What I'd do differently

Surface who verifies Context's own information earlier — right now that only shows up once someone's already deep into a result.

What I'd track

How often someone opens the full breakdown versus stopping at the flag, and whether a “limited context” result changes what people do with a claim at all.