Minimum Viable Product Quotes

As you consider building your own minimum viable product, let this simple rule suffice: remove any feature, process, or effort that does not contribute directly to the learning you seek.

Even in engineering-driven Silicon Valley, the buzzwords of the moment call for building a “lean startup” that can “adapt” and “evolve” to an ever-changing environment. Would-be entrepreneurs are told that nothing can be known in advance: we’re supposed to listen to what customers say they want, make nothing more than a “minimum viable product,” and iterate our way to success. But leanness is a methodology, not a goal. Making small changes to things that already exist might lead you to a local maximum, but it won’t help you find the global maximum. You could build the best version of an app that lets people order toilet paper from their iPhone. But iteration without a bold plan won’t take you from 0 to 1. A company is the strangest place of all for an indefinite optimist: why should you expect your own business to succeed without a plan to make it happen? Darwinism may be a fine theory in other contexts, but in startups, intelligent design works best.

In Silicon Valley, start-ups don’t launch with polished, finished businesses. Instead, they release their “Minimum Viable Product” (MVP)—the most basic version of their core idea with only one or two essential features. The point is to immediately see how customers respond. And, if that response is poor, to be able to fail cheaply and quickly.

When you first start off trying to solve a problem, the first solutions you come up with are very complex, and most people stop there. But if you keep going, and live with the problem and peel more layers of the onion off, you can oftentimes arrive at some very elegant and simple solutions. Most people just don't put in the time or energy to get there.

Perfectionism is a disease. Procrastination is a disease. ACTION is the cure.

The Lean Product Process consists of six steps: Determine your target customers Identify underserved customer needs Define your value proposition Specify your minimum viable product (MVP) feature set Create your MVP prototype Test your MVP with customers

Eric Ries, author of The Lean Startup, explains that the best way to get to Product Market Fit is by starting with a “minimum viable product” and improving it based on feedback—as opposed to what most of us do, which is to try to launch publicly with what we think is our final, perfected product. Today,

The main reason products fail is because they don't meet customer needs in a way that is better than other alternatives.

The MVP has just those features considered sufficient for it to be of value to customers and allow for it to be shipped or sold to early adopters. Customer feedback will inform future development of the product.

We do everything wrong: instead of spending years perfecting our technology, we build a minimum viable product, an early product that is terrible, full of bugs and crash-your-computer-yes-really stability problems. Then we ship it to customers way before it’s ready. And we charge money for it. After securing initial customers, we change the product constantly—much too fast by traditional standards—shipping new versions of our product dozens of times every single day.

As entrepreneurs, product managers, developers, and designers, we love to spend our time coming up with cool new feature ideas and designing great user experiences. However, those items sit at the top two levels of the pyramid of user needs. First and foremost, the product needs to be available when the user wants to use it. After that, the product's response time needs to be fast enough to be deemed adequate. The next tier pertains to the product's quality: Does it work as it is supposed to? We then arrive at the feature set tier, which deals with functionality. At the top, we have user experience (UX) design, which governs how easy—and hopefully how enjoyable—your product is to use. As with Maslow's hierarchy, lower-level needs have to be met before higher-level needs matter.

As a [type of user], I want to [do something], so that I can [desired benefit].

Here are descriptions of the five customer segments: Innovators are technology enthusiasts who pride themselves on being familiar with the latest and greatest innovation. They enjoy fiddling with new products and exploring their intricacies. They are more willing to use an unpolished product that may have some shortcomings or tradeoffs, and are fine with the fact that many of these products will ultimately fail. Early Adopters are visionaries who want to exploit new innovations to gain an advantage over the status quo. Unlike innovators, their interest in being first is not driven by an intrinsic love of technology but rather the opportunity to gain an edge. The Early Majority are pragmatists that have no interest in technology for its own sake. These individuals adopt new products only after a proven track record of delivering value. Because they are more risk averse than the first two segments, they feel more comfortable having strong references from trusted sources and tend to buy from the leading company in the product category. The Late Majority are risk-averse conservatives who are doubtful that innovations will deliver value and only adopt them when pressured to do so, for example, for financial reasons, due to competitive threats, or for fear of being reliant on an older, dying technology that will no longer be supported. Laggards are skeptics who are very wary of innovation. They hate change and have a bias for criticizing new technologies even after they have become mainstream.

