Start with the problem
Describe who you are helping, the task they need to complete and why the current approach is difficult. A clear problem statement is more useful than a long feature list.
Choose one meaningful outcome
Decide what a successful first release should help someone do. Use that outcome to separate essential functionality from things that can wait.
Test the uncertain parts early
A prototype or small pilot can reveal whether the workflow makes sense before a larger build begins. Record what you need to learn and how you will judge it.
Plan for the next decision
An MVP is a starting point. Agree how feedback will be gathered, who will review it and how the next investment decision will be made.
Have a question about this article? Contact Stacklark.