There’s No “Shitty” in MVP

Lean Startup isn’t responsible for the deluge of crappy products being released by mediocre startups.

Erick Schonfeld makes that suggestion in his recent post Details Matter. I’d argue that the mainstream usage of things like Twitter and Facebook (along with social media’s ability to create incredible influencers), lower costs and barriers to entry (development is easier/faster), and the popularization of startups overall, has collectively increased the volume of startups. Startup founders are now celebrities. I suspect that the economy plays a role too; when college students look into the job market and see fewer and fewer opportunities, the alternative is to do something on your own. None of these things have anything to do with Lean Startup.

If anything, Lean Startup has grown popular in response to the overwhelming volume of startups launching (and failing), because more entrepreneurs need more help.

Erick is right on one point though: details matter. They matter a lot. And no one has ever argued otherwise. Just look at a Lean Canvas and the constraints it provides, and you understand (in this case for designing your startup) just how detail oriented you have to be. There’s no room in a Lean Canvas to be anything but detailed. The same holds true when thinking about user flows, user acquisition, and the overall experience in your application.

Erick also suggests “crafting something really extraordinary,” which makes perfect sense. That should be your goal. You should be selling magic not technology.

The question of course is how you define “really extraordinary”?

If you’re thinking solely about design or “polish” you may build something that’s beautiful but not valuable. Design can be crucial, but by itself it doesn’t create enough value. And I think this is what Erick is suggesting — that you need to be extremely attentive to the details around polish and design. Turns out it’s extremely hard to do, most people won’t get this right, and most will fail. But more than that, most will fail to create value. That’s just the reality of things.

The acronym MVP stands for Minimum Viable Product not Minimum Shitty Product.

Lots of people will create shitty products. It’s just the way it goes. Lots of people will also create beautiful products that are still shitty because they don’t provide enough value. Lean Startup provides a learning framework for recognizing mistakes and not repeating them. Most importantly, it provides a framework for trying to understand value creation for customers, which is what really matters.


Performance vs. Features — Which is More Important?

It’s fairly well understood at this point that performance is a critical aspect of building for the web. Better performance typically means better results (for whatever you’re trying to get people to do.) E-commerce transactions go up. Sign-up conversions go up. And so on.

The same holds true with B2B / enterprise software. People will overlook all kinds of product and feature limitations if performance is amazing. Part of the reason is that they’re able to more quickly create & discover workarounds that they’re willing to live with, in exchange for top notch performance. I’m more willing to change my behaviour, adjust how I work, or lower my product expectations if performance is fantastic. When performance is bad, every workaround or product limitation is magnified many times over.

Recently I was involved in a product purchasing decision. I won’t name names (it doesn’t matter.) One product had limited features for what I was looking to do (in part because it’s a “generalist” product and not a “specialized” product — perhaps a debate for another time), while the other was specialized for my needs (vertically-focused). We first went to the specialized product, but then moved to the generalist product (because the product breadth was wider.) As we used the generalist product, we talked through and experimented with different workarounds to address the product’s limitations. It wasn’t a big deal initially, every product has limitations and fitting them into your existing processes and workflow requires some massaging. But after a couple days, we went back to the specialized product.

Why?

Performance.

The specialized product provides more functionality as well – which is handy – but more importantly, it’s fast. Working within the product is a joy vs. frustration, and it makes it easier for me to encourage use of the product amongst other team members as well. At one point someone suggested using Google Spreadsheets. Why? It’s fast. We knew Google Spreadsheets wouldn’t scale, and we didn’t really want to use it, but it’s easy, convenient and fast.

It’s also important to note that the specialized product is more expensive than the one we abandoned (~5x more expensive). Cost was never part of our decision-making process, except initially when we thought we could use the generalized product for more things (instead of going vertical.) And we would have, if performance had been there.

The importance of performance for B2B software and enterprise applications is only going to increase.

With a bigger move to mobile devices (especially in the enterprise), people want all the power and functionality in the palm of their hand. Performance has a huge impact on uptake (which is always challenging in the enterprise) and long-term adoption. People will “suffer” a lack of features if they can still get things done quickly.


The Curse of Knowledge in Product Design

You know your product best. You know every feature, how it all works, the bugs, nuances and hiccups too. You know what’s coming next in the product roadmap. You definitely know more than your customers, right?

Yup, you have the Curse of Knowledge.

The Curse of Knowledge is described in Dan and Chip Heath’s book, Made to Stick. The basic concept is that the more you know about a subject (the more you become an expert) the harder it is for you to communicate your knowledge. The more you know, the harder it becomes to understand and appreciate that others don’t know as much.

Startups are often struck by the Curse of Knowledge, specifically when it comes to product design and development.

It becomes so easy to design products based on our own expertise (in those very products) and ignore the fact that we’ve stopped designing with our customer top of mind. This is when you start to see meaningless icons and clever UIs (or just plain confusing UIs) bubble to the surface. Icons and clever UIs are easy to use when you “know everything about the product” and make the assumption that others know as much as you, and will respond the same way. Des Traynor has a great blog post about this: The Language of Interfaces. One of his key points is, “clear first, clever second.”

The Curse of Knowledge pushes us towards clever and complex, because we’re already such experts in our own products we want to take them to “the next level.” Except too often, we’re leaving customers behind.

The first step to solving the problem is to genuinely recognize that you have the Curse of Knowledge. Then keep that top of mind – and more importantly, keep your customers front and center – whenever doing any product design and development. Make sure you do usability testing with customers and non-customers (because you want to know how well non-customers on-board into becoming customers!) Make sure you test. Make sure you listen. Make sure you simplify, simplify, simplify. Make sure you talk in your customer’s voice when designing your product. Really put yourself in their shoes and brain space. The Curse of Knowledge can quickly ruin a good idea and a good product. It might not be obvious immediately, but over time, iteration after iteration, as your product gets more complex and confusing, it will lose what customers originally loved about it. And you may not even notice, or know why customers are leaving, if you don’t face the Curse head on.


Ben Yoskovitz
I'm VP Product at GoInstant.

I'm also a Founding Partner at Year One Labs, an early stage accelerator in Montreal. Previously I founded Standout Jobs (and sold it). MY BIO >>

Follow this blog via email

Advertisement
Startup Resources
A collection of posts I've written over time on key subjects:

Find Stuff
My Photos