Discussion about this post

User's avatar
Brian Austin's avatar

I understand the need to pivot quickly and to stop working on the wrong things, given user feedback. But there is a real risk, in some industries with putting an incomplete MVP in front of people when you are trying to disrupt an incumbent software system.

Karthik Hariharan put it this way "A simple MVP won’t cut it. Your competition is no longer non-software solutions. It’s probably existing, but suboptimal software. Which means if you’re going to compete with it, your software needs to be significantly better."

It may still work in B2C markets, but B2B will have a lot of boxes to check and that can lead to an awkward conversation if your product is missing too many key features.

Expand full comment
Akos Komuves's avatar

Jumping aboard the enterprise software development team after years of freelancing, I can see what you're talking about. 😃

Yes, we had a long planning week, but the POC feature I'm going to build in the next two months will be released for preview. We haven't made any plans for perfecting it; we just want to get it out to the users, see how they'll use it, and then move forward or kill the feature.

I think anyone who can reduce a feature to a shippable product that can be done in a reasonable amount of time can follow this pattern. Of course, that requires being critical about "must have" and "nice to have" features and lowering your expectations for the initial round!

Expand full comment
9 more comments...

No posts