Graham McNicoll

Most product teams spec out the entire feature before they've shipped a single line of code. The real question nobody is asking first: what indication do you have that this product is actually worth building? We use a framework called HAMM. Hypothesis, Actions, Metrics, and MVP. What are you actually trying to build? What actions would a user take to indicate your hypothesis is true or false? What metrics would confirm those actions? And what is the smallest thing you can build to validate the assumption? That last one is where most teams get it wrong. They skip straight to building the full feature. The goal is to know what is worth building before you commit to it. What is the smallest thing you could ship this week to validate your next big feature?

Only one snapshot so far — the engagement-over-time curve appears once the daily scrape has captured this post at least twice.