The MVP trap that keeps catching first-time founders

Watching another founder friend pour six months into building "just the core features" hurt to witness. By the time he launched, three competitors had already validated the market with uglier, simpler products.

The harsh truth I've learned? Most devs (myself included) over-engineer MVPs because we're solving for scalability instead of learning. We build for millions of users when we have zero.

Finally started looking at how successful lean startups actually structure their initial builds. The approach is almost minimalist enough to test assumptions, nothing more.

Been reading through some methodologies that have completely shifted my perspective on what an MVP should actually look like.

The mindset shift from "build it right" to "build it to learn" is deceptively difficult. What's your take on MVP scope these days?