In the second workshop, we go a level deeper and focus on the product itself; we talk about what and for whom we want to build it. We focus on the app users and how they will use it, both end-users and users managing it, such as admins or the support team.
User journey mapping is an essential tool during design workshops. It's a framework thanks to which we learn about the real needs of the users. We recreate product usage scenarios by the end customer.
For example, suppose we create a tool for ordering food. In that case, we recreate the entire process, from placing the order via the app, through the restaurant accepting and delivering it, to the end-user receiving the order.
The result of Design Workshops is a product sketch or a simple prototype that visually shows what we want to build. Importantly, creating such a prototype often occurs in real-time during live design sessions, where the designer talks to the client and makes a live interface sketch.
Example questions
- What is the main benefit of the app for the end-user?
- How often do people use your app?
- Under what circumstances?
- Do users use the app once, or do they come back regularly?
- What is the key feature for the user?
- How many and what steps do users take in our app?
- What application design do you want?
- What should the app's interface look like?
- How do you want to stand out from your competitors?
Match theory with practice
Thanks to Design Workshops, you will see your application with your eyes for the first time. Finally, after weeks, months, or even years of planning and theorizing, you will face your solution's (very basic and general) prototype.
Because we'll talk about specific features, their complexity, and the visual side of the product (which has a large impact on the final cost), you will learn with greater precision what the final price of the application will be. At the design workshops stage, we define the budget with an accuracy of approx 85%.
In addition, when creating sketches and mockups, we immediately create visual documentation on which developers will base their sprints. It will be the backlog of the project.
