The problems of first products
We often don’t know what the problem or the need is and we just think it’s a good idea. Product teams don’t iterate enough and don’t focus on the people that are going to use the system.
Users are spoiled with fast interfaces and user therefore gets frustrated if the system doesn’t work. The interface needs to become invisible, after using it for a few moments; the interface becomes automatic and intuitive
Work with users, asses the work done and asses the feedback.
Why should you prototype?
- It’s a highly valuable tool with the purpose of rapidly creating an approximation of the product.
- It enables to get feedback and insight right away. Try, learn and then improve.
- Understand concretely what you are proposing – learn how to deal with the unknown unknowns.
- Don’t stay long on the wrong path. It’s not the final product; it’s not worth going to the extensive details
What strategy should we follow?
- Focus on the goals of the design – you need concrete goals. Set the goal in early days.
- Early on you should be thinking on broad ideas and then in details (fonts, colours).
- Do serial iteration. Consider the cost of changes. Big changes in products represent a very high cost. In software is low in comparison with physical products but it is still substantial. People also tend to get used to software and changes can confuse them and upset them
What should you prototype?
- Feel: how does it look
- Implementation: How does it work
- Roles: Experience of using the system, basic user vs. advanced users
———
Subscribe to our monthly newsletter
Receive a summary of the daily tips, files you can work with and other products directly to your inbox!
Have any questions about this post? Contact us, we will be happy to help!
We won’t spam you, we promise.