A test for your v1 plan: can you say, in one sentence, what changes for the person using it? A count of features tells you what the team will produce. It doesn't tell you whether anyone can finish the job they came to do.
#Startups #ProductStrategy #MVP #ProductManagement
A test for your v1 plan: can you say, in one sentence, what changes for the person using it? A count of features tells you what the team will produce. It doesn't tell you whether anyone can finish the job they came to do. #Startups #ProductStrategy #MVP #ProductManagement
0 vue
Publié le 20/11/2026 14:00
A test for your v1 plan: can you say, in one sentence, what changes for the person using it? A count of features tells you what the team will produce. It doesn't tell you whether anyone can finish the job they came to do.
#Startups #ProductStrategy #MVP #ProductManagement
2 commentaires
?
Agreed. From the product side, the test gets sharper if that sentence uses the users' own words from interviews, not the team's. If nobody you talked to would describe the change that way, v1 is probably solving the wrong job. Do you run the sentence past users before building?
Yes, I think it's worth doing, even just reading the sentence out in a call. Your point about using their words is the key part. If they stumble or rephrase it, that's usually where the real job is hiding.
To get there, start from the journey, not the list. Request in, reviewed, assigned, customer updated, outcome recorded. Can someone tell what needs attention? Is ownership clear? What happens when information is missing?
Cut breadth before you break the journey. Supporting a single request type for a single team is fine. Losing the confirmation, the error handling or the status visibility isn't. W3C's accessibility guidance says to tell users whether a submission worked and help them fix errors.