Measuring UX

Outputs, outcomes & impact

When a design effort feels unmeasurable, it's usually being described at the wrong altitude. An output is what you made. An outcome is the behavior that changed because of it. An impact is what that was worth to the business or the person. Stakeholders fund the top two; portfolios that stop at the bottom read as activity, not results. Pick a piece of work and watch it climb.

Checkout redesign

Outputwhat you made

Rebuilt checkout as a single page with inline validation and clearer error states.

Outcomewhat changed

More shoppers who start checkout finish it, instead of abandoning at a confusing step.

Measure: Checkout completion rate; abandonment at the payment step

Impactwhat it was worth

Higher revenue per session and fewer support contacts from failed or duplicated orders.

Measure: Revenue per session; order-related support tickets

The assumption it rests on

That abandonment was driven by friction in the flow — not by price, shipping cost, or intent. If shoppers were leaving over cost, a smoother form moves nothing.

Onboarding flow

Outputwhat you made

Designed a three-step guided setup with a progress indicator and sensible defaults.

Outcomewhat changed

More new users reach their first real moment of value instead of stalling in setup.

Measure: % of new users completing setup / reaching activation

Impactwhat it was worth

Higher trial-to-paid conversion and stronger first-week retention.

Measure: Activation-to-paid conversion; day-7 retention

The assumption it rests on

That reaching the 'aha' moment is what drives conversion — that activation is a genuine leading indicator of paying, not just correlated with users who were already sold.

Error-message rewrite

Outputwhat you made

Rewrote form error messages to say what went wrong and exactly how to fix it.

Outcomewhat changed

Users recover from errors on their own instead of abandoning the form or contacting support.

Measure: Error-recovery rate; form completion after an error

Impactwhat it was worth

Fewer support tickets and a higher completion rate on a revenue- or conversion-critical form.

Measure: Support ticket volume; cost per completed form

The assumption it rests on

That the errors were a comprehension problem, not a validation-rules problem. If the form rejects valid input, kinder copy just explains a wall more politely.

Design system rollout

Outputwhat you made

Shipped a component library and adoption guidelines across the product teams.

Outcomewhat changed

Teams assemble screens from shared components faster, with fewer one-off rebuilds.

Measure: Component reuse rate; design-to-dev handoff cycle time

Impactwhat it was worth

Faster time-to-market and lower ongoing design and engineering maintenance cost.

Measure: Release velocity; UI defect / rework rate

The assumption it rests on

That teams actually adopt it. A design system's impact is famously indirect — prove adoption (the outcome) before you claim velocity (the impact), or you're crediting the library for work it never touched.

Search & filtering

Outputwhat you made

Added faceted filters and a helpful empty state to the catalog search.

Outcomewhat changed

Shoppers find a relevant result faster and abandon search far less often.

Measure: Search success rate; zero-result and search-exit rates

Impactwhat it was worth

More search-driven purchases and higher conversion for the catalog overall.

Measure: Search-to-purchase conversion; revenue from search sessions

The assumption it rests on

That search was a discovery bottleneck — that people wanted the catalog and couldn't navigate it, rather than not wanting what the catalog held.

Carry this to your own work

We shipped [output], so that [users] now [changed behavior] — the outcome — which moves [business or human metric], the impact.