<?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[Sooner Safer Happier - Medium]]></title>
        <description><![CDATA[Better ways of working, AI Transformation, Business agility - Medium]]></description>
        <link>https://medium.com/sooner-safer-happier?source=rss----9015db1a7b56---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Sooner Safer Happier - Medium</title>
            <link>https://medium.com/sooner-safer-happier?source=rss----9015db1a7b56---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 04:01:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/sooner-safer-happier" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is BVSSH?]]></title>
            <link>https://medium.com/sooner-safer-happier/what-is-bvssh-523efe87a7fb?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/523efe87a7fb</guid>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[strategy-to-execution]]></category>
            <category><![CDATA[team-topologies]]></category>
            <category><![CDATA[business-agility]]></category>
            <dc:creator><![CDATA[Myles Ogilvie]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 17:18:03 GMT</pubDate>
            <atom:updated>2025-12-04T17:48:58.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*7-zliWxoMTwFMHQkVcn-Wg.png" /></figure><p>September 2015 was the last time that seven of the top ten firms by market value were <em>not</em> information technology firms. Fast forward less than two years, to June 2017 and seven of the top ten firms <em>are</em> IT firms. By June 2018, General Electric, the last remaining original constituent of the Dow Jones index, created in 1896, was removed from the index, a sign of the moving tectonic plates.</p><p>Only two years later, by mid 2020, accelerated by a global pandemic, it’s not seven firms in <em>any </em>position in the top ten which are IT firms, it’s <em>the top seven </em>most valuable firms in the world. At the time of writing, only one firm remains in the Dow which joined prior to the invention of the microprocessor and half of the Dow constituents have been in the index for 15 years or less.</p><p>Clearly, with the latest technology-led revolution, we have tipped from one Age to another. We have gone from the Age of Oil and Mass Production where work was mostly repetitive and knowable to the Age of Digital where work is mostly unique, emergent and unknowable. Like going from the Stone Age to the Bronze Age, there is a new means of production, which creates new expectations. In order to survive and thrive, there is a need to adopt ways of working suited to the new means of production. In the Age of Digital every company is a software company directly or indirectly, and there are few cases where value delivery does not in some way involve Information Technology.</p><p><strong>Better Value Sooner Safer Happier (BVSSH)</strong> is an outcome oriented approach to continuously improve ways of working.</p><p>It is a collection of <strong>principles and patterns</strong> for improving business outcomes, as firms pivot from ways of working dating back two technology revolutions ago, to ways of working suited to the nature of work in the Age of Digital.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qx5Ml7Ih4NoXiBey.jpeg" /></figure><p>An antipattern is inflicting a capital ‘A’, capital ‘T’, Agile Transformation. Agile is one of many possible ‘means to an end’, along with Lean, DevOps, Cloud and more, however it is not the ‘end’ itself. Organisations can be ‘doing Agile’ and not seeing an improvement in business outcomes. The eye is on the wrong ball.</p><p>Instead, focus on a positive trend on the outcomes, and use agile, lean, DevOps, systems thinking, design thinking, theory of constraints and so on as figurative tools in the toolbox, suited to your context. Every organization is unique and is a complex adaptive system, <strong>there is no one size fits all approach</strong>.</p><p>The key outcomes are <strong>Better, Value, Sooner, Safer and Happier</strong>. These are a balanced set of outcomes. See the book for the collection of Antipatterns and Patterns as to how to get there.</p><p><strong>Better</strong> is quality. Quality is built in rather than inspected in later. With smaller slices of value and multidisciplinary teams, changes are within a team’s cognitive load (that is, complexity that fits in your head) and there is a limited “impact radius.” There are fewer incidents and outages. There is less rework, less failure demand. More time is spent proactively rather than reactively.</p><p><strong>Value</strong> is unique; it’s why you are doing what you are doing. It is of value to someone. It could be financial; it could be maintaining public safety; it could be charitable. As the future is not knowable, value is articulated via outcome hypotheses with leading and lagging measures. OKRs done well are a good way to measure value. The leading measures acting as an early indicator, an early feedback loop. This enables pivoting and agility in order to maximise the outcome or have the cheapest cost of failure.</p><p><strong>Sooner</strong> is time to market, time to learning, to pivoting, to de-risking, to avoiding a “sunk cost fallacy,” to locking in progress and value early and often. There are three key measures.</p><ul><li><strong>Lead Time</strong> is the time from starting work on an item of value to getting it into the hands of a customer.</li><li><strong>Throughput</strong> is the count of items of value delivered into the hands of a customer in a given time period. As lead time comes down, throughput should go up.</li><li><strong>Flow Efficiency</strong> is the percentage of time that work is actively being worked on during its elapsed end-to-end lead time, as opposed to waiting to be worked on. For most large service-based organizations, flow efficiency is typically 10% or lower. This means that work is waiting at least 90% of the time. This is where significant gains can be made. Focus on where the work isn’t, not where the work is.</li></ul><p><strong>Safer</strong> is Governance, Risk, and Compliance (GRC), information security, data privacy, regulatory compliance and resilience in chaos, be that a cyber-attack or a global pandemic. It is customers trusting your organization. It is agile rather than fragile. It is speed and control, not one or the other. It is cultural, keeping the conversation on risk alive. The better the brakes, the faster you can go.</p><p><strong>Happier</strong> covers customers, colleagues, citizens, and climate, as it is not about “more for less” at any human or climatic cost. It is high levels of customer advocacy and colleague engagement with a positive impact on society and the one planet we live on. It is a more humane way of working, with empowered multidisciplinary teams and high levels of psychological safety, enabling experimentation and improvement.</p><p>Together, <strong>Better Value Sooner Safer Happier</strong> balance each other. If Sooner is achieved by working people harder or cutting corners, the result will be a reduction in Better, Safer and Happier.</p><p>With <strong>BVSSH</strong> measures, it is important to look at the trends over time, the vector metrics, rather than absolute values. What matters is not the absolute difference between teams, rather that teams are continually improving. Improvement trends can be compared across contexts.</p><p><strong>BVSSH</strong> contains two sets of outcomes. Better Sooner Safer Happier are the <strong>how </strong>outcomes. They measure the improvement in the system of work. Value is the <strong>what</strong>, the business outcome hypotheses that the system of work produces. The two sets of outcomes form a virtuous circle.</p><p>Improvements in the how leads to improvement in the what due to faster feedback, the ability to pivot, higher quality, and more engaged colleagues and customers. Rather than inflicting one set of practices, focus on BVSSH and empower teams to improve using their own brains, with support, in their unique context. With incentivisation and psychological safety, this will build a new muscle memory, a continuously learning and improving organization.</p><p><strong>BVSSH</strong> is a collection of Principles and Patterns for improving how we do what we do. For more see the book ‘Sooner Safer Happier’ <a href="https://www.soonersaferhappier.com/book">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*ifjCvu1T0JqASlLt.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=523efe87a7fb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/what-is-bvssh-523efe87a7fb">What is BVSSH?</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pop the bubbles, create a learning ecosystem]]></title>
            <link>https://medium.com/sooner-safer-happier/pop-the-bubbles-create-a-learning-ecosystem-9eebe5be7944?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/9eebe5be7944</guid>
            <category><![CDATA[vuca]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-agility]]></category>
            <category><![CDATA[learning-organization]]></category>
            <dc:creator><![CDATA[zsolt berend]]></dc:creator>
            <pubDate>Sat, 07 Dec 2019 23:30:57 GMT</pubDate>
            <atom:updated>2019-12-07T23:30:56.879Z</atom:updated>
            <content:encoded><![CDATA[<p>The population of Detroit doubled between 1910 and 1920, it went from half a million to a million. The key driver of the growth was the automobile industry, and the majority of the new recruits were immigrants from Italy, Russia, Hungary and other parts of Eastern Europe (<a href="https://books.google.co.uk/books?id=j0LC6XZtH84C&amp;pg=PT271&amp;lpg=PT271&amp;dq=1915+survey+highland+park+languages&amp;source=bl&amp;ots=dI1_Bdxgi6&amp;sig=ACfU3U3g-ZD2cTgqT-e1_2aULk93eCqdSA&amp;hl=en&amp;sa=X&amp;ved=2ahUKEwjn_L6Pl6jlAhVZURUIHRhvCZMQ6AEwAnoECAcQAQ#v=onepage&amp;q=1915%20survey%20highland%20park%20languages&amp;f=false">ref</a>).</p><p>A 1915 survey showed that the workforce in Highland Park Ford Plant spoke <strong>more than 50 languages</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UrMb_L6xaxxL0kozSc-xug.jpeg" /><figcaption>Source: Google Maps</figcaption></figure><p>Highland Park Ford Plant produced the legendary Model T (<a href="https://en.wikipedia.org/wiki/Highland_Park_Ford_Plant">ref</a>) which is arguably one of the greatest engineering masterpiece of its time. So I wonder how was it possible for workers who did not share a single common language to work together to assemble this complex, sophisticated vehicle.</p><p>As paradoxical as it sounds, the answer is they did not have to. There was no need to work together, to discuss, to share information and learnings.</p><p>Assemblers worked in perfect division of labour, their task was to put nuts and bolts in the parts. The fact that they could not speak to their fellow assemblers had no impact on the productivity of Ford’s assembly line. This was the world of <a href="https://en.wikipedia.org/wiki/Scientific_management">Taylorism</a>, the world of Scientific Management.</p><p>As a stark contrast, today, 100 years later working in silos, not being able to collaborate, share learnings has a direct negative impact on productivity and organisational outcomes. We are living in the era of the knowledge workers.</p><p><a href="https://www.youtube.com/watch?v=gCHhWywIKpE"><em>“Our brain loves patterns … culture is a bunch of patterns, patterns of behaviours”</em></a> Dr Steve Robbins</p><p>I will share a number of anti-patterns that experience and research shows are hindrance to the creation of a learning organsiation and corresponding patterns.</p><h3><strong>Anti-pattern 1: Information and Learning Siloes</strong></h3><p><em>“I shall reconsider human knowledge by starting from the fact that we can know more than we can tell.”</em> Mihaly Polanyi, <strong>tacit</strong> knowledge</p><p>As Mary and Tom Poppendieck pointed out in their book: Implementing Lean Software Development: From Concept to Cash. Addison-Wesley, 2006. (ref) a great amounts of tacit knowledge remain with the creator and never get handed off to the receiver. They suggest that taking a conservative estimate, up to 50% of the knowledge is lost by each hand-offs.</p><p>It makes it even worse that the knowledge loss is compounded.</p><p>So considering a usual software delivery through analysis, design, code and test role based silos, this would translate to <strong>~87% of knowledge loss by the 3rd handoff.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_hXBpD0bOSlUzhmgx9TSA.png" /></figure><p>Yet most software delivery set-ups, solution delivery life cycles are based on role based silos.</p><h3><strong>Anti-pattern 2: Outputs over Outcome</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8O1XsI0MAeJW8ccySfBkrg.png" /><figcaption>Stuck in the Busy Trap. Photo: Zsolt Berend, Time Square, NYC</figcaption></figure><p>Modern corporate culture glorifies “busyness” as <a href="https://www.fandm.edu/uploads/files/507732845908040890-the-busy-trap-nytimes-com.pdf">Tim Kreider calls it we stuck in the ‘busy’ trap</a>. Since I read Tim Kreider’s blog I keep testing the audience at conferences with the question of what is the standard response they get when they ask a colleague: how they are doing, how is work? The most significant words in the world cloud of the responses are always: <strong>‘busy’</strong> and its synonyms.</p><p>This behavioural pattern is a legacy of 19th century <a href="https://en.wikipedia.org/wiki/Scientific_management">Taylorism</a> when there was a linear, direct correlation between “busyness” and organisational outcomes which is unfortunately still applied in the knowledge workers’ world.</p><h3><strong>Anti-Pattern 3: Bubble Effect</strong></h3><p>Human beings are<strong> social animals </strong>according to Aristotle, the great ancient Greek philosopher.</p><p>We also follow tribal behavioural patterns.</p><p><em>“Humans are </em><strong><em>tribal</em></strong><em>. We need to belong to groups. We crave bonds and attachments, which is why we love clubs, teams, fraternities, family. Almost no one is a hermit. Even monks and friars belong to orders. But the tribal instinct is not just an instinct to belong. It is also an instinct to exclude.”</em> Amy Lynn Chua, American lawyer, academic and writer.</p><p>This promotes the creation of <strong>social bubbles </strong>whether consciously or unconsciously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zFTctJHEnpeJMk6k" /><figcaption>Photo by <a href="https://unsplash.com/@sharonmccutcheon?utm_source=medium&amp;utm_medium=referral">Sharon McCutcheon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We can observe various forms of bubbles within organisations. Role based silos, agile, scrum, kanban teams, long lived value stream aligned teams etc. Besides the positives of these social structures they all share some undesired effects. They all suffer from the <a href="https://twitter.com/zsoltberend/status/1172967747787087873?s=20"><strong>bubble effect</strong></a><strong>:</strong></p><p><strong>Silo mentality</strong></p><p>People, teams within the bubble develop <a href="http://www.businessdictionary.com/definition/silo-mentality.html">silo mentality</a> a mindset of wanting to protect and not to share information with others within the same company.</p><p><strong>Limited discoverability</strong></p><p>Are we living in a Universe or Multiverse? Learnings, knowledge, information outside the bubble can not be reached, discovery is limited.</p><p><strong>Poor learning retention</strong></p><p>Since the bubbles are disconnected, when people leave the company the learnings are lost forever</p><p><strong>Duplication</strong></p><p>Same ideas could be developed, same impediments could be tackled, duplication of work, inefficiency.</p><h3><strong>Anti-Pattern 4: Deterministic Culture.</strong></h3><p>“God does not play dice” — <em>Albert Einstein</em></p><p>It is hard to argue with a statement when it comes from one of the greatest minds in human history. However as it happens sometimes even Einstein made mistakes. He did not believe in the non-deterministic nature of the world of atomic particles. This world is ruled by <a href="https://www.britannica.com/science/uncertainty-principle">Heinsberg’s uncertainty principle</a>, nothing can be certain, things, e.g. speed or location of particles can only be described as probabilities.</p><p>Behind the deterministic mindset lay the fear of uncertainty. The fear of not being able to tell when things are going to get done, to estimate the length of the delivery pipeline. This leads to lengthy up-front planning process, big upfront design and architecture.</p><p>This promotes command and control style leadership. Leaders who exhibit these behavioural patterns want deterministic plans with all milestones identified, agreed upfront and strong control over the execution.</p><p>However as <a href="https://medium.com/u/88acf190aaee">Jonathan Smart</a> points out in his blog: <a href="https://medium.com/sooner-safer-happier/agility-build-the-right-thing-69d316aeb56b">Agility: Build the right thing</a></p><p><em>“You don’t know </em><strong><em>when</em></strong><em> you’re going to reach a milestone. The last 20% of the journey might take 80% of the time. There might be roadworks, an accident or a flooded river crossing. You only know you’ve reached a milestone when you reach a milestone. And even then, given your </em><strong><em>intent</em></strong><em>, you might find that it’s not the optimal place to be.”</em></p><p>These behavioural patterns lead to no or limited space for learning for individuals and for the whole of the organisation, promotes ignorance outside the very narrow specialization.</p><p>The quote below from Frederick Winslow Taylor: <a href="https://en.wikipedia.org/wiki/Scientific_management">Scientific Management</a> gives a sobering picture of this approach.</p><p><em>“In our scheme, we do not ask the initiative of our men. We do not want any initiative. All we want of them is to obey the orders we give them, do what we say, and do it quick.”</em></p><p>Todays’ theory X leadership style has strong roots in Taylorism. <em>“This management style assumes that the typical worker has little ambition, avoids responsibility, and is individual-goal oriented.” Source: </em><a href="https://en.wikipedia.org/wiki/Theory_X_and_Theory_Y"><em>Wikipedia</em></a></p><h3><strong>Anti-Pattern 5: Weaponised Metrics</strong></h3><p>“When a measure becomes a target, it ceases to be a good measure.” Goodhart’s law</p><p>Theory X leaders fear data or at least data that show that they will not reach a set target. The infamous <a href="https://en.wikipedia.org/wiki/Traffic_light_rating_system#Project_management">RAG status</a> lead to the watermelon effect:</p><p>Green, Green, Green …. and just days or very close proximity of the go live it goes Red overnight.</p><p>Such fear promotes faking certainty, gaming metrics. Targets are reached, by faking them.</p><p>As an example, some NHS Hospital Trusts introduced <strong>Hello Nurses</strong> to meet the targets of seeing patients quickly in the emergency department. Yet patients left waiting for treatment for hours. ‘People have got around this by achieving the target, rather than the spirit of it, which is that those who need attention receive it as quickly as possible,’ says Gordon Mitchell, deputy chief executive of medical assessment charity Health Quality Service (<a href="https://samathieson.com/sa-mathieson/take-aim-at-nhs-targets/">ref</a>)</p><h3><strong>Pattern 1: Optimise for Learning</strong></h3><p>As pointed out in <strong>Anti-pattern 1: Information and Learning Siloes </strong>handoffs lead to loss of information, silos prevent free uninterrupted flow of knowledge, shared learnings.</p><p>In order to optimise the flow first we need to install transparency, to make queues, handoffs points, bottlenecks, impediments visible.</p><p>This can be done using <a href="https://en.wikipedia.org/wiki/Value-stream_mapping"><strong>value stream mapping</strong></a>. Through a positively intense couple of hours and lots of postits teams produce a map of all steps, activities the work is going through from concept, through business case, analysis, design etc. all the way to production. This is an awesome learning exercise for the entire team, which results in a number of impediments and improvements to act on.</p><p>One of the default results is the need to shift activities left, to start earlier and to collaborate more.</p><p>Collaboration is a true game changer. You can have cross functional team that covers all necessary skills to deliver value to the customer. Yet they still work in role based slios.</p><p>It only changes when individuals start working together, pairing up, swarming on the same work. This leads to developing new skills and eventually breaking specialisation, breaking silos. Such teams go from having deep and narrow specialists, I-shaped to having team members with broad and multiple specialist skills like T, PI, Comb-shaped.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_07tUDd3Qy5kNg8f" /><figcaption>Breaking specialisation through developing new skills</figcaption></figure><p><em>“Under certain conditions, matter will spontaneously self-organise.” </em>Jeremy England, theoretical physicist, studying the origins of life</p><p>Teams and individuals require autonomy and empowerment, the right leadership support to self-organise, collaborate, develop new skills, break specialisation and with that to create shared learning ecosystem.</p><h3><strong>Pattern 2: Nested learning with built-in feedback loops</strong></h3><p><em>“Ironically, jobs are actually easier to enjoy than free time, because like flow activities they have </em><strong><em>built-in goals</em></strong><em>, </em><strong><em>feedback</em></strong><em> rules, and challenges, all of which encourage one to become involved in one’s work, to concentrate and lose oneself in it. Free time, on the other hand, is unstructured, and requires much greater effort to be shaped into something that can be enjoyed.” </em><a href="https://www.amazon.co.uk/Deep-Work-Focused-Success-Distracted/dp/0349411905">Cal Newport, Deep Work</a></p><p><strong>Continuous learning</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/653/1*gYExz9U4sOROz926wL1UFQ.png" /><figcaption>Nested Learning with built-in feedback Loops</figcaption></figure><p>Install learning by creating a routine, kata, habit for learning in a nested cadence. Sessions like <strong>daily </strong>stand-ups, coordination, pairing-ups, <strong>weekly </strong>planning, replenishment, retrospectives, <strong>monthly </strong>show and tells, open spaces, unconferences, internal meet-ups, <strong>yearly </strong>conferences are all good examples of feedback-loops on ways of working, behavioural patterns, team policies, routines, mental models.</p><p><strong>Daily</strong>, <strong>weekly</strong>, <strong>monthly </strong>releases into production, <strong>quarterly </strong>OKRs, business outcomes driven insights, leading indicators, team shared objectives, <strong>yearly </strong>portfolio objectives, lagging indicators, <strong>multi-year</strong> company level strategic objectives are all good example of cadences to learn whether the <strong>RIGHT </strong>things get delivered.</p><p>Once we establish these routines of seeking and getting feedback the next building block is to use these learning to improve.</p><p><strong>Continuous improvement</strong></p><p>Experiment with lean principles and practices for continuous improvement.</p><p>One powerful practice is the <a href="https://en.wikipedia.org/wiki/Toyota_Kata#The_Improvement_Kata">Improvement Kata</a>. It is a routine for moving from a current state to a new desired state iteratively, which uncovers obstacles that need to be worked on. Below is a canvas where on the left there are the current and future states supported by data and articulation of leading and lagging indicators. On the right hand side on the top is the next target state and the bottom right is a Kanban board with the steps to do to reach the next target state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*32ji4drHg0FbAKuYzCYjjg.jpeg" /><figcaption>Create based on <a href="https://blog.crisp.se/2013/05/14/jimmyjanlen/improvement-theme-simple-and-practical-toyota-kata">Jimmy Janlen</a> and Mark Williams</figcaption></figure><h3><strong>Pattern 3: Over Communication</strong></h3><p>Pop the bubbles, destroy the fantasy of living in an isolated world and with that all the undesired behavioural patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*rprbbEmGQ6UhivvwElLltQ.png" /></figure><p><strong>Conferences, </strong><a href="https://en.wikipedia.org/wiki/Unconference"><strong>Unconferences</strong></a><strong>, </strong><a href="https://en.wikipedia.org/wiki/Open_Space_Technology"><strong>Open Space</strong></a></p><p><em>“</em><strong><em>Open</em></strong><em> some </em><strong><em>space</em></strong><em>, and Spirit will certainly show up. Allow the magic of self-organization to work for you, and the complex adaptive system that we are will find its own power.” </em><a href="https://en.wikipedia.org/wiki/Open_Space_Technology">Harrison Owen, civil rights activist, developed the idea of Open Space Technology in 1980.</a></p><p>Invite people across the organisation to openly share their topics of interest and co-design, co-develop the ideas. Unconferences are great format to run these sessions.</p><p>Organise internal conferences and open up for internal and external people to speak, share their knowledge and experience reports.</p><p><strong>Awards</strong></p><p>Sharing success stories is a great thing, collecting them though is not an easy thing due to:</p><ul><li>people are ‘busy’ as <strong>we stuck in the busy trap</strong></li><li><strong>discoverability is limited</strong> as we live in our own <strong>bubbles </strong>so we do not know the teams that could submit a success story</li><li>takes a long time to write, review and approve the content as teams and leaders are suffering of <strong>silo mentality</strong> not wanting to share knowledge as they like living in their bubble</li></ul><p>The major problem is ultimately that this is a <strong>push </strong>approach.</p><p>So instead, flip it around and generate <strong>pull. Run awards. </strong>E.g. an annual agility awards open to all teams agnostic whether IT or non-IT and size. You will get a flood of submissions, rich in content and data. Besides awards and celebrations which attracts a lot of people these submissions are gold source for sharing in webinars, show and tells, roadshows, conferences, internal meetups.</p><p><strong>Rotation, Secondment, Mobility</strong></p><p>Accelerate up-skilling and sharing knowledge by rotating people between teams. Provide discoverability of skills and experiences through making CVs, interests, experiences searchable across the organisation. Encourage internal mobility.</p><p><a href="https://en.wikipedia.org/wiki/Psychological_safety"><strong>Psychological Safety</strong></a></p><p>“Being able to show and employ one’s self without fear of negative consequences of self-image, status or career”, Kahn, 1990</p><p>Establish an environment of physiological safety so people can bring themselves to work, learn, develop without fear.</p><p><strong>Centre of Enablement Fractal</strong></p><p>Establish fractal or hub and spoke like distribution of small centre of enablement teams of change agents and coaches to nurture the culture, explore and connect the bubbles.</p><p><strong>Communities of Practice (CoPs)</strong></p><p>Establish global community of practices with local chapters. Have local ‘community organisers’ mobilise and run activities based on common interest, like in the form of conferences, unconferences. Establish channels for sharing and discussing topics like internal chat channels, file sharing spaces, webinars and events etc.</p><h3><strong>Pattern 4: Be comfortable with uncertainty</strong></h3><p>“<em>So God does play dice with the universe. All the evidence points to him being an inveterate gambler, who throws the dice on every possible occasion.</em>” <em>Steven Hawking</em> (<a href="http://www.hawking.org.uk/does-god-play-dice.html">ref</a>)</p><p>We live in a world of <strong>uncertainty </strong>combined with <strong>volatility</strong>, <strong>complexity </strong>and <strong>ambiguity </strong>(<a href="https://en.wikipedia.org/wiki/Volatility,_uncertainty,_complexity_and_ambiguity">VUCA</a>). In order to navigate in this world we need to develop an <a href="https://en.wikipedia.org/wiki/Mindset#Fixed_and_Growth_Mindset">growth mindset</a>. A mindset of embracing trial and error culture, defining and running experiments and using the learnings to define the next set of experiments.</p><p>According to <a href="https://hbr.org/2014/11/how-companies-can-profit-from-a-growth-mindset">Carol Dweck’s research</a>, employees in organisations that encourage growth mindset are <strong>47%</strong> likelier to say that their colleagues are trustworthy, <strong>34%</strong> likelier to feel a strong sense of ownership and commitment to the company, <strong>65%</strong> likelier to say that the company supports risk taking, and <strong>49%</strong> likelier to say that the company fosters innovation.</p><p>Leaders with growth mindset encourage learning loops, experimentation.</p><p>As Stanley McChrystal describes “Many leaders are tempted to lead like a chess master, striving to control every move, when they should be leading like <strong>gardeners</strong>, creating and maintaining a viable ecosystem in which the organization operates.”</p><h3><strong>Pattern 5: Metrics for Learning</strong></h3><p><em>“If a measurement matters at all, it is because it must have some conceivable effect on decisions and behaviour. If we can’t identify a decision that could be affected by a proposed measurement and how it could change those decisions, then the measurement simply has no value”</em> Douglas W. Hubbard,<a href="https://www.goodreads.com/work/quotes/433383"> How to Measure Anything: Finding the Value of “Intangibles” in Business</a></p><p><strong>Pivot from output to outcome metrics</strong></p><p>Measuring outputs #specifications, #enhancements, #features encourage the wrong behaviour to create more and more which leads to busy trap. It does not bring any insights, learnings.</p><p>In a conference, one speaker described proudly how his company had delivered more than 1,500 features the previous year. What the speaker didn’t detail was how many of those features were used. He didn’t say how many were creating revenue or what impact they had had on the organisational performance. Outputs are always much easier to define, monitor, and track than outcomes.</p><p><strong>Outcome metrics</strong> on the other hand are articulated with corresponding leading, launch and lagging indicators. They are designed to help sense, generate insights and learnings.</p><p>As described in <a href="https://medium.com/u/88acf190aaee">Jonathan Smart</a> blog: <a href="https://medium.com/sooner-safer-happier/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Focus on Flow, Quality, Happiness, Safety and Value</a></p><p>“For us, our desired outcomes are described as <strong>Better Value Sooner Safer Happier</strong>, each of which is measurable.”</p><ul><li>Better =&gt; Quality (#incidents in production)</li><li>Value =&gt; bespoke to context of product and service (OKRs, Outcomes with leading, launch and lagging indicators, e.g. #visits, #complaints, %increase in market segment, #referrals, #activation, #retention</li><li>Sooner =&gt; Flow metrics (e.g. concept to learning, release frequency, throughput, flow efficiency)</li><li>Safer =&gt; GRC Control Compliance (e.g. InfoSec, Know-Your-Client, Data Privacy, GDPR type mandatory requirements). Speed &amp; Control. Agile not fragile.</li><li>Happier =&gt; customer and colleague satisfaction, citizens, climate</li></ul><p><strong>5 Whats</strong></p><p>Run workshops, open space to co-create a starter set for metrics. Follow the thought process, derivation of:</p><p>What do <strong>we need to measure</strong>? Any top strategic measures, KPIs?<br><strong>What level </strong>do we need to aggregate? app, product, team, value stream etc.? <br>What do <strong>we want to measure</strong>? <br>Off of that <strong>what can we measure</strong>? We have data for.<br>Off of that what are the measures that are <strong>easy to measure</strong>? Small set.</p><p><strong>Self-serve dashboard</strong></p><p>Install transparency, create a self-serve dashboard for data consumption and drill down capabilities. Ideally the underlying data is auto harvested from the various sources across the value delivery pipe.</p><p><strong>Correlations, insights</strong></p><p>Data is gold. Use data analytics to draw correlations between data. E.g. between release frequency and number of defects.</p><p><strong>Vector metrics, %s and trends</strong></p><p>Avoid absolute numbers, use vector metrics, %s and trends as much as you can. This helps ease the fear of revealing data and have the right focus on analysing, decision making, learning from whether the lever we used brought the desired effects.</p><h3><strong>Summary</strong></h3><p>Pivot from disconnected learning bubbles to a <strong>learning ecosystem</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*tN325jfB81QREAv60JVSLw.png" /></figure><h3>Blogs</h3><ul><li><a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> (Medium.com)</li></ul><h3>Acknowledgements</h3><p>Thanks to <a href="https://medium.com/u/88acf190aaee">Jonathan Smart,</a> <a href="https://medium.com/u/51573d8dcfb4">Simon Rohrer,</a> <a href="https://medium.com/u/23497b276165">Tony Caink</a>, Richard James, Jim Roberts</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9eebe5be7944" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/pop-the-bubbles-create-a-learning-ecosystem-9eebe5be7944">Pop the bubbles, create a learning ecosystem</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agility: Build the right thing]]></title>
            <link>https://medium.com/sooner-safer-happier/agility-build-the-right-thing-69d316aeb56b?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/69d316aeb56b</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Jonathan Smart]]></dc:creator>
            <pubDate>Mon, 02 Sep 2019 16:38:58 GMT</pubDate>
            <atom:updated>2020-08-31T14:02:14.354Z</atom:updated>
            <content:encoded><![CDATA[<p><em>From discrete Output to continuous Outcomes</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dPGlJ-rGpv5-Xc60" /><figcaption>A milestone</figcaption></figure><p>Milestones mark miles. They are made of stone. They are hard to move and are no longer valid once moved. They don’t exhibit agility, nor do they need to. They resemble tombstones and are often referred to as ‘dead-lines’, or ‘drop dead’ dates.</p><p>They don’t convey any expectations on <strong>why </strong>you want to get to where you’re going, <strong>how </strong>you might get there, <strong>how else </strong>you might get there, <strong>if</strong> you’ll make it there at all (the level of <strong>safety </strong>en-route), the <strong>quality </strong>and <strong>experience</strong> of your journey nor <strong>if </strong>it’s even the right destination, given your <strong>intent</strong>.</p><p>They are one dimensional. The distance between two fixed points along one fixed route. Originating 2,300 years ago in the Roman Empire, milestones were set more than 2 feet into the ground, stood 5 feet tall and weighed more than 2 tons. They measured 1,000 paces. They were immovable.</p><p>You don’t know <strong>when</strong> you’re going to reach a milestone. The last 20% of the journey might take 80% of the time. There might be roadworks, an accident or a flooded river crossing. You only know you’ve reached a milestone when you reach a milestone. And even then, given your <strong>intent</strong>, you might find that it’s not the optimal place to be.</p><p>Are milestones a good mental construct to use for unique change with a rapidly changing terrain? I think not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*ZgC6ilE82Da-5ukpIFfvFA.png" /></figure><p>This is the fourth post in a <a href="https://medium.com/sooner-safer-happier">series</a> sharing a number of observed <strong>antipatterns </strong>and corresponding <strong>patterns </strong>on the topic of organisational agility, for organisations who want to deliver <a href="https://itrevolution.com/sooner-safer-happier/">Better Value Sooner Safer &amp; Happier</a>.</p><p>We are in a new Deployment Period in a 50 year cycle, in the Age of Digital, as <a href="https://www.strategy-business.com/article/Are-We-on-the-Verge-of-a-New-Golden-Age">well articulated</a> by Carlota Perez in ‘<a href="https://www.amazon.co.uk/Technological-Revolutions-Financial-Capital-Dynamics/dp/1843763311">Technological Revolutions and Financial Capital</a>’.</p><p>Today, for <a href="https://en.wikipedia.org/wiki/Cynefin_framework#Complex">complex </a>knowledge work, many large organisations are still applying a <a href="https://en.wikipedia.org/wiki/Scientific_management">management model from the early 1900s</a> optimised for manual labour in factories.</p><p>With new means of production and consumption, with on-demand compute, information and communication power which is in the cloud and in our pockets, if traditional organisations want to survive and thrive, want to keep up with competitors and challengers, there is a need to adopt new ways of working to maximise the outcomes from the new means of production.</p><h4>Survival is not mandatory</h4><p>This is of course optional, as survival is not mandatory, a path that UK department store <a href="https://www.theguardian.com/business/2019/apr/09/debenhams-is-taken-over-by-lenders-mike-ashley-loses-sta">Debenhams has taken</a>. Debenhams, founded in 1778, went into administration 241 years later, on 9th April 2019 with 165 stores and 25,000 employees. To quote Richard Lim, chief executive of industry analysts Retail Economics,</p><blockquote>“Put simply, the business has been outmanoeuvred by more nimble competitors, failed to embrace change and was left with a tiring proposition. The industry is evolving fast and it paid the ultimate price.” (<a href="https://www.theguardian.com/business/2019/apr/09/debenhams-is-taken-over-by-lenders-mike-ashley-loses-sta">source</a>).</blockquote><p>Time will tell if Debenhams is following in the footsteps of Toys R Us, Maplins, BHS, House of Fraser, HMV, Kodak, GM, Blockbuster, Nokia and Sears as firms who have chosen, implicitly, to not be a going concern either at all or in what was their core market.</p><h4>Takeaways</h4><p>This post focuses specifically on how organisations choose (implicitly or explicitly) what work to do and how it is approached, in the context of product development, as organisational agility increases or needs to increase.</p><p>A scenario often observed is that processes <em>upstream</em> of product development teams become the primary constraint to valuable flow, especially as product development teams increase their agility.</p><p>How do large, traditional, organisations make sure that teams are working on the best possible things as agility increases? Done badly, and anything can be done badly, it’s <em>fragile</em> rather than <em>agile</em>. As empowerment and autonomy are increased, the system of work could become chaotic and disconnected. Or, capital ‘A’ Agile is imposed with a culture of fear, with all change still having drop-dead predictive output milestones, waterfall dressed up as agile, which doesn’t maximise the benefits of agility.</p><p>First we take a look at four antipatterns: (1) <em>Local Optimisation &amp; the Urgency Paradox (2) Milestone Driven Predicted Solutions (3) Headless Chickens </em>and (4) <em>Start Starting</em>. Then we look at the corresponding pattern per antipattern, namely: (1) <em>End to End Flow (2) Outcome Hypotheses (3) Strategy Alignment </em>and <em>(4) Stop Starting, Start Finishing</em>.</p><p>These antipatterns and patterns are based on lessons learnt through doing, through learning, through running experiments (the only failed experiment is one which generates no learning. Even then that itself is a learning). This includes being a servant leader on better ways of working, applying agile, lean, DevOps, systems thinking and so on, across a large (80,000 people), old (300+ years old), global, not-born-agile, highly regulated enterprise. I have been delivering change with an agile mindset, principles and practices since the early 1990s, about a decade prior to the Agile Manifesto, when the term ‘lightweight processes’ was used. The antipatterns and patterns are also based on learnings from many horses (rather than unicorns) on similar journeys.</p><h3><strong>Antipattern 1: Local Optimisation &amp; the Urgency Paradox</strong></h3><p>The following scenario is a common one I’ve experienced, especially with business areas early in the journey to delivering Better Value Sooner Safer and Happier.</p><p>I had met with a software development team who were rightly proud of their progress with increasing their agility. The <strong>Team Outcome Lead</strong> (aka Scrum Master) showed me their improvement of Cycle Time, from the time work is pulled off the backlog to development done. It was an impressive improvement with the 85th percentile Cycle Time approximately halved from what it used to be 12 months previously. During this time the team had become multidisciplinary, limiting Work In Progress with more smaller stories, which had reduced complexity per change, de-risked delivery and led to faster feedback and learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fiw1pP9QxHXYr0oA" /></figure><p>However, something wasn’t quite right. The recipients of the change were complaining that they weren’t seeing the claimed benefits of agile. Things were taking just as long as before.</p><p>I asked what happened after development and testing was done to get the product into the hands of users. “<em>Well, we need to wait for integration testing because we’ve got lots of dependencies, we haven’t decoupled the architecture, and we’ve got three or four or five systems that all need to be deployed together. So we have to wait for integration</em>”.</p><p>Okay, so when you’ve done integration testing, are you then good? Are you then ready for production? “<em>Well, no, because we then have to wait for user acceptance testing</em>”.</p><p>Okay, fine, so you do your acceptance testing, and then anything else before you can then put that into production? “<em>Actually yes, because we batch up releases. So we have to wait for the release cadence, we have to wait for that to happen and for IT Ops to be happy to do the release.</em>”</p><p>Okay, is there anything else after that in order to reduce the time to market? “<em>No, after that, then we’re done</em>”.</p><p>And so then I’ll ask, okay, so what’s the cadence on this, what’s the frequency?. “<em>Well, integration testing is monthly, acceptance testing is quarterly, and releasing is quarterly</em>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TCSNWB2s2SHCZEk1" /></figure><p>I ask, to the left, prior to the work getting to the dev team what happens?</p><p>“<em>Well, prior to the work getting to the dev team there is a Product Backlog with epics which need to be refined, analysed and broken down into stories. In some other teams that work is predictively planned into multiple iterations over a quarter, with a focus on commitment of output, rather than experimenting to best achieve outcomes, which feels kind of traditional”.</em></p><p>“<em>Prior to that, a detailed design needs to be reviewed by the organisation-wide Technical Design Authority and before that there is a Detailed Business Case which needs to be completed for each programme or project, funding agreed and approved by a business line steering committee</em>“.</p><p>“<em>Before all of </em><strong><em>that </em></strong><em>there is an Outline Business Case approval step to filter the business cases going into Detailed Business Case review and ahead of that there is Idea Triage</em>”.</p><p>How often do these happen, I ask.</p><p>“<em>That’s a good question. It’s monthly for the Idea Triage, quarterly for the Outline Business Case and an annual planning process which typically takes 6 months to complete, using the Detailed Business Cases, which determines what programmes and projects we work on for the following calendar year. It’s always been this way, we start planning in September for the following year, with endless cycles of big up front planning and around March we know our level of funding, on the premise that it delivers the big up front plans, which by the end of the year are 18 months old. Usually there’s gaming of the system, going in high, knowing that it will be knocked back, usually ending up the same or just lower than last year</em>”.</p><p>However, when you speak to the dev teams they say:</p><blockquote>‘<strong>WE’RE SO FREAKING AGILE, YAY!</strong>”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ghN0dIKQzPeiTPSr" /><figcaption><em>“We’re so freaking Agile, yay!” (credit: </em><a href="https://www.amazon.co.uk/Rethinking-Agile-Nothing-Business-Agility/dp/3903205397"><em>Klaus Leopold</em></a><em>)</em></figcaption></figure><p>Software development teams can improve all they like, however the time from customer need identified to need met, the time to pivot based on a market event or learning, hasn’t materially reduced. Often I’ve heard recipients of change comment, quite rightly, that they have not seen an improvement in time to market.</p><blockquote>“A system of local optimums is not an optimum system”, Eli Goldratt, <a href="https://www.amazon.co.uk/Goal-Process-Ongoing-Improvement/dp/0566086654/ref=sr_1_1_twi_pap_1?ie=UTF8&amp;qid=1552153651&amp;sr=8-1&amp;keywords=the+goal">The Goal</a></blockquote><p>Delivery risk is lower with faster learning within development, however it might be the wrong thing being built. Time to learning, time to value, time to delighting customers, flow, has not materially changed end to end. This was a lesson learnt in manufacturing a long time ago. Don’t improve the performance of a non-bottleneck as it will stack up more inventory at the bottleneck and not improve end to end flow of value. There is, however, a human benefit in the local optimisation, where it is likely making working lives more humane and rewarding within the local optimisation, even if the overall human endeavour is not generating broader benefits.</p><p>What was also witnessed was an <strong>Urgency Paradox</strong> (Don Reinertsen &amp; Preston Smith, “Developing Products in Half the Time”). Valuable ideas sit in 12m to 18m of big up front planning with no sense of urgency, no questioning if they might add more value than what has already been locked in the plans for the year. As soon as they reach the product development team they are urgent. However, often by then the <a href="https://xprocess.blogspot.com/2016/04/understanding-cost-of-delay-and-its-use.html">Cost of Delay</a> profile has plateaued.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AGXu7TfIRPl8qTcR" /><figcaption><em>The Urgency Paradox</em></figcaption></figure><blockquote>As per Douglas Hubbard, author of “How to Measure Anything”, the most valuable data for investment decisions is (1) whether the product will be used at all and (2) how quickly it will be used. These two factors trump all other data, including expected cost (<a href="https://www.cio.com/article/2438748/the-it-measurement-inversion.html?page=2">source</a>).</blockquote><p>This adds further weight to the Urgency Paradox of not waiting one rotation of Earth around the Sun before deciding what to invest in for the next orbit. A lack of flow end to end and an inability to pivot reduces the probability that teams are working on the most valuable thing, both due to a lack of feedback and an inability to respond to a changing environment.</p><blockquote>Why wait one rotation of the Earth around the Sun before deciding what to invest in next?</blockquote><h3>Antipattern 2: Milestone Driven Predicted Solutions</h3><p>Traditionally, milestones in a Gantt chart focus human endeavour on activity completion, on output, predicted at the time of knowing the least, instead of continually thinking about how to maximise outcomes based on strategic intent and ever increasing knowledge of the landscape, in the context of unique product development.</p><p>“Have we achieved the activity”, rather than “What shall we do next, given what we’ve learnt so far, in order to try to best achieve the desired outcome”. The former is order-giver and order-taker with thinking put on hold. The latter requires everyone to use their brains.</p><blockquote>“Don’t mistake activity for achievement”, John Wooden</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*urQMBSbEmpPdSvsU9sYf9g.png" /></figure><p>Milestones are an unsuitable metaphor to use for unique product development (which is emergent), within organisations (which are emergent), to continually delight customers (who are emergent), in a landscape (you guessed it, which is emergent), where they are all changing faster than ever. The metaphor, in this context, traditionally has been overloaded to predict distance (work done), the quality of the destination and time.</p><p>Add in managers vs. workers, business vs. IT, low psychological safety with fear, blame and reprisals, individual incentivisation over team incentivisation, tribal identity by task based job role and not surprisingly, success is low at 29% (Standish Group, 2015, <a href="https://standishgroup.com/sample_research_files/CHAOSReport2015-Final.pdf">source</a>) and employee engagement, while rising, is low with 34% of people actively engaged, 53% not engaged and 13% are actively disengaged (Gallup, 2018, <a href="https://news.gallup.com/poll/241649/employee-engagement-rise.aspx">source</a>). The Standish Group survey also reports that an agile approach is four times more successful than a waterfall approach.</p><p>This is not to say that fixed dates don’t exist, they do. More on this later. Specifically, the word and metaphor of “milestone” is sub-optimal, perpetuating old behaviours and outdated ways of thinking for unique change.</p><p>I’ve often heard milestones being referred to as ‘drop dead dates’. With a long lead time, big bang, traditional approach, the activities to reach the drop dead date have at times been called a ‘death march’. Indeed, the term <strong><em>deadline</em></strong> has its origins from prisoner of war camps in the American Civil War in 1864, where the ‘dead line’ was literally a railing or a ditch which if crossed would result in death.</p><p>In one organisation I worked at, project managers set <em>deadlines, </em>fixed output milestones, in advance, without consulting those doing the work, at the point of knowing the least. There was big batch, feast to famine work passing by role, with finger pointing. The <em>deadlines</em> never moved. During the ‘feast’ phase of work per role, people were working unsustainably. I asked some of the people why they were still working there. The answer I got, said seriously: “<em>We are united through a common suffering</em>”. A form of organisational Stockholm Syndrome. An undercurrent of do this thing by this date or die. How’s that for colleague engagement and satisfaction at work?</p><p>In the Age of Digital, with a new means of production, with a rapidly changing terrain, there are better ways of working, if an organisation wants better outcomes. This is of course optional. Surviving and thriving is not mandatory.</p><h3><strong>Antipattern 3: Headless Chickens</strong></h3><p>In this scenario, product development teams have adopted agile ways of working and have become a <strong><em>Feature Factory</em></strong> churning out stuff, disconnected to company strategy and typically incentivised by activity or output (e.g. velocity, Say Do ratio, commitment), rather than by Outcomes. Teams become a self-fulfilling prophecy of backlog replenishment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d6RgOnp6HWpb2Khy" /><figcaption><em>Teams are disconnected from strategic intent, yet continue producing stuff</em></figcaption></figure><p>This could be because there is a lack of flow coming from upstream, as the PMO, portfolio management, investment case approval and technical design authority processes are big batch and infrequent.</p><p>It could be due to a lack of clear strategic alignment, a lack of clear North Star, no link between the work being done and strategic goals. There is low alignment and high autonomy, resulting in brownian motion.</p><p>It could also be due to disconnect from the customer, a lack of seeking or responding to feedback. A behaviour I’ve observed is Product Owners (especially new POs who used to be project managers) being so focussed on ‘I <strong>OWN </strong>this Product’ that they forget to speak to the customer and understand what might be most valuable for them.</p><p>As an aside, to help address this point, we’ve been experimenting with renaming the Product Owner role to <strong><em>Stakeholder Outcome Lead</em></strong>, to make the self identity more clear. The Stakeholder Outcome Lead is a servant leader focussed on the <strong>What</strong>, an outward focus on the customer, economic, societal and environmental outcomes (<strong>Value</strong>. See <a href="https://en.wikipedia.org/wiki/Triple_bottom_line">Triple Bottom Line</a> and this significant <a href="https://www.businessroundtable.org/business-roundtable-redefines-the-purpose-of-a-corporation-to-promote-an-economy-that-serves-all-americans">statement</a> from the Business Roundtable signed August 2019 by 181 US CEOs, moving away from short-term shareholder primacy to all stakeholders, including society and the environment). This complements the <strong><em>Team Outcome Lead</em></strong> (aka Scrum Master in Scrum) who is a servant leader with an inward focus on the <strong>How </strong>and building the muscle of continuous improvement as a daily habit practiced by everyone (<strong>Better Sooner Safer Happier</strong>).</p><p>Another possible reason for this anti pattern of teams churning out stuff agnostic of strategy, feedback or value, is a traditional mindset around resource utilisation with a view that people need to always be busy, leading to overproduction in siloes, rather than coming together, swarming and helping to alleviate the constraints of a lack of flow and strategy alignment, coming from upstream.</p><blockquote>“An [operation] in which everyone is working all the time is very inefficient”, Eli Goldratt</blockquote><p>If there is a traditional mindset around resource utilisation, with a desire for people to always be busy, this will have the opposite effect to that desired, in that Lead Time <em>rises exponentially</em> as utilisation increases in a system of work with variability, as is the case with product development. There is no time for continuous improvement, for resolving impediments, for reflecting, for pivoting, for swarming and the system of work goes slower. People are fully occupied pushing the square wheels. For a great online simulation of the effect of utilisation on lead time, see Troy Magennis’s interactive article <a href="https://observablehq.com/@troymagennis/how-does-utilization-impact-lead-time-of-work?collection=@troymagennis/agile-software-development">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/0*8xaKB-rf84xMeLKm" /></figure><h3><strong>Antipattern 4: Start starting</strong></h3><p>In this antipattern, organisations keep on ‘<em>start starting</em>’ instead of ‘<em>stop starting, start finishing</em>’. This is like adding more cars to an already busy motorway, the cars go slower.</p><p>Blissfully unaware of the capacity of the system of work and treating it as a push based rather than pull based system, organisations keep on starting more initiatives, more projects, saying yes to customers or stakeholders demands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L849Gtjc2GaY75nW" /><figcaption><em>Start starting</em></figcaption></figure><p>In one specific case, an area was saying yes to twice as many requests from an internal customer, than the natural capacity of the system of work, such that each month the backlog of committed work grew by another month. Applying traditional thinking, the focus was on SLAs at each sequential stage and people incentivised to work harder to meet the SLA, a series of local optimisations, pushing work and actually making the end to end lead time longer by having unlimited work in progress, building up queues at each stage.</p><p>The result in this context was an acceptance by the recipients of change that things take a long time to get done, driving a desire to start more things otherwise they’ll never get done (‘the best time to plant a tree is 20 years ago, the second best time is now’), an us and them behavioural norm and growing piles of invisible inventory. This results in lower quality as people try to work harder rather than smarter to meet local optimisation SLAs, and lower engagement. It’s a no win situation with a lack of awareness of the system of work.</p><p>The most important measures for teams, and teams of teams, to know are their Flow measures: Lead Time, Work In Progress, Throughput and Flow Efficiency. This determines the health of the system of work. For more on this see <a href="https://medium.com/sooner-safer-happier/know-your-flow-a436eb7c8af">Know Your Flow</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YWDbzbQwYQiziBQL" /></figure><h3><strong>Pattern 1: End to end Flow</strong></h3><p>Where the antipattern is local optimisation, the pattern is to focus on end to end flow, looking at the whole system of work.</p><p>First, identify long lived value streams. A value stream is producing something which is of value to one or more internal and or external customers, going from needs identified to needs met. It is why you are doing what you are doing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BGrihpjZ8Rez9X__" /></figure><p>It is likely that the organisational structure of the business is already set up as value streams, for example, mortgages, savings, investments, health insurance, travel insurance, luxury bags, jet engines, helicopter engines, renewable energy generation, immigration, recruitment, finance, internal audit and so on. Key is that a value stream should be end to end and ideally with as few dependencies as possible. That is, the value stream should have high cohesion and low coupling. Importantly, value streams are <strong><em>nested</em></strong>. For example, Bank ➜ Investment Bank ➜ Capital Markets ➜ Trading ➜ Equities ➜ Market Making.</p><p>Value Streams are represented horizontally, with a logical flow of value from left to right, from need identified to need met, from hypothesis to validated learning. Value streams have a quality of service.</p><p>Personas (e.g. young person, family, retired couple) are not Value Streams. They consume the Value Streams. Organising by persona can lead to duplication of the actual value production. Personas are a facade, a specific way of serving up the value streams aligned to the customer segment.</p><p>Customer journeys (e.g. sign up, onboard, search, purchase, renew, query, close) are also not value streams, as whilst some customer journeys are specific to a value stream, other customer journeys straddle multiple value streams (where, again, a value stream is the reason you’re in business, e.g. transport, fashion, financial services, energy, insurance and so on). Customer journeys are an action, or an operation, on one or more value streams. For example, when I become a customer of bank, I might want to open a current account, a tax-free index tracker investment account, a credit card, a business account and take out travel insurance. Whilst the experience of account opening is important, the <em>raison d’etre</em> of an organisation is unlikely to be having the best new customer on-boarding process, and then having low quality, long lead times and a lack of innovation for the value propositions themselves, which are the reason I became a customer in the first place.</p><p>The primary alignment is <em>value</em> (the reason you’re in business)<em>, </em>with customer journeys serving up that value. The serving up of the value is enabled via distribution channels (e.g. mobile, web, mail, phone, store), which implement the customer journeys, optionally aligned to persona. There is a ‘business oriented architecture’, with most people organised around customer need and customer value and a smaller percentage of people focused on how that is served up via the distribution channels. In the Age of Digital that value can be (or in the case of regulation such as the Payment Services Directive 2 (PSD2) in Europe, has to be) served up via each value stream having APIs (Application Programming Interfaces). This is relevant in the context where the customer journey can be automated, for example, the transfer of money from one account to another account, or the online purchase of ‘vanilla’ insurance.</p><p>In addition, rebadging existing role based teams, fiefdoms and calling them Value Streams, are likely also not Value Streams.</p><p>Value Stream Mapping is a technique which can be used to shine a light on the steps involved in the end to end value creation flow, including wait time vs. value adding time. This provides a Flow Efficiency measure. For most large organisations, Flow Efficiency for knowledge work is very low at around 10%, which means that work is waiting 90% of the time.</p><p>The value streams should be as self contained as possible, with dependencies eliminated or mitigated over time, part of a network of interdependent services. This won’t be the case at the beginning, there will likely be many dependencies. Spend time breaking dependencies rather than just managing them. Ways to do this for software products include shared code ownership, internal open source, service virtualisation and breaking monolithic balls of mud into microservices.</p><p>In my experience typically 80% of value streams are customer facing and 20% are internal shared services, for example HR and Finance.</p><h4><strong>Long Lived Products</strong></h4><p>Having identified the value streams that enable the organisation to economically, socially and environmentally serve its purpose, next, map long lived products to the long lived value streams.</p><p>These products are often IT systems. For example an Equities Trading System which enables the Equities Market Making value stream, or an HR system which supports the onboarding of new employees, or a smartphone app which enables management of personal finances or to shop online or to publish a photo of your lunch. The mapping of IT products to value stream shines a light on duplication of systems and eases simplification and decommissioning efforts.</p><p>It also shines a light on big monolithic IT systems which straddle multiple value streams and inhibit agility due to in-built hard dependencies. In some cases, the mapping of products to value streams leads to an organisation actually having a product inventory for the first time.</p><h4><strong>Long Lived Teams</strong></h4><p>The long lived value streams should have long lived small (&lt;10 people) multi-disciplinary teams on them. This results in teams going through forming, storming, norming, performing (Tuckman) and staying together, unlike temporal project teams. The teams get to understand the unarticulated needs of the customers. The multidisciplinary nature of the teams means that most of the time they have all the skills necessary to deliver end to end value. Team members are ‘T-shaped” generalising specialists. This minimises dependencies on individuals and other teams and hence enables flow, fast feedback and learning. It should not require multiple teams to get value to production, early and often.</p><p>The alignment of long lived teams to long lived value streams, creates a tribal identity around the value stream, away from a tribal identity of ‘I’m business’ or ‘I’m IT’ or by job role. Instead ‘we are mortgages’ or ‘we are luxury bags’ or ‘we are helicopter engines’. The nature of the organisation of human endeavour has people working <em>together</em> daily to iterate towards common business outcome hypotheses.</p><h4><strong>Funding</strong></h4><p>Funding is aligned to the value streams. Each value stream, with long lived teams, is capacity funded. <em>Funding is a constraint on which to maximise the value curve</em>. For knowledge work, the main cost for value streams are people, who are aligned to value streams. Funding is value stream aligned, with a rolling roadmap of value outcome hypotheses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OdG8JTsG4qIRbMs9" /><figcaption>Long lived Value Streams with long lived multidisciplinary teams . Value Streams are funded.</figcaption></figure><h3><strong>Pattern 2: Outcomes Hypotheses</strong></h3><blockquote>“It’s better to do the right thing wrong than the wrong thing right. The righter you do the wrong thing the wronger you become”, Russell Ackoff (<a href="https://www.youtube.com/watch?time_continue=50&amp;v=MzS5V5-0VsA">source</a>)</blockquote><p>Where the antipattern is big up front milestone driven predicted solutions, the pattern is to focus on outcome hypotheses with experimentation. From deterministic output to outcome hypotheses.</p><h4>Emergence</h4><p>We can’t travel in time, product development is emergent, it is unknowable, what people want, how it’s going to be built, what obstacles we’ll come across on the way and how external market forces will change over time. Acting in the space, changes the space. The North Star should not be a fixed <em>solution</em> or <em>output </em>by a date. It is not a knowable straight path from A (current condition) to B (desired outcome). The bigger the distance from A to B is, the less knowable the journey is. It is beyond our knowledge threshold. A traditional approach is placing a fixed bet at the beginning of the race when the least is known.</p><p>Instead it is a wiggly journey from A to B, optimised with fast, real, feedback and learning, with safe to fail experiments, in order to test the Outcome Hypothesis. For unique work, we want to maximise variability and run multiple experiments, maximising learning, early and often. This approach enables changing bets on the race while the race is running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*9KkiL91spyuNXEz-" /><figcaption>Toyota Improvement Kata, Mike Rother</figcaption></figure><h4>Outcomes</h4><p>The outcomes are <strong><em>nested</em></strong>, at multiple cadences. Daily, weekly, monthly, quarterly, yearly, multi-year. The key focus is the quarterly Business Outcome (also known as an <a href="https://en.wikipedia.org/wiki/OKR">OKR</a>). A three month time period is not too close and not too far away. This is broken down into monthly Features, which are experiments to test the hypothesis. These are in turn broken down into Stories which are daily and optionally into hourly Tasks. Therefore there is learning and innovating many times a day, on the desired outcome hypothesis.</p><p>The Business Outcome hypothesis is written along the lines of the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*IYsFhpvrQqH62IXVvJfxzg.png" /></figure><p>Each quarterly Business Outcomes has a Portfolio Epic parent, a higher level North Star outcome hypothesis. Each business area has a handful of Portfolio Epics, limiting work in progress. This is strategy alignment. The &lt;12 month Portfolio Epics are nested within multi-year Portfolio Objectives, which are business unit level strategic items. And for larger firms, they are contained within a handful of Strategic Objectives which is the top, group-level, strategic intent, spanning all business units.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k3NipIRvEODLZv0A" /></figure><p>The nested Outcomes are represented vertically, from multi-year strategic intent down to daily stories. Typically each level has its own Kanban board, with WIP being limited at all levels.</p><p>Value, which is unique and not aggregatable, is expressed in the Lagging Value Measures. It is important that these are measurable, that they are quantitative.</p><h4>Example</h4><p>A multi-year Portfolio Objective might be a hypothesis to be in the top 3 of market share for credit card providers, in order to reverse a decline in market share, to increase profitability, to keep people in gainful employment and to help more people with responsible financial liquidity. An in-year Portfolio Epic might be a hypothesis to launch a partner card with an airline, in order to increase market share. A quarterly Business Outcome might be a hypothesis that issuing one partner credit card, to at least one customer and using it for at least one transaction end-to-end, in a live environment, will de-risk delivery, enable fast learning in a safe to fail environment, and will result in delighted customers, hence helping to increase market share. The approach is outcome-oriented, in business language (not IT activities), with real feedback and learning and the ability to pivot.</p><p>Rather than eat the elephant in one go, aim for <em>elephant carpaccio</em>, try to get the thinnest vertical slice of real value, to maximise learning and making it safe to fail, which is necessary in order to learn.</p><blockquote>Elephant carpaccio, over eating the elephant whole</blockquote><p>The key shift in paradigm here, is moving to being able to pivot to maximise the desired outcome bet, changing the bet mid race, either because the hypothesis is not valid or to be able to ‘<em>cut the tail</em>’ when it appears that the high value, low effort features have been implemented.</p><h4>Rolling roadmap of outcome hypotheses</h4><p>Also, importantly, it is a rolling roadmap of outcome hypotheses. More fine-grained up close and more coarse-grained further out, with a logarithmic scale. For example, the current Quarter, Quarter+1, 6 months. A great example of this is from the GOV.UK experiments in roadmapping <a href="https://www.mindtheproduct.com/2014/07/experiments-roadmapping-gov-uk/">here</a>, where they intentionally picked a curved glass partition, so that the future is out of view, they literally can’t see what’s around the corner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/0*JnusGzxK6xqrWMId" /></figure><p>With multiple nested cadences, daily, weekly, monthly, quarterly there are actionable learning loops. This way, multi year strategic intent is getting daily feedback. And, those who are closest to the customer, to the detail, closest to understanding unarticulated needs, are able to see clearly the strategic intent and are best placed to innovate.</p><h4>Dealing with fixed scope and fixed dates</h4><p>Don’t artificially lock in a fixed date, if it doesn’t need to be fixed. Don’t back yourself into a corner unnecessarily. I’ve seen many cases of leaders insisting on fixed output with fixed dates unnecessarily, which limits the ability to respond to learning, in order to best achieve the desired outcomes. Outcomes, which are quarterly, defacto have a date. The ninja move here is to define the <em>Outcome</em> not the <em>Output</em>. This is synonymous with the move from detailed command to <a href="https://en.wikipedia.org/wiki/Mission_command">mission command</a> in the military.</p><p>There are cases where there are fixed dates with fixed scope, such as mandatory regulatory change. Examples of this include GDPR and the Dodd-Frank legislation after the 2008 credit crisis. Having implemented many regulatory initiatives pre and post 2008, all fixed date and fixed scope, all of them agile, all completed early, even if you think that the scope is fixed, in reality legislation is usually written in a way which enables near infinite ways to implement it.</p><p>Also, even if you think the rule writing is fixed, it may not be. For example, around 2012, we implemented the most risky, least understood bit of the UK version of the Dodd-Frank legislation within the first month, tested it with production data, got insights back, took those insights to the Bank of England, who updated the legislation as it would have put the UK at a competitive disadvantage to other financial centres globally.</p><p>A waterfall approach with value and learning delayed to the end, is far too risky an approach for fixed date, fixed scope work. Everything should be done to remove ignorance, to maximise early and often learning, with the most time to act on it.</p><h4><strong>From PMO to Value Enablement Team</strong></h4><p>The role of the traditional Project Management Office (PMO) changes in the pivot from temporal projects to long lived products with long lived teams and a rolling cadence of outcome hypotheses. The pivot is to become more of a servant leader team with a focus on the <strong>Value </strong>part of <em>Better </em><strong><em>Value</em></strong><em> Sooner Safer Happier</em>, in particular the Lagging Value Measures which are on each quarterly Business Outcome. To make the change in identity clear, it can help to rename the team. For example <em>Value Enablement Team (VET)</em> or <em>Value Realisation Office</em>. The VET coaches teams in articulating and measuring Business Outcomes, gathers the Leading and Lagging Measure data together and provides consolidated data for a monthly cadence with senior leaders to inspect &amp; adapt on the quarterly and annual outcome hypotheses. More on this in this talk <a href="https://youtu.be/R-fol1vkPlM">here</a>.</p><h3><strong>Pattern 3: Strategy Alignment</strong></h3><p>Where the antipattern is headless chickens, teams producing output disconnected from the strategy, the pattern is strategy alignment, by bringing together the horizontal nested value streams with the vertical nested outcome hierarchy.</p><p>Each long lived team, on a long lived value stream, with long lived products have clear Business Outcomes hypotheses to work on, with clear lineage up to the top handful of Strategic Objectives.</p><p>This enables High Alignment (clear nested North Star outcomes) with High Autonomy (the multi-disciplinary teams empowered to use their own brains and mastery to achieve the nested North Stars).</p><p>There is strategy alignment and the Business Outcome value metrics articulate value realisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RVHk9b5s9ErW1pja" /></figure><p>With a tribal identity of the value that is being produced, with multi-disciplinary teams (business, IT, finance, compliance, etc.), there is a shared purpose, clear outcome bets, written in business language, to experiment on. In my experience, this really starts to remove the behavioural boundary that traditionally-organised companies have between ‘the business’ and ‘IT’ due to the previous order-giver, order-taker ways of working. Instead people work together, as a team, to achieve and test desired outcomes. The ‘tribe’ becomes the value stream rather than by job role.</p><p>No longer are there headless chickens, where agile teams are disconnected from strategic intent, being a self-fulfilling feature factories. Instead, there is clear strategic alignment, with two-way strategy, down and back up. Strategy with rapid testing and learning. This two-way strategy in Japan is known as ‘<a href="https://www.leanproduction.com/hoshin-kanri.html">Hoshin Kanri</a>’. Traditionally Western firms have practiced one way strategy, top down.</p><h3><strong>Pattern 4: Stop Starting, Start Finishing</strong></h3><p>Having organised the horizontal long lived nested value streams with long lived teams and the vertical outcomes, running at multiple nested cadences, the next thing to do, in order to reduce Lead Time, the time to learning, the time to market, and to increase flow efficiency is to <strong>Stop Starting and Start Finishing</strong>, instead of Start Starting.</p><p>Doing less work concurrently and ensuring that people are less than 80% allocated (see antipattern 2), significantly reduces the lead time, the time to value, learning, de-risking, pivoting, avoiding sunk cost and allows time to improve the system of work.</p><blockquote>Go slower to go faster. Or you will end up going slower.</blockquote><p>This is analogous to cars on a motorway. The more cars, the slower they go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*cxQZDlUfAt-fo3sM" /></figure><p>Reducing Work In Progress (WIP) is a forcing function, an enabling constraint. As less work is done in parallel with shorter lead times, it shines a light on the impediments to flow. If an item of value is blocked and cannot progress, the team do not park it, instead they swarm on it, to clear the blocker. This means that the system of work is permanently improved. Like the tide going down, you see the rocks and shopping trolleys, the impediments to flow efficiency, that were always there, just not visible previously.</p><blockquote>Impediments are not in the path. Impediments ARE the path.</blockquote><p>Work in Progress should be limited at all levels in the Outcome Hierarchy.</p><h4><strong>Visualise</strong></h4><p>Information should be radiated. Ideally, there should be one or more Enterprise Visibility Rooms (EVR). Here the system of work is made visible. Very quickly, too much WIP and blocked items become visible. The previously invisible system of work for knowledge work becomes visible. Often, it’s the first time that people have actually seen the full end to end value stream. There may be multiple kanban boards, representing the multiple cadences (multi year, year, quarter, month, daily) along with Cumulative Flow Diagrams which is an incredibly insightful visualisation.</p><h4><strong>Pull based over Push based</strong></h4><p>In line with ‘Stop Starting, Start Finishing’, an Outcome, Feature or Story is not pulled until another one has been done. This results in the system of work becoming a pull based system, rather than a push based system. Every system of work has a natural capacity. By being a pull based system of work, the work flows at the capacity of the system, the natural capacity of the system of work can be identified and then improved.</p><blockquote>Focus on the work not the workers</blockquote><h3>Pattern Summary: Nested Value Streams with Nested Outcomes</h3><blockquote>From by Role to by Value</blockquote><blockquote>From temporal Projects to rolling Outcome Hypotheses</blockquote><h4>Focus on the whole system of work, the whole value stream network.</h4><p>The whole organisation is in scope, <a href="https://medium.com/sooner-safer-happier/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">starting small</a>. There are small, multi-disciplinary, long lived teams, aligned to long lived, nested, value streams, with autonomy, psychological safety and support in experimenting to achieve the nested outcome hypotheses. The tribal identity is to the value stream (e.g. Mortgages, equity trading, cloud provisioning, payments, luxury bags, taxi dispatch, customer sign up, etc.) bringing together many roles with a common purpose and working as a team, not an alignment by job role with work passing.</p><blockquote>Outcome oriented teams focus on maximising outcomes</blockquote><blockquote>Project oriented teams focus on predetermined output</blockquote><h4><strong>Focus on Outcome hypotheses, nested North Stars.</strong></h4><p>Multi-year, yearly and quarterly outcome hypotheses. There is a clear strategic intent with autonomy in how to best achieve it. The focus of human endeavour becomes experimenting and learning to achieve the desired outcomes, working as multidisciplinary teams, with a capability to pivot based on fast feedback.</p><blockquote>Outcome hypotheses over predictive solutions</blockquote><h3>Summary</h3><ol><li>End to end Flow over Local Optimisation : nested horizontal Value Streams</li><li>Outcome Hypotheses over Predictive Milestones : nested vertical Outcomes</li><li>Strategy Alignment over Headless Chickens : the intersection of both</li><li>Stop Starting, Start Finishing over Start Starting : limit WIP at all levels</li></ol><p>This requires experimentation. Experimentation requires psychological safety.</p><p>How to start?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/179/1*2q4I6ZcgFH9KHOvkPezxWw.png" /></figure><p>Start <a href="https://medium.com/sooner-safer-happier/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">small</a>. Learn Fast. ‘S’ curve adoption, by <a href="https://medium.com/sooner-safer-happier/organisational-agility-give-people-a-voice-5d5e68449aa7">invitation</a>.</p><h4>See also</h4><ul><li><a href="https://youtu.be/R-fol1vkPlM">The PMO is dead, long live the PMO</a></li><li><a href="https://youtu.be/ZKrhdyjGoM8">Better Value Sooner Safer Happier</a></li></ul><h4>Book</h4><ul><li><a href="https://itrevolution.com/sooner-safer-happier/">Sooner Safer Happier</a></li></ul><h4>Blogs</h4><ul><li><a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> (Medium.com)</li></ul><h4>Talks</h4><ul><li><a href="https://www.youtube.com/playlist?list=PL8L2SDNuMGpsn2JUapVsyRnwicLAmODvA">Sooner Safer Happier</a> (YouTube)</li></ul><h4>Acknowledgements</h4><p>Thanks to Zsolt Berend, Mike Burrows, Scott Carberry, Jason Cox, Dominica Degrandis, Klaus Leopold, Troy Magennis, Myles Ogilvie and Simon Rohrer for feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69d316aeb56b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/agility-build-the-right-thing-69d316aeb56b">Agility: Build the right thing</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus is it a Unicorn?]]></title>
            <link>https://medium.com/sooner-safer-happier/focus-is-it-a-unicorn-5458801316a3?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/5458801316a3</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[neuroscience]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[flow]]></category>
            <category><![CDATA[focus]]></category>
            <dc:creator><![CDATA[zsolt berend]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 20:53:50 GMT</pubDate>
            <atom:updated>2019-01-07T20:53:50.744Z</atom:updated>
            <content:encoded><![CDATA[<h3>Focus: is it a Unicorn?</h3><p>Co-author: <a href="https://medium.com/@tonycaink">Tony Caink</a></p><p>Focus is hard enough as an individual, even harder in a team of brilliant minds. Why is it so hard?</p><p>Based on the study lead by Gloria Mark (at the University of California, Irvine) the bad news is that on average it takes <a href="https://www.fastcompany.com/944128/worker-interrupted-cost-task-switching"><strong>23 minutes and 15 seconds </strong>to regain focus after switching to a new task</a>. So now think about having not only one but multiple context switches in a work day, which is far from being unusual: the cost is just too high to ignore and yet we keep context switching, trying to multitask.</p><p>So why are we doing it?</p><p>Shockingly enough, neuroscientists suggest that our own brain actually works against us: it rewards the wrong behaviour.</p><p>As the studies point out, multitasking is supported by a dopamine-addiction feedback loop, effectively <strong>rewarding </strong>the brain <strong>for losing focus</strong>. Daniel J Levitin writes about how <a href="https://www.theguardian.com/science/2015/jan/18/modern-world-bad-for-brain-daniel-j-levitin-organized-mind-information-overload">our brains have a <strong>novelty bias</strong></a>, meaning our attention can be easily distracted. This is also referred to as the “<strong>bright shiny object syndrome</strong>”</p><p>I was in Richmond Park taking this photo early morning just around sunrise. If you have never been, or not heard about this park, this is home of hundreds of magnificent free living deer. So I am there and witnessing a beautiful stag eating the grass and quickly abandoning it when our shiny, type G2 star rose above the horizon. The good news is that sapiens are not alone, stags are also suffering from bright shiny object syndrome :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pIUJiY8Q9hJ8ihNSMx72GA.jpeg" /><figcaption>photo copyright: zsolt berend</figcaption></figure><p>We also suffer of what’s called the “<strong>busy trap</strong>” of nowadays corporate culture. We <strong>glorify “busyness”</strong>: when you ask your colleague how are they doing, how is work, you most probably will get the answer of “busy”, “crazy busy” and the default response we give is <a href="https://opinionator.blogs.nytimes.com/2012/06/30/the-busy-trap/">“good to be busy”, “good problem to have”</a>. This is a legacy of 19th century <a href="https://en.wikipedia.org/wiki/Scientific_management">Taylorism</a> when there was a linear, direct correlation between “busyness” and productivity which is unfortunately still applied in the knowledge workers’ world. Also, it is worth considering the correlation between wait time and utilisation which is best described in <a href="https://www.amazon.co.uk/Phoenix-Project-Devops-Helping-Business/dp/1942788290/ref=sr_1_1?ie=UTF8&amp;qid=1544440544&amp;sr=8-1&amp;keywords=phoenix+project">The Phoenix Project</a>. When the utilization (busyness) goes past 80%, the wait time runs to the roof.</p><h4>Hacking the brain to reward the right behaviour</h4><p>So how do we hack our brain to help ourselves and the team to turn our days into productive days as oppose to just busy days?</p><p><strong><em>1. Stop glorifying busyness, avoid the busy trap</em></strong></p><p><em>Know your biorhythms</em></p><p><a href="https://hbr.org/2007/10/manage-your-energy-not-your-time">Pay attention to your biorhythms (chronobiology)</a>. Keep balance between activity and being idle e.g. 90 min followed by 20 min. This is when you can have a coffee with Tony and think about whether focus is a unicorn or while you are idle dreaming discover the nuclear chain reaction like Leo Szilard did when the traffic light changed to green and<a href="https://nucleardreams.wordpress.com/2007/11/05/the-traffic-light/"> he stepped off the curb at the British Museum on September 12, 1933</a> and the rest is history.</p><p>You can define time slots of no interrupt, deep work as part of the team charter, and agreed signals like headphones. Carl Newport lists many creative practices in his book, <a href="http://calnewport.com/books/deep-work/">Deep Work</a>.</p><p><em>Introduce slack time</em></p><p>Introducing slack not only prevents the problem of too much utilisation (above) but unleashes creativity and innovation. Tom DeMarco, in his book <a href="https://www.amazon.co.uk/Slack-Getting-Burnout-Busywork-Efficiency/dp/0767907698">Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency</a>, makes the point that business kills innovation.</p><p><strong><em>2. Install transparency</em></strong></p><p>Visualize all things the team is working on, <a href="https://en.wikipedia.org/wiki/Kanban_board">use simple boards</a>.</p><p><em>Walk the board</em></p><p>Focus on the work not on the individual. Ask why an item is stuck on the board, who can you help, who can you pair up with, swarm to move the item to DONE. Alistair Cockburn defines product development, quite rightly as a <a href="https://www.infoq.com/news/agile-software-cockburn-book-2ed">“cooperative game.”</a></p><p><em>Stop starting…</em></p><p>To keep yourself and the team focused introduce limit the work in progress.</p><p>When pulling new work run through the decision tree first: “should I start this story”, “the story has value (a customer wants it)”, “the story is clear enough to work on (ready)”, “the system has (we have) capacity”. If any answers are No, then just say No. Stop starting.</p><p><em>…and start finishing</em></p><p>By finishing work you get two rewards: “getting things done” and “thank yous”. Communicating your results (whether they are positive or negative) means that others will recognise your work, resulting in more positive feedback. Praising and recognising the work of your colleagues can also increase your dopamine!</p><p>Dominica DeGrandis in her book <a href="https://www.infoq.com/articles/making-work-visible-book-review-interview-dominica-degrandis">Making Work Visible: Exposing Time Theft to Optimize Work &amp; Flow</a> talks about the problem with too much Work in Process (WIP), the negative impact on flow by not finishing or only partially finishing items and starting new ones.</p><p><strong>3. <em>Set objectives at team level</em></strong></p><p>Establish team level objectives instead of individual ones. Reject work that does not contribute to team objectives. Seek the big reward that comes from sustained, focused effort instead of empty rewards. Focus on how great you will feel when your project is complete. A study of the <a href="https://www.entrepreneur.com/article/306204">University of Michigan professors found that results-driven focus motivated people</a> to complete their work.</p><p><strong>4. <em>Install Learning</em></strong></p><p>Articulate business objectives and outcomes with measures, build in learning capabilities. Leading indicators provide feedback, helps you tell whether you are delivering the right thing and helps you to sustain focus. Build measure learn.</p><p>Will you create a system to reward progress and real rewards or will you let bright shiny object syndrome destroy your productivity?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5458801316a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/focus-is-it-a-unicorn-5458801316a3">Focus is it a Unicorn?</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organisational Agility: Give People a VOICE]]></title>
            <link>https://medium.com/sooner-safer-happier/organisational-agility-give-people-a-voice-5d5e68449aa7?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d5e68449aa7</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Jonathan Smart]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 18:21:21 GMT</pubDate>
            <atom:updated>2022-09-23T14:42:41.137Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Don’t Mandate One Way™.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TdPg0PTsRuFh-hwF" /><figcaption>Photo by <a href="https://unsplash.com/@aaronburden?utm_source=medium&amp;utm_medium=referral">Aaron Burden</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>“You are special, you are a beautiful and unique snowflake”</blockquote><p>You are, your team is and so are the complex adaptive systems that you are part of.</p><p>This is the third article in a series, sharing a number of observed <strong>antipatterns </strong>and corresponding <strong>patterns </strong>on the topic of organisational agility.</p><p>We are entering a new Deployment Period in a 50 year cycle, in the Age of Digital, as <a href="https://www.strategy-business.com/article/Are-We-on-the-Verge-of-a-New-Golden-Age">well articulated</a> by Carlota Perez in ‘<a href="https://www.amazon.co.uk/Technological-Revolutions-Financial-Capital-Dynamics/dp/1843763311">Technological Revolutions and Financial Capital</a>’.</p><p>Traditional organisations need to adopt new ways of working in order to survive and thrive, to leverage the on-demand compute, information and communication power which is in the cloud and in our pockets, to keep up with competitors and challengers, and to delight customers. Today, for <a href="https://en.wikipedia.org/wiki/Cynefin_framework#Complex">complex </a>knowledge work, many are still applying a <a href="https://en.wikipedia.org/wiki/Scientific_management">management model from the early 1900s</a> optimised for manual labour in factories.</p><p>The antipatterns and patterns are based on lessons learnt through doing, including learning from failing. We have been servant leaders on better ways of working, applying agile, lean, DevOps, design thinking, systems thinking and so on, across a large (80,000 people), old (300+ years old), global, not-born-agile, highly regulated enterprise. I have been delivering change with an agile mindset, principles and practices since the early 1990s, about a decade prior to the Agile Manifesto, when the term ‘lightweight processes’ was used. The antipatterns and patterns are also based on learnings from the community, from other horses, rather than unicorns, on similar journeys.</p><h3>Antipattern: Golden Hammer</h3><p>The mandating of one set of prescriptive practices, organisation-wide, is often combined with the <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">capital A Agile</a> and <a href="https://medium.com/@jonathansmart1/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">capital T Transformation</a> antipatterns. The <a href="https://en.wikipedia.org/wiki/Law_of_the_instrument">Golden Hammer</a> antipattern was summed up by Abraham Maslow in 1966 who said, “<em>I suppose it is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail</em>”. Herein lie two antipatterns: (1) Golden and (2) Hammer.</p><h4>Antipattern part 1: Golden</h4><p>Mandating any one set of practices on people and teams is an antipattern.</p><blockquote>“Imposing a process on a team is completely opposed to the principles of agile, and has been since its inception. A team should choose its own process — one that suits the people and context in which they work. Imposing an agile process from the outside strips the team of the self-determination which is at the heart of agile thinking. Not only should a team choose their own process, the team should be in control of how that process evolves.”, Martin Fowler, 2006 (<a href="https://martinfowler.com/bliki/AgileImposition.html">source</a>)</blockquote><p>The <a href="http://agilemanifesto.org/">Agile Manifesto</a> emphasises individuals and interactions over processes and tools, collaboration over contract negotiation, motivated individuals who are given support and trusted to get the job done, self organising teams regularly reflecting on how to be more effective, tuning and adjusting their behaviour, practices and processes.</p><blockquote>“With so many differences, how can we say there’s one way that’s going to work for everybody? We can’t. And yet what I’m hearing so much is the <a href="http://newtechusa.net/aic/">Agile Industrial Complex</a> imposing methods upon people, and that to me is an absolute travesty. I was gonna say “tragedy”, but I think “travesty” is the better word because there is no one-size-fits-all. ”, Martin Fowler, Agile Australia 2018 (<a href="https://martinfowler.com/articles/agile-aus-2018.html">source</a>)</blockquote><p>Unfortunately, it is common at the moment to see prescriptive processes being mandated across teams and across organisations. This should not be done. Inflicting <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">capital ‘A’ Agile</a> is not empowering, it does not show respect for people, it drives fear and resistance and it is not taking an agile approach to agility. It moves the locus of control to be external, reducing psychological ownership and intrinsic motivation.</p><p>Perhaps this is not surprising where many leaders in large, traditional firms have got to where they’ve got to with a reductionist, predictive, command &amp; control mindset. This gives rise to the Agile Industrial Complex. An old ways of working view is being applied to new ways of working. In some cases, it may take a new generation of leaders.</p><blockquote>“Knowledge workers themselves are best placed to make decisions about how to perform their work”, Peter F. Drucker</blockquote><h4>Antipattern part 2: Hammer</h4><p>There is no one-size-fits-all for organisational agility. There is no One Way™ that optimises outcomes in all contexts.</p><p>Your organisation, your customers, your value propositions, your environment, your processes, your system of work, your leaders, your teams, your constraints, your starting point, your behavioural norms, your heritage, your brand, your team and you, are unique.</p><blockquote>“If the path ahead is clear, you’re on someone else’s path”, Joseph Campbell</blockquote><p>Organisations are heterogeneous, not homogeneous. Organisations are emergent, not predictive. Organisations are complex adaptive systems.</p><blockquote>“A complex adaptive system is a dynamic networks of interactions, their relationships are not aggregations of the individual static entities, i.e., the behavior of the ensemble is not predicted by the behavior of the components. They are adaptive in that the individual and collective behavior mutate and self-organize corresponding to the change-initiating event.” Wikipedia (<a href="https://en.wikipedia.org/wiki/Complex_adaptive_system">source</a>)</blockquote><p>Growing agility (rather than <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">scaling capital ‘A’ Agile</a>) enterprise-wide is about leveraging that complexity, diversity and emergence, not inflicting sameness on every team. The approach to organisational agility cannot be cookie-cutter.</p><p>Your context is unique. To illustrate this point, here are some of the factors that make up your context:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*jLTCUUTD4-jtHV_8vmeVkA.png" /><figcaption>Contextual Criteria</figcaption></figure><p>It is interesting to note that the People category has the most contextual criteria and Tooling the least, reinforcing how much this is about people.</p><p>It was a quick exercise to brainstorm these contextual criteria and it surprised me that as many as 90 criteria emerged in a short amount of time. This is 1.2 x 10²⁷ (1.2 octillion) unique combinations of the criteria, assuming the criteria are binary, which they aren’t, there are many more combinations. Clearly, your context is unique and across a large organisation there are many unique contexts, like fingerprints. And your context is changing. And that pace of change is getting faster.</p><p>There are two contextual criteria in particular that I’d like to call out. Scaling Agile and Culture.</p><p><strong>Scaling Agile </strong>can have many interpretations and meanings, from a handful of teams on one large product with dependencies not broken, all the way to the diversity and complexity of organisation-wide agility with thousands of value streams, teams and contexts. Depending on why you want to ‘Scale Agile’ and what you mean by ‘Scaling Agile’, your approach will differ.</p><p><strong>Understanding the Incumbent Culture </strong>is key. Within one large organisation there will likely be a number of separate prevalent cultures, due to history, folklore, location, leadership style and so on. It would be foolish to take one approach across different cultures. There are many cultural models to use as a guide. Take <a href="https://qualitysafety.bmj.com/content/13/suppl_2/ii22">Westrum’s typology</a> as one example. If the starting culture is Pathological, then psychological safety will be thin on the ground. An autocratic culture is prevalent and in the worst cases there is a culture of fear with <a href="https://en.wikipedia.org/wiki/Learned_helplessness">learned helplessness</a>. I’ve spoken to teams who didn’t dare to inspect and adapt. A revolutionary approach to changing ways of working is not likely to be successful in this context. I have seen it fail with the imposition of Scrum and synchronised Sprints, which was a case of inflicting revolution in an environment with a lack of safety. A better approach in this context is inviting evolution over imposing revolution, starting with what you do now, for reasons I go into below.</p><blockquote>“The level of consciousness of an organisation cannot exceed the level of consciousness of its leader”, Frederic Laloux</blockquote><p>If the starting culture is Generative, if there is psychological safety, if there are already pockets of mastery, if there is strong survival anxiety with a high cost of delay, then it is possible that inviting revolutionary change is preferable in this context.</p><h4>Frameworks</h4><p>The challenge for any framework of practices in an emergent context is the balancing line between prescription for beginners and flexibility as people gain mastery. A framework either explicitly caters to adaptability to context by not being prescriptive on practices, shining a light on the problems and letting people work out how to solve them, or it is prescriptive and dogmatic. In the latter case as mastery grows you can treat the framework as a departure point and inspect &amp; adapt away from it, so it is no longer being ‘done’, if that improves your outcomes.</p><p>Scrum and its scaled variants such as SAFe, LeSS, Nexus and Scrum@Scale, are revolutionary rather than evolutionary as they introduce new roles, artifacts, events and rules. The new roles, artifacts and events are non-negotiable. You’re either doing it or you’re not doing it. The scaled variants have evolved in in a context of scaling vertically, many teams on one large product, with dependencies. Disciplined Agile supports context sensitive choice with guidance. It suits the context of enterprise agility and scaling horizontally, catering to diversity and emergence, with guardrails. The Kanban Method is evolutionary, you apply it to your process, it shines a light on flow and impediments to flow. More on this topic in a subsequent post.</p><p>All are useful tools to have in the toolbox. One size does not fit all.</p><h3>Pattern: Give People a VOICE</h3><p>Don’t mandate one set of prescriptive practices across your organisation. Instead, apply an agile mindset to organisational agility and <strong>give people a VOICE</strong>.</p><blockquote><strong>V</strong>alues &amp; Principles</blockquote><blockquote><strong>O</strong>utcomes</blockquote><blockquote><strong>I</strong>ntent Based Leadership*</blockquote><blockquote><strong>C</strong>oaching</blockquote><blockquote><strong>E</strong>xperimentation</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1RUeSA81tdtgdtpE" /><figcaption>Photo by <a href="https://unsplash.com/@goian?utm_source=medium&amp;utm_medium=referral">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have your own clear and updated <strong>Values &amp; Principles</strong> that guide every decision across contexts. Focus on <strong>Outcomes</strong> (for example, <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Better Products Faster Safer Happier</a>), with a clear Why, with measures and fast feedback loops, not agile for agile’s sake or because your competitors are doing it. Practice <strong>Intent Based Leadership*</strong> and empowerment, decentralise decision making, strive for high autonomy with high alignment, including teams working out for themselves how they will improve on the Outcomes in their context. Agility by invitation, not Agile Imposition. Leaders go first, role modelling the desired behaviours, with a clear employee engagement model. Provide <strong>Coaching</strong> and support to unlearn old habits and learn new ones, to grow mastery and to remove organisational impediments. Leverage many bodies of knowledge, have many tools in the toolbox. Be an <a href="https://en.wikipedia.org/wiki/Omnism">omnist</a>. Leaders at all levels coach and support continuous improvement and technical excellence. Perform <strong>Experimentation </strong>at all levels with fast feedback. Probe, Sense and Respond at the organisational, business unit and team level. Implement <a href="https://en.wikipedia.org/wiki/Double-loop_learning">double loop learning</a>. Become a learning organisation. Be the best at being better.</p><h4>Values and Principles</h4><p>Determine, update and repeatedly communicate the <strong>Value and Principles </strong>for your organisation, which inform every decision. These are the behavioural guardrails. They signal intent and they allow for behaviour which is not in line to be called out. This includes teams holding their leaders behaviour to account, helping teams to manage up. They should be timeless (for example, ‘Customer Obsession’ or ‘Continuous Improvement’) and apply across contexts.</p><p>Having defined your Principles, with many unique contexts, the practices will differ. To quote <a href="https://speakerdeck.com/tastapod/you-keep-using-that-word?slide=16">Dan North</a>:</p><blockquote>Practices = Principles(Context)</blockquote><p>Practices will emerge by applying your unique Context to your Principles, with coaching and experimentation, leveraging many bodies of knowledge.</p><h4>Outcomes</h4><p>As articulated in the <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">first post in this series</a>, for the organisation clearly articulate <strong>Why </strong>you are looking to improve ways of working and what the desired <strong>Outcomes</strong> are (for example, <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Better Products Faster Safer Happier</a>), each one having one or more measures. The Agendashift From Obstacles To Outcomes (<a href="https://www.agendashift.com/15-minute-foto">FOTO</a>) exercise is one tool which can help identify the Outcomes. Another source of inspiration are the Capabilities listed in <a href="https://itrevolution.com/book/accelerate/">Accelerate</a> (Forsgren, Humble, Kim, 2018) which are correlated to higher organisational performance.</p><h4>Intent Based Leadership*</h4><p>Adopt <a href="https://youtu.be/pYKH2uSax8U"><strong>Intent Based Leadership</strong></a> as modelled by modern military command, as written about by David Marquet. Having provided the high alignment, give people high autonomy, empowering teams to improve on the Outcomes how they see fit, with fast feedback, data and support, starting small. Move authority to the information, not information to authority, decentralising decision making. Do not impose prescription. Make improvement of the desired Outcomes transparent. Adopt a pull, not push approach, within guardrails so that it is agile not fragile. Critically, foster psychological safety, so that people feel safe to experiment, moving the locus of control to be internal. Be a <a href="https://itrevolution.com/book/transformational-leadership-quick-start-guide/">Transformational Leader</a>, moving away from a command and control leadership style from the 1900s in the context of manual labour in a predictive environment. As per the <a href="https://puppet.com/resources/whitepaper/2017-state-of-devops-report">State of DevOps Report</a>, Transformational Leadership is highly correlated with higher organisational performance.</p><p>To engage colleagues in change, there are engagement models such as <a href="https://www.agendashift.com/">Agendashift</a> or <a href="http://openspaceagility.com/">OpenSpace Agility</a> which can assist, such that it is participatory, inclusive and appeals to intrinsic motivation.</p><blockquote>“If you want to build a ship, don’t drum up people to collect wood and don’t assign them tasks and work, but rather teach them to long for the endless immensity of the sea.”, Antoine de Saint Exupéry</blockquote><h4>Coaching</h4><p>Provide <strong>Coaching and support </strong>on agility, not just on one prescriptive framework. Provide coaching and support on a high bar of technical excellence, on removing organisational impediments to flow and on continuous improvement both small (Kaizen) and radical (Kaikaku).</p><p>A federated, fractal structure of small Enablement Teams is a pattern which we have had success with. They perform a Servant Leadership role. Servant: there to nurture culture, remove organisational impediments, support leaders and teams, with autonomy, pull not push. Leadership: there to ensure high alignment, that there are clear outcomes with feedback loops and organisational guardrails to ensure that it’s agile not fragile and to enable both speed &amp; control.</p><h4>Experimentation</h4><p>Now that you have a hypothesis-driven desired outcomes with measures and you have autonomy within guardrails, with coaching and support in a fractal manner, <a href="https://medium.com/@jonathansmart1/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">starting small</a>, it is time for <strong>Experimentation </strong>with fast feedback in order to make progress on your desired outcomes.</p><p>As you are performing unique <a href="https://en.wikipedia.org/wiki/Cynefin_framework#Complex">complex</a> work within a unique complex adaptive system, you need to probe, sense and respond in that order. As with any experiment, everything is a hypothesis to test. The outcome of the experiment is not guaranteed as the system of work is emergent. Acting in the space, changes the space. Due to this, consider that many experiments may not be reversible and cannot be replicated, as the complex adaptive system will already have reacted to the input. As per <a href="https://medium.com/disruptive-design/tools-for-systems-thinkers-the-6-fundamental-concepts-of-systems-thinking-379cdac3dc6a">Systems Thinking</a>, there is not a linear cause and effect.</p><p>To get started, I find the following model for navigating change, from Dan North, works well:</p><blockquote>“Visualise, Stabilise, Optimise”, <a href="https://speakerdeck.com/tastapod/swarming?slide=19">source</a></blockquote><p><strong>Visualise</strong>: Before you can run experiments, first you need to ‘see’ and measure your current system of work. Pick a big wall and physically map out your workflow steps and the work in the system. End to end, not just in IT. For the vast majority of teams they have never before ‘seen’ their knowledge work like a factory floor and it is a shock. Impediments become apparent. Add aging on the tickets. Typically work is waiting 90% of the time in large organisations. This is where the waste is, slowing down the system, like too many cars on the motorway. You should <a href="https://hackernoon.com/know-your-flow-a436eb7c8af">Know Your Flow</a>.</p><blockquote>Look where the work isn’t</blockquote><p><strong>Stabilise</strong>: Control the amount of work in progress (WIP) in order to stabilise flow. Start putting fewer cars on the motorway. Introduce WIP limits, meaning that no work can be started until there is a free slot. The system now becomes a pull system, with work being pulled to the right.</p><blockquote>Stop starting, start finishing</blockquote><p><strong>Optimise</strong>: Identify what you believe your biggest constraint to flow is and focus your improvement efforts on alleviating it, starting small, with fast feedback. Run one experiment (probe) and inspect the Outcome measures (sense). Remember that cause and effect are not linear. Work out what your next improvement experiment will be and go again (respond), amplifying positive experiments and dampening negative experiments. Make use of all bodies of knowledge, consider all frameworks to identify optimum practices for your unique context. <a href="https://less.works/less/principles/systems-thinking.html#SeeingSystemDynamics:CausalLoopDiagrams">Causal loop diagrams</a> are a useful tool.</p><p>Once insights are generated from the improvement experiments, practice <a href="https://en.wikipedia.org/wiki/Double-loop_learning">double loop learning</a> to reflect back on the original Principles and Outcomes. Reflect, with contextual evidence, whether they should be updated as you gain more insight.</p><h4>Be an Omnist</h4><p>Any frameworks, practices or tools are a departure point, not a destination. Be an <a href="https://en.wikipedia.org/wiki/Omnism">omnist</a>. Draw from multiple knowledge bases, don’t only have one tool in the toolbox. Find your own way.</p><blockquote>“Omnism affirms the necessity of one arriving at an understanding of reality based on personal experience, engagement, and inquiry, and an acceptance of the validity and legitimacy of the differing understandings of others. In this, there is, however, an implied system of values.” (<a href="https://en.wikipedia.org/wiki/Omnism">source</a>)</blockquote><h3>Summary</h3><p>As per <a href="https://www.amazon.co.uk/Drive-Surprising-Truth-About-Motivates-ebook/dp/B0033TI4BW">Drive</a> (<a href="https://medium.com/u/e2618df8579f">Daniel Pink</a>, 2009), innate motivators are Autonomy, Purpose and Mastery.</p><p><strong>Values &amp; Principles</strong> and <strong>Intent-based Leadership*</strong> give people <em>autonomy </em>within guardrails. <strong>Outcomes</strong> provide <em>purpose</em>. <strong>Coaching</strong> &amp; <strong>Experimentation</strong> help people to build <em>mastery</em>.</p><blockquote>OH: “It doesn’t feel transformational because the people affected by the changes are the ones driving those changes”</blockquote><p>This approach shifts the <a href="https://en.wikipedia.org/wiki/Locus_of_control">locus of control</a> of the complex adaptive system inward, such that people are invited to be, and with safety and support become, masters of their own destiny. In some cases, this requires overcoming an entire career of conditioning that the locus of control is external, that both the how and the what are prescribed. For some people, cultures, contexts and complex adaptive systems, <em>Kaizen</em>, evolutionary change is needed first, to show that the sky won’t fall in, to build confidence.</p><p>In order to deliver better business outcomes, to engage colleagues and delight customers, for change to be successful and lasting, don’t Inflict Agile, instead <strong>give people a VOICE</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*JsoazSPyZmdFlolqGyo2sQ.png" /></figure><p>Series:</p><ol><li><a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Want to do an Agile Transformation? Don’t. Focus on Flow, Quality, Happiness, Safety and Value</a></li><li><a href="https://medium.com/@jonathansmart1/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">Want to scale agile? Don’t. Descale the work first. Achieve big through small</a></li></ol><p>See also:</p><ul><li><a href="https://dannorth.net/2018/01/26/in-praise-of-swarming/">In praise of SWARMing</a>, Dan North</li><li><a href="https://www.agendashift.com/">Agendashift</a></li><li><a href="http://openspaceagility.com/">OpenSpace Agility</a></li></ul><p>Also by the author:</p><ul><li><a href="https://hackernoon.com/know-your-flow-a436eb7c8af">Know Your Flow</a></li><li><a href="https://medium.com/@jonathansmart1/agile-manifesto-values-add-on-for-large-enterprises-f3fdc1abcd65">Agile Manifesto Values add on for large enterprises</a></li><li><a href="https://www.youtube.com/watch?v=R-fol1vkPlM">The PMO is dead, long live the PMO</a></li><li><a href="https://www.youtube.com/watch?v=Tj0qMTgBX2s&amp;t=5s">The Yin and Yang of Speed and Control</a></li></ul><p>Acknowledgements: thanks to Zsolt Berend, Mike Burrows, Tony Caink, Steve Denning, Mark Lines, Angie Main, Dan North, Simon Rohrer for feedback.</p><p>* Source: <a href="http://ibli.com/">IBLI.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d5e68449aa7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/organisational-agility-give-people-a-voice-5d5e68449aa7">Organisational Agility: Give People a VOICE</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to scale agile? Don’t. Descale the work first. Achieve big through small.]]></title>
            <link>https://medium.com/sooner-safer-happier/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/7bdd09962540</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Jonathan Smart]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 18:20:10 GMT</pubDate>
            <atom:updated>2019-01-05T14:36:42.921Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5vbi0i8zmZrlNsLI" /><figcaption>Photo by <a href="https://unsplash.com/@chuttersnap?utm_source=medium&amp;utm_medium=referral">chuttersnap</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is the second post in a series, sharing a number of observed <strong>anti-patterns</strong> and corresponding <strong>patterns </strong>on the topic of organisational agility (aka digital transformation).</p><p>We are in the midst of a Turning Point in a 50 year cycle, in the Age of Digital, as <a href="https://www.strategy-business.com/article/Are-We-on-the-Verge-of-a-New-Golden-Age">well articulated</a> by Carlota Perez in ‘<a href="https://www.amazon.co.uk/Technological-Revolutions-Financial-Capital-Dynamics/dp/1843763311">Technological Revolutions and Financial Capital</a>’. At the time of writing, seven of the top ten firms by market capitalisation are technology companies. Less than two months ago, on 26th June 2018, General Electric, the last remaining original constituent of the Dow Jones index which was created in 1896, left the index, as it was contributing less than half a percent. In 2004, GE was the largest firm in the world by market value and only two years ago, in 2016, GE was still in the top ten. This is an indication of how we are in the Turning Point, how the previous industrial incumbents are shrinking and how firms with new business models and new ways of working, leveraging significant shifts in technology have become the new dominant forms of human organisation.</p><p>In sharing the anti-patterns and patterns, it is worth noting that everything is context dependent. An anti-pattern for one scenario might be a pattern in another context, in particular based on the current cultural norms of an organisation. That said, I believe that the anti-patterns to be presented are applicable in the context of the majority of large, old, bureaucratic, global enterprises (horses rather than unicorns).</p><p>They are based on lessons learnt through doing including learning from failing. Along with many talented people, we’ve been servant leaders on better ways of working (the application of agile, lean , DevOps, design thinking, systems thinking and so on) across a large (80,000 people), old (300+ years old), global, not-born-agile, highly regulated enterprise, with personal experience of delivering change with an agile mindset, principles and practices since the early 1990’s, about a decade prior to the Agile Manifesto, when the term ‘lightweight processes’ was used. The anti-patterns and patterns are also based on learnings from the community, from other horses (rather than unicorns) on similar journeys.</p><h3>Anti-pattern: The bigger the capital ‘T’ Transformation, the bigger the change curve</h3><p>The <strong>Kubler-Ross Curve</strong> originated from psychiatrist <a href="https://www.biography.com/people/elisabeth-kubler-ross-262762#pioneering-psychologist">Elisabeth Kubler-Ross</a>’s work on grief, published in 1969. It has been found to be valid in the majority of situations relating to change and we have repeatedly observed this pattern to hold true via feedback from colleague surveys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*-XR0rEcbD0XRn5iz" /></figure><p>The bigger the capital ‘T’ Transformation, the bigger the change curve. If embarking on one large, broad, Transformation, expect an almighty big and deep dip in the curve. The bigger the dip, the harder it is to climb out of and the longer it takes. Given that some firms are facing an <a href="https://www.bbc.co.uk/news/business-43240996">existential threat</a>, there may not be sufficient time to climb out of that big dip.</p><p>In large, diverse, regulated, multinational organisations, where the cultural norm is most likely to be control or competence based, a capital ‘T’ Transformation with a big dip in the curve, will make the journey a harder and more challenging one. There will be a greater degree of denial, frustration and anger. The change stands a higher chance of cultural tissue rejection, with more ammunition for those averse to change. Things will get significantly worse before they get better.</p><p>For organisations that take this approach, with a broad scope, where people leave as a Project Manager on a Friday and rejoin as a Scrum Master on Monday, and in some cases need to reapply for their new role, the chances of genuine, embedded, internalised, long lasting, successful change which leads to improved business outcomes, over <a href="https://en.wikipedia.org/wiki/Cargo_cult">cargo cult</a> behaviours and new labels on existing ways of working, are greatly lowered. As per <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">this post</a> , this drives fear, which drives a lack of action and resistance.</p><h4>Hardest at the beginning</h4><p>When starting out on transforming ways of working, increasing organisational agility, embarking on a ‘digital transformation’, it is hardest at the beginning. The antibodies to change are strong, there are vested interests at stake, the impediments to better ways of working and flow will be at the their highest, there will be the most amount of dependencies impeding flow, understanding is low, the force is strong with <a href="https://en.wikipedia.org/wiki/List_of_cognitive_biases">cognitive biases</a> with no anecdotal stories or hard data from the organisation to challenge them and this is Yet Another Transformation (time to put your head in the sand and let it blow over). An analogy is skiing. It’s cold, painful, slow and hurts when learning to ski. It’s hardest at the beginning, uses up the most energy, when snow ploughing. Break past that, and once able to parallel turn, enjoyment goes up, speed goes up, energy usage for the same distance and time goes down, it becomes fun and addictive. Does it make sense to have a large number of people all snow-ploughing at the same time, on poor quality snow, in an environment not yet set up for skiing, bumping into each other, without enough ski instructors to go around?</p><h4>Limited re-learning velocity</h4><p>Furthermore, large, old, bureaucratic, traditional organisations have a limited capacity and a tolerance with which they can change over time. Organisations have a limited re-learning velocity. Re-learning requires organisational unlearning, which is harder than learning from a clean sheet. Behavioural science <a href="https://www2.deloitte.com/insights/us/en/focus/behavioral-economics/government-technology-adoption-behavioral-nudges.html">studies</a> show that cognitive overload is a major theme in rejection of change. Cognitive reasoning is finite and easily depleted. According to research by Dr Wendy Wood, approximately 40% of decisions that people make everyday are not decisions, but are habits and the majority of these habits in going from a traditional to a new way of working, need to be unlearnt.</p><blockquote>“The thoughtful intentional mind is easily derailed and people tend to fall back on habitual behaviors. Forty percent of the time we’re not thinking about what we’re doing. Habits allow us to focus on other things…Willpower is a limited resource, and when it runs out you fall back on habits.” (<a href="https://www.sciencedaily.com/releases/2014/08/140808111931.htm">source</a>)</blockquote><p>Where the change has not been internalised and embedded, where it is forced across an organisation in a broad manner, it is like one large elastic band, as soon as a leader mandating capital ‘T’ Transformation moves on, the organisation (people’s habits and codified processes) snap back into previous ways of working. It takes 3 to 5 years, best case, for a large traditional organisation to develop a new muscle memory. And then there is no end date to continuous improvement. For more on this topic, see <a href="https://medium.com/u/9ef5c7874c2f">Barry O&#39;Reilly</a>’s book <a href="https://www.amazon.co.uk/Unlearn-Success-Achieve-Extraordinary-Results/dp/1260143015">Unlearn</a> (Nov 2018).</p><h4>Big Bang. Big Risk.</h4><p>This approach is also not living it’s own values or applying its own principles. It is not applying an agile mindset to increasing organisational agility. It is big batch, big bang and big risk. It is approaching change in a manner counter to the change being asked of colleagues.</p><h4>Bureaucracy</h4><p>According to <a href="https://en.wikipedia.org/wiki/Parkinson%27s_law">Parkinson’s Law</a>, <em>“ work expands so as to fill the time available for its completion”.</em></p><p>I propose a corollary to this which is that “<em>processes, control points and standards expand based on the number of audit and control staff employed</em>”. This is in an uncontested space (i.e. in the absence of a group of people focussed on optimal ways of working)</p><p>Parkinson goes on to say that <em>“the number employed in a bureaucracy rise by 5–7% per year irrespective of any variation in the amount of work (if any) to be done”.</em></p><p>He cites two factors: <em>(1) “An official wants to multiple subordinates, not rivals” </em>and <em>(2) “Officials make work for each other”</em> and he gives the British Colonial Office as an example. In the nearly twenty years from 1935 to 1954, looking only at peacetime years, the average rate of growth of employees at the Colonial Office was 5.89% each year (within a narrow range of 5.24% to 6.55% p.a.), whilst the British Empire <a href="https://en.wikipedia.org/wiki/Territorial_evolution_of_the_British_Empire">shrunk</a> by 76% from 17 to 4 million square miles in the same time period. The size of the Colonial Office was inversely proportional to the size of the the Empire.</p><blockquote>“It would be rational, prior to the discovery of Parkinson’s Law, to suppose that these changes in the scope of Empire would be reflected in the size of its central administration. But a glance at the figures shows that the staff totals represent automatic stages in an inevitable increase. <strong>And this increase, has nothing to do with the size — or even the existence — of the Empire</strong>.” (<em>Cyril Parkinson, 1955)</em></blockquote><p>As large, old, enterprises, with years of organisational scar tissue and 100 year old ways of working are going to be at the highest level of inefficiency and bureaucracy that their revenues can (or perhaps in the Age of Digital, cannot) support, this is one reason why it is sub-optimal to take that organisation and apply a scaled agile framework across the whole organisation in one go.</p><p>It is important to descale the organisation, to descale the work, before scaling agility (not scaling capital ‘A’ Agile, which is doing not being).</p><blockquote>Achieve big through small</blockquote><p>Start with small teams, small slices of value and small investments.</p><blockquote>“Nail it before you scale it” <em>(thanks </em><a href="https://medium.com/u/562f2ab97562"><em>Cliff Hazell</em></a><em>)</em></blockquote><h3>Pattern: In order to scale, descale first. Achieve big through small</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oAX75_0y6Ws6vI2b" /><figcaption>Photo by <a href="https://unsplash.com/@serhatbeyazkaya?utm_source=medium&amp;utm_medium=referral">Serhat Beyazkaya</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Instead of a big bang transformation, with one big dip in the curve, achieve a big outcome through early, often and small slices of value.</p><p>Pursue evolutionary and continuous transformation aligned to outcomes, linking together a series of smaller change curves. Start in areas which are naturally receptive, the natural champions. The dips are not as deep, the learning and feedback is quicker, there is less risk and the champions, who have been trying to do this despite the firm in the past, are best placed to beat a path through the organisational jungle, likely with a <a href="https://en.wikipedia.org/wiki/Mindset#Fixed_and_growth">growth mindset</a> and personal resilience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*W7Ona52IgxSEHh6ouVuQMw.png" /></figure><p>This approach is in line with the <a href="http://www.djaa.com/principles-general-practices-kanban-method">Kanban Method</a> principle “Agree to pursue incremental, evolutionary change”. As time goes by, I have found myself to value <a href="https://medium.com/u/1bdaaff8694e">David J Anderson</a>’s Kanban Method <a href="http://www.djaa.com/principles-general-practices-kanban-method">principles and practices</a> more and more, in the context of organisational agility, at all levels from strategy to the team.</p><p>Hence, don’t take a large team working in a traditional manner, on a traditionally developed product (whether IT or not) and apply revolution all in one go. Apply an agile mindset to the rollout of agile. Achieve big outcomes through (1) small teams, (2) small investments and (3) small slices of value, supported with capability building, training and coaching as well as help to remove organisational impediments. Identify where there is ‘elephant carpaccio’ which can be delivered, when starting out with a traditional waterfall team, likely as per Conway’s Law, with a monolithic system. Eventually there should be no elephant in the room. Leaders should ensure that there is a psychologically safe environment for experimentation and learning.</p><h4>Case study of descaling work</h4><p>By way of an example, I’m aware of a scenario where there was a team of about 100 people who had multiple multi-year failed attempts to deliver business value in a waterfall manner. Following this, with the appointment of a leader who had a track record of successful delivery, a team of five was created, working with agile principles and practices. Within 12 weeks, there was a product in the hands of customers, in a production environment, solving a customer need and providing much needed learning and feedback. From this point on, the team size didn’t grow to be above three teams of nine or fewer people each, despite expanding significantly in scope in terms of the business lines supported, due to the success in the first business line.</p><p>Taking the original 100 people and applying a frog march of mandated certification, re-applying for your job with a different title and a cookie-cutter approach would not have addressed the inherent bloat at the time (it’s not a 100 person problem, in fact 100 people is a large part of the problem), would not have internalised the change so that it comes from within thus building a learning organisation, is not optimised to context, is costly and does not maximise business outcomes &amp; customer delight.</p><h4>Fractal</h4><p>For large organisations, and the approach that we have taken, where there are multiple business units (each one large enough to be standalone company in it’s own right, and in fact used to be, with their own culture and folklore), the ‘achieve big through small’ approach can be taken concurrently (whilst limiting Work In Progress) in a fractal manner. Each business unit pursues a limited series of small change experiments starting in fertile soil, with a small central Centre of Enablement (CoE) providing servant-leadership support and dealing with bubbled up organisational impediments. An agile mindset is applied in terms of empowerment and not being prescriptive on the How (within guardrails and a common vocabulary). This in turn can be done at the sub-BU level, and so on. The leads from each business unit come together weekly as a virtual team. Applying an agile mindset, all of the virtual teams of BU or sub-BU leads are agile team sized (single digits). It’s quick to spot common organisational constraints and allows for swarming on alleviating the constraints.</p><h4>Scale agility, not Agile, vertically then sideways</h4><p>A mistake that we’ve made in the past has been to start at the team level and go sideways (more teams), along with the top level support. However, even with specific targeted training, this can fail to engage one or more levels of middle management, also known as the Frozen Middle or more kindly, the Pressurised Middle, as there is not always a clear role to play in the change. This is a common characteristic in any culture change in large organisations and is not a reflection of the people, it is a reflection of the situation they are in and how people in these roles are engaged.</p><p>A personal learning, when starting small, from a people perspective, is to have a vertical slice of an organisation go first. The leadership team is team #1. With the existing structure, have a vertical slice of that org volunteer to go first, including leaders at all levels, preferably natural champions, with as few dependencies on other teams as possible. Ideally this will be value stream / product / service aligned, not a role-specialisation alignment, such as just the BAs or just the Engineers or just the PMs. Middle management at as many levels as there are, have an explicit role, coaching and being coached on continuous improvement in ways of workings, as per the Toyota <a href="http://www-personal.umich.edu/~mrother/The_Coaching_Kata.html">Coaching Kata</a> and with multiple-level portfolio Kanban being adopted to focus on visualising and limiting work in progress.</p><p>Then scale agility (not capital ‘A’ Agile) sideways, at a sustainable pace, working towards the organisation becoming a network of interdependent services. Go for more slices of the organisation, which are value stream / product / service aligned, supported by a small BU Centre of Enablement, providing coaching, training, shared learning, clearing the path for the teams. Pursue incremental, evolutionary, outcome-oriented, continuous transformation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHvdc7uxr9zY9TS3Y3PBDw.jpeg" /></figure><p>This doesn’t mean that scaled agile frameworks are not used. It is up to each team and area to decide what works best for them. Each framework is a valuable body of knowledge and can be a good departure point. In some cases they can provide a common vocabulary and in all cases it’s about trying what works in your unique context, with a focus on better business outcomes (as per my <a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">previous post</a>). We aim to avoid framework fundamentalism, preferring to be <a href="https://en.wikipedia.org/wiki/Omnism">Omnists</a>. For more on this topic, see <a href="https://twitter.com/tastapod">Dan North</a>’s excellent article on <a href="https://dannorth.net/2018/01/26/in-praise-of-swarming/">SWARMing</a>.</p><p>Again, at the beginning it’s the hardest, as the rest of the organisation is not set up for Continuous Everything. Several years in and good progress has been made by supporting functions (GRC type functions, InfoSec, Compliance, Audit and so on) also working in a way which supports small and often, conversation over a contract, with multidisciplinary long lived small teams, value stream aligned and in a context-relevant not one-size-fits-all manner.</p><h4>Exemplar Community</h4><p>To help amplify the learning, the overcoming of impediments, and adoption of better ways of working, we have an Exemplar Community. There are benefits of membership, such as additional training, external speakers, shared learning and prioritisation on the pull of the virtual andon cord. You don’t need to be exemplary to join, it is voluntary and there is a psychological contract in that teams agree to strive to become exemplary, jumping in with both feet, with a focus on measurable business outcomes (not activity or output). Consistently these teams exhibit far superior outcomes (for example 23x fewer production incidents on average), provide hard data as to benefits for the critics who are swayed by hard data, provide storytelling for emotional buy in and via cellular mitosis are able to spread better ways of working.</p><h4>UK Government Digital Service (GDS)</h4><p>UK GDS have taken a similar path. To <a href="https://www.slideshare.net/AdamMaddison/scaling-agile-in-gds-agile-cambridge-2016">quote</a> <a href="https://medium.com/u/c51ada7de3e2">Adam Maddison</a>, ex-Head of Agile Delivery at GDS from Agile Cambridge 2016:</p><p><em>“What’s our approach to scaling at GDS? Do not scale. But we do have a number of large programmes.”</em></p><p><em>“At GDS we absolutely haven’t ignored scaling frameworks. We’re quite happy to use features from those frameworks if they truly deliver value. But we are absolutely not wedded to any methodology or framework. We will always adapt features to our own use.”</em></p><p>In both the case of GDS and in our context, the ‘big’ in ‘achieve big through small’ is articulated via the <a href="https://insidegovuk.blog.gov.uk/2017/02/13/the-2017-to-2018-gov-uk-roadmap/">Roadmap</a>, which articulates Strategic Objectives and quarterly Business Outcomes on long lived value streams / products / services. These in turn are broken down into small vertical slices of value, like layers of an onion, as outcomes not activities and delivered via Continuous Everything. Achieving big outcomes through many small steps and continuous learning.</p><h4>Summary</h4><ul><li>Achieve big through small</li><li>Descale the organisation and the work first</li><li>Nail it before you scale it</li><li>Scale agility, not capital ‘A’ Agile, at a sustainable place, with support</li><li>Leaders go first</li><li>Work towards the organisation becoming a network of interdependent long-lived services, with high cohesion, low coupling and customer-centricity</li><li>Apply an agile mindset to the adoption of agility</li></ul><p>See also:</p><ul><li><a href="https://medium.com/@jonathansmart1/organisational-agility-give-people-a-voice-5d5e68449aa7">Organisational Agility: Give People a VOICE</a></li><li><a href="https://medium.com/@jonathansmart1/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Want to do an Agile Transformation? Don’t. Focus on Flow, Quality, Happiness, Safety and Value</a></li><li><a href="https://hackernoon.com/know-your-flow-a436eb7c8af">Know Your Flow</a></li><li><a href="https://medium.com/@jonathansmart1/agile-manifesto-values-add-on-for-large-enterprises-f3fdc1abcd65">Agile Manifesto Values add on for large enterprises</a></li><li><a href="https://www.youtube.com/watch?v=R-fol1vkPlM">The PMO is dead, long live the PMO</a></li><li><a href="https://www.youtube.com/watch?v=Tj0qMTgBX2s&amp;t=5s">The Yin and Yang of Speed and Control</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bdd09962540" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">Want to scale agile? Don’t. Descale the work first. Achieve big through small.</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to do an Agile Transformation? Don’t. Focus on Flow, Quality, Happiness, Safety and Value]]></title>
            <link>https://medium.com/sooner-safer-happier/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/11e01ee8f8f3</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital]]></category>
            <dc:creator><![CDATA[Jonathan Smart]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 18:18:55 GMT</pubDate>
            <atom:updated>2019-07-03T16:46:43.236Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jonathan Smart on Twitter</h3><p>Want to scale agile? Don&#39;t. Descale the work. Want to do an agile transformation? Don&#39;t. Focus on Flow, Quality, Happiness and Value</p><p>It was a Saturday morning. I was standing in line at a coffee shop, thinking about flow, as I often find myself doing when waiting in line. I reached for my phone to pass the time (while stuck behind a constraint in the cafe’s system of work) and sent the tweet above. This tweet went, relatively-speaking for me, viral, breaking in to triple digits of likes and retweets. It seems to have struck a chord.</p><blockquote>If you want to do an Agile Transformation, don’t. Focus on Flow, Quality, Happiness, Safety &amp; Value and you will end up transforming to have agility</blockquote><p>This is the first of a series of posts, where I’m going to share a number of <strong>anti-patterns</strong> and corresponding <strong>patterns</strong>. It is worth noting that everything is context dependent. An anti-pattern for one scenario might be a pattern in another context. That said, I believe that the anti-patterns to be presented are applicable in the majority of contexts.</p><p>This is based on lessons learnt through doing including learning from failing. Along with many talented people, we’ve been servant leaders on better ways of working (the application of agile, lean , DevOps, design thinking, systems thinking and so on) across a large (80,000 people), old (300+ years old), global, not-born-agile, highly regulated enterprise, with personal experience of delivering change with an agile mindset, principles and practices since the early 1990’s, about a decade prior to the Agile Manifesto, when the term ‘lightweight processes’ was used. The anti-patterns and patterns are also based on learnings from the community, from other horses (rather than unicorns) on similar journeys, as we are all at a turning point in the Age of Digital.</p><h3><strong>Anti-pattern:</strong> <strong>Doing a capital ‘A’, capital ‘T’ Agile Transformation</strong></h3><p>A capital ‘A’, capital ‘T’ Agile Transformation, from the perspective of an employee, infers involuntary, mandatory change being done <strong><em>to</em></strong> you, whether you like it or not.</p><p>The capital ‘T’ denotes that you <strong><em>have</em></strong> to change and the capital ‘A’ denotes <strong><em>how</em></strong> you are going to change. Both of these words carry baggage.</p><p>Not surprisingly, this triggers fear and resistance for <a href="https://hbr.org/2012/09/ten-reasons-people-resist-chang">many reasons</a>, including loss of control, uncertainty, changing habits, fear of failure, fear of incompetence, more work, change fatigue and ‘better the devil you know’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*spcz--MtiQBP_zhV" /><figcaption>by <a href="https://unsplash.com/@rossf?utm_source=medium&amp;utm_medium=referral">Ross Findon</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>From an evolutionary perspective, depending on the messaging of the <strong>why</strong> and depending on <strong>how</strong> the change is approached, and in particular for those with a <a href="https://en.wikipedia.org/wiki/Mindset#Fixed_and_growth">fixed mindset</a>, change drives a fear of survival, which leads to resistance and less rational thought as the primitive brain takes over.</p><p>Can I change? What if I can’t adapt? Will I still be able to pay the bills?</p><p>Looking at autonomy, purpose and mastery, as per <a href="https://medium.com/u/e2618df8579f">Daniel Pink</a>’s <a href="https://www.danpink.com/books/drive/">Drive</a> and that human motivation is primarily intrinsic for knowledge work, two of the top three motivators have been taken away. There is a lack of autonomy (you have to do this thing) and a lack of mastery (you’re a beginner again, possibly after a long career). If the <strong>why</strong> is articulated as cost reduction or profitability, meaningful purpose is also removed, taking away all three categories of human motivation.</p><blockquote>“The problem with the amygdala and its fight-or-flight response today is that it sets off alarm bells whenever we want to make a departure from our usual, safe routines. The brain is designed so that any new challenge or opportunity or desire triggers some degree of fear. Whether the challenge is a new job or just meeting a new person, the amygdala alerts parts of the body to prepare for action — and our access to the cortex, the thinking part of the brain, is restricted, and sometimes shut down.” <em>(</em><a href="https://www.amazon.co.uk/Small-Step-Change-Your-Life/dp/076118032X"><em>One Small Step Can Change Your Life. The Kaizen Way</em></a><em>, Dr Robert Maurer, 2014)</em></blockquote><p>This evolutionary fear of change is also seen in loss aversion, which is people’s tendency to prefer avoiding losses to acquiring equivalent gains. This evolutionary tendency to loss aversion further cements people’s desire to maintain the status quo.</p><blockquote>“Humans may be hardwired to be loss averse due to asymmetric evolutionary pressure on losses and gains: for an organism operating close to the edge of survival, the loss of a day’s food could cause death, whereas the gain of an extra day’s food would not necessarily cause an extra day of life.” <em>(</em><a href="https://en.wikipedia.org/wiki/Loss_aversion"><em>Loss aversion</em></a><em>, Wikipedia)</em></blockquote><p>Agile should not have a capital A unless it is at the start of a new sentence. Agile is not a noun. It is not a trademark. You can’t buy Agile In A Box (really, you can’t). By the very fact that agility is optimal in complex contexts, where the What and the How is inherently unknowable in advance, where acting in the space changes the space, there cannot be a one size fits all solution. It is about exhibiting agility, being agile not doing Agile. It is first and foremost a mindset that informs every single deliberate decision and automatic reaction.</p><blockquote>“If the path ahead is clear, you are on someone else’s path”, Joseph Campbell</blockquote><p>The capital ‘A’ Agile mindset leads to the<a href="http://newtechusa.net/aic/"> Agile Industrial Complex</a>. It leads to a number of anti-patterns, such as the imposition of practices on people and to certification schemes with questionable value. We don’t want agile for agile’s sake or DevOps for DevOps sake. This can lead to local optimisations where the expected business benefits, end to end, do not materialise.</p><p>There is a need to focus on Why are we doing this and what the desired business outcomes are. Then agile, lean, DevOps, Design Thinking and so on are bodies of knowledge, they are tools in the toolbox, to achieve those outcomes, applying what works in your unique context and continually improving through experimentation.</p><h3><strong>Pattern:</strong> <strong>Start with Why and focus on Outcomes</strong></h3><p>First, as well articulated by Simon Sinek,<a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action"> start with why</a>. There should be a clear and well communicated <strong>Why</strong> for the organisation of the need to change ways of working, why constant improvement is needed, with nuanced context-sensitive and relevant definitions of why for the any sub-organisations within the parent organisation which may have their own cultural norms, history, folklore and legacy ways of working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4Gsczaf7OiqmFD3v" /><figcaption>by <a href="https://unsplash.com/@gaellemm?utm_source=medium&amp;utm_medium=referral">Gaelle Marcel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The ‘why’ should be more than profitability, shareholder returns or stock price. As per the article ‘<a href="https://www.mckinsey.com/business-functions/organization/our-insights/the-irrational-side-of-change-management">The Irrational Side of Change Management</a>’</p><blockquote>“what motivates leaders does not motivate most of the employees”</blockquote><p>Research shows that when employees are asked what motivates them the most in their work they are equally split across five forms of impact: (1) society (2) customer (3) company (4) team (5) the individual.</p><blockquote>“What the leader cares about (and typically bases at least 80 percent of his or her message to others on) does not tap into roughly 80 percent of the workforce’s primary motivators for putting extra energy into the change program.”</blockquote><p><a href="http://www.reinventingorganizationswiki.com/Teal_Organizations">Teal organisations</a>, the most evolved, are driven by a higher level purpose. This is echoed in ‘Drive’ by Dan Pink, where people are motivated by a transcendent purpose. Ensure that the definition of why has a higher level purpose and covers society, customers, company, team and the individual.</p><p>From there, identify high level, thematic desired <strong>outcomes</strong>. Start with what does awesome look like, what is the current reality and what are the obstacles. Next, derive, prioritise and theme outcomes which get you to your state of awesomeness.</p><p>For us, our desired outcomes are described as <strong>Better Value Sooner Safer Happier</strong>, each of which is measurable.</p><ul><li>Better =&gt; Quality =&gt; Production Incidents, Resilience, Static code analysis measures</li><li>Value =&gt; context specific unique measures per quarterly Business Outcome (e.g. customer Net Promoter Score increased 10 points, reduced carbon usage by 10%, increased gender diversity by 15%, increased lending to small and medium firms by £100m, reduced Risk Weighted Assets held on balance sheet by 20%, etc.)</li><li>Sooner =&gt; Flow =&gt; Lead Time, Throughput, Release Cadence, Flow Efficiency. Be wary of becoming a feature factory. Reduce Lead Time and spend more time with the end users, refactoring and innovating.</li><li>Safer =&gt; GRC Control Compliance (e.g. InfoSec, Know-Your-Client, Data Privacy, GDPR type mandatory requirements). Speed &amp; Control. Agile not fragile.</li><li>Happier =&gt; increased customer and colleague satisfaction, via surveys and feedback loops</li></ul><p>Ultimately, it is all about Flow. This needs balancing measures, as anything can be done badly, so that it is not Flow at the expense of quality, happiness, safety or value.</p><p>On a regular cadence, a one pager is sent to senior leaders with measures for the above, including vector measures, the rate of improvement. Everyone can see everyone else’s data. In addition, a real time dashboard with drill down is available.</p><p>The scope is the whole organisation, to enable organisational agility. It is Incremental and Disruptive, Exploit and Explore. It is equally aiming to delight customers in existing markets and to delight new customers in new markets.</p><p>Then, for the reasons above, rather than doing a capital ‘A’, capital ‘T’, Agile Transformation for the sake of agile and framing it as such, and commence the rollout of a set of prescriptive practices or a prescriptive framework, frame the change around the <strong>Why</strong> and around the improvement in the identified <strong>Outcomes</strong>.</p><p>This appeals to <a href="https://en.wikipedia.org/wiki/Motivation#Intrinsic_motivation">intrinsic motivation</a>, it is asking people to bring their brain to work, to understand and internalise the mission, and in an empowered manner to take personal ownership for working out <strong>how</strong> to achieve the desired outcomes. Agile principles and practices, Lean, DevOps, Systems Thinking, Design Thinking and so on are tools in the toolbox, and are supported with training, coaching and psychological safety in a context sensitive, not one-size-fits-all, pull-based not push-based manner.</p><p>See also:</p><ul><li><a href="https://medium.com/@jonathansmart1/organisational-agility-give-people-a-voice-5d5e68449aa7">Organisational Agility: Give People a VOICE</a></li><li><a href="https://medium.com/@jonathansmart1/want-to-scale-agile-dont-descale-the-work-first-achieve-big-through-small-7bdd09962540">Want to scale agile? Don’t. Descale the work first</a></li><li><a href="https://medium.com/sooner-safer-happier/know-your-flow-a436eb7c8af">Know Your Flow</a></li><li><a href="https://medium.com/@jonathansmart1/agile-manifesto-values-add-on-for-large-enterprises-f3fdc1abcd65">Agile Manifesto Values add on for large enterprises</a></li><li><a href="https://www.youtube.com/watch?v=R-fol1vkPlM">The PMO is dead, long live the PMO</a></li><li><a href="https://www.youtube.com/watch?v=Tj0qMTgBX2s&amp;t=5s">The Yin and Yang of Speed and Control</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11e01ee8f8f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/want-to-do-an-agile-transformation-dont-focus-on-flow-quality-happiness-safety-and-value-11e01ee8f8f3">Want to do an Agile Transformation? Don’t. Focus on Flow, Quality, Happiness, Safety and Value</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Know Your Flow]]></title>
            <link>https://medium.com/sooner-safer-happier/know-your-flow-a436eb7c8af?source=rss----9015db1a7b56---4</link>
            <guid isPermaLink="false">https://medium.com/p/a436eb7c8af</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jonathan Smart]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 18:09:43 GMT</pubDate>
            <atom:updated>2017-09-16T13:59:14.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_wh838Y0J50lqqLX_i5rg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/ZIC_DVO0WVQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dimitri Tyan</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Picture this. A gaggle of CIOs from various industries meeting to discuss digital transformation and business agility. About 20 in the room. I ask <strong><em>“how many of you know a flow metric for your organisation?”</em></strong>. Any data point of any flow measure would have done. Lead time, cycle time, throughput, release cadence, averages, percentiles, median, a flow efficiency measure, percentage of strategic products in their organisation with the 80th percentile Lead Time consistently less than 4 weeks for the past rolling 6 months, a vector metric trend of any of the above, etc.</p><p>How many CIOs out of 20 do you think knew at least one data point on Flow for any part of the organisation that they are the technology lead for?</p><blockquote>Not one CIO knew even one flow metric for their organisation</blockquote><p>This is irresponsible.</p><p>I am sure that each CIO will know What, When and How Much. Or think they know. What the high priority items in the book of work are, a set of milestones for them and how much they are going to cost. And I’m sure that the majority in the room would view these as knowable and predictable up front. <em>‘Project Greenfield Silver Bullet, go live date 2nd April next year. The success of business line X depends on it’</em>.</p><p>But, not one of them knew How. How efficiently, how effectively, how quickly they can learn, how quickly feedback can be generated, how quickly hypotheses can be tested, how quickly customer’s needs can be met, how quickly value can be monetised, how quickly teams can stop, pivot, go again, how quickly customer feedback can be acted on, how manual activity has been supplemented with automation removing waste and manual error, how value can be maximised by cutting the tail on low value add features.</p><p>Not one could see if a frequent release cadence is facade of agility, due to long lead times and multiple release streams of work running concurrently with a high cost of context switching (for example, monthly releases with 6 streams running concurrently, each with a 6 month lead time, each staggered by one month). From the perspective of the recipient of the change, the lead time is not agile, it’s 6 months from the point of commitment (never mind how long it’s been in the wishlist for).</p><p>Or the movement over time. How better or worse their areas are at How they do What they do. A vector metric, showing a trend. How well a process of constant improvement is removing constraints in the system of work, how limiting work in process is reducing lead time and increasing throughput of the most valuable features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*0QqRZZFx092Y5_T-Kb1HEA.jpeg" /></figure><p>Not one was able to correlate an improvement action to a flow metric. Or conversely to see the impact of a cost cutting initiative, the increase in hidden costs, slowing time to market, increasing lead time, slowing responsiveness, reducing throughput.</p><h3>Focus on Flow, Quality and Happiness</h3><p>Focus on Flow and everything else tends to fall into place. That is, sustainable Flow by addressing the system of work, not unsustainable flow by working people harder, at the expense quality or happiness.</p><blockquote>‘A bad system beats a good person every time’, W. Edwards Deming</blockquote><p>Costs tend to drop away, as impediments, inefficiencies, constraints in the system need to be resolved to achieve flow. Bureaucratic processes need to be made lean. Quality tends to rise, as repetitive tasks are automated, as quality shifts left and as the change deltas become smaller, it’s complexity that can fit in your head. To enable flow, blue-green deployments are implemented. There are more independently deployable components with bounded contexts. The blast radius is smaller.</p><h4>Sustainable Flow with high Quality, engaged Colleagues and delighted Customers</h4><p>The goal is to sustainably reduce lead times, increase quality and increase colleague &amp; customer happiness (measured via surveys and Net Promoter Scores). These should be measured as trends, as everyone’s context and starting point is unique. And made visible to as many people as possible, especially senior leaders in the organisation. It leads to the right questions being asked.</p><p>A focus on a positive trend, then also tends to lead to a Kaizen process of constant improvement. Inspect and adapt. What level do we pull now to improve, is there a broader organisational impediment which we can shine a light on with data.</p><p>A great thing about Flow metrics such as end to end Lead Time, a Cycle Time per step in the process, Throughput, Release Cadence and Flow Efficiency (time work is worked on / elapsed time) is that they are aggregatable, they are distributions, can be averaged, percentiles can be calculated and vector metrics calculated. And it is hard, empirical data, which is difficult for leaders with their heads in the sand to argue against. It shines a light on the reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*OlV2xrwGEUcM8GWg." /></figure><p>Note that I don’t include story point based velocity in the category of Flow metrics, as it is meaningless outside of the team and even then is of questionable value over story counting, where all stories are approximately the same size and will have regression towards to the mean.</p><p>Anything can be done badly. Flow done badly is unsustainable, it’s working people harder, it’s not quality-first, it’s not limiting work in process, it’s asking teams to increase flow without fixing the broader system of work. This was evidenced in the <a href="https://puppet.com/resources/whitepaper/state-of-devops-report">2017 State of DevOps Report</a> showing that lower performers had increased release cadence and reduced lead time from the 2016 survey, however had slower recovery times and higher failure rates than the higher performers.</p><h3>Empower Teams and Leaders to Continuously Improve</h3><p>In addition to shining a light on the Flow, Quality and Happiness and the trends of them over time, and ensuring that this data is transparent and visible, teams and leaders should be empowered and expected to have a <a href="https://en.wikipedia.org/wiki/Kaizen">Kaizen </a>process of constant improvement. Progress is evidenced via the Flow, Quality and Happiness vector metrics.</p><p>Empowered &amp; expected to dig into the data, to visualise the work in the system at many levels, to run experiments, to pull one lever (for example, CI, TDD, co-located feature teams, a less bureaucratic portfolio management process, less WIP) and to see the impact on Flow.</p><p>Empowered &amp; expected to run Observe, Orient, Decide, Act (<a href="https://en.wikipedia.org/wiki/OODA_loop">OODA</a>) loops and <a href="http://www-personal.umich.edu/~mrother/The_Improvement_Kata.html">Improvement Katas</a>.</p><h3>‘Valuetivity’</h3><p>There is one more measure which is critical which is Value.</p><p>A team or a department or a business can have great Flow, Quality and Happiness, within their constraints of budget and location, but they are doing a great job of producing something which is of little value.</p><p>Productivity is defined as <em>“the effectiveness of productive effort, especially in industry, as measured in terms of the rate of output per unit of input”</em></p><p>But, we don’t just want output being churned out. Sometimes we want to reduce productivity in order to innovate, to do a gemba walk, to sit and talk with customers, to learn, to reflect.</p><p>We want ‘Valuetivity’. We want to maximise the value curve, most value first, then cut the tail. This will be a topic for a future post.</p><p>In summary, make sure you Know Your Flow.</p><p>Flow. Quality. Happiness. Value.</p><p>See also: <a href="https://medium.com/@jonathansmart1/agile-manifesto-values-add-on-for-large-enterprises-f3fdc1abcd65">Agile Manifesto Values add on for large enterprises</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a436eb7c8af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sooner-safer-happier/know-your-flow-a436eb7c8af">Know Your Flow</a> was originally published in <a href="https://medium.com/sooner-safer-happier">Sooner Safer Happier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>