Start with a task, not a feature list.
Write down the one thing a customer should be able to accomplish. Design the smallest complete journey around that task, including what happens when something goes wrong.
Make learning part of the release.
Decide what you want to learn before development starts. Pair usage patterns with conversations. A feature being used does not always mean it is solving the right problem.
Leave room for what comes next.
A focused first release still needs reliable foundations: accessible interfaces, sound data handling, and a codebase the team can maintain. Keep the scope small without making the experience feel unfinished.