The journal

Product thinking · 8 min read

Design for outcomes, not output.

Connect your design work to the change people need—and use AI to help measure whether it happened.

A shipped screen is output. A customer who can now finish a task faster, with fewer mistakes and more confidence, is an outcome. Excellent design work is judged by the second. AI makes output dramatically cheaper, which makes the discipline of designing for outcomes more valuable, not less.

Write the outcome before the brief

Describe the change you want in a person’s situation, in plain words: “New account owners can invite their team without contacting support.” Then name a signal you could observe: completed invitations in the first week, fewer related support tickets, or successful task completion in a usability test.

An AI assistant can help you draft possible measures and spot ones that are easy to game. Choose the measure with your product and engineering partners so everyone agrees on what success means before design starts.

Map the path to the outcome

List the steps someone takes from the moment they need the outcome to the moment they have it. Mark where people hesitate, drop off, or ask for help, using whatever evidence you have. This map shows where design can make the biggest difference, which is often not the screen everyone was planning to redesign.

Define success and guardrails together

Every change can improve one thing while harming another. A faster checkout should not create more accidental purchases. A shorter onboarding should not leave people confused later. Pair each success measure with a guardrail measure you will watch at the same time.

Use AI to learn after launch

After release, AI tools can help summarize open-ended feedback, cluster support conversations, and draft a readout of what changed. Keep the same discipline as in research: cite the source data, separate observation from interpretation, and check the summary against the numbers. A tidy narrative is not evidence that the outcome happened.

Close the loop

Share what you learned, including when the change did not work. A design team that reports outcomes honestly earns more trust and better problems to solve. Over time, a record of outcome-focused decisions becomes the strongest portfolio a designer can have.

Try it yourself

Pick a feature you designed recently. Write one sentence describing the outcome it was meant to create, one signal that would show it worked, and one guardrail. Then find out whether anyone has checked.

Keep learning

A better brief for your AI design partner.