<?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 Grant Baker on Medium]]></title>
        <description><![CDATA[Stories by Grant Baker on Medium]]></description>
        <link>https://medium.com/@BakoInd?source=rss-94e434260100------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cQZef83pTG88CUTSZDxbew.jpeg</url>
            <title>Stories by Grant Baker on Medium</title>
            <link>https://medium.com/@BakoInd?source=rss-94e434260100------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:33:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@BakoInd/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[Reviewing the Continuous Discovery and Design Model]]></title>
            <link>https://medium.com/@BakoInd/reviewing-the-continuous-discovery-and-design-model-538b28fd866b?source=rss-94e434260100------2</link>
            <guid isPermaLink="false">https://medium.com/p/538b28fd866b</guid>
            <category><![CDATA[design-methods]]></category>
            <category><![CDATA[design-methodology]]></category>
            <dc:creator><![CDATA[Grant Baker]]></dc:creator>
            <pubDate>Thu, 12 Jan 2023 16:04:52 GMT</pubDate>
            <atom:updated>2023-01-12T16:04:52.515Z</atom:updated>
            <content:encoded><![CDATA[<p>The Continuous Discovery and Delivery (CDD) is one model to capture the design process. It is similar to a Lean UX approach in its etic perspective and to a Double Diamond process in its structure. The product manager leads a team continuously through these 5 stages:</p><ol><li>Product Discovery</li><li>Prototype Discovery</li><li>Product Delivery</li><li>Products and Product/Market Fit</li><li>Product Vision</li></ol><h3>Product Discovery</h3><p>Product Discovery is the first stage in CDD. Its purpose is an idea winnowing function. Throughout this phase, ideas are dreamed up and evaluated against a set of criteria designed to eliminate 4 risks:</p><ol><li>Assess Value. Will users buy it (or use it)?</li><li>Assess Usability. Can they figure out how to use it?</li><li>Assess Feasibility. Can the engineers build it?</li><li>Assess Viability. Can stakeholders support it?</li></ol><p>Speed is the number one priority in the CCD model. Discovery must be quick and the model expects that the product team spins through many ideas. While Cagan does place some importance on understanding the domain itself, the volume of ideas is primary. The output of this phase is a validated product backlog.</p><h3>Prototype Discovery</h3><p>Prototypes are the hinge around which the Cagan model of product design turns. The model equates prototypes with experiments and are to be both quick and inexpensive. This way, a team can learn fast without spending too many resources. In this model, a mature product team will test 10–20 product ideas per week.</p><p>The Product Designer handles constructing the prototypes throughout this phase. The prototype is the designer’s “primary canvas” according to Cagan.</p><p>Cagan attempts to draw a comparison of an old and new way of product design. In this old way, he says, prototyping came at the end of a product design.</p><blockquote><em>The main difference today is that we do usability testing in discovery — using prototypes, before we build the product — and not at the end, where it’s really too late to correct the issues without significant waste or worse.</em></blockquote><blockquote><em>(Cagan, 2017)</em></blockquote><p>He is correct that usability testing is far more valuable prior to launch, but this is hardly a new concept. <em>Don’t Make Me Think</em>, by Steve Krug and published in 2000, outlined the same idea. The fact that Cagan feels the need to address it 17 years later shows that there is still a long way to go for corporations and design teams to fully embrace prototype testing as a design tool.</p><h3>Product Delivery</h3><p>Once an idea has been selected and prototyped, the product team delivers a robust, reliable product that can fund a company. The project team concentrates on maturing the product so that it is:</p><ul><li>Scalable</li><li>Performant</li><li>Reliable</li><li>Fault tolerant</li><li>Secure</li><li>Private</li><li>Internationalized</li><li>Localized</li><li>Works as advertised</li></ul><h3>Products and Product/Market Fit</h3><p>At this stage, the product is officially released as the smallest possible product that still meets the needs of a particular market. The product manager evaluates the market fit at this stage. This identifies what market size exists and how well the product meets the needs of that market.</p><h3>Product Vision</h3><p>The product vision stage is the connection point to making this a continuous process. The vision is a leap of faith and accomplishing it may not be possible and if it is, not for a few years.</p><h3>A Critique of the Continuous Discovery and Delivery Model</h3><p>The Continuous Discovery and Delivery model is adequate for many product teams. Yet there are several cautions to adopting it wholesale.</p><p>Read the <a href="https://www.bakoindustries.com/evaluating-the-continuous-discovery-and-delivery-model/#critique">rest on my blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=538b28fd866b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>