Checking for relevance · The AI Advantage

Checking for relevance

Vibe coding is great, but what I keep seeing is people shipping loads of solutions that then go on a desperate search for a problem. Plenty of solution shipped, problem still (partly) unsolved.

find below some key questions you really should have absorbed BEFORE:

Problem Statement - Who has the problem? What is it? Why does it matter?
Competitive Research - What already exists? Why is your approach different?
Jobs to be Done - What progress are your users trying to make?
Personas - Who specifically are you building for?
Interview Script - How would you validate your assumptions?
Product Document - Vision + outcome-driven requirements assembled from all the above.

You can run this in an existing repo or for a new project, and it chases you through the types of hard and uncomfortable questions that are better asked before than after, and produces a hardened scope for whatever it is you want to build.

6 comments