from Savvy 2020
You can consider pivoting as well. Change the scope, or package your product, or target other users, or change the product itself.
How should we be designing in a situation where so many things are changing?
- UX Process that we used universally
Universal method not only for design but also IT. It focuses on how to design innovative products.
In software design, it places its core value to make products that can be sold in the market while minimising the time and resources required.
5-day process for resolving problems and testing new ideas.
The goal of the design process is to find a solution for major design problems by turning design problem to a validate prototype
Possible to see the outcome earlier or more frequently suing prototyping. Prototypes determines whether the processes is going the right direction and are the essential element getting feedbacks from the users.
Follows the concept of the Lean UX. It can start from the generated prototype to capture users needs and ends with evaluated prototype to validate the final solutions.
Prototyping should be used rapidly throughout the UX process.
We should get rid of the idea of “we know about the users”, we actually don’t know.
- Validate existing products: If there is no changes in the used environment or constrains, but there are some changes in users’ need. It is necessary to re-verify the current concept about your products. The target users group may have changed a lot from the previous device persona
- Build new products + Digital Transformation: you need to adapt digital transformation when you build the products therefore you can have more chances to succeed in the changing market
- Improve Accessibility: improve the product more accessible in the environment
Valuable wordings: Spend more time on prototyping and verifying based on user research.
Q: How can we prototype data-heavy project, such as dashboard design which really data and key contents will influence user experience?
A: You can define some typical scenarios. Upon the predefined scenario, you can make some prototype with dummy data. In order to make prototype in dummy data, you should define what the main proposal the prototype is.
Q: Would you recommend a design team to start with low-fidelity prototypes first then increase the fidelity level as we iterated it, or use high-fidelity one from the start as users usually interact better with them.
A: I would like to recommend start from low-fidelity and ends with high-fidelity because the proposal of the low-fidelity prototypes are total different from the high one. Basically low-fidelity prototype aims to verify the userflow or basic layout and requirement of the features. Then you make it more sophisticated and functional, also some graphical things. You can run user research on low-fidelity prototype too