What Info Should a Persona Provide? Good personas convey the relevant demographic, psychographic, behavioral, and needs-based attributes of your target customer. Personas should fit on a single page and provide a snapshot of the customer archetype that's quick to digest, and usually include the following information: Name Representative photograph Quote that conveys what they most care about Job title Demographics Needs/goals Relevant motivations and attitudes Related tasks and behaviors Frustrations/pain points with current solution Level of expertise/knowledge (in the relevant domain, e.g., level of computer savvy) Product usage context/environment (e.g., laptop in a loud, busy office or tablet on the couch at home) Technology adoption life cycle segment (for your product category) Any other salient attributes

Increasingly, product developers roll out what’s known as a minimum viable product (MVP).6 An MVP accomplishes the goal of the customer—it tracks your exercise, cooks your food, or monitors your blood sugar—with services and some style, to support the higher price tag it carries. Companies that ship MVPs know that they will improve them and that ideas for those improvements will be generated from the people who first use the product. As Stefan Olander, vice president and general manager of digital sport at Nike, puts it “Get going. Then get better.”7 Software development for websites and applications is undergoing a revolution, from huge complex projects and infrequent releases to the continuous, agile development cycles happening now.

The greatest thing Jobs designed was his business. Apple imagined and executed definite multi-year plans to create new products and distribute them effectively. Forget “minimum viable products”—ever since he started Apple in 1976, Jobs saw that you can change the world through careful planning, not by listening to focus group feedback or copying others’ successes.

first, use a minimum viable product to establish real data on where the company is right now. Without a clear-eyed picture of your current status—no matter how far from the goal you may be—you cannot begin to track your progress.

This philosophy teaches us to leave safe harbor for the rough seas of real-world experience, and to accept that a rough copy out in the world serves us far greater than a masterpiece sitting quietly on our shelves.

It appears, at least from my perspective, that each and every position in Jiu Jitsu regardless of the seeming complexity is really governed by no more than a handful of minimum viable products. Pursue to understand these essentials, and you will see that complexity is a myth perpetuated by lack of understanding, and it is this understanding which is possible for each of us.

The minimum viable product is the smallest product release that successfully achieves its desired outcomes.

Here comes the hard part… We’re just guessing. When we slice out a bunch of software functionality and call it a minimum viable solution, we don’t really know if it is. The problem with outcomes is that you can’t really observe them until things come out. When you slice out a release, you’re forced to hypothesize what will happen. You might have to guess about what customers will buy your product, what users will choose to use it, if they can use it, and what’s feasible to build in the time you have. You’re forced to guess at how much will make them happy. That’s a lot of guessing.

Some companies like Airbnb and Instragram spend a long time trying new iterations until they achieve what growth hackers call Product Market Fit (PMF); others find it right away. The end goal is the same, however, and it’s to have the product and its customers in perfect sync with each other. Eric Ries, author of The Lean Startup, explains that the best way to get to Product Market Fit is by starting with a “minimum viable product” and improving it based on feedback—as opposed to what most of us do, which is to try to launch publicly with what we think is our final, perfected product.

Forget “minimum viable products”—ever since he started Apple in 1976, Jobs saw that you can change the world through careful planning, not by listening to focus group feedback or copying others’ successes.

Good interviewers excel at listening closely to what customers say, repeating statements back to ensure understanding, and asking additional probing questions to illuminate the problem space.

I developed a framework and process for how to achieve product-market fit.

Apple imagined and executed definite multi-year plans to create new products and distribute them effectively. Forget “minimum viable products”—ever

