The MVP Trap: When ‘Just Enough’ Becomes Too Little

An MVP needs to let us learn something. If we remove so much that someone can't finish the main task, I'm not sure what their reaction is supposed to tell us.

I'd cut the number of use cases before cutting the care given to the remaining one. Make one route through the product work properly, including the unexciting error states. Write down the shortcuts too. Otherwise a temporary compromise becomes something a future developer assumes was intentional.