Focus on the problem first, then determine which technology enables the solution
Start with the user problem and desired outcome, then evaluate which technology best enables that solution. Don't lead with technology choices (AI, automation, etc.) before understanding the core problem.
When to use
When planning product features or considering new technology adoption; when evaluating whether to automate something
Don't do this
Deciding to use a specific technology (AI, blockchain, etc.) before deeply understanding the user problem
5 Founders Who Did This
Focus on problem-solution fit before adding AI features - technology should enable the problem you are solving, not define it | Evidence: Anton came from physics background: "Don think about technology first because you want to solve the problem and then figure out what technology can enable it." This principle guided both Depict.ai (ecommerce merchandising problem) and Lovable (software creation bottleneck problem).
Solve a specific, painful problem rather than building a general-purpose solution
Chose web personalization as starting point after evaluating where abundant data existed, ownership was unclear (easier to sell), integration was minimal (just JavaScript), and demand was proven.
Focused on the software problem rather than hardware - partnered with existing CGM manufacturers (FreeStyle Libre, Dexcom) to avoid building physical devices, and invested in the software layer that translates raw glucose data into actionable behavioral insights
Identified that no one had integrated travel agents and clients into a single technology system. Focused on the problem (agents lack agile tech infrastructure) before determining the solution