Simon Joliveau Breney

3. Start with the problem, not the solution. It’s tempting to jump into ideation but we are often wrong about the underlying problem. Make sure the problem is clearly stated and communicated.

But learning how to think with visual information (not just react to it) requires a different way of seeing, one that enables you to pause the instinctual labeling and stereotyping of the visual images you’re processing and see the individual elements in the image

We keep telling ourselves that previous voice interfaces like Alexa or Siri didn’t succeed because the underlying AI wasn’t smart enough, but that’s only half of the story. The core problem was never the quality of the output function, but the inconvenience of the input function: A natural language prompt like “Hey Google, what’s the weather in San

168 hours is enough time to work 50 hours a week, sleep 8 hours a night, and still spend massive amounts of time with your children. But since all hours aren’t created equally, making this come out right involves moving around chunks of hours like puzzle pieces.

Moving from feature teams to empowered product teams is at the core of changing how you solve problems, and this involves introducing real product discovery skills. Yet it’s easy to just continue doing the design and development of new features, but now pretend this is product discovery.

The key is whether or not the solution generates the necessary