Results

Results is where the business finds out whether a bet paid off.A bet predicts that people will keep choosing what the team built, and that the business will feel it. Results checks that prediction against what actually happened, over the window the bet named. Without that check, teams report launch-day numbers, call them proof, and move on.What Results answersEach facet ends in a block that judges one quality, as people experience it. Results closes Lead, and the quality it judges isviability: "I keep using it, coming back and paying."Question it answersWhat it checksWhat it hands upDid it move the business enough to keep funding it?The outcome against the baseline over the window, read through Mapping's link typesA verdict on the business priority, which re-ranks the next roundResults is accountable forAdoptsignals: what people actually do over time. Retention, repeat use, spend, and adoption show whether people kept choosing the design after the test was over. Business numbers show whether that behavior was enough to matter.Test results are leading reads. They belong to Measure: Findings and Focus: Bets. Results reads the lagging measures that only exist once the change is live.The loop Results closesEvery piece of work runs through four layers. Initiatives and Bets come from Focus, Findings come from Measure, and Outcomes are what Results checks.LayerWhat it holdsWhere it comes fromInitiativesThe framed area of work and its goalFocus: InitiativesFindingsCalled hunches and Use signals from testsMeasure: FindingsBetsCommitted options with a predicted outcomeFocus: BetsOutcomesWhat people did and what the business sawLead: ResultsWorkflows hold these layers together: they are the functions that own each KPI and act on each verdict.How to Check an OutcomeSTEP 1Start from the bet's predictionTake the predicted outcome from the Bet Output: the behavior that should follow, the metric that shows it, and the window. If the bet has no prediction, there is nothing to check. Write one with the bet's owner before reading any data.STEP 2Set the baselineMeasure the same metric, for the same audience, over a comparable period before the change. Without a baseline, a number after launch has nothing to be compared with.STEP 3Read Adopt behavior over the windowWait for the window the bet named, then read what people did: did they come back, repeat, stay, or pay? Launch-day adoption is not the outcome. A lift that fades by day 60 is a different result from one that holds.STEP 4Read up the chain by link typeMove from the user outcome to the product KPI and the business KPI using the links Lead Mapping recorded. How strongly you can claim the business moved depends on the link type.Link typeWhat it meansWhat you can claimCausalA tested change moved the KPI (an experiment, holdout, or staged rollout)The change caused the moveCorrelatedThe KPIs move together across users, accounts, or periodsThey move together; the cause is not provenSequentialA before-and-after readThe KPI moved after the change; other things may have tooLinked: DefinedTrue by formula, such as pay rate as part of revenueCertain, but says nothing about whether design moved itLinked: Stated or PlannedSomeone says so, or a plan assumes itUnproven; never report it as causalSTEP 5Give a verdict on the business priorityCall the bet against the priority it served.VerdictWhen to use itWhat it does to the priorityHeldAdopt behavior and the business KPI moved as predicted, through a link strong enough to claimKeep funding; scale the betPartly heldBehavior moved, but the chain broke before the business KPIKeep the priority; fix the broken linkDidn't holdThe predicted behavior did not appearMove the priority down; send the gap back as a new hunchToo earlyThe window has not closed, or the data is missingNo verdict yet; set the next check dateSTEP 6Re-rank the next roundA verdict changes what the business funds next. Held raises the priority and the bets that serve it. Didn't hold lowers it, and the gap goes back to Measure as a hunch or to Focus to re-rank the remaining bets.Three Outcome LevelsLevelQuestionMeasured byUser outcomesDid people keep using it?Adopt behavior: return, repeat use, retentionProduct outcomesDid adoption or retention move for the product?Product KPIsBusiness outcomesDid revenue, cost, or growth move enough to keep funding it?Business KPIs, against the priorityPerfect attribution is rare, and that is fine as long as the claim matches the link. A Sequential read can say the KPI moved after the change. Only a Causal link can say the change moved it.Case StudyUniversity Website RedesignWhat the tests showedEnrollment had stalled, and leadership wanted the website to recruit better. Testing narrowed 44 concept areas to three flows: navigation, the homepage, and the request-for-information form. The tests showed navigation usability up 36%, form findability up 19%, and homepage impressions up 57%.These are Findings: leading reads from tests. They justified the bets. They are not the outcome.The betsNavigation:simplify menus around the goals prospective students arrive with.Homepage:lead with Degrees & Majors ahead of Apply Now.Request form:move it higher on the page.What Results readsBaseline:request-form submissions and program-page visits for the same months of the previous admissions cycle.Window:one full admissions cycle after launch.User outcome (Adopt):do prospective students return to program pages, and finish the request form at a higher rate than the baseline?Product outcome:do more qualified leads reach admissions?Business outcome:do applications and enrollment move against the Growth priority?Link type:form submissions to applications is Sequential unless admissions can run a holdout; the claim stays at "moved after the change."The verdictThe verdict comes at the end of the window, against the enrollment priority. Until then the case is Too early, however strong the test results look.When Outcomes Keep MissingIf bet after bet ends in Partly held or Didn't hold, the problem is usually in how the team works, not in one design. The Design Assessment, reached from Lead: Workflows, rates that across five dimensions: Organizing Work, Managing Complexity, Building Proof, Guiding Decisions, and Scaling Influence.ResourcesThe Value and ROI of UX, by Debbie LevittHow to Measure the Business Impact of UX Design, by Emilie RoussetyWhy Doing Everything is a Bad UX Strategy, by Jeff HumbleThe State of UX in 2025, by Fabricio Teixeira and Caio BragaROI of UX: How to Prove the Value of Good User Experience, by Disha ModThe ROI of UX is so massive that no one will believe you, by Pavel SamsonovDino Frankehad this to say..Measurements can sometimes be messy. Because design lives at the intersection of business goals and human behavior, the biggest challenge is getting teams to agree on which metrics truly matter before starting the project.AI PromptThis prompt helps you close the loop between a design initiative and the business outcome it was meant to drive.Start with one initiative that has gone through findings and decisions but hasn't yet been connected to a measurable outcome. It guides you to:Map the initiative through all four layers: Initiatives, Findings, Decisions, and OutcomesIdentify which layer is missing or broken using the 15-symptom diagnosticApply the right calibration from the five-dimension maturity modelFrame the outcome as direction-of-travel proof rather than a single precise numberYou'll end with structured proof of impact that's ready to share in a leadership update, not assembled after one.Use this after any significant design effort when you need to show what the work actually changed and connect it to a business outcome leadership can verify.AI SkillThe Results skill file teaches your AI the full four-layer Project Work loop and maturity model so it can help you close the gap between any design effort and the business outcome it was meant to drive.Load it when you need to go deeper on the 15-symptom diagnostic, the five Dimensions of Design Maturity, or using the University Website case study as a reference for what a complete Results loop looks like in practice. It gives your AI:The four-layer Initiatives to Outcomes loop with the break-identification processThe five Dimensions of Design Maturity with scoring rubric and micro-actions for eachThe complete 15-symptom diagnostic with verbatim calibration tipsThe Results Alignment Checklist and the University Website case studyDownload the skill file below to use the full Results framework with your AI assistant.

Related links

Kevin Waltz

Walks through psychological drivers like autonomy, achievement, novelty, and recognition that shape how users engage with a product. Useful when making engagement features and you want a psychology lens on what to build.

Stacey Barr

Provides a decision tree to figure out whether a result actually needs a KPI before adding one, to avoid metric overwhelm. Useful when leaders keep asking for new KPIs and you want to push back with a process.

Kristy Sullivan

Kristy Sullivan groups UX outcome metrics for digital products, including revenue, conversion, and customer acquisition cost. Useful when a designer needs to tie design work to business-facing outcomes.

Identify where decision quality breaks down

The Glare Design Assessment helps teams spot weak validation, stakeholder friction, alignment gaps, and assumptions that scale without measurable learning—so you have a clearer starting point for improvement.

About 5 minutes · Team-based · Diagnostic snapshot you can act on

Take the Design Assessment