Member-only story
How to translate insight into product design differently.
Translating useful information into actionable steps and valuable experiences through two simple considerations.
After talking to several Product designers, the problem of translation of insight into product design to create value and emotion seemed to be quite challenging, so I started to think about how to do this translation more effective by reflecting about my own process and making it conscious:
- Think about what behavior you want to change or encourage in users, not only about product features or requirements.
The first step to avoid this, is to link behavioral outcomes to product requirements and specific interactions. If you are making a banking app and one of the requirements is to show expenses more clearly, think about what would help users in your context, for example, if users are using installments and credit to make ends meet but then end up paying a lot of interests, what would help them change this habit? What would help them spend more wisely? The N26 banking app has this great interaction where you scroll and you see how your budget has been increasing or decreasing in time:
