During an early venture exploration, our team listed a wide range of everyday problems. Nearly every idea had a plausible trend and market story. The list only began to narrow when we asked whether we could test those stories against something a real user had recently done.
We screened each opportunity for three things: access to users, whether we could observe the key behaviour within the project, and the responsibility our team could feasibly take on. Some promising directions had to wait. For some, we could not get specific enough feedback. Others exceeded our capacity or added breadth to the presentation without addressing the core problem.
Problem framing and prioritisation tools helped us record why each option was dropped. External feedback recognised the work at that stage. Market demand and repeated use still needed testing. When I revisit an early project, I look for the assumption that changed, the reason the direction shifted, and the evidence that would justify further investment.