A first version can be small, but its scenario must be complete. Half of every feature is usually worse than one journey that reaches a real outcome.
Choose one change
A sound MVP tests one transition: a user gets access faster, a manager stops copying data, an owner sees payment status. If version one promises to change the whole business, the boundary is not defined.
Complete the journey
The scenario has an input, processing, outcome and failure state. Analytics, roles and ten integrations can wait; leaving the user with no clear result after a click cannot.
Write down what is excluded
An exclusion list protects the timeframe better than a wish list. It makes tradeoffs visible and stops every new idea from quietly becoming mandatory.
Leave an evolution path
A small version does not have to be disposable. Data structure, states and critical interface decisions should allow the next scenario without a full teardown.