最小可行产品方法

by George Krasadakis

通过乔治·克拉萨达基斯(George Krasadakis)

最低可行产品，说明 (The Minimum Viable Product, explained)

一个MVP到底是什么，以及如何从中受益 (What an MVP really is and how you can benefit from it)

The term MVP was coined and defined by Frank Robinson and popularized by Steve Blank and Eric Ries. A popular definition is the following:

MVP是由Frank Robinson创造和定义的，并由Steve Blank和Eric Ries推广。 流行的定义如下：

“… the minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future development…”

“……最低可行产品(MVP)是一种产品，其功能足以满足早期客户的需求，并为未来的发展提供反馈意见……”

If you analyse this definition, you will see three major components there:

如果您分析此定义，那么您将在其中看到三个主要组成部分：

1. MVP提供“足够的功能” (1. An MVP provides ‘Just enough features’)

Assuming you have a product backlog — a list of all the features you want to build in your product — you have to decide the order to build them and when to release your product. The idea is to prioritize the features and release a smaller instance of my product, faster. But what would be the criteria for the prioritization? And how many of the top prioritized features are enough to deliver value to your early customers?

假设您有产品积压订单(要在产品中构建的所有功能的列表)，则必须确定构建这些功能的顺序以及何时发布产品。 这个想法是优先考虑这些功能，并更快地发布我的产品的较小实例 。 但是确定优先级的标准是什么？ 多少个最重要的优先功能足以为您的早期客户带来价值？

The criteria for ranking your features should be [a] value for the users and [b] feasibility: you need to identify the best subset of features in your complete product backlog, the subset which is expected to deliver the most value for your users; and which is also feasible for your team to build, launch and operate.

对功能进行排名的标准应该是[a] 用户价值和[b] 可行性 ：您需要在完整的产品积压订单中确定功能的最佳子集 ，该子集应该为用户带来最大价值； 并且对于您的团队的建立，启动和运营也是可行的。

To identify the ‘red line’ — that is, after which feature to release your MVP — you need to think both as a user and also as an entrepreneur: apply business and product sense to find the minimum set of those top-ranked features which solves the problem for your customers. This is your MVP — and this justifies the Minimum in the MVP.

要确定“红线”(即发布MVP的功能之后)，您既需要以用户的身份也要以企业家的身份思考 ：运用业务和产品意识来找到那些最重要的功能中的最小集合为您的客户解决问题。 这是您的MVP ，这证明了MVP中的最小值 。

2. MVP“满足早期客户” (2. An MVP ‘satisfies early customers’)

This first instance of your product must be good enough to solve the problem for your customers — they should get value out of it from day one. Your MVP must be usable and effective so users engage with it and potentially pay for it.

您的产品的第一个实例必须足够好，可以为您的客户解决问题-他们应该从第一天开始就从中获得价值。 您的MVP必须可用且有效，以便用户参与其中并有可能为此付费。

Your early customers should be so happy with your product to act as promoters — to recommend it to others and publicly share their satisfaction (if not excitement).

您的早期客户应该对您的产品感到高兴，可以充当促销员—向他人推荐该产品并公开分享他们的满意度(如果不是兴奋的话)。

3. MVP“为未来发展提供反馈” (3. An MVP ‘enables feedback for future development’)

As a product manager, it is critical to deeply understand what your users want and potentially reflect it to your product strategy. You need the right mechanisms and processes to capture the level of user engagement and measure how users interact with your product — across platforms, channels and markets.

作为产品经理，至关重要的是深入了解用户的需求，并将其潜在地反映到您的产品策略中。 您需要正确的机制和流程来捕获用户参与度并衡量用户如何跨平台，渠道和市场与您的产品进行交互 。

Telemetry systems and the right reporting and analysis tools can cover these analytical needs — along with specialized product performance dashboards, which present KPIs in the right context to enable quick comparisons and decisions.

遥测系统以及正确的报告和分析工具可以满足这些分析需求，以及专门的产品性能仪表板 ，这些仪表板在正确的上下文中显示KPI，从而可以进行快速比较和决策。

