Role
Product Designer
Timeline
7 days
Responsibilities
User research
UI Design
Prototyping
User testing
Tools
Brain
Figma
Jitter
I've gotten pretty annoyed many times with voice messages, especially long ones. Turns out, a lot of people feel the same way. So, that got me thinking ...
Research
I began by conducting desk research, exploring articles, Reddit threads and utilizing AI tools to gather insights. Then, I interviewed a mix of individuals to understand pain points they were experiencing with (long) voice messages.
Addresses these pain points:
🤔
I often forget a lot of what's said, especially the first part of the message.
🥱
Voice messages often drag on, with a lot of talking but not much useful info.
Addresses these pain points:
🤔
I often forget a lot of what's said, especially the first part of the message.
👨🦯
It's hard to keep track of what each voice message is about. They all look the same, so finding something specific later is a hassle.
Addresses this pain point:
🔎
There's no way to search for keywords or context within voice messages, unlike in text messages.
Addresses this pain point:
🤷♀️
I never really know how private a voice message is. Can I safely listen in public, or should I wait until l'm alone?
Reflection
Takeaways
During this project, I learned that you don't need fancy features to create effective solutions. Sometimes, the best answers are as simple as writing something down on paper, or in this case, on your phone. What matters most is that the solution truly solves the problem at hand.