UX Clarity Canvas

What is the UX Clarity Canvas?

The UX Clarity Canvas helps a product team decide what to do about one clarity problem. It aligns the team on the user outcome, the evidence behind it, the priority problem, the proposed intervention and what success means.

Its output is a one-page decision brief. The brief links to the underlying research rather than duplicating it, so anyone outside the room can follow the decision back to its evidence.

The canvas is not the UX Clarity Framework. The framework is a diagnostic: it reviews a product across six dimensions and rates each one from 1 to 10. The canvas carries no score. It takes one problem the team has found and turns it into a shared decision.

If your team already knows the canvas format from the Business Model Canvas, the difference is scope: that canvas describes a whole business on one page, while this one describes a single UX decision.

The eight fields

Fill the fields in order. Each one answers a question the next field depends on.

1. User and context

Who is trying to do what, and under which relevant conditions? If the team keeps a research-based user persona, point to it here instead of restating it. User personas: a practical guide covers what makes one trustworthy.

2. Intended outcome

What useful result should they reach? What is the basis for choosing it?

3. Journey boundary

Where does this investigation start and end? Which branches matter? A journey map helps draw the boundary, and customer journey mapping 101 explains how to build one.

4. Evidence

Which observations, captures, and reviewed cases support the discussion? Link the sources. If the notes are still raw, research synthesis turns them into findings first.

5. Priority obstacle

What expectation gap matters most? Which pattern codes fit, and why? What remains unknown?

6. Design hypothesis

What change do we propose, and why should it improve the outcome? This is the field that separates the canvas from a design brief: a brief sets the scope and constraints of a whole project, while the canvas states one testable change tied to the evidence above.

7. Success and guardrails

What observable result would support the hypothesis, and what must not get worse? A baseline makes the comparison concrete: the Pulse Clarity Score or a UX Snapshot taken before the change gives you something to compare against afterwards.

8. Owner and next review

Who moves it forward, what is the next action, and when will the evidence be reviewed?

The canvas (blank template)

This table is the reusable artifact. Copy it into any shared format your team already uses: a doc, a whiteboard or a sheet of paper. Keep one canvas per decision.

Field	Prompt	Your answer
User and context	Who is trying to do what, and under which relevant conditions?
Intended outcome	What useful result should they reach? What is the basis for choosing it?
Journey boundary	Where does this investigation start and end? Which branches matter?
Evidence	Which observations, captures, and reviewed cases support the discussion?
Priority obstacle	What expectation gap matters most? Which pattern codes fit, and why? What remains unknown?
Design hypothesis	What change do we propose, and why should it improve the outcome?
Success and guardrails	What observable result would support the hypothesis, and what must not get worse?
Owner and next review	Who moves it forward, what is the next action, and when will the evidence be reviewed?

How to fill it

1. Fill the user, outcome and journey fields.
2. Link evidence and clearly mark assumptions.
3. Select the obstacle to address and justify the pattern match where one exists.
4. State a specific intervention and its predicted effect.
5. Agree on success, guardrails, owner and next review.
6. Revisit the canvas when evaluation changes the team's understanding.

A blank Evidence field is a finding in itself: it shows the team has a research need. Do not fill it with invented behavior, and do not let a confident hypothesis cover for it.

Keep observation, interpretation and recommendation separate. An observation is what someone saw. An interpretation is what the team thinks it means. A recommendation is what the team proposes to change. Writing them in different fields lets a reader challenge one without discarding the others.

Name patterns from TYPENORM's pattern registry by their stable names or codes. A pattern match is an interpretation, and matching a pattern does not establish that a fix works. That still has to be checked against the success field.

Review and update

A canvas records the team's current understanding, so it changes when that understanding does. Revisit it when an evaluation comes back, when new evidence contradicts a field, or when the next review date arrives.

Keep the owner and the next-review date current. A canvas with no owner or a past review date has stopped being a decision and become a record of an old one. When a field changes, note what changed and why, so the history of the decision stays readable.

How it connects the framework family

The canvas sits beside TYPENORM's other frameworks and takes input from each of them:

• Frictions Map supplies journey findings, pattern matches, impacts and possible responses.
• 5L UX Onboarding Flow supplies onboarding lenses when the journey concerns first value.
• Research-to-Design Loop supplies the hypothesis, the evaluation and the learning record.

The canvas keeps the current decision and its evidence understandable across the team.

Getting started

The canvas is a deliverable, and it follows the same test as every other one: it should settle a decision. The UX deliverables hub covers that test and the templates that feed the canvas fields. For what "clarity" means across TYPENORM, see the UX clarity hub.

Start with one problem your team keeps arguing about, copy the blank table, and fill the first three fields together.