The Fastest Growth Test Is the Feature You Cut
An MVP is defined by what it leaves out, not by what it ships.
A method that works in scope meetings:
1. Name the one job. One user, one problem, one finish line.
2. Write the cut list. Every feature that job doesn't need goes on it, in writing.
3. Give "later" a trigger. "When 50 users ask" or "when we sign a second market". No trigger means it stays cut.
An MVP that isn't minimal delays feedback and blurs what the test proved.
What was the hardest feature you ever cut?