3 min read

[Weekly Retro] Solution looking for a problem

#39 - Mar.2024

Happy Friday!

Here is a quick idea before you head off for the weekend:

Signals that you are trying to find a problem for your solutions instead of working backward from your customer’s needs: 

  • You stop experimenting.
  • Struggle to clearly name who is your customer
  • Refrain from being curious to learn more about the problem
  • Not able to explain how big is the pain (or the opportunity)
  • Lack of data points (facts or anecdotes) to support your hypothesis
  • You start from the technology with the hope of fitting the solution
  • You focus on the feature delivery throughput rather than the value
  • Adopting any technology trend without assessing how it fits the end purpose

Start with the problem. Always.

Post from this week

Generative AI: what is left for creators?
#98 - Knowledge bites on tech innovation, design, and creativity. Generative AI: what is left for creators. Ideas on the impact and opportunities for the creative industry.

Interested in more ideas like this one? Check out and subscribe to my blog where you’ll find more knowledge bites on design, innovation, and technology. Takes less than a minute!

Interesting links I found during this week

How Accessibility Standards Can Empower Better Chart Visual Design — Smashing Magazine
Accessibility for data visualization extends well beyond web standards, at least if you’re trying to create an experience that’s actually useful. This article focuses on techniques for creating useful and accessible visualizations that extend well beyond compliance.
The Interview Snapshot: How to Synthesize and Share What You Learned from a Single Customer Interview - Product Talk
Use this one-page template to summarize and share what you learned from each and every customer interview.
The 3 capabilities designers need to build for the AI era
The reverse reckoning of UX design.

Quote of the week:

"Explain what you learned to someone else. Teaching forces learning." - Naval Ravikant