Is Fully Defining a New Product at Odds with a “Minimum Viable Product”?

A recent article focused on the number one problem in new product development: too many projects for the available development resources (1). In that article, one of the prescriptions proposed was to resist the temptation for the scope of a project to expand. Scope creep not only impacts that specific project but the entire project portfolio because of resource dependencies.

It was proposed that to avoid scope creep, it is best to fully define new products before development starts. That means a fully agreed-upon written description. The requirements for defining new products should be enshrined in your phased development process.

But is that advice at variance with the lean concept of a “minimum viable product”, or MVP? This is a popular “best practice” for creating new products, services and business models (2). The idea is to create a prototype quickly and get customer feedback. The new product, service or business model then “emerges” during that process.

To address that question, you must step back and first understand project uncertainty (3). There are four key sources of uncertainty in any project, whether for a product, service or new business model. These include task variation, foreseeable uncertainty, unforeseeable uncertainty (also known as “unknown unknowns”) and complexity.

When you are faced with a development (or even a new business model) that is dominated by “unk-unks”, then the best way to “define” that product is by using iterate-and-learn, based on the “plan-do-check-act” learning cycle. This is the fundamental basis of all the lean methodologies.

You accept the fact that you really don’t quite know how to define the product or service or business model, and so you want to prototype and test; to “fail fast and fail cheap”. This is really the purpose of an “MVP”. It’s the basis of the “lean startup” mentality. It is also embedded in the scrum technique for software development, for the same reason.

So my comment about “fully defining” a product to avoid scope creep can be refined somewhat based on the above comments. In other words, if you really do not understand what the customer wants then “fully defining” (e.g. writing a detailed description) the product (or service or business model) and moving to development is a waste of time and resources. You really need to learn exactly what needs to be developed before you even get to the point where you can fully define it, let alone expend scarce resources in development.

But make no mistake, once you get to that point, fully defining a new product and making sure all the stakeholders in the organization agree on a written description is absolutely necessary to prevent endless scope creep that delays the development and impacts the entire project portfolio.

If you do not face significant “unk unks” or complexity in a development, then the previous discussion might not apply. For instance, if you are incrementally improving an existing product, the concept of an “MVP” is really not applicable. In that case, you can “fully define” the product from the beginning, reducing the risk of scope creep.

Bottom line? How you will get to the documented, written product definition is context specific. New products, services or business models are on a continuum from incremental all the way to radical, new-to-the-world developments. You have to choose the right tools that are applicable for that specific project.

Getting caught up in the desire to create a “MVP” for every development does not make sense. The reality is that for most companies, 80% of their projects are incremental, where the use of an “MVP” is not necessarily needed. There is nothing wrong with incremental projects. It pays the bills.

Notes:

  1. See this article: “The Biggest Problem in Product Innovation May Surprise You”
  2. See for example: Eric Ries, The Lean Startup. (New York, NY: Crown Publishing, 2011)
  3. See these articles: “How Risk Impacts New Product Development” and “Tools to Manage Risk in New Product Development”

About the Author

Jeff Groh is President of New Product Visions located in Flat Rock, NC. New Product Visions helps companies drive revenue and earnings growth by improving their innovation management practices. We focus on processes, organization, management engagement and culture. Services include consulting, Innovation Coach™ Workshops, Your Innovation Coach online consulting service and software enablers. Mr. Groh spent 30+ years in industry in a variety of management roles in sales, manufacturing and new product development prior to starting New Product Visions. For additional information or to join our mailing list, contact us. Available for select speaking engagements.

 

Your Innovation Coach: A Unique Subscription Service

Brands IC LogoThere are many paths to grow a company’s revenue and earnings. That topic typically consumes the majority of management bandwidth. Organic market growth, geographic expansion and acquisitions are all viable strategies. But are you ignoring the role of innovation? Continue reading

Aligning Manufacturing and R&D in New Product Development (NPD)

New product development (NPD) is about creating knowledge resulting in new products that drive revenue and earnings growth. It is arguably the most important business process and one of the most difficult to manage (1). Why? Because it encompasses a series of workflow, information and decision flow across the entire organization. It is unique as well since every other process in the business can be driven to maximum efficiency. NPD is not just about efficiency, which often is the focus.  The real concern should be how to make it more effective.  Continue reading

Online Portfolio Management Tool: A Case Study