But Triangulate’s team, like many entrepreneurs, neglected yet another Lean Startup precept: complete “customer discovery”—a thorough round of interviews with prospective customers—before designing and developing a minimum viable product. In Nagaraj’s postmortem analysis of Triangulate’s failure, he acknowledged skipping this crucial early step: “In retrospect, I should have spent a few months talking to as many customers as possible before we started to code.

Silicon Valley is famous for mantras like “move fast and break things” and implementing them through strategies like “minimum viable product” (MVP). These types of agile strategies can only work if you have the option to quit. You can’t put out an MVP unless you have the ability to pull it back. The whole point is to get information quickly, so you can quit the stuff that isn’t working and stick with the things that are worthwhile or develop new things that might work even better.

MVP Testing. Prototyping and prototype testing should proceed in iterative loops until a dominant design emerges. Based on test feedback, designers should reject some prototypes and refine others, producing higher-fidelity versions. Once they converge on a single, favored solution, it’s time for minimum viable product testing. An MVP is a prototype—a facsimile of the future product. What distinguishes an MVP from other prototypes is how it is tested. Rather than sitting across a table, getting verbal feedback from a reviewer, you put a prototype that seems like a real product in the hands of real customers in a real-world context. The goal is to quickly but rigorously test assumptions about the demand for your solution—and gain what Eric Ries calls “validated learning”—with as little wasted effort as possible.

Adapt what is useful, reject what is useless, and add what is specifically your own.

build an ideal model of the desired disruption that is based on customer archetypes, launch a minimum viable product to establish a baseline, and then attempt to tune the engine to get it closer to the ideal.

Demographic Segmentation Demographics are quantifiable statistics of a group of people, such as age, gender, marital status, income, and education level. Say you were developing an app for moms to easily share photos of their babies with friends and family. You could describe your target customers demographically as women 20 to 40 years old who have one or more children under the age of three. If you are targeting businesses, you'll use firmographics instead; these are to organizations what demographics are to people, and include traits such as company size and industry.

It’s best practice that an ICO also have a minimum and maximum amount that it plans to raise. The minimum is to ensure the development team will have enough to make a viable product, and the maximum is to keep the speculation of crowds in check.

Years later, Steve Blank and Eric Ries would dub this a “minimum viable product” (MVP). For LinkedIn, the MVP included a user’s professional profile, the ability to connect to other users, a search function to find other users, and a mechanism for sending messages to friends.

Ries wrote that startups operate in an environment of “extreme uncertainty” in which it is impossible to know whether the product they have developed is one that consumers will value. “We must learn what customers really want,” he advised, “not what they say they want or what we think they should want.” The only way to do that is to “experiment.” Create a “minimum viable product,” put it in front of consumers, and see what happens. With lessons learned, change the product, ship again, and repeat the cycle. Ries called this the building phase, as multiple iterations gradually build the final product. I would call it the planning phase, as the design of the product evolves following the dictum “Try, learn, again.” Semantics aside, the only real difference is the method of testing.

You can tell the level of collaboration by how often team members refer to one another as “we” instead of “they.

Customer discovery includes two outside-the-building phases. The first tests customer perception of the problem and the customer’s need to solve it. Is it important enough that the right product will drive significant numbers of customers to buy or engage with the product? The second phase shows customers the product for the first time, assuring that the product (usually a minimum viable product at this point) elegantly solves the problem or fills the need well enough to persuade lots of customers to buy. When customers enthusiastically confirm the importance of both the problem and the solution, customer discovery is complete.

Even in engineering-driven Silicon Valley, the buzzwords of the moment call for building a “lean startup” that can “adapt” and “evolve” to an ever-changing environment. Would-be entrepreneurs are told that nothing can be known in advance: we’re supposed to listen to what customers say they want, make nothing more than a “minimum viable product,” and iterate our way to success.

Apple imagined and executed definite multi-year plans to create new products and distribute them effectively. Forget “minimum viable products”—ever since he started Apple in 1976, Jobs saw that you can change the world through careful planning, not by listening to focus group feedback or copying others’ successes.

