<aside> 💡 This document provides a high level overview of the product that you are building. It describes the business process behind the app and each step in that process. This is a place where you describe user journey, workarounds, friction points and everything that will contribute to understanding of users steps. But to get there, first you need to interview your users and test your hypothesis defined in the
</aside>
<aside> ℹ️ Why is this document important: to understand end-to-end scenarios (users’ journey) for each role, and to understand the information architecture and business flow for each of the features. This will be a starting point for the development team to break down work items into epics. Understanding the process will help the team in making decisions and building better solutions.
</aside>
The best products are build with user-centric approach in mind. So start building your product by writing down observations from your user interviews and contextual analysis. There are 4 steps for you to better understand the users and their needs:
<aside> 💡 Now that you finished all the interviews, put your observations in the empathy map. This will help you better understand your users, and structure your hard earned insights. The structure will help you cluster the needs and common patterns that the users expressed during the interview.
</aside>
After you finish with user interviews, contextual analysis and classification of your interview notes, you are ready to identify and specify user pains and gains. In other words, you will be able to understand what users want and need, and what are they frustrations and bottlenecks in their current solution.
<aside> 👉 Now that you got a certain level of understanding, you can start with creating a user journey map. A journey map is a visualisation of the process that a person goes through in order to accomplish a goal.
</aside>
| Journey Steps
| Which step of the experience are you describing? | Step 1 | Step 2 | Step 3 | End Goal |
|---|---|---|---|---|
| Actions | ||||
| What does the customer do? | ‣ | ‣ | ‣ | |
| Needs and pains | ||||
| What does the customer want to achieve or avoid? | ||||
| Satisfaction | ||||
| Describe the level of satisfaction for each step | 😱 | 😤 | 🙂 | 🤕 |
| Opportunity | ||||
| What can be improved or introduced? |
<aside> 💡 Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. They ensure the usability and effectiveness of the entire system. Failing to meet any one of them can result in systems that fail to satisfy internal business, user, or market needs, or that do not fulfil mandatory requirements imposed by regulatory or standards agencies. In some cases, non-compliance can cause significant legal issues (privacy, security, safety, to name a few).
</aside>
Examples of NFRs: