Sometimes known as use cases, storyboards, user flows, or user scenarios, they come in many flavors. But no matter what you call them, you know that you need them - a documented set of the high-level things you're trying to solve.

The steps are simple. As soon as the team shares a baseline understanding of their target personas and the competitive environment, an in-person working session is a great way to get all of the possible ideas - from the most basic to the most earth-shattering - out on the table for evaluation, sizing, and prioritization.

Leading software methodologies offer a starting point with the time-tested user story structure:

As a {role}, I want to {goal/desire} so that {outcome}.

Working with client teams and users, the team at Slide UX digs even deeper, asking questions like:

  • How does he know he needs to do this?

  • Why does he want to do this?

  • What information does he need to do this?

  • How does the user achieve this outcome? (in this product or elsewhere)

  • What are the problems with the way the user currently does it?

The outcome? A documented and validated vision. Marching orders toward a better tomorrow for your users and ultimately, your business. And a starting point for the design exercise that will visualize your solution.