A minimum viable product (MVP) helps entrepreneurs start the process of learning as quickly as possible. 3 It is not necessarily the smallest product imaginable, though; it is simply the fastest way to get through the Build-Measure-Learn feedback loop with the minimum amount of effort. Contrary to traditional product development, which usually involves a long, thoughtful incubation period and strives for product perfection, the goal of the MVP is to begin the process of learning, not end it. Unlike a prototype or concept test, an MVP is designed not just to answer product design or technical questions. Its goal is to test fundamental business hypotheses.

Innovation accounting works in three steps: first, use a minimum viable product to establish real data on where the company is right now. Without a clear-eyed picture of your current status—no matter how far from the goal you may be—you cannot begin to track your progress. Second, startups must attempt to tune the engine from the baseline toward the ideal. This may take many attempts. After the startup has made all the micro changes and product optimizations it can to move its baseline toward the ideal, the company reaches a decision point. That is the third step: pivot or persevere. If the company is making good progress toward the ideal, that means it’s learning appropriately and using that learning effectively, in which case it makes sense to continue. If not, the management team eventually must conclude that its current product strategy is flawed and needs a serious change. When a company pivots, it starts the process all over again, reestablishing a new baseline and then tuning the engine from there. The sign of a successful pivot is that these engine-tuning activities are more productive after the pivot than before.

Startups struggle to see their work-in-progress inventory. When factories have excess WIP, it literally piles up on the factory floor. Because most startup work is intangible, it’s not nearly as visible. For example, all the work that goes into designing the minimum viable product is—until the moment that product is shipped—just WIP inventory. Incomplete designs, not-yet-validated assumptions, and most business plans are WIP. Almost every Lean Startup technique we’ve discussed so far works its magic in two ways: by converting push methods to pull and reducing batch size. Both have the net effect of reducing WIP.

Would-be entrepreneurs are told that nothing can be known in advance: we’re supposed to listen to what customers say they want, make nothing more than a “minimum viable product,” and iterate our way to success. But leanness is a methodology, not a goal. Making small changes to things that already exist might lead you to a local maximum, but it won’t help you find the global maximum.

In Silicon Valley, start-ups don’t launch with polished, finished businesses. Instead, they release their “Minimum Viable Product” (MVP)—

When an engineer with years of familiarity in a problem space begins designing a product, it’s easy to imagine a utopian end-state for the work. However, it’s important to differentiate aspirational goals of the product from minimum success criteria (or Minimum Viable Product). Projects can lose credibility and fail by promising too much,

In recent years, Eric Ries famously adapted Lean to solve the wicked problem of software startups: what if we build something nobody wants?[ 41] He advocates use of a minimum viable product (“ MVP”) as the hub of a Build-Measure-Learn loop that allows for the least expensive experiment. By selling an early version of a product or feature, we can get feedback from customers, not just about how it’s designed, but about what the market actually wants. Lean helps us find the goal. Figure 1-7. The Lean Model. Agile is a similar mindset that arose in response to frustration with the waterfall model in software development. Agilistas argue that while Big Design Up Front may be required in the contexts of manufacturing and construction where it’s costly if not impossible to make changes during or after execution, it makes no sense for software. Since requirements often change and code can be edited, the Agile Manifesto endorses flexibility. Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.

Many teams get into a lot of grief with the concept of a minimum viable product (MVP) because on the one hand we are very motivated to get this out in front of customers fast to get feedback and learn. And, on the other hand, when we do get out there fast, people feel like this so‐called product is an embarrassment to the brand and the company. How could we possibly consider launching this?

the 2011 book The Lean Startup. Core to its philosophy is the idea that founders don’t know what product the market needs—the market knows what product the market needs. Instead of spending years and millions of dollars secretly creating their idea of the perfect product, startups should move quickly to release a “minimum viable product” that can tease out market demand for different functions. Internet-based startups can then receive instant feedback based on customer activity, letting them immediately begin iterating on the product: discard unused features, tack on new functions, and constantly test the waters of market demand.

