Usablity principles for MVP

"Viable" Implies Usable: Distinguishing clearly between "feature-poor" and "hard to use." An MVP can have fewer features, but the few that exist must work flawlessly. If the interface blocks the user, you aren't testing your business idea, you are just testing the user's patience.

The Red Route Strategy: Focusing 90% of design effort on the Critical Path—the specific sequence of actions the user must complete to receive value. Polishing this single flow to a high standard is non-negotiable, while secondary features can remain raw.

Consistency > Innovation: For an MVP, adopt standard UI patterns (like Material Design or native OS conventions) rather than inventing new interactions. Familiarity reduces the cognitive load, allowing users to focus entirely on the utility of the product rather than learning how to navigate it.

Feedback as a Primary Feature: Integrating feedback mechanisms directly into the interface (e.g., a "Send Feedback" widget or "Did this work?" toggle). Since the goal of an MVP is validated learning, the UI must make it effortless for users to report friction points immediately.