In many cases, it is a great idea to collect additional qualitative feedback — for example by organizing focus groups to evaluate the UX of your MVP; or by hosting user interviews, analysing unstructured feedback etc. Qualitative data will help you understand how you are delivering value to the users and what can be improved.

在许多情况下，收集其他定性反馈是一个好主意-例如，通过组织焦点小组来评估MVP的用户体验； 或通过主持用户访谈，分析非结构化反馈等。定性数据将帮助您了解如何为用户创造价值以及可以改进的地方。

You could also consider using customer satisfaction mechanisms such as the NPS — Net Promoter Score — as a way to capture user satisfaction in a standardized way.

您还可以考虑使用客户满意度机制(例如NPS- 净发起人得分)来以标准化的方式获取用户满意度。

All the above, define a product performance measurement framework, with the insights required to make better, informed decisions and explore further investment areas.

以上所有内容，定义了产品性能评估框架 ，并提供了做出更好，更明智的决策并探索进一步投资领域所需的见识。

From a problem to a well-defined MVP in 8 stepsThe process you need to go through, to properly define your Minimum Viable Productmedium.com

从问题到定义明确的MVP的8个步骤 ，您需要经历的过程，以正确定义最低可行产品 medium.com

关于MVP的误解 (Misconceptions about MVPs)

Although the notion of the MVP is a fairly simple idea, it is not always used in the right way: For instance, the term MVP is frequently used to denote a quick implementation, a draft, a prototype or something ‘to start with’.

尽管MVP的概念很简单，但并非总是以正确的方式使用：例如，术语MVP经常用于表示快速实现，草案，原型或“开始​​”的东西。

In contrast to both ‘Proof of Concept’ and Prototype, the MVP has increased production readiness — as it is exposed to real users/customers.

与“概念验证”和“原型”相反，MVP 增加了产品准备就绪程度 -因为它对真实用户/客户开放。

An MVP is the first instance of a real product; it’s the beginning of the life-cycle of your real product; the basis for future iterations.

MVP是实际产品的第一个实例； 这是您真实产品生命周期的开始； 未来迭代的基础。

优秀MVP的特征 (Characteristics of a good MVP)

Good MVPs are focused, with the user at the center of their designs; they reflect validated user needs and they solve real problems; they provide great, seamless mechanisms to measure user engagement and capture user feedback — to quantify the overall product performance.

优秀的MVP是关注的焦点，用户是他们设计的核心； 它们反映了经过验证的用户需求，并解决了实际问题； 它们提供了出色的无缝机制来衡量用户参与度并捕获用户反馈-从而量化整体产品性能。

MVP定义不明确(或内置)的症状 (Symptoms of poorly defined (or built) MVPs)

Poor MVPs are usually over-complicated and they are not really — ‘minimum’; They are over-engineered or not engineered at all :) In most of the cases, they don’t really reflect the real user needs, and therefore, they are disconnected from the market. Poor user experiences could also destroy a well-defined MVP.

最差的MVP通常过于复杂，而且并不是“最小”。 他们设计过度或根本没有设计：)在大多数情况下，它们并未真正反映出真正的用户需求，因此与市场脱节。 不良的用户体验也可能会破坏良好定义的MVP。

MVP方法如何使您的业务受益 (How the MVP approach benefits your business)

Think of the notion of the MVP as part of a method or a framework to help you define and build a better product — move towards a great product faster and cheaper. As you are adapting and using the Minimum Viable Product approach, you will benefit at many levels — directly and indirectly. You will be able to:

将MVP的概念视为一种方法或框架的一部分， 可以帮助您定义和构建更好的产品 - 更快 ， 更便宜地迈向出色的产品。 在适应和使用最低可行产品方法时，您将直接或间接地从多个层面受益。 你将能够：

1.大考虑您的产品 (1. Think BIG about your product)

Having a solid product vision is very important. The ‘agile way’ in product development empowers you to think big — to create backlogs describing a ‘complete product’ even with expensive and ‘crazy’ features — they can all be captured there in your product backlog and wait for the right conditions and timing in order to be considered for implementation. My recommendation is to capture everything, prioritize wisely.

