<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeff Brunski on Medium]]></title>
        <description><![CDATA[Stories by Jeff Brunski on Medium]]></description>
        <link>https://medium.com/@jeff.brunski?source=rss-77ee38f16189------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ag2xjyMerHfSt5Y9Thc-Og.jpeg</url>
            <title>Stories by Jeff Brunski on Medium</title>
            <link>https://medium.com/@jeff.brunski?source=rss-77ee38f16189------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:07:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jeff.brunski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Chapter 22 — New Product Development Wrap-Up]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/product-development-distillery/chapter-22-new-product-development-wrap-up-b1ff4e2c557a?source=rss-77ee38f16189------2"><img src="https://cdn-images-1.medium.com/max/600/0*8fZfiVonetAcDrSs.jpg" width="600"></a></p><p class="medium-feed-snippet">That&#x2019;s a wrap. Reflections and more resources.</p><p class="medium-feed-link"><a href="https://medium.com/product-development-distillery/chapter-22-new-product-development-wrap-up-b1ff4e2c557a?source=rss-77ee38f16189------2">Continue reading on Product Development Distillery »</a></p></div>]]></description>
            <link>https://medium.com/product-development-distillery/chapter-22-new-product-development-wrap-up-b1ff4e2c557a?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1ff4e2c557a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Fri, 22 May 2020 13:31:20 GMT</pubDate>
            <atom:updated>2021-01-05T18:28:49.962Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Chapter 21 — Product Development Post-Launch]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/product-development-distillery/chapter-21-product-development-post-launch-4c2c6dfe2bee?source=rss-77ee38f16189------2"><img src="https://cdn-images-1.medium.com/max/1280/0*YJHo6dPg55n0VeEm" width="1280"></a></p><p class="medium-feed-snippet">Where you&#x2019;re going, you don&#x2019;t need roads, but you might want a roadmap.</p><p class="medium-feed-link"><a href="https://medium.com/product-development-distillery/chapter-21-product-development-post-launch-4c2c6dfe2bee?source=rss-77ee38f16189------2">Continue reading on Product Development Distillery »</a></p></div>]]></description>
            <link>https://medium.com/product-development-distillery/chapter-21-product-development-post-launch-4c2c6dfe2bee?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c2c6dfe2bee</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Tue, 21 Apr 2020 13:40:08 GMT</pubDate>
            <atom:updated>2021-01-05T18:27:23.657Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Chapter 20 — Product Launch]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/product-development-distillery/chapter-20-product-launch-99f778981af5?source=rss-77ee38f16189------2"><img src="https://cdn-images-1.medium.com/max/823/0*v6Enn-Z0CMu5bo7L" width="823"></a></p><p class="medium-feed-snippet">Launch. Holy shit. Let&#x2019;s talk about the launch management system.</p><p class="medium-feed-link"><a href="https://medium.com/product-development-distillery/chapter-20-product-launch-99f778981af5?source=rss-77ee38f16189------2">Continue reading on Product Development Distillery »</a></p></div>]]></description>
            <link>https://medium.com/product-development-distillery/chapter-20-product-launch-99f778981af5?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/99f778981af5</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Sun, 01 Mar 2020 23:06:46 GMT</pubDate>
            <atom:updated>2021-01-05T18:26:00.790Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Better Product Development: 7 Essential Articles from Harvard Business Review]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.productcoalition.com/better-product-development-7-essential-articles-from-harvard-business-review-a31cba676f75?source=rss-77ee38f16189------2"><img src="https://cdn-images-1.medium.com/max/1981/1*1uHVi2PnMTFckIt1gXn6DA.jpeg" width="1981"></a></p><p class="medium-feed-snippet">From &#x201C;Jobs to be Done&#x201D; to &#x201C;Project Premortems,&#x201D; here are seven essential reads for anyone working in new product development. Enjoy!</p><p class="medium-feed-link"><a href="https://medium.productcoalition.com/better-product-development-7-essential-articles-from-harvard-business-review-a31cba676f75?source=rss-77ee38f16189------2">Continue reading on Product Coalition »</a></p></div>]]></description>
            <link>https://medium.productcoalition.com/better-product-development-7-essential-articles-from-harvard-business-review-a31cba676f75?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31cba676f75</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Tue, 04 Feb 2020 08:30:30 GMT</pubDate>
            <atom:updated>2020-02-08T22:56:01.836Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Chapter 19 — Product Testing]]></title>
            <link>https://medium.com/product-development-distillery/chapter-19-product-testing-6f2528b84d27?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f2528b84d27</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Tue, 28 Jan 2020 14:16:00 GMT</pubDate>
            <atom:updated>2021-01-28T01:13:59.576Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 19 — Product Testing</h3><p><em>Note: This content is from the Product Development Distillery email series: a daily e-mail that helps teach essential product development skills. Click here to sign up:</em></p><figure><a href="http://eepurl.com/driGaH"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GekKrsiJutsOTaYTHkYbvg.png" /></a></figure><h3>19a. Product Testing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8yrD2DvU4vDVAELg" /></figure><p>Let’s talk about testing.</p><p>You: “Wait, testing? We’re talking about testing?! Haven’t we been talking about testing for days with all this build-measure-learn prototype talk?! More testing???!!!”</p><p>OK, OK. Take a deep breath. Calm down.</p><p>Yes, prototyping and experimenting with your product is a form of testing…but testing and prototyping are not the same thing and it’s important to understand the distinctions.</p><p>We’re going to cover that distinction as well as other topics like</p><ul><li>Alpha testing</li><li>Beta testing</li><li>Market testing</li></ul><p>Without further ado…here is testing, distilled.</p><p><strong>Prototyping versus Testing — They Ain’t The Same</strong></p><p>To elaborate on this, testing and prototyping are indeed different. Testing is more about refinement than it is about confirming a hypothesis or understanding Product-Market Fit.</p><p><strong>Prototyping — testing a hypothesis; making decisions; designing to meet customer needs; what should we build?</strong></p><p><strong>Testing — ensuring your product works as expected; refining; debugging; testing under various conditions; preparing for launch.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*8rLSeRikqfYrhIc4" /></figure><p>The distinction between prototyping and testing is perhaps a little subtle, but there is a distinction nonetheless.</p><p>Prototyping questions</p><ul><li>Is this product meeting customer needs</li><li>Should we incorporate this feature</li><li>Are we delivering value to the customer</li></ul><p>Testing questions</p><ul><li>Is the product functioning as expected under various conditions</li><li>Is the product reliable and robustly built</li><li>Is the product not bursting into flames</li></ul><p><strong>Why Testing Is Important</strong></p><p>Testing is your last chance to make sure your product isn’t a hot mess. Product-Market Fit matters, but so does quality.</p><p>There should come a time when you stop altering the product and instead focus on quality and robustness. In other words, at some point you should stop exploring and start refining.</p><p>This can be difficult for product developers.</p><p>Product developers don’t like to stop tweaking. They don’t like to stop improving. A good product developer is always learning and always considering how to modify and improve a product.</p><p>It’s very tempting to watch people test your product and then try to implement changes and improvements.</p><p>Also, there are no “testing police” who will come and arrest you if you try to implement new features <em>after </em>conducting quality testing. Technically, you could be changing things up to the very last possible minute.</p><p>But that’s not a great idea.</p><p>If you keep making changes up to the very last minute, chances are you’re going to launch something that’s going to fail in some manner.</p><p>If you’re building an app that reminds you of when to walk your dog, maybe it’s no big deal if the product fails. If you’re building a surgical tool or a rocket, you might want that thing to work.</p><p>Quality matters, which means testing matters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*QKYDIiPPRu9J2-HxMnE-lQ.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.testbytes.net%2Fblog%2Fsoftware-testing-memes%2F&amp;psig=AOvVaw0bQwvE-lSn6PaMTkf_Pbsf&amp;ust=1611264482960000&amp;source=images&amp;cd=vfe&amp;ved=0CAIQjRxqFwoTCNjuoYy6q-4CFQAAAAAdAAAAABAJ">Source</a></figcaption></figure><h3>19b. Testing 1–2–3 (Testing Basics)</h3><p>Let’s start with some testing basics.</p><p>Testing is done in an attempt to <em>assure </em>quality. If you work in NPD, you’ll become very familiar with QA, or Quality Assurance.</p><p>The QA team’s job is to assure quality. If you don’t have a QA team in your organization, then you are the QA team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/0*KMjTgtI8JMXjQiNf" /></figure><p><em>People who have this picture hanging in their office have a 100% chance of not being the coolest person in the office.</em></p><p>Quality Assurance is not to be confused with Quality Control, which might be a more familiar term to some of you. Quality Control inspects for quality in products that are already in production. Quality Assurance attempts to improve quality before a product launches.</p><p><strong>Being Deliberate</strong></p><p>Like anything else in product development (and like prototyping in articular), testing should be done deliberately during the product development process.</p><p>There should be a clear strategy and objective. You should know what you are trying to learn.</p><p>Yes, it’s fun to just take a product concept and break it, but unless you do it in a rigorous and scientific way, the results are not going to be trustworthy and informative.</p><p>Don’t just be like, “Let’s break this thing.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*vKVoYs0ClZgGt0TU" /><figcaption>Ivan Drago, the ultimate QA Manager</figcaption></figure><p>When running testing, ask yourself, ‘What are we trying to learn?’</p><ul><li>Does the product function under normal working conditions</li><li>Does the product function in extreme conditions</li><li>Does the product pass accelerated lifecycle use testing</li><li>Does the product pass drop testing, vibration testing, or whatever other extreme environmental testing it needs to withstand?</li><li>Does the product pass whatever certifications are required of it, be it environmental or other</li><li>Can your product handle scale — be it scaled manufacturing or scaled loading of users</li><li>Does the product integrate with other products as expected</li></ul><p>These questions are important, but perhaps I jumped over the more important, fundamental question: <strong>Should we even be doing any testing or should we just launch?</strong></p><p>Spoiler alert — I can’t tell you if you should be testing or not. It really depends on the situation, the product, and the market.</p><p>(Unless you’re working on a product that could kill someone. If that’s the situation, then yes, by all means, you should test your product extensively.)</p><p>Otherwise, notwithstanding governmental or industry-specific regulations, it will be the product development team’s responsibility to establish how much testing is sufficient.</p><p><strong>When should you test?</strong></p><p>In a perfect world, you would get a dress-rehearsal for everything. But, the world ain’t perfect.</p><p>The two biggest constraints to testing are probably time and money. And since time is money, well, the biggest constraint is money.</p><p>Testing takes time. Even worse, if you think testing takes time, that ain’t even the half of it; reacting to test results takes time.</p><p>There ain’t nothing quite like being close a deadline and learning that the best solution you have come up with doesn’t really work. It’s a very special kind of panic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*7Wgz3ZOFdv9VMlwltuhxMQ.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Frapidbi.com%2Ffriday-fun-project-management-on-time-delivery-409-ff%2F&amp;psig=AOvVaw1Vd7e0TstLPi8C_3GydrXu&amp;ust=1611264556681000&amp;source=images&amp;cd=vfe&amp;ved=0CAIQjRxqFwoTCMDs4q-6q-4CFQAAAAAdAAAAABAQ">Source</a></figcaption></figure><p>And it’s not just the time to run the test — it can be very costly to react to testing result. If testing happens toward the end of the NPD process, you’ve likely already invested heavily in your current product concept, perhaps in making machinery, tooling, or hours of engineering time building code.</p><p>Changing those things is not trivial. This is why very often the reaction to negative test results is the same: rerun the test, that can’t be right!</p><p>Some Testing Terminology</p><p>EVT — Engineering Validation Testing — Functional testing of the product to confirm that the performance meets expectations. This could include things like how fast a computer starts-up, how reliably an app runs, or how well a car performs in a simulated crash.</p><p>DVT — Design Validation Testing — Testing things like cosmetic wear, overall durability (think phone drop test); trying to answer the question of whether the product will hold-up in the real world environment.</p><p>PVT — Production Validation Testing — If making a hardgood, physical product, this is actually running a small batch or “pilot run” in a production setting to confirm consistency from part to part. If making software, this might be testing scalability (whether your product can function if used by a large number of people).</p><p>False positive — This is when you get a signal that something is wrong but it actually isn’t.</p><p>False negative — This is when you get a signal that something is OK but it’s actually F’d.</p><h3>19c. Alpha and Beta Testing</h3><p>Let’s distill these two concepts and then talk about how/when/why to do them.</p><p><strong>Alpha Testing</strong> — Testing your product internally.</p><p><strong>Beta Testing</strong> — Testing your product externally. Real users testing in a real environment.</p><p>That’s about it. That’s the difference. Boom…distilled.</p><p><strong>Alpha testing</strong></p><p>This is internal testing, so one positive is that there is a reduced risk of publicly embarrassing yourself or harming your brand.</p><p>Alpha Testing should be done deliberately. Carefully establish the parameters of the test and choose clear metrics to measure. This is not that different than Build-Measure-Learn. There should be a rigorous process to examine the results and glean insights from qualitative and quantitative information.</p><p><strong>Beta Testing</strong></p><p>A beta test is done with a number of customers and is specifically meant to validate if the product is functioning as expected.</p><p>It is meant to identify bugs, defects, glitches, or other substandard qualities so that these can be remedied before launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*Ue1-uaAcCJJHmHTjV6yYFg.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fmarketoonist.com%2F2019%2F10%2Ftesting.html&amp;psig=AOvVaw05KFYSg5vyeAat45zRuh66&amp;ust=1611264649519000&amp;source=images&amp;cd=vfe&amp;ved=0CAIQjRxqFwoTCOi41N26q-4CFQAAAAAdAAAAABAm">Source</a></figcaption></figure><p>You might think that you can test the product internally to learn what you need to know. You would be wrong. There is simply no replicating the actual user and market environment inside a laboratory, studio, garage, or wherever the hell you may be developing your product.</p><p><em>“End-use is indeed complex, and there is no way it can be simulated in laboratories, where use is isolated from user mistakes, competitive trashing of the concept, and objectivons by those in the user firm or family whose work or life is disrupted by the change.” </em><a href="https://www.amazon.com/New-Products-Management-Merle-Crawford/dp/007802904X"><em>New Products Management</em></a><em>, Chapter 16.</em></p><p><strong>Other Types of Tests</strong></p><p>Yes, there are other types of tests — many of them. There are internal Beta tests. “Isn’t that an alpha test?” Sort of, but it typically involves the completed product, rather than just sub-elements of the product. If you work in Silicon Valley or a Startup, you might hear the term ‘dogfooding’ (it’s an internal beta test) or ‘are the dogs eating the dogfood?’ If that happens, just keep walking.</p><p><strong>Beta Testing — When</strong></p><p>Stupid answer: beta testing is done before launch and after prototyping.</p><p>In the real world, that answer isn’t all that helpful.</p><p>A more practical approach to schedule Beta testing is to work backward from launch. Consider how long it will take to conduct the testing, to organize and process the results, and then…this part is important…how much time it might take to react to the results. Obviously the amount of time needed for these steps varies depending on product complexity.</p><p>The good thing about this approach is that it generally can be applied to all industries and product types. The negative is that you’ll see just how much time a thorough beta test can take. You’ll likely be trading-off design time. NPD always entails trade-offs between quality, scope, time and money.</p><p><strong>Beta Testing — How and Who</strong></p><p>Ahhh, this is the good stuff…how to run a proper Beta test and who to select for testing.</p><p>Ultimately these two factors — the how and why — will influence the effectiveness of beta testing more than anything. In other words, proceed carefully.</p><h3>19d. Beta Testing — How and Who</h3><p>Answering the “who” question requires revisiting some of the stuff we talked about in the <a href="https://medium.com/product-development-distillery/chapter-4-marketing-96b3e9aac964">chapter on marketing</a>. Things like demographics and market segments.</p><p>Without question, your beta test should be targeted toward the intended consumer of your product. The key idea here is that you are trying to get people to use the product as it will be used in the market. Nobody is better suited to behave like your customers than your actual customers.</p><p>That said, testing is about finding bugs and controlling quality. Contrast that with prototyping where you’re really trying to design the product to better meet customer needs. To some extent, you just need some warm bodies for testing. Enthusiastic warm bodies, who can communicate well. A mute zombie would be the opposite of what you want. Don’t use mute zombie for beta tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7htBg719owgClJSD" /><figcaption>Poor candidates for Beta testing because they can’t effectively verbalize constructive feedback</figcaption></figure><p>There are actually a lot of websites dedicated to helping you find people to conduct beta tests. Google “websites for finding beta testers” and off you go.</p><p><strong>How to Beta Test</strong></p><p>First of all, a disclaimer: I’m hesitant to list specific testing tools because they will become obsolete pretty quickly. There are many platforms and software for creating digital beta tests. Again, use “The Google” or whatever search engine you prefer to find these tools.</p><p>Here are the basics on how to run a beta test, distilled as simple as can be. (Yes, there are more questions here than answers.)</p><ul><li>Set goals. Yes, improving quality is a goal. Anything else?</li><li>Find your tools. You’ll typically need to select specific apps or software to communicate with testers, to distribute the product, and to gather feedback.</li><li>Project manage. Establish the timeline. Coordinate with the team.</li><li>Measure. Collect information in an organized manner.</li><li>Respond deliberately. Carefully consider what actions must be taken based on results.</li></ul><p>Other questions you may want to consider:</p><ul><li>Should the test be supervised or unsupervised?</li><li>How much should we inform the users about the product prior to the test?</li><li>How will we capture and measure results?</li><li>Product tested in one form? Variants? Against competitors? A/B Testing?</li></ul><h3>19e. Market Testing and Testing Summary</h3><p>Alpha and Beta testing are pretty technical in nature. They are generally in the jurisdiction of engineering, R&amp;D, or whatever you call the technical side of the NPD team.</p><p>“What about Marketing and Sales? Shouldn’t those assholes do some testing?!” — A technical person who just completed a Beta test and has to pull an all-nighter to fix a bunch of issues.</p><p>Yes, they probably should.</p><p><strong>Let’s talk about Market Testing</strong>. First, some definitions:</p><p>Product Use Test — A super generic catch-all term; probably what you’re thinking of, when a product is tested in the field or with actual users; more of the technical testing.</p><p>Market Acceptance Testing — More specific way of describing testing that is meant to test if a product is accepted by a certain group of customers; marketing/sales testing.</p><p>Simulated Test Market — Using a small group of customers to represent a market and testing your product with them, generally focusing on Marketing-type learning</p><p>Test Market — When you actually launch your product in a small, controlled market, with the general aim of learning about Marketing-type stuff.</p><p><strong>Market Testing Distilled</strong></p><p>Market Testing is a really broad concept. In the most general meaning, a Market Test is an experiment conducted before the actual launch of the product where you learn things about the market.</p><p>Contrast that with a beta test where you are specifically trying to refine the product. The market test isn’t as focused on the product — it’s focused on the market and on marketing.</p><p>In other words, a market test is specifically meant to help you refine the marketing mix: price, promotion, product, and placement. (That’s right, the four P’s — hopefully you knew them!)</p><p>Here are some of the questions you might answer through Market Testing:</p><ul><li>What features and benefits should we be messaging in advertising?</li><li>How do we answer the tough questions from potential customers?</li><li>How will competitors try to discredit this product, and how will we respond?</li><li>What price should we sell this thing for?</li><li>Do we need to augment the product somehow (warranty, service and support)?</li><li>Should we adjust our forecast due to new insights about demand?</li><li>Should we be selling this product to a different target?</li></ul><p>The mentality in a market test is basically this: <em>‘We know we can’t change the product much at all at this point, but we can change how we talk about it, augment it, and “dress it up” in the market.’</em></p><p>It’s probably intimidating to think about running an entire “Market Test,” but market tests can come in all shapes and sizes.</p><p>Just pitching your product to a friend, a spouse, a barista, a stranger in an elevator, or to the DoorDash guy as he hands you your Ramen still sorta/kinda qualifies as doing a market test.</p><p>Of course, market testing can be huge as well. It can mean launching the entire product into a test market, such as a particular city or region. That’s obviously a big and complicated project and there’s no good way to distill it here. Suffice to say that if you’re involved in executing a test market launch, please do your homework!</p><p><strong>Finally, Testing In Summary</strong></p><ul><li>To test or not: it depends on cost, time, and ability to react with product changes. Like most things in new product development, it depends.</li><li>Testing is like prototyping in that it’s about learning.</li><li>Testing is unlike prototyping in that its purpose is refinement and debugging rather than gauging if customer needs are being met.</li><li>Alpha Testing: internal (inside the company).</li><li>Beta testing: external with actual target users (outside the company).</li><li>Market testing: learning more about the four P’s before launch.</li></ul><p><strong>Best Resources for Testing</strong></p><p><a href="https://www.amazon.com/New-Products-Management-Merle-Crawford/dp/007802904X">New Products Management</a> — This is a textbook that was originally written at least 20 years ago, but it covers testing much more extensively than many other books written more recently.</p><p><a href="https://www.amazon.com/Winning-New-Products-Creating-Innovation/dp/0465025781">Winning at New Products</a> — There’s 10–20 solid pages on testing in here. I like it for a quick read, but it doesn’t dive as deep as New Products Management.</p><p><a href="https://hackernoon.com/6-key-steps-to-follow-for-beta-testing-your-products-cba0e71fc497">6 Key Steps to Follow For Beta Testing Your Products</a> — Hacker Noon</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2528b84d27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/chapter-19-product-testing-6f2528b84d27">Chapter 19 — Product Testing</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Development Resources]]></title>
            <link>https://medium.com/product-development-distillery/product-development-resources-8f9912f6dddd?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f9912f6dddd</guid>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Tue, 31 Dec 2019 05:41:59 GMT</pubDate>
            <atom:updated>2019-12-31T05:41:59.124Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySUS6PGMRaEkcQcU4jZd0w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@tofi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tobias Fischer</a> on <a href="https://unsplash.com/s/photos/database?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Here are a few resources I’m working on at the moment. Yes, the list is short right now. Yes, I’ll eventually build out more content here.</p><h4><a href="https://productcoalition.com/the-best-books-on-product-development-6eb4acb28dc4?source=your_stories_page---------------------------">The Best Books on Product Development</a></h4><h4><a href="https://productcoalition.com/a-product-development-glossary-and-resource-library-4fc784bbe9f0?source=your_stories_page---------------------------">A Product Development Glossary and Resource Library</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f9912f6dddd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/product-development-resources-8f9912f6dddd">Product Development Resources</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 18 — Prototyping III: Moderately Advanced Topics]]></title>
            <link>https://medium.com/product-development-distillery/chapter-18-prototyping-iii-moderately-advanced-topics-81b9ca9cf743?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/81b9ca9cf743</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Thu, 12 Dec 2019 14:16:59 GMT</pubDate>
            <atom:updated>2021-01-28T01:09:44.475Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 18 — Prototyping III: Moderately Advanced Topics</h3><h3>18a. Prototyping To Learn, Explained Yet Again</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ZsEV3HCUeD6zUuqTeDcvUA.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.intoon.com%2Fcartoons.cfm%2Fid%2F3687&amp;psig=AOvVaw0XL2d5Rc4OEJ4CH6R1IjQw&amp;ust=1611264163182000&amp;source=images&amp;cd=vfe&amp;ved=0CAIQjRxqFwoTCPCmovq4q-4CFQAAAAAdAAAAABAm">Source</a></figcaption></figure><p>To say it again, <strong>prototyping is all about learning</strong>.</p><blockquote>“Prototyping…involves producing an early, inexpensive, and scaled down version of the product in order to reveal any problems with the current design. Prototyping offers designers the opportunity to bring their ideas to life, test the practicability of the current design, and to potentially investigate how a sample of users think and feel about a product.” <a href="https://www.interaction-design.org/literature/article/stage-4-in-the-design-thinking-process-prototype">Source</a></blockquote><p>Here’s a list of things you might try to learn by building a prototype. This should help further illustrate what prototyping is used for:</p><ul><li>Does this thing actually work like I think it will?</li><li>Does this part fit into that part?</li><li>Does this feature actually provide a benefit to the consumer?</li><li>What will this taste like? (Chefs make prototypes too.)</li><li>Does this app work intuitively?</li><li>Will people actually use this function?</li><li>Does this web application integrate with that one?</li><li>Does this camera take good selfies?</li><li>Will this screen smash into a million pieces if I drop my phone on the ground while taking a selfie?</li></ul><p>As you can see, the learning which prototypes enable can be narrow or broad:</p><ul><li>Narrow: Does this thing function like it should?</li><li>Broad: Do consumers like / need / want this thing?</li></ul><p>In other words, you can use prototypes to answer the question “Am I building the product right?” or “Am I building the right product?”</p><p>See the critical distinction between those questions?</p><p>Remember, <strong>in the Waterfall method</strong>, where it’s quite expensive to pivot to a new product concept, prototyping is mostly focused on “Am I building the product right?”</p><p>You’re likely more confident in the customer needs. The uncertainties remaining relate to how exactly to meet these needs.</p><p><strong>In the Lean Startup method</strong>, where there is likely more uncertainty and less cost to iterating, prototyping is mostly focused on “Am I building the right product?”</p><p>You care a lot less about how well the prototype is functioning and a lot more about how customers are responding to it (i.e. has it achieved product-market fit).</p><p>People have tried to capture this distinction visually. I think this graphic does a pretty good job:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AQtU0S2cd4iEGvGL" /><figcaption><a href="https://twitter.com/jira/status/804733248861601792">https://twitter.com/jira/status/804733248861601792</a></figcaption></figure><p>So…why clarify this distinction…especially since we already touched on it in <a href="https://medium.com/product-development-distillery/chapter-16-prototyping-cf1e7d12f559">Chapter 16</a> and <a href="https://medium.com/product-development-distillery/chapter-17-prototyping-in-agile-and-lean-263bcf2861d4">Chapter 17</a>?</p><p>Here’s the thing; if you’re relatively new to NPD, you’re going to find a lot of writing and guidance on prototyping. It’s everywhere.</p><p>It’s important to realize that some “prototyping best practices” may only be appropriate for a specific method of NPD (i.e. Lean Startup or Waterfall).</p><p>Understanding that prototyping is handled differently in different industries (or different development methodologies) will allow you to filter/process content that you come across in the future.</p><p>That said, the universal thing I can say — and I’ll say it again for the hundreth time — is that prototyping is about learning.</p><h3>18a. Using Prototyping as a Schedule Mechanism</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*A3LyJ0LhfVwrx5PwvIMUVg.png" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fmemegenerator.net%2Finstance%2F55139566%2Fconspiracy-keanu-prototype-in-production&amp;psig=AOvVaw3imLEqq6XRwOsnP2sOZDwf&amp;ust=1611264332377000&amp;source=images&amp;cd=vfe&amp;ved=0CAIQjRxqFwoTCKjX98q5q-4CFQAAAAAdAAAAABAK">Source</a></figcaption></figure><p>One of the reasons that prototyping is so important to NPD is that it’s not just a tool for learning…<strong>it’s also a tool for scheduling.</strong></p><p>Scheduling new product development can be a very tricky science. Uncertainty is everywhere. Predicting when a product will be ready for market launch is difficult stuff.</p><p>And even if you could perfectly predict when an NPD process would organically complete, we don’t really live in a world where products are launched when they’re ready. Product launches are typically planned years in advance and scheduled to align strategically with market, seasonal, or corporate rhythms.</p><p>In other words, the product doesn’t launch when it’s “ready;” the product launches when it’s due.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*7oNgsBAqKZ9OirjR" /></figure><p>The Challenge: How the hell to hit a product launch deadline.</p><p>One Answer to this Challenge: Use prototype cycles to manage the development schedule.</p><p><strong>The Prototype Cycle as Building Block for the Development Schedule</strong></p><p>In most product development methodologies, the product team will divide the development window into a series of prototype cycles. The team advances toward the launch deadline by building one prototype after the other until time runs out.</p><p><em>“…Prototyping — the build and test activities of each design-build-test cycle — is a key management tool for guiding development projects…management can use prototyping cycles to guide and pace development projects and to assess their progress, pinpoint unresolved issues, and focus resources and attention.” — </em><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298"><em>Revolutionizing Product Development</em></a></p><p>Here’s an example of what I’m talking about:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*wrs7qko8BWxpedPC" /></figure><p>Prototype 1 — Establish technical feasibility and answer some critical questions like “can this actually work?”</p><p>Prototype 2 — Build some more functionality into the concept and get some potential consumers involved. How well is the prototype meeting their needs?</p><p>Prototype 3 — Prototype 2 broke. Shit. Redesign that feature and build out prototype 3.</p><p>Prototype 4 — Now we’re really cooking; this thing is starting to look like something we could launch; this proves we can hit our launch date.</p><p>Prototype 5 — A major build-out or tooling is made; pilot run; beta testing; we’re almost launching…holy shit!</p><p>Launch — This isn’t a prototype…this is the real deal. But yeah we just learned a lot more and have ideas for the next version, so let’s start prototyping that right now…</p><p><strong>Most product development schedules are built using prototype iterations as the fundamental building blocks of schedule.</strong></p><p>As you can see, prototype cycles can divide a single development window into smaller, more manageable chunks of time. The team sets deadlines to complete each prototype, as well as specific goals for performance at each iteration.</p><p>With each round of prototyping, things are built, measured, and learning occurs. The product concept (or concepts) evolve forward, and the team can judge whether the progress made meets expectations.</p><p>Prototyping during the product development process essentially allows product developers to visualize how much learning will take place over time.</p><p><em>“Generational prototypes, and especially periodic prototypes, are effective for accelerating schedules, because they keep constant attention on the schedule. In effect, they allow us to control product, and thus project, performance against time.”</em> — Don Reinertsen, <a href="https://www.amazon.com/Developing-Products-Half-Time-Rules/dp/0471292524">Developing Products in Half the Time.</a></p><p>Most people don’t initially think of “scheduling” when they think of prototyping, but they should. Carefully managing prototype iterations is perhaps the best way to manage the entire NPD process. This is true across industries, and often regardless of whether you’re a small startup or an enormous Fortune 500 company.</p><h3>18c. The Trade-Off Between Speed and Fidelity</h3><p>Prototypes can be made quickly or they can be made accurately — typically not both.</p><p>If you could simply build full-scale products quickly and accurately, you wouldn’t need prototyping.</p><p>Prototyping is — by definition — a scaling back of scope or quality in order to achieve speed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*gIS7sJxlbBcEpRJR" /></figure><p>If you’ve ever heard the expression “fast, cheap, and good, pick two,” prototyping is a lot like that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/263/1*pKn3YJ8DpHVFyR0PPAE1Rw.png" /><figcaption><a href="http://kapiljekishan.com/good-cheap-or-fast-service-which-two-do-you-pick/">Source</a></figcaption></figure><p>This somewhat echoes <a href="https://en.wikipedia.org/wiki/Project_management_triangle">the project management triangle</a> that exists in almost every project: speed (or time), scope, and cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/0*2EZsqTnecNJ6zty-" /><figcaption><a href="https://en.wikipedia.org/wiki/Project_management_triangle">Source</a></figcaption></figure><p>Note that the project management triangle is not to be confused with Silicon Valley’s “conjoined triangle of success.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/0*J9zrC5MXoPFaL_4a" /><figcaption><a href="https://www.reddit.com/r/SiliconValleyHBO/comments/53guvt/the_conjoined_triangles_of_success_its_now_taught/">Source</a></figcaption></figure><p><strong>“Which is more important — speed or fidelity?”</strong></p><p>Interesting question. Like most things in NPD, you’re going to get the typical lawyer’s answer: it depends. There’s just no single best practice.</p><p><strong>The Case for Speed</strong></p><p>Sometimes speed is everything, even if it means building a shitty prototype. One of the mantras of Design Thinking is to have a “bias toward action.” When in doubt, build a prototype.</p><p>Folks in Silicon Valley also love to talk about “failing early and failing fast.” Time is money. It’s typically less expensive to fail sooner rather than later, so just start building and go fast!</p><p><strong>The Case for Fidelity (Quality)</strong></p><p>Alternatively, faster isn’t <em>always </em>better. It is possible to make a prototype so poorly that you can’t learn anything trustworthy from it.</p><p>Running an effective experiment is not easy. If the prototype is garbage, or it’s tested in a manner resembling a dumpster fire, you may end up with garbage results and garbage insights.</p><p><strong>Speed AND Quality!</strong></p><p>There really is no magic answer that works in every situation. If there is any distilling this topic, it would be the following:</p><p>A prototype is a means to an end. The “best” prototype is the one that achieves the objective as quickly and inexpensively as possible.</p><p><strong>Be thoughtful and deliberate in how accurate and fast you need your prototype to be. Consider exactly what you are trying to learn and build accordingly.</strong></p><h3>18D. Actually Selecting a Final Product Concept</h3><p>I know what you’re thinking: it seems unceremonious to have the section on selecting the final product concept buried within a chapter on prototyping.</p><p>Shouldn’t final concept selection be a momentous occasion worthy of its own Chapter?!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*2vRv3H8Fmv_zykxr3ll-lw.jpeg" /><figcaption>A typical product developer after completing prototyping, ready to select a final concept</figcaption></figure><p>The truth is, in many NPD processes, the final product concept simply evolves through a series of prototypes.</p><p>That’s right; not only is prototyping is a learning mechanism and a scheduling mechanism…it’s also a decision-making mechanism.</p><p>Let’s distill this idea.</p><p><strong>Final Product Concept Decisions</strong></p><p>Here’s a diagram of a typical waterfall-type NPD process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/0*3uxayaBijj4nFloC" /></figure><p>Sure, you’ll see a different overall process in Agile or Lean methods, but that “Build-Measure-Learn” loop is present in every single NPD method out there.</p><p>And — in every NPD method — you eventually have to get off the “Build-Measure-Learn” merry-go-round and ultimately make some decisions. It actually might be more accurate to describe the prototype cycle as “Build-Measure-Learn-<strong>Decide</strong>”</p><p><strong>In practice, prototyping is the primary mechanism used to inform decisions related to selecting a “final” concept.</strong></p><p><strong>The Can Be Only One</strong></p><p>Many NPD methods will involve prototyping a few final product concepts. This may apply for the entire “product” as a whole, but it’s probably more likely to apply to subsystems.</p><p>For example, a “subsystem” prototype might be whether an airplane component be made from aluminum or carbon fiber. Or maybe you’re considering two or three different methods for powering a scooter. Or displaying information on an app. Or the on-boarding process of your software.</p><p>Prototyping each of theses concepts will provide you the insight into which works most effectively. You will learn what works and what doesn’t work.</p><p>You may even learn that you need an entirely new concept to accomplish your objectives, and you’ll iterate back to generating new ideas.</p><p>The looping / iterating process can happen for as long as you have time for it to happen. But if you want to actually launch a product at some point, you have to make a decision and select a final concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/0*6oIbApuTWWvXOyul" /></figure><p>Check out this diagram about Design Thinking. Notice that there is no “big decision moment” when a final product concept is selected — the product just evolves forward until it’s either deemed ready, or more likely, until the NPD team runs out of time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*kUf3TsuyPVgybRhB" /></figure><p><strong>Iterative learning and decision-making drive the team toward the best concept. Decisions are made through protoyping.</strong></p><p>Sure, there are some NPD processes where “Concept Selection” consists of picking one, final concept at the outset and then prototyping it until it works right. For whatever reason, it might be too expensive to prototype multiple different concepts and compare them to one another.</p><p>For situations where that is the case, selecting a product concept is a much more momentous occasion. That might look a little bit more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/0*SsBWqb47LFzC-t1U" /></figure><p>Different products and different organizations will take different NPD approaches.</p><p>In many cases, multiple product concepts are prototyped, and it’s not uncommon for new product concepts to emerge even after “Concept Selection”…thanks to the wonderful insights generated during prototyping.</p><p><strong>In Summary</strong></p><p>Prototyping is going to reveal if the product concept is right. That means that NPD processes should use prototyping to go from a narrow list of possible product concepts to a final one.</p><h3>18e. The Last Word on Prototyping</h3><p><strong>Prototyping is a mechanism for learning.</strong></p><p>The nature of the learning is really up to you and how you design and run your experiments.</p><p><strong>Things you might learn through prototyping:</strong></p><ul><li>Testing hypotheses about customer needs, jobs to be done, target users, the customer journey, and everything else in the problem space</li><li>The connection or causal mechanisms between product specs and features, and product performance or customer value.</li><li>Functionality of any kind</li><li>Business implications, like how much you might be able to charge for a product, or how to promote it to the right end-user.</li><li>Simulating user interaction</li><li>Manufacturability</li><li>Durability</li><li>Design effectiveness and how target users respond to the design</li><li>Cost</li><li>Customer reactions</li><li>Yes, this is a long list, and yes, it could be even longer</li></ul><p><strong>Prototyping is a fundamental building block of the development process.</strong></p><p>The development process can look like one vast, overwhelming window of time. Prototype cycles, on the other hand, are much easier to visualize, easier to schedule, and they provide an effective way to plan progress over time.</p><p><em>“Conceptually, any development project can be thought of (and usually is, at least implicitly) as a sequence of design-build-test cycles.” — </em><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298"><em>Revolutionizing Product Development</em></a></p><p><strong>Prototyping improves communication.</strong></p><p><em>“If a picture is worth 1,000 words, a prototype is worth 1,000 meetings.” — Tom &amp; David Kelley.</em></p><p>The stakeholders involved in NPD are often from a wide range of different backgrounds: executives, marketers, engineers, designers, left-brained, right-brained, big-brained, little-brained. Not everyone speaks the same language. Prototypes reduce miscommunications.</p><p><strong>Prototyping enables better Decision-Making</strong>.</p><p>Better decisions are made when people have more information and more accurate information. For important decisions — like selecting final product concepts — prototyping is the often best way to learn about each option.</p><p><strong>Prototyping begets better and faster future prototyping.</strong></p><p>Prototyping is a skill that can be improved through practice or study. While we’ve only distilled the topic here in Chapters 16, 17, and now 18, this is by no means the final word on the topic. See the list of resources below for further reading.</p><p><strong>Resources</strong></p><p><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298">Revolutionizing Product Development</a> has some 65 pages on prototyping: methods, tools, best practices, etc. It’s definitely oriented heavily toward physical products more than digital products.</p><p><a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a> and <a href="https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874">The Lean Product Playbook</a> are both good places to start with understanding lean (and often digital product) prototyping. Or refer to anything written by <a href="https://www.amazon.com/Steve-Blank/e/B002IBT21M">Steve Blank</a>.</p><p><a href="https://www.smashingmagazine.com/2017/12/prototyping-driven-process/">Everything you wanted to know about prototyping</a>. Another good article.</p><p><a href="https://boagworld.com/usability/prototyping/">Good online guide for digital and UX prototyping</a> at boagworld.com</p><p><a href="https://uxknowledgebase.com/prototyping-part-1-e7d606cde30b">A nice infographic on Prototyping</a></p><p>See Product Development Distillery’ <a href="https://medium.com/product-development-distillery/chapter-16-prototyping-cf1e7d12f559">Chapter 16 — Prototyping</a> and <a href="https://medium.com/product-development-distillery/chapter-17-prototyping-in-agile-and-lean-263bcf2861d4">Chapter 17 — Prototyping in Agile and Lean</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81b9ca9cf743" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/chapter-18-prototyping-iii-moderately-advanced-topics-81b9ca9cf743">Chapter 18 — Prototyping III: Moderately Advanced Topics</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 17 — Prototyping in Agile and Lean]]></title>
            <link>https://medium.com/product-development-distillery/chapter-17-prototyping-in-agile-and-lean-263bcf2861d4?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/263bcf2861d4</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Fri, 15 Nov 2019 15:06:01 GMT</pubDate>
            <atom:updated>2021-01-05T18:21:20.950Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 17 — Prototyping in Agile and Lean</h3><p><em>Note: This content is from the Product Development Distillery e-mail series: a weekly e-mail that helps teach essential product development skills. Click here to sign up:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BSiL9GGiyRu04b1l.png" /></figure><h3>17a. Agile and Lean Distilled</h3><p>Having introduced the topic of prototyping in <a href="https://medium.com/product-development-distillery/chapter-16-prototyping-cf1e7d12f559">Chapter 16</a>, let’s now do a brief dive into the worlds of Agile and Lean.</p><p>Agile and Lean involve unique methods and techniques when it comes to prototyping. It would be hard to say you’ve learned “Prototyping 101” without covering them, so we gotta do it.</p><p>Here come Agile and Lean…distilled.</p><p><strong>Agile</strong></p><p>Agile principles were created to facilitate better product development in situations where traditional methods (Waterfall) were not working so well.</p><p>Agile is especially popular in digital and software product development, where an ongoing iterative approach makes sense.</p><p>Agile is really more of a set of principles than it is a rigid set of procedures or methods. There are certainly popular “Agile” methods — things like Scrum and Sprints, which we’ll discuss soon. But while those methods may evolve over time, the foundational principles of Agile do not.</p><p>Here are some more principles of Agile, with some Lean principles mixed in as well:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*nZpIPEEAMyk7j1mt.png" /><figcaption><a href="https://www.scaledagileframework.com/safe-lean-agile-principles/">Source</a></figcaption></figure><p>Agile principles and methods might work for your product development situation, or they may not. It’s best to understand them so that you have the ability to apply them if and when it’s appropriate.</p><p><strong>Lean</strong></p><p>Lean is like Agile in that it’s a set of principles. Lean principles are focused on efficiency, speed, and eliminating waste.</p><p>Lean principles can be applied to anything. You may have heard the term Lean Production or Lean Startup. Those terms just mean doing Production or starting a company in a consciously efficient and fast manner.</p><p><strong>When applied to product development, lean principles are designed to achieve a faster and more efficient product development process.</strong></p><p>If that sentence made your eyes glaze over, here’s an easier thought: <strong>Lean means fast</strong>.</p><p>“The only way to win is to learn faster than anyone else.” — Eric Ries, author of <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a>.</p><p>Here’s another quote, this time about Lean Production.</p><p><em>“Lean production…is “lean” because it uses less of everything compared with mass production — half the human effort…half the investment in tools…half the engineering hours to develop a new product in half the time.” — </em><a href="https://www.lean.org/Bookstore/ProductDetails.cfm?SelectedProductID=160"><em>The Machine That Changed the World.</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*qoD_cpPavvmEhSCw" /></figure><p>The Lean approach includes methods and practices like ‘forming teams of experts,’ ‘concurrent processes,’ ‘cadence and pull,’ and ‘visual management.’ I’m not going to dive into these here, but the common thread to Lean is doing stuff that improves speed and efficiency and reduces waste.</p><p><strong>Why Talk Lean and Agile Now?</strong></p><p>Lean and Agile bring some fresh ideas to the table when it comes to prototyping and the process of Build-Measure-Learn.</p><p>You’ll see how in the next few sections, where we’ll cover:</p><ul><li>The MVP (Minimum Viable Product)</li><li>The Sprint</li><li>Scrum</li></ul><p>Enjoy!</p><h3>17b. The MVP (Minimum Viable Product) Distilled</h3><p>The MVP is one of the “hottest” concepts in all of product development — especially recently in the “Lean Startup” world of Silicon Valley.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*OHqk_L8e5zH2LoNF" /><figcaption><em>Yes, that’s two Zoolander references within the topic of Prototyping.</em></figcaption></figure><p>Let’s distill this often used and abused concept.</p><p><strong>MVP Defined</strong></p><p>The term Minimum Viable Product was popularized by Eric Ries in his book <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a>.<em> </em>Here’s what he has to say:</p><p><em>“The MVP is that version of the product that enables a full turn of the Build-Measure-Learn loop with a minimum amount of effort and the least amount of development time.” — </em><a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898"><em>The Lean Startup</em></a><em>, Eric Ries</em></p><p>See that “build measure learn” reference in there? An MVP is really a prototype in the broadest definition of the word. It’s a minimal version of the product, built to facilitate learning.</p><p>MVP = Minimum Viable Product = A prototype that facilitates testing and learning with minimal investment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t-fJIcG1HGGMkzil" /><figcaption><a href="https://fourweekmba.com/minimum-viable-product/">Source</a></figcaption></figure><p><strong>What’s An MVP For?</strong></p><p>Like I just said, an MVP is all about learning.</p><p><em>“A minimum viable product (MVP) helps entrepreneurs start the process of learning as quickly as possible. 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.” Eric Ries</em></p><p>Steve Blank, the author of <a href="https://www.amazon.com/Four-Steps-Epiphany-Steve-Blank/dp/0989200507">Four Steps to the Epiphany</a>, also uses the term “Minimum Feature Set” to describe essentially the same thing.</p><p>The point here is efficient learning. Don’t build more than you need to in order to start learning about your market and the customers.</p><blockquote><em>“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.” — Eric Ries</em></blockquote><p><strong>Here’s An Example</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/0*UFpFhHXoRwVWdw7O" /><figcaption><a href="https://www.interaction-design.org/literature/article/minimum-viable-product-mvp-and-design-balancing-risk-to-gain-reward">Source</a></figcaption></figure><p>If you suspect that customers need to get around town, and maybe you have a grand vision for something like a car, how would you build an MVP?</p><p>According to the Lean Startup approach, a skateboard is a good start. Then iterate and prototype a scooter. Then a bike…and so on and so forth.</p><p>Each iterative loop of build-measure-learn gives you more and more insight about the customer and his or her preferences. More learning allows you to build better solutions.</p><p>Contrast that with trying to achieve some final vision for the product by prototyping subsystems. That approach does not facilitate learning in the same way.</p><h3>17c. MVPs Help You Learn About the Product and the Market and the Customer</h3><p>I’ve been saying that prototyping is a mechanism for learning. That’s true.</p><p>The critical distinction that you need to know is that in Agile and Lean approaches, the prototype is the mechanism where much of the learning about the customer/consumer happens.</p><p>Contrast this with traditional approaches (Waterfall) where the learning is done more upfront, using market research and voice-of-customer methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*md0aLFUINcTYeTch" /><figcaption><a href="https://brandgenetics.com/sprint-by-google-ventures-speed-summary/">Source</a></figcaption></figure><p>See the difference?</p><p>Building and testing a prototype is one of the most efficient and rapid ways to learn. So if you need to learn about consumer needs, use prototyping!</p><p>You can see why this approach is huge in the startup world. In a Startup, uncertainty is high. We’re talking both product uncertainty and business uncertainty.</p><p>When there’s so much uncertainty, and often only so much time before the money runs out, rapid learning is paramount. You don’t spend months understanding customer needs — you build an MVP in a week and go!</p><p>This is a sound approach…<strong>when it’s possible</strong>.</p><p>Again, there are few things in NPD that apply in every situation, and some products simply don’t lend themselves well to this method. Sometimes it is critically important to know the market and the consumer better from the outset, and then use prototyping to validate well-researched hypothesis.</p><h3>17d. The MVP: Not Just for Startups</h3><p>The Minimum Viable Product is a limited version of a product concept that can help entrepreneurs (or product developers) begin the process of rapid, iterative learning.</p><p>“But I don’t work at a startup. Stop talking to me about MVPs.” — Some people</p><p>OK, fair enough…let’s address this. Are MVPs only relevant for people working at startups?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*XmRpSSJhbknUpM-p.jpg" /></figure><p><strong>Startups and Products — Same Difference — It’s All About Learning</strong></p><p>Yes, most people who talk about MVPs are typically talking about them in the context of startups. Some people — even Eric Ries himself — will draw a distinction between prototoypes and MVPS.</p><p><em>“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 hypothesis.” Eric Ries, author of The Lean Startup</em></p><p>So is an MVP a prototype? Potato potato.</p><p><strong>A simple way to distill it: an MVP is basically a prototype that also tests a business hypothesis, not just a product hypothesis.</strong></p><p>What is ultimately important is that MVPs and prototypes are both methods that share a common goal: learning.</p><p>And since all NPD processes require product developers to learn (about customers, markets, technical features, etc.) it’s worthwhile to study MVPs in order to broaden your learning skill set.</p><p>Whether you are prototyping a company or whole product or a small product feature, you want to build something, test it, and learn how to improve it. That’s a universal skill needed in all product development processes.</p><p><em>“The fundamental activity of a startup is to turn ideas into products, measure how customers respond, and then learn whether to pivot or persevere. All successful startup processes should be geared to accelerate that feedback loop.” — Eric Ries</em></p><p><strong>Some Final Tips For Building MVPs</strong></p><ul><li>Measure something. If you’re not measuring something, how will you know if it worked?</li><li>Fake it. Users can’t tell if a human is behind the curtain making the MVP work. You don’t have to write code if you don’t have to.</li><li>On the one hand, don’t care too much about what people will think of the MVP…</li><li>…On the other hand, don’t bum out your customers. Here’s <a href="https://medium.com/the-happy-startup-school/beyond-mvp-10-steps-to-make-your-product-minimum-loveable-51800164ae0c">a good article</a> about making a Minimum “Lovable” Product which offers some good contrasts to the typical MVP discussion.</li><li>MVP’ing can happen all the time. It’s not a one-and-done process. It can be used over and over for new product features.</li></ul><h3>17e. The Design Sprint</h3><p>The “Sprint” is definitely something worth familiarizing yourself with if you plan to get into product management and/or product development.</p><p>While it sounds somewhat generic (i.e. let’s just go fast!), there’s actually a formula to a Sprint. Let’s distill it.</p><p><strong>What’s a Sprint?</strong></p><p>Sprints are a method used in Agile product development to add a feature, update a product, or push toward some key milestone of learning.</p><p><strong>Sprint </strong>— a fast-paced time-bound exercise designed to learn something about a product or business.</p><p><em>“The “Sprint” is a “five-day process for answering critical business questions through design, prototyping, and testing ideas with customers.” — Google Ventures.</em></p><p>(I cite Google because two people from Google actually formalized the currently accepted recipe for a Sprint. That’s right, the 5-day Sprint was kind of born at Google.)</p><p><strong>Anatomy of a Sprint</strong></p><p>The structure of a Sprint is very much like a micro-version of designing a product:</p><ol><li>Understand</li><li>Diverge</li><li>Decide</li><li>Prototype</li><li>Validate / Test</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/0*eGZaC0jv7HU6s2r_" /><figcaption><a href="https://boagworld.com/usability/prototyping/">Source</a></figcaption></figure><p>Looks kinda familiar, right? It’s kind of an accelerated NPD process. (See P.S. below.)</p><p>Now, this exact 5-day sequence isn’t written in stone; different teams will adapt the general process and timing to their needs But one thing that doesn’t change is that a Sprint is always brief — like a month or less. You can’t really call a two month project a ‘Sprint,’ amirite?</p><p><strong>Sprints have Objectives</strong></p><p>Another key element of a Sprint: clear objectives. Sprints are used to solve something — they are objective driven, not open-ended. Whether it be validating that a market exists or that a product feature should be fully developed, Sprints are much like prototypes — they are a mechanism for rapid learning about something specific.</p><p><strong>P.S. A 30 second rant on the similarities in all of product development</strong></p><p>You: “Wait…is a ‘Sprint’ just an accelerated product development process squeezed into 5 days and repackaged as a new thing?</p><p>Me: “Uh…..sort of?!”</p><p>The Sprint may seem so new and cool, but it’s really very similar to the traditional method of product development.</p><ul><li>Understanding users and needs — that’s always something you have to do (voice of customer, jobs to be done, outcomes, design thinking, get out of the building).</li><li>Diverge? That’s generating ideas and exploring the solution space (OST, Where good ideas come from).</li><li>Decide. Of course as some point you need to converge on a few best concepts.</li><li>Prototype. Yup — everyone does it.</li><li>And validate or test — that’s inherent in the build-measure-learn cycle of prototyping.</li></ul><p>So while the concept of Sprinting is relatively new, it’s really based upon the traditional NPD approach.</p><h3>17f. Scrum</h3><p>Scrum is a very widely used method in Agile development, so let’s distill this concept and understanding the fundamentals.</p><p><strong>The Scrum Process</strong></p><p>Basically, the process is:</p><ul><li>Prioritize the product backlog (i.e. decide “what should we build next?”)</li><li>Sprint planning (i.e. let’s bite of a small chunk of stuff and build just that)</li><li>2–4 weeks sprint (i.e. focused collaborative team effort to ship the new stuff)</li><li>Retrospective (i.e. what went well, what didn’t?)</li></ul><p>Obviously this process is highly simplified, but you get the gist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*Fh8aIeKBNzVPOpfo" /><figcaption><a href="http://www.the-program-manager.com/agilepm/agile-scrum-overview-process-planning/">Source</a></figcaption></figure><p><strong>Scrum Fundamentals</strong></p><p>Scrum is a framework, or a general approach, for “developing, delivering, and sustaining” complex products.</p><p>Scrum uses Sprints to chip away at a product feature Backlog. A backlog is just a prioritized list of new features or updates you want to build for your product.</p><p>Other Fundamental Points:</p><ul><li>Part of Agile</li><li>Utilizes Sprints.</li><li>Has clear roles. Scrum Master. Scrum Team. Product Owner.</li><li>Breaks a bigger project down into pieces</li><li>Good for urgent, complex and novel projects</li><li>Emphasis on communication and cross-functional work</li><li>Repeating rhythm</li></ul><p>Here is a really long quote from <a href="https://blog.trello.com/beginners-guide-scrum-and-agile-project-management">an article</a> that captures Scrum quite well.</p><blockquote><em>“Agile refers to a set of “methods and practices based on the values and principles expressed in the Agile Manifesto,” which includes things like collaboration, self-organization, and cross functionality of teams.</em></blockquote><blockquote><em>Scrum is a framework that is used to implement Agile development.</em></blockquote><blockquote><em>A good analogy would be the difference between a recipe and a diet. A vegetarian diet is a set of methods and practices based on principles and values. A recipe for chickpea tacos would be a framework you can use to implement your vegetarian diet.</em></blockquote><blockquote><em>This is similar to the relationship between Agile (the diet) and Scrum (the recipe you follow).</em></blockquote><p><strong>Daily Scrum Meeting</strong></p><p>When you read about Scrum, you’ll always read about The Daily Standup. This is a daily meeting that actually has a rigid 3-part agenda. That agenda is:</p><ul><li>What did you do yesterday?</li><li>What do you intend to do today?</li><li>Is anything blocking you from doing your work today?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*tzY7x_EKm7PFuiEa" /></figure><p>I think it’s worth familiarizing yourself with The Daily Standup because this type of meeting can be useful in almost any product development method — not just Scrum.</p><p><em>“Scrum enables self-organizing groups by promoting strong communication between the team members along with a few disciplines inside the project. The Scrum model suggests that each and every sprint begins with a short planning meeting and ends with a review. These are the fundamentals of the Scrum idea for project management.” — </em><a href="https://blog.forecast.it/beginners-guide-to-scrum"><em>Source</em></a></p><p>Pro Tip: Bringing the Product Team together to coordinate work is generally a good thing regardless of whether you’re Agile or Waterfall or Whatever.</p><p><strong>In Summary</strong></p><p>The goal of Scrum’s iterative and rhythmic approach is to incrementally improve a product over time. It’s not a “one and done” “new product development” method.</p><h3>Resources</h3><p><strong>Resources for MVPs</strong></p><p>The definitive resource on MVPs is <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a>.</p><p>Here is the author of The Lean Startup Eric Ries giving a talk on MVP from 2009 (<a href="http://www.startuplessonslearned.com/2009/08/minimum-viable-product-guide.html">startuplessonslearned</a>).</p><p><a href="https://boagworld.com/usability/prototyping/">https://boagworld.com/usability/prototyping/</a> — Dang, this is a great article on Prototyping!</p><p><a href="https://www.amazon.com/Lean-Product-Playbook-Innovate-Products/dp/1118960874">The Lean Startup Playbook</a> has very specific instructions for creating and testing MVPs.</p><p><a href="https://www.amazon.com/Four-Steps-Epiphany-Steve-Blank/dp/0989200507">Four Steps to the Epiphany</a> — Steve Blank</p><p><strong>Resources for Scrum</strong></p><p><a href="https://scrumguides.org/scrum-guide.html#purpose">https://scrumguides.org/scrum-guide.html#purpose</a> — START HERE!! Really clear and simple overview</p><p><a href="https://scrumguides.org/docs/scrumguide/v2016/2016-Scrum-Guide-US.pdf#zoom=100">THEEEE Scrum Guide</a> — by Jeff Sutherland and Ken Schwaber, the Godfathers of Scrum.</p><p>Trello <a href="https://blog.trello.com/beginners-guide-scrum-and-agile-project-management">blog</a> on Scrum</p><p><strong>Resources for Sprints</strong></p><p>Brand Genetics <a href="https://brandgenetics.com/sprint-by-google-ventures-speed-summary/">website </a>summarizing the book <a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/1442397683">Sprint </a>by Jake Knapp.</p><p>A <a href="https://www.youtube.com/watch?edufilter=NULL&amp;v=-ivb5R-44ww">video book summary</a> of that same book Sprint.</p><p><a href="http://www.gv.com/sprint/">Google Venture’s site on Sprints</a></p><p><a href="https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/1442397683">Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days</a>. Knapp et al.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=263bcf2861d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/chapter-17-prototyping-in-agile-and-lean-263bcf2861d4">Chapter 17 — Prototyping in Agile and Lean</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 16 — Prototyping]]></title>
            <link>https://medium.com/product-development-distillery/chapter-16-prototyping-cf1e7d12f559?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf1e7d12f559</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Mon, 23 Sep 2019 13:02:45 GMT</pubDate>
            <atom:updated>2021-01-05T18:19:54.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 16 — Prototyping</h3><h3>16a. What is Prototyping</h3><p>Prototyping is one of the main activities in the product development process.</p><p>Along with “Understanding Customer Needs” and “Divergent Thinking,” I’d throw it on the list of “Universal Topics” covered in basically all discussions of product development.</p><p>Let’s understand some of the basics before diving a little deeper into this universally important topic.</p><p><strong>What is a Prototype</strong></p><p>I personally don’t think it’s all that important to narrowly or specifically define the term “prototype.” I use the term broadly and I think it’s perfectly OK to do so.</p><p><strong>Prototype</strong> — An initial or early construction of the product concept, less formed than a “final” product.</p><p><strong>Prototype (definition #2) </strong>— a mock-up, rough draft, a version of your product meant to be iterated upon.</p><p>Pretty much everything made before the final product is a prototype. If you’re designing something that is constantly evolving, like a website, then to some extent, your product is always a prototype of some future version.</p><p>As an activity, <strong>prototyping is all about learning.</strong></p><p>Different NPD methods have their own names for the cycle of building a prototype and learning from it. Some call it “Build Measure Learn.” Others call the cycle “Design Build Test Learn.”</p><p>If you want to get all fancy and advanced (trust me, don’t do it right now), there are some subtle distinctions. But we’re not there yet.</p><p>For right now, just know that prototyping is a catch-all term for building something in order to test a theory. It’s a term that describes a learning system.</p><p><strong>What is the Purpose of Prototyping? (y tho)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/0*PK4jCWo-6JCyj4R2" /></figure><p>Prototyping serves many purposes:</p><p><strong>Learning</strong>. The first obvious purpose of a prototype is to answer the question “will this work?”</p><ul><li><strong><em>Prototyping is an attempt to validate a hypothesis</em></strong>. That hypothesis might be super complex (e.g. our theory is that this system will do X) or super simple (e.g. I wonder if this taco will taste better if I put some tortilla chips into it? Yes, it does.)</li></ul><p><strong>Scheduling</strong>. Another great purpose of prototyping is to drive a project schedule.</p><ul><li>Completing one cycle of building, testing and then analyzing a prototype is a very clear milestone. Many product development teams use a series of prototype iterations as the foundation for their overall project schedule (i.e. we’ll make two prototype iterations and then launch).</li></ul><p><strong>Communication</strong>. Marty Cagen’s book <a href="https://www.amazon.com/Inspired-Create-Products-Customers-Love/dp/0981690408">Inspired</a> purports that the best Product Spec you can build is a prototype. As opposed to writing a 50 page document nobody will read, why not just make a prototype and show people what the product should do?</p><ul><li>While this doesn’t work in all industries (tacos and software maybe, but not rockets), a prototype communicates a lot about the team’s vision for the product. It helps other people “get it” when words just won’t do the trick.</li></ul><p><strong>Ultimately, you’ll see that prototyping is the primary mechanism that product developers use to get from a concept to a finished product.</strong></p><p>We’ll talk more about this subject in coming sections, covering:</p><ul><li>Types of prototypes</li><li>The build-measure-learn cycle</li><li>Learning systems</li><li>As always, best practices and great resources</li></ul><h3>16.b Types of Prototypes</h3><p>Not all prototypes are the same. There are different “types” of prototypes made to accomplish different things. Let’s discuss.</p><p>A <strong>“Looks-Like”</strong> prototype is something that — you guessed it — looks like a product or product concept. It’s a visual representation only. No function. Wireframes are typically “Looks-like” prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*PgFl-pgfKVEAst40" /></figure><p>If you build some functionality into a “Looks Like” prototype, then it becomes a functional prototype. Some people call this a <strong>“Works like”</strong> prototype.</p><p>A “<strong>Functional Prototype</strong>” is a prototype that captures <strong>both </strong>the function and visual appearance of the intended design.</p><p>Functional prototypes don’t work perfectly and are often at a different scale (i.e. smaller) or lacking in some sophistication (i.e. made out of cardboard).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*ogHmvCKSUcKxUJrA" /></figure><p>Sure, I’d call this a Functional Prototype. Pretty clever actually. <a href="https://www.themuse.com/advice/the-fun-30minute-activity-that-will-help-you-solve-your-toughest-work-problems">Source</a>.</p><p>Product developers also use simulation and modeling to prototype products. These are <strong>virtual or analytical prototypes</strong>, thus named because they are virtual and they help you do analysis.</p><p>Virtual prototypes also make pretty pictures for the Marketing department to use in advertising, and you gotta have those if you want to look cool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mDg0goVlpg7vx4ge" /></figure><p>A Virtual or Analytical Prototype. Racecars are cool. <a href="https://mdx2.plm.automation.siemens.com/cfdImage/virtual-wind-tunnel-analysis-f1-race-car">Source</a>.</p><p>Other terms you might want to know include Internal, External, and Public Prototypes</p><ul><li>Internal prototypes — For your eyes only</li><li>External — For key selected users</li><li>Public — For everyone</li></ul><p><strong>System level, sub-system level, component level</strong></p><p>In some cases, prototypes are described by the breadth of the final product they encompass.</p><p>That’s a fancy way of saying that you don’t have to prototype the entire car to test a new brake pad. If you hear the term “sub-system” or “component” prototype, that’s what it means.</p><p><strong>Digital prototyping</strong></p><p>These are often UX prototypes (user experience). They’re used to mimic how the digital product will respond when a user interacts with it. There are many tools to build digital prototypes; you don’t need to learn how to code to make them, which is nice.</p><p><strong>Model</strong></p><p>Even something as unsophisticated as a scale model could be considered a prototype. Below is an image of a scaled-down model of a Center for Children Who Can’t Read Good and Who Wanna Learn To Do Other Stuff Good Too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/0*VY0_9rqvyH9Ag3KV" /><figcaption>Derek Zoolander is not familiar with the concept of prototyping.</figcaption></figure><p><strong>What’s the Best Type of Prototype?</strong></p><p>This is kind of like asking “what’s the best exercise to do in the gym?” It kind of depends on what you’re trying to accomplish. It’s a pretty stupid question, actually.</p><p>The best type of prototype is the one that most effectively accomplishes your goal.</p><p>It’s the tool that gets the job done most efficiently (efficient = lowest cost, fastest).</p><p>Product developers with a wide understanding of prototyping tools and best practices are best equipped to design prototypes efficiently.</p><p>Next we’re going to get into the topic of Build-Measure-Learn, which is the whole point of prototyping.</p><h3>16c. Build-Measure-Learn</h3><p>As said before, prototyping is one of the most important things in all of product development. It’s how you go from concept to product.</p><p>The essence of prototyping can be captured in three simple words: build, measure, curse learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cuFVF-iNXte50N7t" /></figure><p>If I had to summarize what a product development team is doing most of the time, it would be this: people are building shit, measure shit, and learning shit.</p><p><strong>Build-Measure-Learn Distilled</strong></p><p>Prototyping is about building something that might work, testing to see if it does work, and then learning from the result. Build, measure, learn. That’s it.</p><p>Some people change a word or two when describing this process. In general, everyone is talking about the same thing.</p><p>B<strong>uild-measure-learn is ultimately a learning mechanism</strong>. Prototyping is a learning mechanism.</p><p><em>“…the basic cycle consists of taking the current thinking regarding the design, building a prototype that embodies the key aspects of that thinking, and then testing that prototype to determine where additional design refinements are and are not needed.” — </em><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298"><em>Revolutionizing Product Development</em></a></p><p><strong>Why is it So Important?</strong></p><p>Product development is a process that involves hundreds or thousands of decisions.</p><p>In product development, we must go from a state of high uncertainty to a state of low uncertainty.</p><p>In order to make better decisions and to reduce uncertainty, you need knowledge. In order to have knowledge, you need to learn. How do you learn? Through prototyping.</p><p><strong>Iterations</strong></p><p>Product development — and prototyping in general — is highly iterative.</p><p>If we knew how to get the product right on the first try, we wouldn’t need prototyping…but we don’t know how to do that, ergo we need prototyping. (Not often you get to use the word “ergo”)</p><p>You’ll hear terms like “iterative” or “loops” or “cycles” or “spirals” thrown around in product development. In general, these are all the same thing — they describe the build-test-learn process.</p><p>You may also hear the term iteration velocity. It’s a fancy term, but a basic and important concept.</p><p><strong>Iteration velocity</strong> — the speed with which a person/team/organization can build, measure and learn.</p><p>Iteration velocity will determine how many loops or spirals can be achieved in a given time period. If you’re constrained by a market launch target, which is often the case, then your iteration velocity will determine how much learning you can achieve before you go to market.</p><p>More learning, better product.</p><p>Faster iteration velocity, more learning.</p><p>Faster iteration → better product. (That’s the transitive property #logic)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/648/0*VegcRhKitA9Sc_lR" /><figcaption>Source of this image: <a href="https://boagworld.com/usability/prototyping/">Boagworld</a></figcaption></figure><h3>16d. Learning Systems</h3><p>At the risk of being too academic, I’m going to take a minor detour to talk about the fundamentals of learning very briefly.</p><p>This detour will illustrate why “Build-Measure-Learn” isn’t some “new” system invented in the last few years. It’s sort of what everyone has been doing everywhere to learn about stuff.</p><p><strong>Learning System 1: The Scientific Method</strong></p><p>Yes, this is the thing you learned about in middle school.</p><p>I don’t really know how to put this, but the scientific method is <em>kind of a big deal</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/779/0*Jp9b-ULnPCQKw-zv" /><figcaption><a href="https://memegenerator.net/instance/43317663/ron-burgundy-big-deal-i-dont-know-how-to-put-this-but-im-kind-of-a-big-deal-people-know-me">Source</a></figcaption></figure><p>It’s not an exaggeration to say that the Scientific Method is the framework used to make some of the most important discoveries in humanity — you know, things like the evolution of species, vaccines, DNA, and gatorade.</p><p>You can read all about the scientific method <a href="https://en.wikipedia.org/wiki/Scientific_method#Process">on wikipedia</a>, but here’s the distillation: the scientific method involves making a hypothesis, running an experiment, and then comparing the observed results against the prediction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*8exOfW_ZvNImJSHq" /><figcaption><a href="https://miro.medium.com/max/2000/1*BIpwL3Fz6FZ_lL8xROfXvA.png">Source</a></figcaption></figure><p>Look familiar? The Scientific Method is a lot like Build-Test-Learn.</p><p><strong>Learning System 2: P.D.C.A.</strong></p><ul><li>Plan — what did you plan to do?</li><li>Do — what did you actual do?</li><li>Check — what was different between the plan and the do? Why?</li><li>Action — now what?</li></ul><p>P.D.C.A. is technically a control system, but it’s also fundamentally a learning system.</p><p>It asks “Why didn’t the thing that actually happened match what I wanted to happen, and now what do I do about it?”</p><p>Sound familiar?</p><p><strong>Learning Systems</strong></p><p>The Scientific Method and P.D.C.A. are both examples of learning systems. They are a codified process — a system — for learning. Just like the Terminator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/0*43hgIQsNcd9E7mER" /><figcaption><a href="http://ru.memegenerator.net/instance/67256858/terminator-face-my-cpu-is-a-neural-net-processor-a-learning-computer-the-more-contact-i-have-with-hu">Source</a></figcaption></figure><p>Machine Learning actually happens through a process not that different from Build-Measure-Learn or the Scientific Method. Cool, right?</p><p>Also…“the more contact I have with humans, the more I learn”…this is pretty accurate for product developers, not just robots from the future sent back in time to kill or protect us.</p><p>But I digress…</p><p><strong>Build-Measure-Learn is System for Learning.</strong></p><p>Build-Measure-Learn is the (pronounced thee) preferred system for learning in product development. There has yet to be a system invented that works better.</p><p>This is because Build-Measure-Learn is basically modeled after the Scientific Method. And since the Scientific Method has been around for centuries, I’m guessing Build-Measure-Learn is going to be popular for quite some time.</p><p><strong>Last Point — Have a Hypothesis</strong></p><p>In the Scientific Method, it’s critical to have a hypothesis. Scientists don’t just run random experiments — they test certain theories or assumptions.</p><p>The same should happen in product development. Think of a prototype as a hypothesis and an experiment.</p><p>Prototyping should serve to test specific assumptions or theories — from “will this two parts fit together” to “will people actually like this product.”</p><p>Here’s a great quote on this topic from a great book on Innovation called <a href="https://www.amazon.com/Other-Side-Innovation-Execution-Challenge/dp/1422166961">The Other Side of Innovation</a> (capital emphasis mine):</p><blockquote>“Before launching an experiment, write down what you plan to do, what you expect to happen, and why. Draw lessons learned by analyzing differences between what you thought would happen and what actually happened. Then, based on lessons learned, revise the plan….THAT IS THE WHOLE BALLGAME! If you can execute this process rigorously and dispassionately, your chances of drawing the right lessons learned from a business experiment go up dramatically. The crucial learning step is the analysis of the disparities between predictions and outcomes. Through this analysis, assumptions are either validated or invalidated. Lessons are learned. Predictions improve. The process of learning through experimentation is the scientific method.” <a href="https://www.amazon.com/Other-Side-Innovation-Execution-Challenge/dp/1422166961">The Other Side of Innovation</a>.</blockquote><h3>16e. One Prototype Does Not Fit All</h3><p>To wrap up this first section on prototyping (oh yeah, this is just the beginning of prototyping…there’s more to come), let’s compare how prototyping works in two of the most prominent NPD methods out there: Waterfall and Agile/Lean.</p><p><strong>Waterfall</strong></p><p>Recall that in Waterfall, product development flows in a fairly linear path, from voice-of-the-customer activities to the product spec to prototyping and then to final product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*b9rMLz7p0u41g7Zf" /><figcaption><a href="https://www.lollypop.design/media/5644/waterfall-method.jpg">Source</a></figcaption></figure><p>The Waterfall method places relatively more emphasis on “learning about the customer up front” and relatively less emphasis on “prototype and iterate until it works.”</p><p>This is because Waterfall is typically employed for products that are expensive to create, or products which need to be built right the first time. Think satellites or rockets.</p><p>In some of the best books covering Waterfall methodology (<a href="https://www.amazon.com/Winning-New-Products-Creating-Innovation/dp/0465025781">Winning at New Products</a>, <a href="https://www.amazon.com/Product-Design-Development-Karl-Ulrich/dp/0073404772">Product Design and Development</a>), the topic of prototyping is not central or even all that prominent.</p><p>Sure, prototyping is in those books — it’s not like they don’t discuss it — and it certainly happens at a sub-system level. <strong>But the emphasis for Waterfall is on learning about the customer/consumer up-front, and getting the product spec right through rigorous vetting/analysis earlier in the process</strong>.</p><p><strong>Lean and Agile</strong></p><p>These days, the Lean and Agile methods have become more prominent as more and more NPD efforts focus on digital products (software, or apps) as opposed to physical products.</p><p>Since writing code is “free” (other than paying that pesky engineer), the one-and-done linear approach of Waterfall is less applicable and relevant.</p><p>Books like <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a> and <a href="https://www.amazon.com/Four-Steps-Epiphany-Steve-Blank/dp/0989200507">Four Steps to the Epiphany </a>and <a href="https://www.amazon.com/Inspired-Create-Products-Customers-Love/dp/0981690408">Inspired </a>reflect this shift. They are great books, and they all contain some universal NPD lessons, but they are definitely most applicable to software or startups.</p><p>Prototyping is basically the most important NPD process for these types of products because it’s “free” — and highly effective — to just code up a prototype and test it with actual consumers. The general ethos of these books is to just “build something and start learning.” Less emphasis is placed on upfront voice-of-the-customer activities.</p><p>We’re going to talk a lot more about Lean and Agile in coming chapters, so more to come…</p><p><strong>In Conclusion</strong></p><p>Prototyping is pretty, pretty, pretty much a universal activity in product development (read that sentence in Larry David’s voice).</p><p>It is the best method we have to go from a concept to a refined product.</p><p><em>“Except for the easiest of problems, developers are unlikely to come up with a complete, effective design in a single iteration. Instead, developers go through several iterations, learning a little more about the problem and alternative solutions each time, as they converge to a final design and complete, detailed specifications.” — </em><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298"><em>Revolutionizing Product Development</em></a></p><p>Still, there isn’t a one-size-fits-all approach to prototyping.</p><p>Waterfall and Agile methods put a different emphasis on prototyping. This is because the cost (time and money) associated with prototyping varies significantly depending on what kind of product being developed.</p><p>In other words, how and when to use prototyping depends on the nature of the product itself.</p><p>That said, prototyping is universally about learning. No matter what type of product you’re developing or what methodology you’re following, you ain’t gonna get it right the first time.</p><p>Prototyping is a way to iterate forward, gain knowledge, and make better products.</p><p><strong>Key Points on Prototyping</strong></p><ul><li>Pretty much everything other than the final product is a prototype.</li><li>There are lots of different kinds of prototypes — from “looks like” to “works like” to sub-system prototypes and wireframes.</li><li>The goal of prototyping is to learn. It is a learning system, like the scientific method.</li><li>The essence of prototyping is the Build-Measure-Learn cycle.</li><li>Prototyping and product refinement is iterative: cycles, spirals, loops.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf1e7d12f559" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/chapter-16-prototyping-cf1e7d12f559">Chapter 16 — Prototyping</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chapter 15 — Concept Selection]]></title>
            <link>https://medium.com/product-development-distillery/chapter-15-concept-selection-1581bb7caa10?source=rss-77ee38f16189------2</link>
            <guid isPermaLink="false">https://medium.com/p/1581bb7caa10</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jeff Brunski]]></dc:creator>
            <pubDate>Thu, 15 Aug 2019 13:03:11 GMT</pubDate>
            <atom:updated>2021-01-05T18:18:06.324Z</atom:updated>
            <content:encoded><![CDATA[<h3>Chapter 15 — Concept Selection</h3><p><em>Note: This content is from the Product Development Distillery e-mail series: a daily e-mail that helps teach essential product development skills. Click here to sign up:</em></p><figure><a href="http://eepurl.com/driGaH"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GekKrsiJutsOTaYTHkYbvg.png" /></a></figure><h3>15a. Concept Selection Intro</h3><p>Let’s get reoriented.</p><ul><li>We’ve done voice-of-the-customer research and tried to identify the needs of our users, their jobs-to-be-done, and/or the outcomes they care about.</li><li>We’ve detailed the problem space as much as possible, though we know there is still more to learn because we haven’t even begun prototyping our own solutions.</li><li>We wrote a Marketing Spec and used divergent thinking to come up with a lot of solution concepts.</li></ul><p>Next we want to proceed into prototyping with our best concept(s)…we just need to identify which ones those are.</p><p><strong>What does concept selection look like?</strong></p><p>It can look like a whole lot of different things.</p><p>Selecting concepts can definitely look like proceeding with your first idea, because a lot of people don’t take the time to really consider the full range of concepts.</p><p>Selecting concepts can also look like an extensive, “stage gate” process with thorough committee vetting and analysis, because maybe proceeding with the wrong concept could cost you millions of dollars.</p><p>But, selecting concepts might also look like simply building a minimum viable product that can let you start testing some assumptions, because more than anything, time is short and uncertainty is high.</p><p>No matter what it looks like at your organization or situation, the universal thing is that your face is, at one point or another, eventually going to look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/0*wtl9KnGnZSxfPcI7" /></figure><p><strong>Different Strokes…</strong></p><p>Throughout these chapters, I’ve pointed out a number of situations where the path forward diverges and different folks go different ways.</p><p>Concept selection is perhaps the mother of different strokes for different folks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/0*2tg6LYuunct9XtyY" /></figure><p><em>Waterfall</em></p><p>In the waterfall method, making changes downstream is typically very costly.</p><p>If you’re building a new car, a new phone, or a new satellite, you need to select a somewhat narrow group of solution concepts and be fairly confident in them.</p><p>For example, if you think that new phone should be made out of glass instead of aluminum, that’s something you had better be pretty committed to. With so many implications flowing from that decision — and so much time and money required to prototype and test — you had better take the time to ensure that glass is indeed the best concept.</p><p><em>Lean Startup</em></p><p>In software development and product development methods related to digital products (Agile, Lean), you’ll see much less pressure and emphasis on “selecting the best concept at the start of prototyping.”</p><p>In these methods, learning and iterating is typically less expensive; you just need a good concept to start the prototyping/learning process.</p><p><em>An Aside: Lean Startup is Like Natural Selection</em></p><p>One analogy for this lean approach is natural selection. There is no point at which nature stops everything and decides which is the best “concept.” Nature has a mechanism — survival of the fittest — and when a species iterates over and over, that mechanism improves the design and the concept evolves and improves.</p><p>Products which can be relatively easily prototyped (software) can evolve and come into being in a similar fashion. They can be prototyped faster and cheaper than can physical products.</p><p>Thus it is often more important to get right into prototyping than it is to make a really good single decision at the concept selection phase.</p><p><strong>In Summary</strong></p><p>Concept selection is about finding the best concepts to proceed forward with prototyping during the product development process.</p><p>One single approach to concept selection doesn’t fit all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*RsgmiBcBT3Br6s9i" /></figure><p>Understanding the different approaches used across various PD methodologies will give you the perspective to select the tools, methods and techniques that might work best in your situation.</p><p><strong><em>A quick rule of thumb: you should determine how much emphasis to put on good concept selection depending on how expensive (time and money) it is to pivot and change course downstream.</em></strong></p><h3>15b. Concept Selection and the Art of Convergent Thinking</h3><p><strong>Convergent Thinking</strong> thinking is the mongoose to the snake of divergent thinking. Or maybe it’s the snake to the mongoose. Either way it’s like the opposite.</p><p>Where divergent thinking describes going from 3 ideas to 4 — diverging, if you will — convergent thinking is a narrowing-in process — converging.</p><p>Convergent thinking helps you <strong>converge </strong>on an idea (see how those are the same words?!).</p><p>Convergent thinking typically involves analysis, critical thinking, and planning. It’s really not that different from what you do many times a day — which is to <strong>make decisions</strong>.</p><p>Here’s a good video on divergent and convergent thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iFycjSNNR2R2kd1y" /><figcaption><a href="https://www.youtube.com/watch?time_continue=13&amp;v=xjE2RV6IQzo">Link</a> to this video on Convergent Thinking (Harvard University)</figcaption></figure><p>Or my favorite image from Tim Brown:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/0*bk8R2KlTZOiK1vQx" /></figure><p>Since concept selection deals with going from many solution concepts to the one or two or ten that you’ll proceed forward with into prototyping, <strong>convergent thinking is basically the universal mechanism used in concept selection.</strong></p><p><strong>Convergent Thinking Done Right</strong></p><p>For a lot of people, decision-making is difficult.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/0*DqdPX2ENvJoXicQU" /></figure><p>Me, just trying to figure out where to go to lunch.</p><p>If this is what you look like when you need to make a decision or think convergently, that’s OK! Convergent thinking is not an innate talent that some lucky few are born with; it is a skill and it can be developed.</p><p><strong>Bad Methods of Making Decisions</strong></p><p>It is stupid easy to proceed forward with decision-making in a haphazard way.</p><p>Here’s what typically happens: you need to make a decision, you call a meeting, you present the information, and then…people start talking and all hell breaks loose.</p><p>Typically the highest paid person’s opinion carries the day (<a href="https://www.forbes.com/sites/derosetichy/2013/04/15/what-happens-when-a-hippo-runs-your-company/#b86767b40cf5">HIPPO</a>) and people move on with their lives, happy to be out of the meeting, but typically not so happy with the outcome.</p><p>Other bad methods include:</p><ul><li>The shiny new object, most new idea is best</li><li>The first idea is the best idea because we’re most comfortable with it</li><li>The “what does my gut tell me” method of convergent thinking</li><li>The “spin the wheel or flip a coin” leave-it-to-chance method</li><li>The “what does our biggest customer want” approach</li></ul><p>Long story short: these are not effective convergent thinking methods.</p><p><strong>Good Methods of Convergent Thinking</strong></p><p>I’m going to cover two main methods: structured methods and a democratic method.</p><p><em>Structured Methods</em></p><p>Many traditional PD books show step-by-step processes for convergent thinking or decision-making. I call these “structured decision making processes.” They have structure, or a clear process. Do A then B then C.</p><p>These methods may seem prescriptive and therefore stale and not cool, but as we distill them, you’ll see that they are based on the natural, logical foundations of analytical thinking.</p><p><em>Democratic Methods</em></p><p>In more modern product development teaching, there is a big emphasis on cross-functional teamwork. This means a team of people from different disciplines — Engineering, Marketing, Sales, Manufacturing — working together. Concept Selection absolutely benefits from a cross-functional approach, and I’m going to call any approach that emphasizes gathering cross-functional input a “Democratic Approach.”</p><p>In the next two sections, I’m going to distill these two methods.</p><h3>15c. Convergent Thinking Using Structured Decision-Making</h3><p>Every day, we all make decisions. We all think convergently. The method we use in our day-to-day lives is actually quite similar to the structured method advocated in many NPD books. In this section, I’ll distill this <strong>structured decision-making process</strong>.</p><p><strong>Structured Decision-Making Distilled</strong></p><p>In almost every single case, all structured systems for convergent thinking look the same: different concepts are compared across a few key criteria, using scoring and weighting to give each option a single final “score.” The option with the best score is the best option.</p><p>Here’s an image that makes this approach much more clear:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b6FBGOILleCJObNf" /></figure><p>Source: Ulrich and Eppinger</p><p>As you can see, different concepts — a lever stop, swash ring, and dial screw — are compared across a bunch of different criteria: ease of handling, ease of use, durability, etc.</p><p>The relative weighting of these criteria is also assigned. By doing some basic math, a total score and rank for each option can be calculated.</p><p>This process goes by many names: matrix-rating, category-weighting, decision-matrix.Call it what you want — the overall structure is relatively consistent:</p><ul><li>List your options</li><li>Create categories based on what is important for the choice to achieve</li><li>Weight each category</li><li>Score each option in each category</li><li>Total it up</li></ul><p>Here is <a href="https://www.youtube.com/watch?time_continue=111&amp;v=xO7xJ1sTyPI">a 2 minute video</a> on making a decision matrix.</p><p><strong>Pugh Matrix</strong></p><p>A Pugh matrix is just like a decision-matrix, but it is different in two ways. First, it was invented by a dude named Pugh. Second, it replaces numbered scoring with a simple “+, 0, -” scoring.</p><p>These scores can loosely be translated to “better than” and “similar to” and “worse than.”</p><p>Here’s a Pugh matrix example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Hkqntdxbnlg2f5j7" /></figure><p>A Pugh matrix is a little more simple and elegant than the number-based decision-matrix.</p><p><strong>Not Necessarily One Single Concept</strong></p><p>Check out the last row in that Pugh matrix. See how it says “Continue?” And then for some concepts, it says “combine?”</p><p>Remember, the goal is to develop the best concept. Combining concepts or stealing from one and adding to another is not illegal.</p><p>If in the course of your convergent thinking process, you see how to improve a concept or combine two concepts into one super concept, then do it!</p><p>Also, if you look at the entry for <a href="https://en.wikipedia.org/wiki/Convergent_thinking">convergent thinking in wikipedia</a>, it describes converging on a single, “correct” answer.</p><p>In most product development situations, you don’t need to pick just one “correct” concept to prototype.</p><p>Concept Selection is a narrowing process; <strong><em>HOW</em></strong> narrow — one, two, ten — depends on the situation.</p><p>And in some cases, you really don’t need to “select” a concept so much as “deselect” concepts. Turning projects off and eliminating concepts is called “Concept Screening.” It’s very helpful — perhaps equally helpful to Concept Selection.</p><p><em>Product Developers use Concept Selection and Concept Screening as necessary to narrow in on a workable number of product concepts to pursue.</em></p><p><strong>A Structured Decision-Making Example</strong></p><p>Here’s a stupid simple example from our everyday lives to visualize this process that you’ve surely used a million times without even realizing it.</p><p>Example: Something amazing (an event, a sale, a gathering, a seminar on product development) is happening across town. You just gotta get to it…but how?!</p><p>First, you mentally consider the “solution space” of concepts: by car, by walking, by bus, by hitchhiking, by train, by bike, by uber/lyft, by scooter, etc.</p><p>Then, you start to compare these options across a variety of criteria:</p><ul><li>Which would be fastest?</li><li>Which would be easiest?</li><li>Which would be safest?</li><li>Which would be cheapest?</li></ul><p>Now you do some mental math. Is cost more important than safety? Is easiest really most important? And so on.</p><p>Within a few seconds, you decide; “I should just walk because that’s least expensive, I won’t have to worry about parking, and it’s also probably fastest.”</p><p>Boom — you just thought convergently using Decision Matrix Analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/0*6Gk9MpqEK6Yd9-WR" /></figure><p><strong>Structured Convergent Thinking in Concept Selection in the Real World</strong></p><p>It would be nice if you could just plug in your product concepts into a decision matrix, assign some numbers and do some math and select the best concept.</p><p>It doesn’t often work that way.</p><p>In the real world, comparing product concepts is complicated; there are unknowns, risks, and various strategic factors to consider.</p><p>These things also need to be considered during convergent thinking, and they can’t always be scored with a single number rating.</p><p>In nearly every book/article on decision-making and convergent thinking, experts recommend a “reflect on the outcome” step. Reflect on the outcome roughly means “take a second and make sure that simple table you just made really produced a path forward that makes sense in the broader context of your strategic objectives.”</p><p><strong>In Summary</strong></p><p>Don’t “shoot from the hip.” Use a structured process to think convergently.</p><p>The decision matrix is a simple way to compare options across a variety of criteria. It can be used as a building block method to attack complex situations where convergent thinking is required.</p><p>You’re already using this system in your head for simple daily decisions, so it shouldn’t be too new and scary.</p><p>For more reading on decision making and convergent thinking in much more complex situations, try these resources:</p><ul><li>Annie Duke’s <a href="https://www.amazon.com/Thinking-Bets-Making-Smarter-Decisions/dp/0735216355">Thinking in Bets</a></li><li><a href="https://www.amazon.com/Product-Design-Development-Karl-Ulrich/dp/0073404772">Ulrich and Eppinger</a> Textbook, per usual</li><li>Step by Step process for using a <a href="https://www.decision-making-confidence.com/pugh-matrix.html">Pugh Matrix</a></li></ul><h3>15d. Convergent Thinking via the Democractic Method of Voting</h3><p>Voting. Decision-making by committee. It can be messy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*CQOPkZANuJ7RkFW6" /></figure><p>Fortunately, there is a somewhat effective method of using the wisdom of the crowd: dot voting!</p><p><strong>Dot-Voting Distilled</strong></p><p>Show all the options in some consistent manner, like as 1-page summaries on a wall</p><p>Give people a limited number of votes.</p><p>The votes are green (good) and red (bad) sticky note dots</p><p>Let them vote for their favorite concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/193/0*6cOki5L5v9I7AoTV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*1QezRLwTFBlClf7b" /><figcaption><a href="https://creativesolvers.com/methods/sticky-dots/">Source</a></figcaption></figure><p>Dot-voting has also been called the “Butterfly method” by some people in Design Thinking because, when you use post-it notes instead of sticky dots, the wall starts to look like it has a bunch of butterflies on it. Cool, huh?</p><p>Anyway…</p><p><strong>What Dot-Voting is Good For</strong></p><p>More than anything, dot-voting is a pretty quick and easy way to gauge relative interest from a group of people.</p><p>And if you empower a diverse group of people to vote — say folks from Manufacturing, Design, and Marketing — you then see a diverse range of opinions in the results. That’s a good thing.</p><p>Dot-voting can also be used to vote for features or critical specs — not just “product concepts.” This might reveal, for example, that regardless of what concept is chosen, the team feels strongly that the final product should have X feature.</p><p><strong>What Dot-Voting Ain’t Good Fer</strong></p><p>Just blind, majority-rules decision-making. After all, the masses or hordes are not exactly strategic in their thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/0*eBo71YSpnM02Zdp_" /></figure><p>Like most decision-making or convergent thinking processes, dot-voting is usually followed by a <strong><em>reflection process</em></strong>. Decision-makers reflect on the new insights rather than simply just selecting the concept with the most votes.</p><p>Reflection might involve analyzing why the results came out as they did, how concepts might be combined or evolved to further improve the landscape of options, or how some concepts might need further refinement before they can be properly evaluationed.</p><p><strong>What to Watch Out For</strong></p><p>One common problem for dot-voting is that the concept which is presented best tends to get more votes. Like any election, you want to make sure not to confuse “a good looking option” with an option that actually has merit. (I’ll refrain from making any political jokes at this time.)</p><p>Point being, ensure you’re comparing concepts in a similar consistent manner</p><p>More best practices and pitfalls are listed in this well-researched <a href="https://medium.com/@stephenanderson/whats-wrong-with-dot-voting-exercises-9f121e20474a">article</a>.</p><p>Dot-macracy. Make it work for you!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ZuPmzMi1OCQPWSTu" /><figcaption>I like this image cause it shows concepts being combined. <a href="https://medium.com/@stephenanderson/whats-wrong-with-dot-voting-exercises-9f121e20474a">Source</a></figcaption></figure><h3>15e. Summary of Concept Selection</h3><p>The decision matrix, Pugh matrix, and similar “structured” methods are useful for comparing and contrasting different product concepts in a simple, clear framework.</p><p>They might not be able to capture all the complexity of real world decision-making, but that doesn’t render them useless. They’re certainly better than alternative unstructured methods like going with your gut, going with your first idea, or going with the opinion of the highest-paid person in the room.</p><p>Remember that Screening is a part of Concept Selection. Getting bad ideas out of the mix is progress.</p><p>Remember too that the idea is to proceed forward into prototyping with good concepts. It can be more than one concept. And don’t be afraid to combine the best features of popular options if possible.</p><p><strong>Typical Pitfalls</strong></p><p>I think the most common pitfall I see is that these methods <em>just simply aren’t used</em>. Like totally ignored.</p><p>It’s extremely easy to get excited about a product concept; after all, it’s your baby! This excitement can blind product developers from the fact that a product needs to provide value for the customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/0*ABV9QLdJge9rpfe2" /></figure><p>Returning to customer needs, outcomes, and jobs-to-be-done over and over, and rigorously examining how a concept might deliver on those things, is key.</p><p><strong>Remember, it’s a Concept Not a Fully Formed Product</strong></p><p>Remember, as the PD process moves forward, the concept will evolve. We’re going to talk a lot about prototyping. Prototyping is iterative. Trust that it can and will refine your product concept into something that truly meets customer’s needs or jobs-to-be-done.</p><p><em>“A single design-build-test cycle generates insight and information about the connection between specific design parameters and customer attributes. That information becomes the basis for a new design-build-test cycle and the process continues until developers arrive at a solution — a design — that meets the requirements.” </em><a href="https://www.amazon.com/Revolutionizing-Product-Development-Quantum-Efficiency/dp/1451676298"><em>Revolutionizing Product Development</em></a><em>, p 225.</em></p><h4><strong>Resources</strong></h4><p><a href="https://www.amazon.com/Product-Management-Dummies-Brian-Lawley/dp/1119264022">Product Management for Dummies</a>. This book is pretty handy; I’m a fan. It is not too dissimilar to what this content is all about — easy to read nuggets on product management. Product managers are often tasked with evaluating “is this feature/product/spec better?” so there is some good content in here about evaluating concepts.</p><p>There’s a pre-made Decision Matrix provided with the book Product Management for Dummies.</p><p><strong>Books</strong></p><ul><li>Annie Duke’s <a href="https://www.amazon.com/Thinking-Bets-Making-Smarter-Decisions/dp/0735216355">Thinking in Bets</a></li><li><a href="https://www.amazon.com/Product-Design-Development-Karl-Ulrich/dp/0073404772">Ulrich and Eppinger</a> Textbook, per usual</li></ul><p><strong>Articles</strong></p><p>Here’s <a href="https://www.nngroup.com/articles/dot-voting/">a good article </a>on dot voting.</p><p>And here is a really well detailed <a href="https://medium.com/@stephenanderson/whats-wrong-with-dot-voting-exercises-9f121e20474a">article</a> on some of the downfalls of dot voting. This is a helpful read to understand that dot voting is a tool, and like any tool, it can be misused. Link.</p><p>Article with step-by-step process for using a <a href="https://www.decision-making-confidence.com/pugh-matrix.html">Pugh Matrix</a></p><p><em>Click here to sign up for PDD!</em></p><figure><a href="http://eepurl.com/driGaH"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GekKrsiJutsOTaYTHkYbvg.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1581bb7caa10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-development-distillery/chapter-15-concept-selection-1581bb7caa10">Chapter 15 — Concept Selection</a> was originally published in <a href="https://medium.com/product-development-distillery">Product Development Distillery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>