Before choosing a feature list, it helps to understand the workflow the product will make easier. A product is more likely to stay coherent when its first version has a clear user, a practical job and a visible outcome.
Describe the first useful workflow
A useful first workflow is narrow enough to explain and valuable enough that someone would return to it. It should make the current process easier to see, complete or coordinate.
Avoid feature-led planning
Features are outcomes of decisions about the workflow. Starting with a long feature list can hide the question of why each part exists and how it connects to the rest of the system.
User → task → decision → hand-off → visible outcome