in the technology industry we would call The Life of Pablo a minimum viable product. That may sound like a pejorative term, but a minimum viable product is actually incredibly important. Only after it gets something out in the market can a business gather customer feedback and use this data to iterate and improve in a continuous deployment cycle. The MVP is a defining principle of cloud software development, and Kanye applied it to his music-writing process.

Innovation development, as we originally knew it, has changed fundamentally. It is increasingly a question of bringing new products and services into the market as quickly as possible. To meet changes in the market today means to realize new ideas with astonishing speed. Agile methods, such as design thinking or a focus on minimum viable products (see chapter MVP), help achieve

Agile thought leader Bill Wake created a set of guidelines for writing good user stories; to make them easier to remember, he uses the acronym INVEST: Independent: A good story should be independent of other stories. Stories shouldn't overlap in concept and should be implementable in any order. Negotiable: A good story isn't an explicit contract for features. The details for how a story's benefit will be delivered should be open to discussion. Valuable: A good story needs to be valuable to the customer. Estimable: A good story is one whose scope can be reasonably estimated. Small: Good stories tend to be small in scope. Larger stories will have greater uncertainty, so you should break them down.

We do everything wrong: instead of spending years perfecting our technology, we build a minimum viable product, an early product that is terrible, full of bugs and crash-your-computer-yes-really stability problems. Then we ship it to customers way before it’s ready.

So you hire minimum viable people, and much like improving your minimum viable product, you improve your minimum viable employee.

Usability answers the question, “Can customers use your product?” Delight answers the question, “Do customers enjoy using your product?

Even in engineering-driven Silicon Valley, the buzzwords of the moment call for building a “lean startup” that can “adapt” and “evolve” to an ever-changing environment. Would-be entrepreneurs are told that nothing can be known in advance: we’re supposed to listen to what customers say they want, make nothing more than a “minimum viable product,” and iterate our way to success. But leanness is a methodology, not a goal. Making small changes to things that already exist might lead you to a local maximum, but it won’t help you find the global maximum. You could build the best version of an app that lets people order toilet paper from their iPhone. But iteration without a bold plan won’t take you from 0 to 1. A company is the strangest place of all for an indefinite optimist: why should you expect your own business to succeed without a plan to make it happen? Darwinism may be a fine theory in other contexts, but in startups, intelligent design works best.

minimum viable product.” He said, “The sooner you get it out there, users can start telling you what they want instead of you guessing. If you sit down and think of the perfect implementation, the problem is you’re thinking of the perfect implementation of the wrong thing.

minimum viable product, or MVP. The MVP is the product you are developing with just enough features, the minimum amount, to be feasibly, or viably, tested by real people.

A good product is designed with focus on the set of needs that are important and that make sense to address together.

Focus is critical when defining a new product.

Customers don't care about your solution. They care about their problems.” Keeping problem space and solution space separate and alternating between them as you iteratively test and improve your hypotheses is the best way to achieve product-market fit.

Changing customer behavior is always difficult—especially in the upper right quadrant—and you need to create a certain amount of excess value to get customers to switch from a product they routinely use. The notion of needing to have “10×” better performance comes to mind again.

fidelity refers to how closely the artifact looks like the final product, whereas interactivity means the degree to which the customer can interact with the artifact

The real-world manifestation of software products that customers see and use is the user experience (UX), which is the top layer of the Product-Market Fit Pyramid. Beyond software, this is also true for any product with which the customer interacts. The UX is what brings a product's functionality to life for the user.

You can think of this as a three-tier ​pyramid with must-haves on the bottom, performance features just above that, and delighters at the top.

People think focus means saying yes to the thing you've got to focus on. But that's not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. I'm actually as proud of the things we haven't done as the things I have done. Innovation is saying no to 1,000 things.