A simplified Lean UX · A walkthrough for mentees
From a shared canvas to a prioritized, iterated build.
Lean UX turns a fuzzy request into testable bets, then lets real iterations decide what earns more investment. This is that loop end to end — align on a Product Canvas, turn the canvas into hypotheses, prioritize them by value against effort, ship the quick wins, measure what happened, and repeat.
The worked example: a performance dashboard for the call center at Meridian Bank, built as a new screen inside their internal Compass platform. This is a deliberately simplified, adapted take on Lean UX — the spine of the method, not the full canonical process.
↻ Steps 3–5 repeat every iteration — each build is sized to teach us the next thing worth prioritizing.
Align
Aligning first: the Product Canvas.
Before designing anything, I facilitate the room through four questions — captured together, in their words, on one shared canvas. The value isn't the document; it's the shared understanding that keeps everyone solving the same problem, for the same people, toward the same goals.
The move: get everyone to agree on the problem, goals, users, and outcomes before anyone proposes a solution. Alignment first, pixels later.
Align
Defining the problem.
The first cell of the canvas, and the one everything else hangs on. Before a single goal or feature, the whole room agrees — in one sentence — on the pain we're actually solving. Get this wrong and every decision downstream solves the wrong thing, however well it's built.
Leadership can't quickly or reliably see performance across the call center — because the data reaches them through slow, hand-built supervisor reports that each measure things differently.
Facilitated to consensus with leadership, supervisors, and ops in the kickoff canvas session — specific, solution-free, and written down.
Align
What are the business goals?
The problem, broken into measurable goals — each paired with the outcomes that would prove it solved. Goals give the work a target; the outcomes are how you'll know you actually moved it, not just shipped something.
Align
Users.
Everyone the work touches — not just who logs in. Naming them up front, the people behind the numbers included, is what keeps the design honest to real users instead of an imagined average.
Align
User outcomes.
What each person is ultimately trying to accomplish — stated as outcomes, not features. Get these right and the solution space stays wide open; skip them and you'll design features nobody actually asked for.
Align
The canvas, filled out.
Four questions answered — one shared page the whole team points back to when a decision gets contested. This alignment is what the rest of the loop is built on: everything after here traces to a cell on this canvas.
Hypothesize
Creating hypotheses.
The canvas gives us the raw material — each hypothesis connects a goal, a person, an outcome, and a feature into one testable sentence.
The move: rewrite every wish as a testable bet — goal, person, outcome, feature — so later you can tell whether it actually worked.
| We will Achieve [business goal] | If [persona] | Attains [outcome] | Through [feature] |
|---|---|---|---|
| Zero report requests to supervisors | Senior leadership | Instant comparison of product lines, teams, and individuals | A self-serve overview with side-by-side comparison views |
| Best and worst product lines, obvious at a glance | Senior leadership | A side-by-side view of productivity and quality, at a glance | A ranked product-line leaderboard on the landing view |
| Best and worst product lines, obvious at a glance | Senior leadership | A side-by-side view of productivity and quality, at a glance | A quadrant chart plotting volume against rejection rate |
| Best and worst product lines, obvious at a glance | Senior leadership | A side-by-side view of productivity and quality, at a glance | Small-multiple trend cards, one per product line |
| Problems surfacing in days, not report cycles | Senior leadership | Problem areas that surface themselves — no hunting | Threshold-based alerts pinned to the top of the dashboard |
| Problems surfacing in days, not report cycles | Senior leadership | Problem areas that surface themselves — no hunting | A weekly digest of anomalies, delivered without logging in |
| Decisions made on today's data, not last month's | Senior leadership | Enough trust in the numbers to act on them | "Data as of" timestamps and a visible refresh cadence |
| Decisions made on today's data, not last month's | Senior leadership | Enough trust in the numbers to act on them | A metric glossary one click away from every number |
| Problems surfacing in days, not report cycles | Supervisors | A clear read on who needs coaching this week — and on what | Automated problem-area alerts on the supervisor's team view |
| One meaning of "top performer," everywhere | Call-center reps | Confidence they're measured the same as everyone else | A personal scorecard built on the shared metric definitions |
| Every decision citing one shared source | Analysts | Same-day answers to leadership's follow-ups | Saved views and exports that inherit the standard metrics |
Prioritize
Hypothesis prioritization.
Same hypotheses, now competing — value to the business against effort to build.
The move: rank the bets by value against effort, and start where the payoff is high and the cost is low — the quick wins.
Value (vertical) against effort (horizontal) sorts every bet into four zones:
- Quick wins — high value, low effort. Do these first.
- Big bets — high value, high effort. Plan and stage them.
- Fill-ins — low value, low effort. Only if there's slack.
- Time sinks — low value, high effort. Skip.
High value
Low value
Effort
The hypotheses.
Build
Iteration one, built.
The three quick wins become one leadership screen inside Compass — small enough to ship, real enough to learn from.
The move: ship the smallest slice that can teach you something real — not the whole backlog. The other eight bets wait until this one reports back.
Learn
What iteration one taught us.
Shipping the slice was never the point — learning from it was. Before touching the backlog, we measured how leadership actually used the three things we shipped.
The move: every shipped bet carries a signal to watch. Usage — not opinion — decides what to keep, refine, or kill.
Self-serve side-by-side overview
Signal: report requests to supervisors fell 74% in three weeks, and leadership opened the dashboard on 18 of 20 working days.
Decision: keep it — this is now the default landing view.
Ranked product-line leaderboard
Signal: leaders opened 4 of 5 exec check-ins from the leaderboard's bottom row — then immediately asked "which team?", which it couldn't answer.
Decision: the ranking works; it needs drill-down. → becomes a round-two bet.
Volume-vs-rejection quadrant chart
Signal: only 1 of 8 users read the quadrant correctly unprompted; most ignored it and leaned on the leaderboard instead.
Decision: pull it — the leaderboard already answers this, more simply.
One win to keep, one bet to refine, one feature to kill — that's what shapes round two. Skip the measuring and you're not doing Lean UX; you're just shipping in small batches.
Prioritize · round two
Prioritization, round two.
Eight hypotheses return from the backlog — joined by four new ones that iteration one's signals surfaced, marked in plum.
The move: re-prioritize with what you now know — the old backlog plus the new bets the last build exposed.
Value (vertical) against effort (horizontal) sorts every bet into four zones:
- Quick wins — high value, low effort. Do these first.
- Big bets — high value, high effort. Plan and stage them.
- Fill-ins — low value, low effort. Only if there's slack.
- Time sinks — low value, high effort. Skip.
High value
Low value
Effort
The hypotheses.
Build · round two
Iteration two, built.
Three round-two quick wins layered onto the same screen — each one a direct answer to a gap we found in iteration one.
The move: repeat, deliberately. Each pass buys down a real gap the last one exposed — and opens the next question worth testing.
Recap
The whole loop, in one place.
Same five moves, every time. The goal was never to ship features fast — it was to spend the least effort needed to learn what's actually worth building next.
- Align — get the room to agree on the problem, goals, users, and outcomes on one shared canvas, before anyone proposes a solution.
- Hypothesize — rewrite each thing you want to build as a testable bet: which goal, which person, which outcome, which feature.
- Prioritize — plot the bets by value against effort, and take the quick wins first.
- Build — ship the smallest slice that can teach you something real, and leave the rest in the backlog.
- Learn — decide the signal before you ship, then let usage — not opinion — pick what to keep, refine, or kill. Then loop back to prioritize.