A strong MVP contains only what a selected user needs to reach one meaningful value and what the team needs to measure behavior. Anything that does not change the test result can wait.
An MVP is a business experiment
The purpose is not to prove that the team can build an app. It is to gather evidence that a specific user chooses the new solution and receives value.
What usually stays
A clear entry into the core workflow
One complete moment of value
Minimum error handling and security
Behavior measurement
A channel for qualitative feedback
What can usually wait
Complex roles and permissions
Complete back-office automation
Many variants of the same workflow
Personalisation without evidence
Features included only because competitors have them