<?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 H. Javier Castillo Suazo on Medium]]></title>
        <description><![CDATA[Stories by H. Javier Castillo Suazo on Medium]]></description>
        <link>https://medium.com/@hjavixcs?source=rss-597d37401b2c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GmESm5Cv5NBui2khZ2pcOg.jpeg</url>
            <title>Stories by H. Javier Castillo Suazo on Medium</title>
            <link>https://medium.com/@hjavixcs?source=rss-597d37401b2c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 04:34:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hjavixcs/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[A summary of the book “Good Strategy, Bad Strategy”]]></title>
            <link>https://hjavixcs.medium.com/a-summary-of-the-book-good-strategy-bad-strategy-d28b1c93ea01?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d28b1c93ea01</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 11:18:50 GMT</pubDate>
            <atom:updated>2025-11-30T11:21:32.182Z</atom:updated>
            <content:encoded><![CDATA[<h2>A summary of the book “Good Strategy, Bad Strategy”.</h2><p>I was flying back from Bulgaria to Barcelona after an intensive two-day company workshop and after a nightmare of lost flight connections. The good part, I’ve finally finished the “Good Strategy, Bad Strategy” reading by Richard Rumelt. Is a book that explains what distinguishes good strategy from bad strategy, both in business and in organizations or governments.</p><p>I’ve posted this summary on my LinkedIn and surprisingly it got many good reactions. So, I decided to post the summary also in Medium.</p><p>Here you have a summary of the main idea:</p><h3>📘 Central idea</h3><p>Rumelt argues that many organizations believe they have a strategy… but in reality, they only have goals, slogans, or wish lists — in other words, bad strategy.</p><h3>✔️ What good strategy is</h3><p>A good strategy is built around a core made up of three elements:</p><ol><li>Clear diagnosis: Understanding and explaining the nature of the problem or challenge.</li><li>Guiding policy: A coherent approach to addressing that diagnosis.</li><li>Coherent actions: A set of coordinated steps that implement the guiding policy.</li></ol><p>Good strategy requires focus, coherence, and the ability to say no to what doesn’t contribute.</p><h3>✖️ What bad strategy is</h3><p>Rumelt describes bad strategy as:</p><p>•	Empty statements (“be the market leader”).</p><p>•	Goals without means.</p><p>•	Confusing targets with strategy.</p><p>•	Avoiding identification of the real problems.</p><p>•	Lack of prioritization.</p><h3>🎯 Key insights</h3><p>•	Strategy isn’t a big, complex document; it’s clarity about the problem and the actions.</p><p>•	Competitive advantage often comes from identifying a leveraged point and concentrating effort on it.</p><p>•	Strategy requires tough choices and trade-offs.</p><blockquote>I think not just Executives and Senior Leaders would find this book valuable to read. We need “good strategy” at many levels in our organization.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EvnRlkuLiEXyu6LFEXkZvw@2x.jpeg" /></figure><p>Read my full review at goodreads: <a href="https://www.goodreads.com/review/show/4275481531">https://www.goodreads.com/review/show/4275481531</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d28b1c93ea01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Something About Dependency Management]]></title>
            <link>https://hjavixcs.medium.com/something-about-dependency-management-cab1e888c9c0?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cab1e888c9c0</guid>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 15:31:41 GMT</pubDate>
            <atom:updated>2024-06-24T15:31:41.428Z</atom:updated>
            <content:encoded><![CDATA[<p>I was reading a LinkedIn <a href="https://www.linkedin.com/posts/klausleopold_flightlevels-dependencies-flightlevel2-activity-7209418787354267648-MbAh?utm_source=share&amp;utm_medium=member_ios">post</a> by Klaus Leopold (Creator of Fligh Levels®). He started rising a question, “Is it better to eliminate dependencies rather than manage them?”, then I wanted to share my thoughts about Dependency Management.</p><p>IMO as Software Engineer and Agile Coach, there’s no way to truly eliminate dependencies, most of the cases you’re moving the dependencies some where else. So why we don’t assume the fact that we have dependencies and manage them instead of invest a lot of time and effort trying to “eliminate” dependencies?</p><p>Of course first thing you want to do is identify the dependencies and visualize them. That would be the first step, then you want to sequence the work in order to properly address the work without blockings. But that’s assumes you identified all the dependencies. A classic approach (at scale) is the big room planning. But let’s be honest, are we really able to identify everything in advance? Also, in many cases the “dependency management” ends in the big room planning. Then no body is managing (coordinating and supporting the teams in that regard) those dependencies (and the new ones neither).</p><p>The Flight Levels approach will help you to understand and manage your flow between teams (Level 2: End-to-end coordination), including dependencies as you could see in the post I’m sharing.</p><p>I also like the Dependency Management in Kanban. The Kanban method (in the Kaban Maturity Model) present a wide range of techniques to manage dependencies according to the nature of the decepedencies (it take in account context, organizational maturity, cost of delay and other factors).</p><p>Since Flight Levels is not a (Scaling) Framwork and it doesn’t not prescribe any framework, methodology or method, you could introduce different approaches and/or techniques. that better makes sense for in your organizational context. But seriously, take a look at the Kanban way!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*TT-LLi7SKT4V4lqJIHQBGg@2x.jpeg" /></figure><p><em>Image generated with OpenArt AI</em></p><p>𝘓𝘦𝘢𝘳𝘯 𝘮𝘰𝘳𝘦 𝘢𝘣𝘰𝘶𝘵 𝘋𝘦𝘱𝘦𝘯𝘥𝘦𝘯𝘤𝘺 𝘔𝘢𝘯𝘢𝘨𝘦𝘮𝘦𝘯𝘵 𝘪𝘯 𝘒𝘢𝘯𝘣𝘢𝘯:</p><p><a href="https://djaa.com/what-is-dependency-management-in-kanban/">𝗪𝗵𝗮𝘁 𝗶𝘀 𝗗𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝘆 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 𝗶𝗻 𝗞𝗮𝗻𝗯𝗮𝗻?</a></p><p><a href="https://www.kanbanmaturitymodel.com/2020/11/03/seven-lessons-about-dependency-management/">𝗦𝗲𝘃𝗲𝗻 𝗟𝗲𝘀𝘀𝗼𝗻𝘀 𝗔𝗯𝗼𝘂𝘁 𝗗𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝗰𝘆 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁</a></p><p>𝘓𝘦𝘢𝘳𝘯 𝘮𝘰𝘳𝘦 𝘢𝘣𝘰𝘶𝘵 𝘍𝘭𝘪𝘨𝘩𝘵 𝘓𝘦𝘷𝘦𝘭𝘴:</p><p><a href="https://www.flightlevels.io/what-is-flight-levels/">𝘄𝗵𝗮𝘁 𝗶𝘀 𝗙𝗹𝗶𝗴𝗵𝘁 𝗟𝗲𝘃𝗲𝗹𝘀?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cab1e888c9c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[As a Lean-Agile Coach, I like to combine the Agile and Lean mindset]]></title>
            <link>https://hjavixcs.medium.com/as-a-lean-agile-coach-i-like-to-combine-the-agile-and-lean-mindset-both-complement-each-other-415457d1523b?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/415457d1523b</guid>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Tue, 21 May 2024 18:36:56 GMT</pubDate>
            <atom:updated>2024-05-21T19:09:37.208Z</atom:updated>
            <content:encoded><![CDATA[<p>And both mindset complement each other very well. I embrace the Agile mindset to support teams and the organisation to improve collaboration, and deliver value soon. And what about reduce time to market, here is where I found in the Lean mindset a great ally.</p><p>If and organization wants to be able to act in a truly agile way, it has to look at all value streams from strategy to implementations (end-to-end improvement), not just focus on making “agile teams” (sub-optimization).</p><p>I recommend to managers VISUALIZE their processes (at least the most important/critical) and instead of just aiming to improve velocity or throughput, identify waste and remove it or reduce it. You’ll gain a lot of efficiency with the same resources!</p><p>Here you have the most common “Thieves of Time” that Dominica DeGrandis points out on her book “<a href="https://www.goodreads.com/book/show/34696396-making-work-visible">Making Work Visible : Exposing Time Theft to Optimize Work &amp; Flow</a>“ (I recommend it! <a href="https://www.goodreads.com/review/show/2510225250">Check my review</a>).</p><p>Here they are:</p><ul><li>Too much work in progress</li><li>Unknown dependencies</li><li>Unplanned work</li><li>Conflicting priorities</li><li>Neglected work</li></ul><p>For sure there’re other types of waste. Take a look at the 8 Wastes of Lean (manufacturing). Those wastes are, defects, overproduction, waiting (thieves of time), unused talent, transportation, invenentory, motion, extra-processing. You could find an adaption of these wastes to the Software Development industry.</p><p>Who in your team (service/product) is taking care on managing situations mentioned above?</p><p>You could use this fabulous tool (Value Stream Mapping) to visualize your process and spot wastes (and value of course). Great post from Ivan Carillo, thanks for sharing! As a Lean-Agile Coach, I like to combine the Agile and Lean mindset. Both mindsets complement each other very well.</p><p>If and organization wants to be able to act in a truly agile way, it has to look at all value streams from strategy to implementations (end-to-end improvement), not just focus on making “agile teams” (sub-optimization).</p><p>I recommend to managers VISUALIZE their processes (at least the most important/critical) and instead of just aiming to improve velocity or throughput, identify waste and remove it or reduce it.</p><blockquote>Just by reducing waste in your process, you’ll gain a lot of efficiency with the same resources!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*-7tKyzOWnNmnlrNJb43pJA@2x.jpeg" /></figure><p>Image created by <a href="https://openart.ai/">OpenArt</a>.</p><p>Here you have the most common “Thieves of Time” that Dominica DeGrandis points out on her book “Making Work Visible“ (I recommend it!).</p><p>Here they are:</p><ul><li>Too much work in progress</li><li>Unknown dependencies</li><li>Unplanned work</li><li>Conflicting priorities</li><li>Neglected work</li></ul><p>For sure there’re other types of waste. Take a look at the 8 Wastes of Lean (manufacturing). Those wastes are, defects, overproduction, waiting (thieves of time), unused talent, transportation, invenentory, motion, extra-processing. You could find an adaption of these wastes to the Software Development industry.</p><p>Who in your team (service/product) is taking care on managing situations mentioned above?</p><p>You could use a fabulous tool, “Value Stream Mapping” to visualize your process and spot wastes (and value of course). I used this tool for a group of teams and we spotted constraints in our main Value Stream and trigger actions and initiatives to reduce waste and mitigate impact. I recommend this great <a href="https://www.linkedin.com/feed/update/urn:li:activity:7190803779259088898?utm_source=share&amp;utm_medium=member_ios">post from Ivan Carillo at LinkedIn</a>.</p><p>What’s your story about reducing waste, visualising work, or combining Agile and Lean mindset?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415457d1523b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design the Kanban System]]></title>
            <link>https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1b45fec4f3e</guid>
            <category><![CDATA[statik]]></category>
            <category><![CDATA[kanban-system]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[kanban-system-design]]></category>
            <category><![CDATA[kanban-board]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Sat, 28 Nov 2020 17:41:15 GMT</pubDate>
            <atom:updated>2020-11-28T23:17:53.574Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><strong>Design the Kanban system</strong></li><li>Socialize design &amp; negotiate implementation</li></ol><h3>Modeling your Kanban System</h3><p>The moment we’ve all been waiting for! It’s time to put together the system learning and vision acquired over the previous sessions and model the Kanban system.</p><ul><li>The main steps of the workflow tend to fall into columns here.</li><li>Activities in progress tend to already be categorized in types of demand.</li><li>Services classes tend to become rows (swim-lanes) on your board.</li><li>The metrics collected can form the basis for defining WIP limits.</li></ul><figure><img alt="Example of a Kanban System" src="https://cdn-images-1.medium.com/max/456/1*ItOKnompEdXrg4YdQxnE9g.png" /></figure><p>At this point, it’s useful to have a checklist of the elements likely to be included, for example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*mrQrBJjW8etwTG9VsqTKNA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*KJ7yE_UuZmrOKbHsoXkxRw.png" /></figure><h3>Kanban Board</h3><p>A Kaban board is a work and workflow visualization tool that enables you to optimize the flow.</p><p>Physical Kanban boards, typically use sticky notes on a whiteboard to communicate status, progress, and issues.</p><figure><img alt="Example of a Kaban Board" src="https://cdn-images-1.medium.com/max/457/1*deQ8QuLCR-g-nNHC4ie7qg.png" /><figcaption>Online Kanban boards draw upon the whiteboard metaphor in a software setting.</figcaption></figure><h3>Kanban Card</h3><p>The core functionality of a Kanban card is to visually convey a work item’s progress as it flows through a system or process.</p><p>The face of a Kanban card presents details that are relevant to the team, such as:</p><ul><li>A unique identifier or title</li><li>A brief description of the work</li><li>A rough estimate of the size of the work</li><li>Who’s been assigned to it</li></ul><figure><img alt="Kaban card example" src="https://cdn-images-1.medium.com/max/476/1*XpEPDzwJpebnb0hlH2tOag.png" /><figcaption>Face of a sample Kanban card.</figcaption></figure><h3>Kanban System</h3><p>Here is an overview of the five steps you’ll want to take in order to implement a lasting and effective Kanban system</p><ul><li>Map your current workflow</li><li>Visualize your work</li><li>Focus on flow</li><li>Limit your WIP</li><li>Measure and improve</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*NMB2LJHNG9wxvFfqUUZW_Q.png" /><figcaption>Kanban System example.</figcaption></figure><p>Remember your first version of your Kanban System should reflect the actual process not the desired. So, there’s no template or default design to adapt to. Instead you’ll create a system that adapts to your reality and context and then start improving your system.</p><h3>Scaling Kanban?</h3><p>If you need to bring the benefits of Kanban beyond a team maybe you’re thinking if you could implement Kanban at scale (today we have many Agile Scaling Frameworks as SAFe, LeSS, Nexus, Scrum@Scale). Well, <strong>scalability is an inherent part of Kanban</strong> and therefore one cannot not scale Kanban. Scaling in a Kanban context means: <strong>Doing more Kanban</strong>. This can be done in two directions: in depth and in breadth.</p><p>Here you are a few examples of above aproaches:</p><h4>Width-wise growth example</h4><figure><img alt="Widh-wise growth Kanban System example" src="https://cdn-images-1.medium.com/max/1024/1*_lB7eEONhfkpCzWI4mISfg.png" /><figcaption>Width-wise growth example. This board also shows the use of minimum and maximum WIP limits.</figcaption></figure><h4>Height-wise growth example</h4><figure><img alt="Height-wise growth Kanban System example" src="https://cdn-images-1.medium.com/max/1024/1*c0zdrozMDibUZrvK4-Xjkg.png" /><figcaption>Height-wise growth example.</figcaption></figure><h4>Depth-wise growth example</h4><figure><img alt="Depth-wise growth Kanban System example" src="https://cdn-images-1.medium.com/max/1024/1*T-gn54Av4SL0kfb0duXDaw.png" /><figcaption>Depth-wise growth example.</figcaption></figure><h4>A Wider/Deeper example</h4><figure><img alt="Upstream Kanban" src="https://cdn-images-1.medium.com/max/1024/1*7WESwKim1ZJmdV0enP1NAg.png" /><figcaption>Upstream + Downstream Kanban example</figcaption></figure><p>There’s a short and free <strong>Essential Upstream Kanban</strong> ebook in the <a href="https://resources.kanban.university/shop/">Kanban University resources</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3mpDNKj1dfMFUKJKgXB_KA.png" /><figcaption>A Kanban board design of their first Kanban System.</figcaption></figure><blockquote>“A system is never the sum of its parts”. It’s the product of the interaction of its parts”</blockquote><p>Next STATIK’s step is Socialize design &amp; negotiate implementation. Or review the previous step, <a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1b45fec4f3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identify and define classes of service]]></title>
            <link>https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fea21e2734c</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[cost-of-delay]]></category>
            <category><![CDATA[class-of-service]]></category>
            <category><![CDATA[statik]]></category>
            <category><![CDATA[kanban-system]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Sat, 29 Aug 2020 15:36:01 GMT</pubDate>
            <atom:updated>2020-11-28T17:54:59.244Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><strong>Identify and define classes of service</strong></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><h3>Identify and define classes of service</h3><p>Classes of Service (CoS) have two main purposes: to classify different work items according to their priority and to clearly define how the items in each CoS should be treated.</p><p>Classes of Service are used to mitigate external risks associated with a work item. The more urgent, critical, or valuable an item, the higher its class of service is likely to be.</p><p>Some examples of CoS are Work Item Type, Cost of Delay, Customer, Project, OKRs.</p><p>The selection of the Class of Service should depend on what is more important (in terms of business strategy) for the service or for the organization. CoD is the most I use or recommend within my Kanban implementations when the company has no clear strategical drivers in place. In the end, many business organizations don’t want to lose their money, and this Classes of Service allow us to manage risk related to the cost of delay in their service delivery.</p><h4>COST OF DELAY PROFILES</h4><p>Cost of Delay (CoD) is the perceived economic value of a work item through time. It helps teams understand how the value of an item they are working on can diminish over time.</p><p>The most common CoD profiles or archetypes are generally as follows:</p><ul><li><strong>Expedite </strong>— we are losing a lot of money right now</li><li><strong>Standard </strong>— do it as soon as possible</li><li><strong>Fixed date </strong>— campaigns, regulations, agreements with customers, …</li><li><strong>Intangible </strong>— it will eventually become an expedite if you don’t do it</li></ul><figure><img alt="Cost of Delays profiles" src="https://cdn-images-1.medium.com/max/1024/1*Oh2AI0PcYKBjeK0d-Zzs6Q.png" /><figcaption>Cost of Delay Profiles.</figcaption></figure><p>Teams assess the impact of a delay in the delivery of a feature, project, or solution to an issue. Delaying the release of a version of your software that is aimed at giving you a competitive advantage will definitely have a high cost of delay. In the same way, not being able to immediately release a solution to a critical production issue entails a high cost of delay, as you stand to have dissatisfied customers or even lose them because of it.</p><h4>IDENTIFYING CLASSES OF SERVICE</h4><p>Bring examples of expedite, fixed date, standard and intangible demands in their context, and for each example, say which characteristic classifies the demand in its class of service. Then agree with the team about their policies of working.</p><figure><img alt="Examples of Classes of Services and its policies" src="https://cdn-images-1.medium.com/max/373/1*yV5QGqHht8qUD5BEYvOpSw.png" /><figcaption>Examples of Classes of Service by Cost of Delay and their policies.</figcaption></figure><figure><img alt="Identifying Classes of Service" src="https://cdn-images-1.medium.com/max/1024/1*cPmztrhrq1Uq46g5Fe-x5g.png" /><figcaption>Identifying Classes of Service.</figcaption></figure><p>Next STATIK’s step is Design the Kanban system. Or review the previous step, <a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5fea21e2734c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Model the service delivery workflow]]></title>
            <link>https://hjavixcs.medium.com/model-the-service-delivery-workflow-f5c3884f4fec?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5c3884f4fec</guid>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[kanban-system]]></category>
            <category><![CDATA[statik]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Fri, 28 Aug 2020 11:10:30 GMT</pubDate>
            <atom:updated>2020-11-28T17:55:19.481Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><strong>Model the service delivery workflow</strong></li><li><a href="https://medium.com/@hjavixcs/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><h3><strong>Model the service delivery workflow</strong></h3><p>In this step we are already delving into the core of the Kanban System design. We want to clearly identify boundaries of the service, stakeholders, customers, dependencies and the workflow.</p><p>We want to really understand service’s current situation (what the team actually does as opposed to what the team thinks it does or they would like to be doing).</p><figure><img alt="Jira workflow sample" src="https://cdn-images-1.medium.com/max/472/1*sfBr-g80Yd1o1Iigu7fq_Q.png" /></figure><h4>MODEL THE SERVICE DELIVERY WORKFLOW</h4><p>Model and draw the workflows for each type of demand which has been identified. Jump into the service area of responsibility and model the workflow. It is very important here that we model what the service is currently doing, not what they think they are doing or they would like to be doing.</p><figure><img alt="Drawing a workflow on paper" src="https://cdn-images-1.medium.com/max/1024/1*Qh2ehV3voQzmjom9rUQMAQ.png" /><figcaption>Model the service delivery workflow.</figcaption></figure><p>Next STATIK’s step is <a href="https://medium.com/@hjavixcs/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a>. Or review the previous step, <a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5c3884f4fec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Analyze the source and nature of demand]]></title>
            <link>https://hjavixcs.medium.com/analyze-the-source-and-nature-of-demand-63724e1f436c?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/63724e1f436c</guid>
            <category><![CDATA[demand-response]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[statik]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[delivery-management]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 12:11:34 GMT</pubDate>
            <atom:updated>2020-11-28T18:02:04.800Z</atom:updated>
            <content:encoded><![CDATA[<h3>Analyze the source and nature of demand and current delivery capacity</h3><p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><strong>Analyze the source and nature of demand</strong></li><li><strong>Analyze current delivery capability</strong></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><h3><strong>Analyzing demand and delivery capability</strong></h3><p>Before we analyze demand and delivery capabilities, we need to identify the work item types. Then we can analyze for each item type, how much we’re demanded of this type of work and how much we can serve or deliver. So we can identify what’s happening in our processes by visualizing work and creating metrics.</p><h4><strong>IDENTIFYING WORK ITEM TYPES</strong></h4><p>First, remember all the services that the team provides to other parties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*OESiIAMER11Glk6p_5hhlQ.png" /><figcaption>The team identifies any type of service no matter they’re related or not.</figcaption></figure><blockquote>Work Item Types — essentially a service a team provides that is requested by another party.</blockquote><p>Then, group similar items into no more than seven groups. Give each group a (short) name that summarizes the service provided</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*SmZLHQcOUtkmj-aFdqcjwA.png" /><figcaption>The group names are our work item types.</figcaption></figure><p>Optionally, each team member writes their name on post-its and attach them to the groups with which they’re involved.</p><blockquote>This activity can be useful in understanding the level of specialization inside a team</blockquote><h4><strong>ANALYZING DEMAND AND DELIVERY CAPABILITY</strong></h4><p>Now is time to look at each work item type and identify its patterns of arrival and delivery, as well as other useful information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rnZFloP5rDXYq9KwXHGYSw.png" /><figcaption>Analyzed demand and delivery for each identified work item type</figcaption></figure><p>This analysis is not pretending to accurately measure demand and delivery capabilities but to everybody understand the nature of their work and drive further conversations in order to improve their work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KO4hoCWzdevrQhXiru54TQ.jpeg" /><figcaption>Source of demand + Delivery capability activities outcomes.</figcaption></figure><p>Next STATIK’s step is <a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a>. Or review the previous step, <a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63724e1f436c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understand sources of dissatisfaction]]></title>
            <link>https://hjavixcs.medium.com/understand-sources-of-dissatisfaction-7de1c1db1d12?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7de1c1db1d12</guid>
            <category><![CDATA[stakeholder-analysis]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[dissatisfaction]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[statik]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Tue, 14 Jan 2020 14:08:05 GMT</pubDate>
            <atom:updated>2020-11-28T17:58:36.090Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><strong>Understand sources of dissatisfaction</strong></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><h3>Understanding the source of dissatisfaction</h3><p>Before identifying the source of dissatisfaction, I recommend identifying and mapping by influence/interest your stakeholders.</p><p><strong>IDENTIFYING STAKEHOLDERS</strong></p><p>Identify who your stakeholders are (names, roles, groups) on post-its.</p><figure><img alt="Stakeholders" src="https://cdn-images-1.medium.com/max/908/1*wrJEg65sN06ajuf2Ghe9Kw.png" /><figcaption>Examples of stakeholders.</figcaption></figure><p><strong>STAKEHOLDERS MAPPING</strong></p><p>Next, work out their power, influence, and interest, so that you know who you should focus on.</p><figure><img alt="Power/Interest matrix" src="https://cdn-images-1.medium.com/max/804/1*2Umc_WUxEh-0KM75TZRR1g.png" /><figcaption>Power/Interest matrix.</figcaption></figure><p><strong>SOURCES OF DISSATISFACTION</strong></p><p>First, allow each one to fulfill and expose their dissatisfaction with the current system. Then, grouping and prioritizing the dissatisfaction in a group.</p><figure><img alt="Internal and external dissatisfaction" src="https://cdn-images-1.medium.com/max/1024/1*IJfZuMbsjSRWAO1770wW1A.png" /><figcaption>It’s often useful to split sources of dissatisfaction into two categories: Internal and External.</figcaption></figure><figure><img alt="Source of dissatisfaction activity" src="https://cdn-images-1.medium.com/max/1024/1*zQUoOdVwjQ35PT6TJF9LQw.jpeg" /><figcaption>Source of dissatisfaction activity outcomes.</figcaption></figure><p>Next STATIK&#39;s steps are <a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand and current delivery capacity</a>. Or review the previous step <a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7de1c1db1d12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understand what makes the business fit for purpose]]></title>
            <link>https://hjavixcs.medium.com/understand-what-makes-the-business-fit-for-purpose-803ed128b245?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/803ed128b245</guid>
            <category><![CDATA[fit-for-purpose]]></category>
            <category><![CDATA[purpose-driven-business]]></category>
            <category><![CDATA[purpose]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[statik]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Tue, 14 Jan 2020 13:52:59 GMT</pubDate>
            <atom:updated>2020-11-28T17:59:00.288Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a series of posts from the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a> wich it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><strong>Understand what makes the business fit for purpose</strong></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><h3>Understanding fit for purpose</h3><p>Let’s start understanding what’s the purpose of a team, or area where I want to implement Kanban. What the team or area do for satisfying their clients? Does everybody have the same understanding of their purpose?</p><p>For facilitating this activity, I start by asking the audience and briefly debate.</p><ul><li>Why does the team exist (from their point of view)?</li><li>What is their routine?</li><li>Who is their customer (or who is consuming their services)?</li></ul><p>Then I lead the following activity:</p><p><strong>DEFINING THE TEAM PURPOSE STATEMENT</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*i6SldohMGo7ClvrD-6vtRA.png" /></figure><ol><li><strong>Describe WHAT your team does? </strong>In five or six words or sentences, write down what your team does, what it delivers or what it produces.</li><li><strong>WHO are you doing it for?</strong> Clarify who your most important stakeholder is by establishing who has most to gain or lose by your success.</li><li><strong>WHY are we doing what we do?</strong> Ask yourself, ‘What is the final impact for the end-user of our product or service?’ In this way, you’re creating a clear thread that shows how what you do is important, and how it impacts the final customer.</li></ol><figure><img alt="Marketing mission statement" src="https://cdn-images-1.medium.com/max/1024/1*4UJXO6HRjzqh8LkfJnN1Yw.png" /><figcaption>Make sure the language in your Team Purpose Statement isn’t marketing speak.</figcaption></figure><p>This is an optional step. But I like to do it always. I ask the audience reframing the purpose statement in the ‘Elevator Pitch’ format. Note we already identify the missing parts in the previous activity (What, Who, Why).</p><p><strong>ELEVATOR PITCH</strong></p><p>Create an elevator pitch by groups, then converge by consent/consensus.</p><figure><img alt="Elevator Pitch format" src="https://cdn-images-1.medium.com/max/998/1*ASVgeKoDEXTYjE7Vou9dhw.png" /><figcaption>Elevator Pitch format.</figcaption></figure><p>So now the team or area is (literally) on the ‘same page’.</p><figure><img alt="Fit for purpose activity" src="https://cdn-images-1.medium.com/max/1024/1*p3ExlYsdQlejS0daxqEBlA.jpeg" /><figcaption>Fit for purpose activity outcomes.</figcaption></figure><p>If you want to go further this activity, fit for purpose is an entire topic, there’s a <a href="https://www.goodreads.com/book/show/36455731-fit-for-purpose">book </a>with the same title and also there’s a specific <a href="https://djaa.com/fit_for_purpose/">training</a>. Remember that STATIK not only works for implementing Kanban.</p><p>Next STATIK&#39;s step is <a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a>. Or review the main topic <a href="https://medium.com/@hjavixcs/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a">STATIK (Systems Thinking Approach to Introduce Kanban)</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=803ed128b245" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[STATIK (Systems Thinking Approach to Introduce Kanban)]]></title>
            <link>https://hjavixcs.medium.com/statik-systems-thinking-approach-to-introduce-kanban-13996dbe414a?source=rss-597d37401b2c------2</link>
            <guid isPermaLink="false">https://medium.com/p/13996dbe414a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[statik]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[workshop]]></category>
            <dc:creator><![CDATA[H. Javier Castillo Suazo]]></dc:creator>
            <pubDate>Tue, 14 Jan 2020 13:30:34 GMT</pubDate>
            <atom:updated>2020-11-28T17:59:37.135Z</atom:updated>
            <content:encoded><![CDATA[<p>Maybe you already know Kanban, have some experience as a practitioner or supporting a team or maybe you’ve read something about kanban. And the idea of implementing kanban is in your main but you are not sure where or how to start. Maybe you are still deciding on kanban or scrum. Kanban is doing very well not only for software maintenance teams (it is what I hear most repeatedly) but in reality like any other agile methods, they depend a lot on the context. I have had experiences as an Agile Coach in teams that during the development of a new product have gone from XP to Scrum and then to Kanban. Because the conditions and restrictions of the project were changing. Although simple rules can be used to determine what kind of methodology to use (at least between Scrum, Kanban, Lean Startup, and Waterfall) depending on the degree of knowledge of the problem and the degree of knowledge of how to solve the problem, that is another story I’ll tell in another post.</p><p>If you have decided to implement Kanban in your team or your organization, this series of posts could help you on that journey.</p><p>Before go beyond, let me introduce what I do. I’m an Agile Coach working in the Agile Chapter team of Accenture Digital Spain, we support and accompany our clients on their journey towards the adoption of new ways of working as an accelerator of their digital transformation.</p><p>Some months ago one of our clients (a company belonging to one of the leaders of the banking sector in Spain) has needed to accelerate its infrastructure area and we have recommended implementing Kanban as part of its transformation towards new agile ways of work. Note that I have said that it is an infrastructure area, not properly software development.</p><p>So I prepared this workshop for our client, which I could later use for another internal client and then I wanted to share in the <a href="https://www.meetup.com/es-ES/Agile-Barcelona-Meetup/events/263613095/">Agile-Barcelona Meetup</a> and <a href="https://www.meetup.com/es-ES/AgileNorte/events/264746902/">Agile Norte</a> communities and now I want to share it with you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3DvuNKdEzZVpzx9zFbyNQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7bbsJoEiuP6IwtbPUc1OaA.jpeg" /><figcaption>Material and graphic facilitation for the workshop meetup.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZ712sXuzMUHxvnVL550Ew.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ta9uY23cs6gVz17DKKw_Kg.jpeg" /><figcaption>STATIK workshop at the Agile-Barcelona Meetup.</figcaption></figure><p>Please note I’ve prepared the material for the workshop in a smaller format for working in groups over the tables. I used A3 sheets instead of the classic A1 flipchart paper. You can use whatever it works for your audience, but the general rule is to have a good visualization for the participants and everybody can see and read standing in front of the visual facilitation.</p><p>The idea of this post (or workshop) is not to explain what Kaban is, and the members of the team or area where Kanban is going to be implanted do not have to know what Kaban is at the time of running this workshop. Of course, at some point, the training of Kanban will have to be done. My recommendation for learning Kanban is playing with some dynamics or board games or directly doing Kanban. Of course, it is a good idea to explain briefly what Kaban is before starting the workshop.</p><h3>What is Kanban?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*0r-ibwVz3jMUS-lxHwXHGg.png" /><figcaption>Kanban Card.</figcaption></figure><p>From Japanese, Kanban is translated as ‘billboard’ or ‘signboard’. Kanban is a workflow management method designed to help you visualize your work, maximize efficiency, and be agile. Initially, it arises as a scheduling system for lean manufacturing, originating from the Toyota Production System (TPS). Today, <a href="https://twitter.com/lki_dja">David J. Anderson</a> is known as the father of the Kanban Method and author of the books such as <a href="https://www.goodreads.com/book/show/8086552-kanban">Kanban: Successful Evolutionary Change for Your Technology Business</a> and many others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*a47e0sCGlIPVgDtiNtnGvw.png" /><figcaption>A scheduling system from the Toyota Production System (TPS).</figcaption></figure><p><strong>CORE PRINCIPLES</strong></p><ol><li>Start With What You Do Now</li><li>Agree to Pursue Incremental, Evolutionary Change</li><li>Respect the Current Process, Roles &amp; Responsibilities</li><li>Encourage Acts of Leadership at All Levels</li></ol><p><strong>KANBAN PRACTICES</strong></p><ol><li>Visualize Work</li><li>Limit Work in ̶ ̶P̶r̶o̶g̶r̶e̶s̶s̶ ̶ Process (WIP)</li><li>Focus on Flow</li><li>Continuous improvement</li></ol><h3>What is STATIK?</h3><p><strong>STATIK (Systems Thinking Approach to Introduce Kanban)</strong> it’s an exploratory and collaborative approach to implement Kanban. It helps to understand the current demand and dynamics, to design and implement a Kanban work model that allows increasing the efficiency and quality of the service through the culture and techniques of continuous improvement.</p><p>It is also a good tool to discover all the services provided by a team, its workflows, and its alignment with the purpose and expectations of the client.</p><p>The STATIK method helps answer the following questions:</p><ul><li>What is the purpose of the area? What are the services you provide? To Whom?</li><li>How is the current way of carrying out the work?</li><li>What are the sources of dissatisfaction?</li><li>What are the sources of demand?</li><li>What is the current service capacity?</li><li>What are the workflows? What kinds of services are there?</li><li>How to design a Kanban system that allows me to visualize and control the work?</li></ul><figure><img alt="Systems thinking and the elephant metaphor" src="https://cdn-images-1.medium.com/max/958/1*i98FQBA3ozCYUnzDi5SK7A.png" /><figcaption>Systems thinking (defined by Peter Senge), is a way of analyzing organization patterns from a broad point of view, instead of looking at small parts in isolation (the elephant metaphor).</figcaption></figure><h3>Statik Steps</h3><p><strong>As an iterative approach, STATIK suggests you go through the following steps.</strong></p><p><strong>For each identified service:</strong></p><ol><li><a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a></li><li><a href="https://medium.com/@hjavixcs/understand-sources-of-dissatisfaction-7de1c1db1d12">Understand sources of dissatisfaction</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze the source and nature of demand</a></li><li><a href="https://medium.com/@hjavixcs/analyze-the-source-and-nature-of-demand-63724e1f436c">Analyze current delivery capability</a></li><li><a href="https://medium.com/@hjavixcs/model-the-service-delivery-workflow-f5c3884f4fec">Model the service delivery workflow</a></li><li><a href="https://hjavixcs.medium.com/identify-and-define-classes-of-service-5fea21e2734c">Identify and define classes of service</a></li><li><a href="https://hjavixcs.medium.com/design-the-kanban-system-b1b45fec4f3e">Design the Kanban system</a></li><li>Socialize design &amp; negotiate implementation</li></ol><p>The STATIK method was defined by D̶a̶v̶i̶d̶ ̶J̶.̶ ̶A̶n̶d̶e̶r̶s̶o̶n̶,̶ ̶l̶e̶a̶d̶e̶r̶ ̶o̶f̶ ̶t̶h̶e̶ ̶K̶a̶n̶b̶a̶n̶ ̶m̶o̶v̶e̶m̶e̶n̶t̶ <a href="https://twitter.com/asplake">Mike Burrows</a> in his 2014 book “<a href="https://www.goodreads.com/book/show/23162381-kanban-from-the-inside">Kanban from the inside</a>” (thanks <a href="https://medium.com/u/e4ed9714c0be">Bruno Baketaric</a>). Recently, I had the honor to met him. My colleagues and I attended the Kaban Professional Management (KPM) training with him, and we’ve created a lot of insights on how to help teams and organizations on how to implement and manage Kanban Systems.</p><h3>Facilitating the STATIK workshop</h3><p>Although you don’t need to follow them in a specific order those steps and it is a good practice to revisit the steps for further improvement.</p><p>I’ll explain on individual posts how I facilitate every step. Please go through every STATIK step link above. I’ll do my best to posting every step as soon as possible.</p><figure><img alt="STATIK Steps" src="https://cdn-images-1.medium.com/max/870/1*Q23bJpS4KZv2pYWh-6fvWA.png" /><figcaption>My graphic facilitation for the STATIK Steps.</figcaption></figure><p>The first step of the STATIK method is <a href="https://medium.com/@hjavixcs/understand-what-makes-the-business-fit-for-purpose-803ed128b245">Understand what makes the business fit for purpose</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13996dbe414a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>