LogoFor any size business that undertakes multiple simultaneous projects, the ability to manage the project portfolio is a constant struggle (1). Think about what happens at most companies, large and small: over time, more projects get started before existing projects are complete, and new ideas become higher priority. Engineers are expected to work on not just one or two projects, which is ideal, but now must multi-task across multiple projects. On top of that, important customers demand new software features or enhancements to existing products or services, further diluting the focus on current projects. Statements like “every project seems to be late, never early”, “we always underestimate project cycle time” and “we constantly pull team members from a project to fix high priority customer requests” are common, especially in small to mid-sized firms. There are simply too many projects for too few resources, and the system grinds to halt. This article will describe a simple-to-use, cost effective online portfolio management tool.  Continue reading

Innovate Your Innovation Process

innovateAre you a small to mid-sized (SME) manufacturing company with a singular focus on understanding your customer needs, providing superior products to meet those needs and growing your revenue and earnings? It goes without saying that for every company, these goals should and do consume significant management bandwidth. The problem is that most organizations become too inwardly focused (1). They do not consider what might be happening outside their company, and even beyond their industry, and leverage that knowledge to create new customer value. This has driven the popularity of the concept of “open innovation”. Maybe we should extend the concept of open innovation to other important aspects of a business such as the innovation management process. Why not, in other words, “innovate your innovation process” by learning from others? Continue reading

Looking Beyond Your “Four Walls”: Revisited

Four WallsSeveral months ago, I wrote an article on a topic of great interest to me (1). A consistent problem with many companies I work with is that senior management and those in position of leadership in new product development (NPD) do not consider what might be happening in other industries.  There is a need, as I like to say, to look beyond your “four walls”. Continue reading

Assessing Your New Product Development (NPD) Process

continuous learningFor anyone responsible for managing a new product development (NPD) process, continually assessing your process and learning from other’s experiences is a must. These whitepapers available at no charge cover a wide range of topics including the role of management in NPD success, metrics, project definition, portfolio management and online tools, project risk, among others.   Continue reading

Online Portfolio Management Made Simple

SimplicityFor any size business that undertakes multiple simultaneous projects, the ability to manage the project portfolio is a constant struggle (1).  In particular, the portfolio over time tends to move to a higher state of disorder akin to the concept of entropy (2). Think about what happens at most companies, large and small: over time, more projects get started before existing projects are complete. Engineers are expected to work on not just one or two projects, which is ideal, but now must multi-task across multiple projects. On top of that, important customers demand new software features or enhancements to existing products, further diluting the focus on current projects. Statements like “every project seems to be late, never early”, “we always underestimate project cycle time” and “we constantly pull team members from a project to fix high priority customer requests” are common, especially in small to mid-sized firms. There are simply too many projects for too few resources, and the system grinds to halt.  Continue reading

New Project Portfolio Management Tool for Small to Mid-Sized Companies

LogoFor any size business that undertakes multiple simultaneous projects, the ability to manage the project portfolio is a constant struggle (1).  In particular, the portfolio over time tends to move to a higher state of disorder akin to the concept of entropy (2). Think about what happens at most companies, large and small: over time, more projects get started before existing projects are complete. Engineers are expected to work on not just one or two projects, which is ideal, but now must multi-task across multiple projects. On top of that, important customers demand new software features or enhancements to existing products, further diluting the focus on current projects. Statements like “every project seems to be late, never early”, “we always underestimate project cycle time” and “we constantly pull team members from a project to fix high priority customer requests” are common, especially in small to mid-sized firms. There are simply too many projects for too few resources, and the system grinds to halt.  Continue reading

Project Portfolio Management Tool for Small to Mid-Sized Companies

Portfolio2For any size business that undertakes multiple simultaneous projects, the ability to manage the project portfolio is a constant struggle (1).  In particular, the portfolio over time tends to move to a higher state of disorder akin to the concept of entropy (2). Think about what happens at most companies, large and small: over time, more projects get started before existing projects are complete. Engineers are expected to work on not just one or two projects, which is ideal, but now must multi-task across multiple projects. On top of that, important customers demand new software features or enhancements to existing products, further diluting the focus on current projects. Statements like “every project seems to be late, never early”, “we always underestimate project cycle time” and “we constantly pull team members from a project to fix high priority customer requests” are common, especially in small to mid-sized firms. There are simply too many projects for too few resources, and the system grinds to halt.  Continue reading