It looks like a variation of needs-based design– a central user-centered practice. Outcomes would seem like an extension of user journeys that begin with insight around the core needs you’re looking to satisfy.

The only caveat I would add, is that needs can be validated researched, while outcomes are assumed until you’re able to test them through prototyping the service itself. Users will understand their own needs, but may not be able to describe desired outcomes until they see/experience it for themselves.

Written by

Experience Design at Netflix • Follow @kaigani

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store