<?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 Bruno Alves Fernandes on Medium]]></title>
        <description><![CDATA[Stories by Bruno Alves Fernandes on Medium]]></description>
        <link>https://medium.com/@brunoalvesfernandes?source=rss-fbff9d5c8b07------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*SZLZhlZlZ73P_EcXq8TKJg.png</url>
            <title>Stories by Bruno Alves Fernandes on Medium</title>
            <link>https://medium.com/@brunoalvesfernandes?source=rss-fbff9d5c8b07------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:18:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brunoalvesfernandes/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[Dual-track agile & the design sprint diamonds — the powerful combo to make business impact]]></title>
            <link>https://medium.com/design-bootcamp/dual-track-agile-product-discovery-the-powerful-framework-to-make-business-impact-c447f4317fce?source=rss-fbff9d5c8b07------2</link>
            <guid isPermaLink="false">https://medium.com/p/c447f4317fce</guid>
            <category><![CDATA[dual-track-agile]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Bruno Alves Fernandes]]></dc:creator>
            <pubDate>Fri, 07 May 2021 07:44:08 GMT</pubDate>
            <atom:updated>2021-10-18T05:48:32.145Z</atom:updated>
            <content:encoded><![CDATA[<h3>Dual-Track Agile &amp; The Design Sprint Diamonds</h3><p><em>We all know that agile methodologies need to be integrated with our design processes, but how we can integrate them in an effective way?</em></p><p>First of all, I really like to be concise and I truly believe that we need to know how to manage our energy throughout the day to achieve the best ratio between effort and value provided in each activity that we are performing. That being said, I&#39;ll try to write this article with the least amount of text possible while delivering that highest amount of value for you.</p><p>Ok? Let&#39;s get it. 🤘</p><h3>Dual Track Agile Concept</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BOtjhyPuf5bux6OOz0w92g.png" /><figcaption>Image from: Agile Alliance.</figcaption></figure><p>Basically, the dual track agile methodology consists of pairing a <strong>Product Discovery Track</strong> with a <strong>Product Delivery track</strong> to create a product development continuum with both tracks running in parallel. <br><a href="https://www.agilealliance.org/resources/experience-reports/multi-product-teams-in-an-agency-combining-design-thinking-lean-and-agile/">Learn more from Agile Alliance.</a></p><p>This method will enhance the product development process with a bunch of synchronized cycles of discoveries and deliveries for the product, enabling a <strong>Lean Ux Validation Process, </strong>a<strong> Rapid Product Iteration </strong>and a<strong> Quick Learning Cycle between the Discovery and Delivery, </strong>while also driving the cross-functional team towards <strong>Continuous Integration</strong> and <strong>Continuous Delivery. </strong>It provides a lot of value.</p><h3>The Product Discovery Track</h3><p>In this track the team will design and validate product solutions, before the implementation, to ensure that the product concept is <strong>viable</strong>, <strong>desirable</strong> and <strong>feasible</strong> and it worth the development cost spent. Here is where the <strong>Lean Ux approach</strong> comes into play. The team should validate the concept in a lean way, avoiding any waste — like very deep and long research cycles and high fidelity prototypes for instance (if they aren&#39;t really necessary to measure the value of the solution).</p><p>However, we need to add <strong>two ingredients</strong> here to make this track work properly with the Lean Ux concept and also to enable it to succeed when the moment to connect with the delivery track arrives. These two ingredients are: the <strong>adapted Design Sprint Framework</strong> and <strong>The Triad Model.</strong></p><ol><li><strong>The Design Sprint Framework</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9p0s5aLx8az_oPG5FjVfQ.png" /><figcaption>Image from: <a href="https://design-sprint.com/">https://design-sprint.com/</a></figcaption></figure><p>The <strong>Google Design Sprint Framework</strong> is a pretty nice framework to understand the problem space, diverge and converge a bunch of information and potential solutions and, <strong>in a lean way</strong>, prototype and test them.</p><p>Besides, the framework will enable our Lean Ux approach while guiding the team through a clear design process. Additionally, you can also use a lot of different <strong>design thinking tools and methods</strong> to leverage the potential of each phase — e.g. You can use the <a href="http://link/">&quot;Crazy Eight&quot;</a> method to diverge a lot of potential solutions or the <a href="http://link/">&quot;Heart Metrics&quot;</a> method to define success metrics. in the define phase. You can really use any design thinking method you want here — you just need to understand the purpose of it and apply it correctly. Therefore, the team will use the design sprint framework to run the Product Discovery track.</p><p>However — and this is something very important — <strong>you&#39;ll adapt this framework to match the sprint cycles of the team.</strong> Instead of running the design sprint in 5 days as the original methodology, <strong>you&#39;ll run one phase or maybe be two, in one or more sprint cycles. </strong>E.g — you can take one sprint or maybe two to run the Understand phase. Then, you can take the next sprint to run the define and sketch phases and so forth.</p><p>You can learn more and discover different design thinking methods for each phase at the<a href="https://designsprintkit.withgoogle.com/"> Google Design Sprint Kit website</a>.</p><p><strong>2. The Triad Model</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7xT_It8tx79WFssRUJF94A.png" /><figcaption>Image by <a href="https://medium.com/@cdrumond?source=post_page-----86946b099b--------------------------------">Claire Drumond</a></figcaption></figure><p>The triad is a <strong>smaller group</strong> of a cross-funcional team that will run the discovery track in order to <strong>design and validate the product concept</strong>. The triad should be assembled with team members that has the necessary skills to properly address the business, users and technology needs and constraints in order to craft a really good product solution. This is why, in general, a triad is formed by a <strong>Product Manager,</strong> a <strong>Product Designer</strong> and a <strong>Technology Lead</strong>.</p><p>The triad is also a <strong>flexible cell</strong> that mimics a cross-functional team behaviour, but spending much less energy while reduce the cost to validate or not new product opportunities. Additionally, and because its nature, the triad will enable the product solution to grow in the correct way to be properly consumed by the delivery team, when the moment to scale it arrives.</p><p>As mentioned, the triad will follow the design sprint framework adapted to the sprint cadence of the team, and will run different rounds of validation before the delivery team start to build the solution. When the product solution is <strong>mature enough</strong>, the triad will start to include the delivery team in the loop by running <strong>refinement sessions </strong>to<strong> </strong>present the product solution, align the implementation, spot potential implementation issues and to receive all team&#39;s feedback. This moment will be crucial to also <strong>give ownership</strong> to the delivery team.</p><h3><strong>Connecting the tracks</strong></h3><p>To synchronize the discovery track with the delivery track, the team can use the <strong>DOR (Definition of Ready)</strong> criteria to define when the product solution is ready to be implemented. <br>The triad should also plan and define the <strong>scope of the first release</strong> — that could be a MVP — and also plan <strong>the road map of the next releases</strong>. The team can also break down the concept to implemented into <strong>user stories</strong> to help the implementation and also the quality assurance phase of the delivery track.</p><p>That’s all folks. Now you have a way to integrate <strong>Dual Track Agile</strong>, <strong>Lean UX</strong> and the <strong>Design Sprint Framework </strong>to make business impact by creating awesome product solutions. Leave your comments below if you want to discuss any topic on this article. There’s no truth in product development. Everything is adaptable. As Bruce said, be water my friend.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c447f4317fce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/dual-track-agile-product-discovery-the-powerful-framework-to-make-business-impact-c447f4317fce">Dual-track agile &amp; the design sprint diamonds — the powerful combo to make business impact</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are you a 20th or 21st Century Product Designer?]]></title>
            <link>https://uxdesign.cc/are-you-a-20th-or-21st-century-product-designer-cdba682d3cf9?source=rss-fbff9d5c8b07------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdba682d3cf9</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Bruno Alves Fernandes]]></dc:creator>
            <pubDate>Mon, 18 May 2020 05:35:30 GMT</pubDate>
            <atom:updated>2022-04-24T18:57:07.237Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzUPM5CMxCNMme0t4cqqyg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">charlesdeluvio</a> on <a href="https://unsplash.com/s/photos/design?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><em>Nowadays we can see a bunch of product designers saying they are &quot;Modern&quot;. However, they are 100 years late. Are you one of them?</em></p><p>Firstly, let&#39;s define the bottom line of this discussion. This is not something that I&#39;m saying just considering my experience as a Digital Product Designer. This is something that Don Norman is saying after 50 years as a reference designer for all of us:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7FJNsqoC4tI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7FJNsqoC4tI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7FJNsqoC4tI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/11382a0f40c1d1c0a2084022b2f2cc99/href">https://medium.com/media/11382a0f40c1d1c0a2084022b2f2cc99/href</a></iframe><blockquote>&quot;How we design a procedure? How we design a service? That&#39;s not covered in traditional design.&quot; — Don Norman</blockquote><p>Basically, Don Norman is saying that you don&#39;t need all those craft design skills that traditional design universities teach you to be a 21st designer. However, it doesn&#39;t mean that they are not important at some level. But, the truth is that the traditional design discipline is too narrow and doesn&#39;t cover the wide range of knowledge that a 21st Designer need to design modern services and digital systems.</p><p>Today, we can see that a lot of the best designers in the world have a background in physics, engineering and mathematics, for instance. It&#39;s easy to imagine that when these professionals are in a meeting with the team trying to define a problem or trying to find a solution for it, they generally contribute a lot for the problem space. They usually have a logical and systematic way of thinking that enable them to generate clear and connected assumptions and outcomes. They also have a wide range of knowledge that easily enables them to diverge possibilities and also converge them logically into possible and feasible solutions. All their power comes from the background disciplines that taught them how to understand the world.</p><blockquote>&quot; When I&#39;m designing a service like being in a waiting line at a bank or a cafeteria; or at customs controls I don&#39;t need craft skills. I&#39;m not building anything that&#39;s going to be beautiful to look at. But I do wanna build something that takes account all the needs of all the people.&quot; — Don Norman</blockquote><p>In this context, Norman introduces the concept of Service Design as the basis of the design of the future, because it has two components in its foundation: the Journey Map and the Service Design Blueprint.</p><p>The Journey Map is a well known but sometimes totally underestimated concept that map all the phases that a customer needs to go through in order to achieve its objective in a store or a bank, for instance. We see a lot of designers that know what this tool is, but don&#39;t know how or when effective apply it.</p><p>Additionally, we have The Service Design Blueprint which has two dimensions: the vertical and the horizontal. The horizontal, which is the time dimension, is basically the Journey Map. The vertical one, is where we plot all the different things that customer interact with such as cashiers, attendants and also different systems. Therefore, the Service Design Blueprint is basically the Journey Map for each of these different components. Moreover, and to make it more valuable, we can also map the emotions that each one of these layers develop as they go through their own journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7bgOmJyjkhfivHV30PQceA.png" /><figcaption>Nielsen and Norman Group Service Design Blueprint</figcaption></figure><p><em>The Nielsen and Norman Group has a pretty nice article about Service Design Blueprints. Click </em><a href="https://www.nngroup.com/articles/service-blueprints-definition/"><em>here</em></a><em> to take a look.</em></p><p>At the end of the day, the question as Norman says, is: where those skills to plan the user experience for complex systems like these come from? How can we teach those, and what else is necessary?</p><p>When you go to a dedicated design school, they not teach you how to understand the world. They just teach you about the craft of design. It doesn&#39;t mean, as I said at the beginning, that you don&#39;t need any of those skills. We can all agree that visual design is an important part of the general user experience. However, knowing just these skills is certainly not enough. Besides, if you are focusing 70% of your energy to just to improve your visual design skills one of the following assumptions are true: or you are a UI specialist, or you are a Ux/Product (whatever) designer that is not understanding the main goal of your role.</p><p>In conclusion, we need to better understand the wide range of disciplines that creates the 21st Century Designer, and apply effort to learn them. Nevertheless, without a clear understanding about the essence of design nowadays it will be impossible to allocate effort to progress in the right direction.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdba682d3cf9" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/are-you-a-20th-or-21st-century-product-designer-cdba682d3cf9">Are you a 20th or 21st Century Product Designer?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>