Scenarios

PDF: About Scenarios + Examples

How to write Scenarios

• Identify the changes to your redesign that you will want to create user flows for and test eventually. 
• Then write scenarios that revolve around these changes to your product and how they relate to your existing personas. 
  • For example, are they trying to post a photo, subscribe to a newsletter, join a watch party, buy something…? How will these tasks fit into their life? Why do they need to achieve these tasks?
• These scenarios can come in different formats, you can choose what works best for you:
  • Short and sweet – to the point, but still providing who the user is, their need, and their goal with the product, as well as naming the scenario. 
  • or
  • Long and detailed – this can be more descriptive, providing further context and more about their motivations and expectations. 
• A simple formula can be used for the short and sweet method if you like? It is up to you though: 
  • As a [type of user] they want to [some goal] so that [some reason].

---

User Flows

PDF: Understanding Navigation

PDF: About User Task Flow + Examples

How to create a user task flow diagram

1. Look at each scenario, which describes the persona, their need, and goal with the product. What task are they trying to achieve with it?
   • For example, are they trying to post a photo, subscribe to a newsletter, join a watch party, buy something…?
2. Write out each step and include each screen it takes to achieve the task, from opening the product to reaching the end goal. 
   • You can do this with just rectangles and written text and labels.
   • or
   • You can do this with rectangles to demonstrate screens and diamonds to represent different decisions/options on each screen.
3. You need to then draw arrows between connecting each step in one direction. 
4. Don’t forget to name the user flow diagrams, with what you are trying to achieve, or simply just pair the written scenarios with each one. 

Tips

• Remember user task flows go in one direction, and show all the steps for one specific task, for one specific scenario at a time. 
  • This is different from a site-map which shows the entire product’s branching structure all at once. 
• Also, you do not need to create user task flows for sections of the product redesign that you are not changing at all.
  • For example, if you aren’t making any adjustments to the profile section/screen, then you do not need a user task flow diagram to reach that screen.

How to Turn In:

1. Scenarios for each of the new features or adjustments you are implementing in your product redesign. These scenarios should be addressing your user personas.
2. User Task Flow Diagrams for each scenario. (You can use InDesign, Illustrator, Power Point, Google Slides, or Invision Freehand or Figma – whatever you feel most comfortable in.)
3. Format is up to you: Can turn in a clear photograph or scan of your hands-on process, or link to Figma, Figjam or Invision Freehand board, or designed in Illustrator or Google Slides? Whatever makes the most sense for your team!