拥有坚实的产品愿景非常重要。 产品开发中的“敏捷方式”使您能够大胆思考 -创建积压成堆的“完整产品”，甚至具有昂贵和“疯狂”的功能-所有这些都可以在产品积压中捕获，并等待正确的条件和时机以便考虑实施。 我的建议是抓住一切，明智地安排优先次序 。

2.减少构建产品 (2. Build your product with less)

The MVP definition process, will enable you to build your product with less: the MVP is about identifying the must-have features, which will keep your early customers engaged and happy; this way you will build a smaller first-instance of your product which will still serve the core of its purpose: to solve the primary problem for the users.

MVP定义过程将使您能够以更少的成本构建产品：MVP旨在确定必备功能，从而使您的早期客户参与并感到满意； 这样，您将为产品构建一个较小的实例，而实例仍将达到其目的的核心：为用户解决主要问题。

It will also help you minimize your development and operational costs, by de-prioritizing the less important features for future iterations. A properly defined and built MVP will save you money.

通过取消为次要迭代使用的次要功能的优先级，还可以帮助您最大程度地降低开发和运营成本。 正确定义和构建的MVP将为您省钱。

3.与您的客户联系 (3. Connect with your customers)

The ability to capture user feedback early enough (and frequently), is probably a success factor on its own. Your MVP should provide streams of feedback in a number of ways — both directly and indirectly.

足够早(且频繁)捕获用户反馈的能力本身可能就是成功的因素。 您的MVP应该以多种方式直接或间接地提供反馈流。

For instance, a properly built MVP should capture all user interactions and append the data into a historical user interaction database (be aware of GDPR and related regulatory constraints here). Proper reporting and data analysis could help you discover really interesting patterns about your users and how the interact with your product. The chances are, that these insights will challenge your initial product assumptions — or even indicate different paths and opportunities to pivot.

例如，正确构建的MVP应该捕获所有用户交互并将数据附加到历史用户交互数据库中(请注意此处的GDPR和相关法规限制)。 正确的报告和数据分析可以帮助您发现有关用户以及与产品如何交互的真正有趣的模式。 这些见解很有可能会挑战您最初的产品假设，甚至可能指示不同的途径和发展机会。

You can also collect and use qualitative feedback — by leveraging embedded forms or online questionnaires or focus groups and user interviews. These, could provide additional signals or insights and perspectives you might have never thought of.

您还可以利用嵌入式表格或在线调查表或焦点小组和用户访谈来收集和使用定性反馈。 这些可能会提供您可能从未想到的其他信号或见解和观点。

4.更快进入市场 (4. Go to market faster)

As your MVP is about building a smaller instance of your product, you will have the opportunity to go to market faster; also, following the same agile pattern, you will be able to release features frequently and retain your flexibility to pivot — according to user feedback and signals from the market.

当您的MVP要构建产品的较小实例时 ，您将有机会更快地进入市场； 此外，按照相同的敏捷模式，您将能够根据用户的反馈和来自市场的信号， 频繁发布功能并保持枢纽灵活性。

5.早些考虑枢轴 (5. Consider pivots, earlier)

As you are more connected to your users, you can use insights and product performance data, to adjust your priorities and your product roadmap. Or, you may discover those signals indicating a potential pivot — that is, a major shift in your product strategy or in the way you solve the problem for your users.

随着与用户的联系越来越紧密，您可以使用洞察力和产品性能数据来调整优先级和产品路线图。 或者，您可能会发现那些指示潜在枢纽的信号，即您的产品策略或您为用户解决问题的方式 的重大转变 。

Thoughts, suggestions or questions are welcome!

欢迎有任何想法，建议或问题！

How to define a Minimum Viable ProductMoving from a concept to a properly defined MVPmedium.freecodecamp.org

如何定义最低可行产品 从概念转变为正确定义的MVP媒介。freecodecamp.org

Cover image: pixabay

封面图片： pixabay

翻译自: https://www.freecodecamp.org/news/the-minimum-viable-product-explained-8f1187ca7cec/

最小可行产品方法