<aside> 👉 User research provides insights into how users behave, how users experience or think about a product, and more. Your research findings will help you understand how to design your product based on what your users really need. →Your goal is to generate as many ideas as possible for potential solutions to the user problems you’ve identified.
</aside>
A goal statement is one or two sentences that describe a product and its benefits for the user. → the ideal solution for your design challenge. → based on the problem statement
Goal statements cover who the product will serve, what the product will do, and why the product solves the user’s need.
Transition from identifying the problem to defining the goal. → can be a single, specific goal or a greater idea that you’ve chosen to be the focus of your design
<aside> 👉 Our [product] will let users [perform specific actions] which will affect [describe who the action will affect] by [describe how the action will positively affect them]. We will measure effectiveness by [describe how you will measure the impact].
</aside>
A user flow is the path taken by a typical user on an app or a website, so they can complete a task from start to finish.
<aside> 👉 Keep in mind that the user flow could change based on the needs of users and their circumstances.
</aside>
A storyboard is a series of panels or frames that visually describes and explores a user’s experience with a product.
The four key elements of a storyboard are:
Character: States the user in the storyboard.
Scene: Gives designers a way to imagine the user’s environment.
Plot: Describes the solution or benefit offered by the design.
Narrative: Describes the problem the user is facing and how the design will solve this problem.
Big picture storyboards focus on what the user needs, their context, and why the product will be useful to the user. Big picture storyboards are often used early in the design process when designers are trying to get stakeholders to support their ideas.
Start with problem statement→ build goal statement→ add a scenario → fill the storyboard panels → show pain points → conclude with the user goal
→The storyboard should show how people use your product and why your product will be helpful to them.
Close-up storyboards concentrate on the product and how it works. They’re best used in the middle to the end of the design process.
open app→ sign in/up → homepage → menu → order preview → payment
<aside> 👉 A design solves a real problem that users are experiencing. And a strong design always puts the user front and center.
</aside>