<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Denis Tuchin, Agile Coach on Medium]]></title>
        <description><![CDATA[Stories by Denis Tuchin, Agile Coach on Medium]]></description>
        <link>https://medium.com/@denistuchin?source=rss-83fa96cd844b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_MUYV69q045etofzN3jK5Q.jpeg</url>
            <title>Stories by Denis Tuchin, Agile Coach on Medium</title>
            <link>https://medium.com/@denistuchin?source=rss-83fa96cd844b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:52:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@denistuchin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Learning Canvas: More Than a Canvas — A Facilitation Framework for Learning and Growth]]></title>
            <link>https://denistuchin.medium.com/learning-canvas-more-than-a-canvas-a-facilitation-framework-for-learning-and-growth-65c20ba030fa?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/65c20ba030fa</guid>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[self-learning]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[collaborative-learning]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 13:52:38 GMT</pubDate>
            <atom:updated>2025-12-13T13:52:38.903Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Learning Canvas: More Than a Canvas — A Facilitation Framework for Learning and Growth</strong></h3><p>Today I want to consider the unfairly forgotten tool the <strong>Learning Canvas.</strong> It is one of those canvases which are not just templates to write down the information, but a facilitation guide. Originally designed to get workers together who shared an interest in the same subject, but were from different backgrounds or from different organisations. But also it could be fresh format for Agile Retrospective</p><h3>🌱 What Is the Learning Canvas?</h3><p>The <strong>Learning Canvas</strong> is a part of <a href="https://management30.com/">Management 3.0</a>. This canvas is a simple yet profound visual tool designed to help groups reflect, share insights, and define next actions.</p><p>It contains guiding sections such as:</p><ul><li><strong>Problems/Symptoms</strong> — details about the topic we are discussing</li><li><strong>Stories/Experience</strong> — how participants solved same problems in their backgrounds</li><li><strong>Ideas/Suggestions</strong> — ideas how to solve problem</li><li><strong>To Try</strong> — concrete next steps</li></ul><p>At first glance, it looks like another canvas. But if you look deeper, you’ll realize it’s actually a <strong>ready-made facilitation guide</strong>. Each section corresponds to a facilitation step, leading participants through a flow of <em>problem</em> <em>→ experience → insight → action</em>.</p><h3>🎯 Why It’s More Than Just a Canvas</h3><p>A typical canvas helps you fill boxes. The Learning Canvas helps you <strong>facilitate transformation</strong>.<br> It provides:</p><ul><li><strong>Built-in psychological safety</strong> — participants focus on shared learning, not blame.</li><li><strong>Structured reflection flow</strong> — ideal for both teams and large groups.</li><li><strong>Clarity of outcomes</strong> — the result is always an actionable backlog.</li></ul><p>When used with skilled facilitation, the Learning Canvas naturally encourages curiosity, collective ownership, and continuous improvement — three essential elements of an Agile culture.</p><h3>🧭 How to Use the Learning Canvas</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8aE-V7JmnmpaEEiLgyl-Eg.png" /></figure><ol><li><strong>Define the purpose.</strong> Why is this meeting (or conversation) happening? Use that answer to formulate the <strong>theme</strong> of your canvas.</li><li><strong>Identify the roles.<br></strong>The <strong>Asker</strong> — the person who brings a question, challenge, or topic for reflection.<br>The <strong>Sharers</strong> — participants who contribute stories, experiences, and ideas.</li><li><strong>Set timeboxes.</strong> Give the Asker time to describe the problem and their vision of a desired outcome (filling in the <em>Expected Results</em> section).</li><li><strong>Invite stories and ideas.</strong> Sharers contribute real examples and practical suggestions.</li><li><strong>Wrap up with action.</strong> The Asker collects the most relevant stories and ideas and moves them to the <em>To Try</em> section — turning insights into concrete next steps.</li></ol><p>This simple structure turns any meeting into a meaningful learning experience — fast, focused, and deeply human.</p><h3>💬 How to Use It in Agile Community Events</h3><p>Community events like <strong>Agile Meetups</strong>, <strong>Lean Coffee sessions</strong>, or <a href="https://agilegatherings.com/agile-intervision-a-peer-coaching-format-for-sustainable-growth/"><strong>Agile Intervisions</strong></a> often bring together people from different teams, roles, and even companies. The challenge? Everyone has diverse experiences, yet you want to build <em>shared learning</em>.</p><p>Here’s where the Learning Canvas shines:</p><ol><li><strong>Kick off with a shared experience</strong> — for example, “How to launch OKR in a company?” or “How to convince a team to conduct Retrospectives every Sprint?”</li><li><strong>Split into small groups</strong> — each fills the canvas from their perspective.</li><li><strong>Harvest insights collectively</strong> — group representatives share insights and next steps of their groups</li></ol><h3>🔁 Using the Learning Canvas for Retrospectives</h3><p>In team retrospectives, the Learning Canvas can replace or enrich traditional formats like “Start-Stop-Continue” or “Mad-Sad-Glad.”</p><p>It could be used for Theme Retrospective or for <a href="https://agilegatherings.com/agile-futurespective/">Agile Futurespectives</a>. When you define the topic what you want to discuss as a team you may use the Learning Canvas for this</p><ol><li><strong>Problems/Symptoms</strong> — current situation</li><li><strong>Stories/Experience</strong> — experience of team members from previous teams.</li><li><strong>Ideas/Suggestions</strong> — how the team can improve the current situation.</li><li><strong>To Try</strong> — the first steps to implement ideas and suggestions from the previous section.</li></ol><p>Unlike a one-time retro board, the Learning Canvas builds a <strong>long-term learning journey</strong>. Each iteration connects to the previous one — helping the team grow consciously, not just reactively.</p><h3>🌍 Bringing It All Together</h3><p>The Learning Canvas isn’t just another template to fill out. It’s a <strong>facilitation compass</strong> that helps Agile communities and teams continuously learn and evolve.</p><ul><li>For <strong>Agile Intervision groups</strong>, it structures deep professional reflection.</li><li>For <strong>Agile community events</strong>, it captures shared insights and fuels collective growth.</li><li>For <strong>Team Retrospectives</strong>, it connects reflection to learning and experimentation.</li></ul><p>In a world where “continuous learning” is often more slogan than practice, the Learning Canvas offers a practical way to make it real — one conversation at a time.</p><p><strong>Want to try it?<br></strong>Download a <a href="https://docs.google.com/document/d/1k6jmMEMkHCw24kiCFOk7aZS3sRP3rjGq2BMvhbP5Msw/edit?usp=sharing">printable template</a> or use <a href="https://miro.com/templates/learning-canvas/">Miro template</a> and use it at your next Agile event or Retrospective. Start with curiosity, end with action — and see how learning becomes your team’s competitive advantage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65c20ba030fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Intervision: A Peer Coaching Format for Sustainable Growth]]></title>
            <link>https://denistuchin.medium.com/agile-intervision-a-peer-coaching-format-for-sustainable-growth-687d2ad614f1?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/687d2ad614f1</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Fri, 04 Jul 2025 08:29:57 GMT</pubDate>
            <atom:updated>2025-07-04T08:29:57.634Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>As Agile Coaches, we spend most of our time supporting others — but who supports us?</strong></p><p>In the emotionally demanding world of facilitation and transformation, it’s easy to feel isolated. You hold space for retrospectives, mediate between teams and management, and act as a mirror for organizational dysfunction. But where do <em>you</em> reflect?</p><p>Several years ago I found a great solution: <strong>Agile Intervision</strong>. It’s a lightweight, peer-based format designed specifically for Scrum Masters and Agile Coaches to support each other — without hierarchy or value judgment.</p><h3>What is Agile Intervision?</h3><p>Agile Intervision is a peer consulting practice where participants bring real work challenges into a structured, time-boxed meeting for exploration. It’s built on three principles:</p><ul><li><strong>Equality</strong> — everyone is a peer; there are no more or less important participants.</li><li><strong>Safety</strong> — judgment is off the table.</li><li><strong>Clarity</strong> — structure helps keep the conversation useful and focused.</li></ul><p>Each session revolves around a “case owner” who shares a challenge. The group listens, reflects, and offers ideas — but only when invited. This isn’t a coaching fishbowl or therapy session. It’s mutual reflection with intent.</p><h3>Why It Works</h3><p>“What happens in Vegas stays in Vegas” — the number one rule of Intervision.</p><p>That means you’re free to be honest. Bring the messy team dynamics, the stakeholder standoff, the retro that didn’t land. Sometimes you’ll get advice, but sometimes you will get insight.</p><p>More reasons to give it a try:</p><ul><li>🌱 You avoid burnout by <em>not</em> solving everything alone.</li><li>🧠 You sharpen your own thinking by hearing others’ thoughts.</li><li>🤝 You create deeper bonds within your coaching community.</li></ul><h3>Where It Works</h3><p>One of the great things about Agile Intervision is its flexibility. You can run it <strong>internally</strong> within your company — or <strong>openly</strong>, with peers from outside your organization. Both formats have their place.</p><h3>🔸 Internal Intervision</h3><p>This is perfect when you have a network of Agile Coaches, Scrum Masters, or facilitators in your organization. It helps strengthen your internal coaching culture, foster mutual support, and align practices across teams.</p><h3>🔹 Open Intervision</h3><p>This becomes especially valuable when:</p><ul><li>You’re the <strong>only Agile expert</strong> in your company</li><li>You want to escape organizational bias or assumptions</li><li>You need a <strong>fresh perspective</strong> or “outside mirror”</li><li>You’re building a broader professional network</li></ul><p>Stepping outside your company removes unspoken rules and politics from the room. It creates a freer, cleaner space for exploration — and can lead to unexpected breakthroughs in how you see your own context.</p><h3>How a Session Works</h3><p>⏱ <strong>One case = 20 minutes</strong></p><ul><li>🗣 The case owner tells their story and formulates a request (5 minutes)</li><li>❔ Participants ask clarifying questions (5 minutes)</li><li>💡 Participants answer case owner request (8 minutes)</li><li>✅ The case owner makes a summary</li></ul><h3>Rules:</h3><ul><li>Vegas Rule</li><li>Respectness</li><li>Participants avoid evaluations and criticism</li><li>All participants are equal</li><li>The facilitator can moderate the discussion</li><li>The case owner can stop the discussion at any moment</li></ul><h3>Getting Started</h3><p>Want to host your first Agile Intervision?</p><ul><li>✅ Invite 3–12 fellow Scrum Masters or Agile Coaches</li><li>✅ Set ground rules (confidentiality, respect, no critique)</li><li>✅ Rotate roles every session</li></ul><p>If your group is small and meets bi-weekly, a 60-minute format is a solid start:</p><ol><li>10–15 for check-in activities</li><li>Two Intervision session (20+20 minutes)</li><li>5–10 minutes for check-out</li></ol><p>For big groups or if you meet rarely you may need more than one hour for one meeting.</p><p>You don’t need a license or a platform — just intention and presence.</p><p><strong>Online Intervision life hacks</strong></p><p>Remote sessions work beautifully, but they demand <strong>trust</strong>. To help your online group stay connected:</p><ul><li>🎥 <strong>Cameras on</strong> — visual contact builds empathy and psychological safety</li><li>⏰ <strong>Join on time</strong> — be ready before the first case starts</li><li>🔇 <strong>Ensure privacy</strong> — join from a place where others can’t overhear sensitive discussion<br>❌ Avoid: open offices, cafés, coworking spaces<br>✅ Better: private meeting room, quiet home office, or breakout room</li></ul><h3>Final Thought</h3><p>Agile Intervision is more than a meeting format. It’s a practice of care, reflection, and mutual growth. In a world where being the helper often means going unseen, Intervision gives us a place to be seen, heard, and held.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=687d2ad614f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Laloux wrote not about Teal]]></title>
            <link>https://denistuchin.medium.com/why-laloux-wrote-not-about-teal-e22cf70188aa?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e22cf70188aa</guid>
            <category><![CDATA[teal-organizations]]></category>
            <category><![CDATA[integral-theory]]></category>
            <category><![CDATA[reinventing-organizations]]></category>
            <category><![CDATA[spiral-dynamics]]></category>
            <category><![CDATA[frederic-laloux]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Mon, 25 Nov 2024 15:09:00 GMT</pubDate>
            <atom:updated>2024-11-25T15:09:00.277Z</atom:updated>
            <content:encoded><![CDATA[<p>Frederic Laloux, in his book <em>Reinventing Organizations</em>, described a model for organizational development using color-coded levels, advocating for so-called “Teal” organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*Eepff8PF-OkyTOXbBne8Kw.png" /></figure><p>These colors weren’t his invention; they are rooted in the Integral theory (AQAL). However, Laloux made several significant inaccuracies in applying this model.</p><p>Let’s break it down:</p><h3><strong>Everyone’s Bad, But I’m All in Teal</strong></h3><p>Laloux structured his book in a way that positions Teal organizations as the pinnacle of coolness, while all other colors seem less desirable. He backed this up with compelling examples but primarily showcased unhealthy manifestations of the Red, Amber, Orange, and Green levels.</p><p>🤒 <em>You can read more about unhealthy levels </em><a href="https://medium.com/@denistuchin/spiral-dynamics-sprint-retrospective-d73ed6a1ef53"><em>here</em></a><em>.</em></p><p>In reality, many successful organizations operate with healthy Red, Amber, Orange, or Green levels:</p><p>🔴 <strong>Red:</strong> Most successful startups thrive on Red — driven by the energy and charisma of their leaders and the team’s collective hunger to conquer markets.</p><p>🔶 <strong>Amber:</strong> Amber organizations dominate globally, and many are highly successful. Their meticulously structured processes allow them to scale almost infinitely. While growth has its limits, the next level — Orange — helps them push further.</p><p>🍊 <strong>Orange:</strong> Most Fortune 500 companies operate at the Orange level, despite what “Teal” consultants might claim. Their success is rooted in leveraging expertise, ambition, and a drive for new horizons, propelling them to dominate their markets.</p><p>🟢 <strong>Green:</strong> Laloux misrepresents the Green level in his book, but more on this later.</p><h3><strong>Do Teal Companies Even Exist?</strong></h3><p>Here’s the most subtle issue. Without conducting fundamental research like Clare W. Graves or Ken Wilber and relying solely on interviews and case studies, it’s hard to grasp levels beyond your own developmental experience.</p><p>📗 The thing is, what Laloux describes as the Teal level is actually the <em>healthy Green level</em> in the Integral theory. Most of the organizations in his book exemplify this healthy Green stage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_q2Aeij3wsuYqMGu79X8dQ.png" /></figure><p>However, the book does contain examples of genuine Teal organizations, such as <strong>Google </strong>circa 2014* and <strong>Morning Star</strong>. There’s even one example of an actual <a href="https://www.buildingthelifeyouwant.com/blog/an-integral-theory-map">Turquoise</a> company: <strong>Patagonia</strong>.</p><p><em>* According to insiders, Google has since regressed to an Orange level.</em></p><h3><strong>Should You Still Read the Book?</strong></h3><p>Absolutely, yes! You might ask why, Denis — didn’t you just tear it apart?</p><p>The book provides many excellent examples of how Green, Teal, and Turquoise organizations operate and the benefits they derive from their cultures. It’s a great source of examples to share with others. Just be mindful of which companies you label as Green, Teal, or Turquoise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e22cf70188aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Another Scrum Guide]]></title>
            <link>https://denistuchin.medium.com/another-scrum-guide-1689254005ac?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1689254005ac</guid>
            <category><![CDATA[large-scale-scrum]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scaled-agile]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 13:44:34 GMT</pubDate>
            <atom:updated>2024-10-08T12:25:00.060Z</atom:updated>
            <content:encoded><![CDATA[<p>In this July, the <a href="https://less.works/resources/about">authors</a> of the LeSS Framework (<a href="https://less.works/ru/less/framework">Large Scale Scrum Framework</a>) published new <a href="https://less.works/less/scrum-guide">Scrum Guide (LeSS Version)</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*hx3cT--l5r6sHuUoqvtDVA.png" /></figure><p>I wrote below the differences between the LeSS version of the Scrum Guide and the original, but first I will tell the story of its appearance as I know it:</p><p>📖 In 2019, the official <a href="https://less.works/">LeSS Framework website</a> was more or less aligned with the <a href="https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-russian.pdf">official Scrum Guide from 2017</a>, but of course there were some discrepancies</p><p>💡 In 2020, the authors of Scrum, Ken Schwaber and Jeff Sutherland, released another update to Scrum and the <a href="https://less.works/">less.works website</a> began to diverge more noticeably from the <a href="https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf">Scrum Guide 2020</a></p><p>🤗 IBefore this year there were no official communication on <a href="https://less.works/">https://less.works</a>.</p><p>😊 The authors of LeSS found a good way out of the situation, in my opinion: to publish their version of the Scrum Guide, which will be consistent with the <a href="https://less.works/less/framework">LeSS guide</a>.</p><p>🚀 It is important to note here that the LeSS Framework itself, just like Scrum, is not static and is constantly evolving. For example, in March of this year, the <a href="https://less.works/less/rules">LeSS Rules</a> were updated with important comments:</p><p>· Now, all teams are always present at Sprint Planning One, without the option to allow only team representatives to participate (the <a href="https://less.works/less/framework/sprint-planning-one">article about the meeting</a> itself has also been adjusted)</p><p>· In addition, now all teams must be Feature Teams, not the majority, as before</p><p>Official explanation from the authors of the new guide (Bas Vodde and Craig Larman):</p><blockquote>The latest versions of Scrum and LeSS have evolved in parallel, which has led to the fact that the supposed Scrum in Large-Scale Scrum has become a combination of different versions of Scrum, which creates inconsistency and a potentially more complex and less adaptive organization in a multi-team situation.</blockquote><p>🍽 I.e. a kind of <a href="https://en.wikipedia.org/wiki/Fork_(software_development)">Fork</a> was created and now LeSS and Scrum will develop in parallel</p><h3>❓ What has changed in the new guide?</h3><p>The updated Guide is mainly based on the original Scrum Guide 2020, but some parts are taken from the Scrum Guide 2017 and 2010:</p><p>- The authors of LeSS decided to return the focus to the delivery of the product instead of solving any <strong>complex tasks</strong> (problems).</p><p>- The concept of <strong>Scrum Team</strong> has been removed — this is a rollback to the <a href="https://www.qagile.pl/wp-content/uploads/2017/01/Scrum-Guide-Feb-2010.pdf">Scrum Guide 2010</a>.<br>Accordingly, <strong>Developers </strong>again became just <strong>Team </strong>as in 2010 (not even <strong>Development Team</strong> as in 2017).</p><p>- <strong>Sprints </strong>have been removed from the <strong>Events </strong>section and now it is a separate concept. The logic here is quite clear: <strong>Sprints </strong>as an <strong>Event </strong>have always seemed far-fetched. It interesting that in the 2010 version, instead of <strong>Events</strong>, there were <strong>Time-boxes</strong>, and including Sprints in them seemed quite logical.</p><p>- <strong>Product Goal</strong> has been renamed to <strong>Product Vision</strong>. This is a matter of taste, in my opinion.</p><p>- <strong>Product Backlog Refinement (PBR)</strong> has been added to Scrum <strong>Events</strong>, but it is stated that this can be done as a parallel process, not as an event.<br>This is obviously aligning with the <a href="https://less.works/less/framework/product-backlog-refinement">LeSS Framework</a>, because as far as I know, <strong>PBR </strong>(formerly <strong>Grooming</strong>) has never been in <strong>Events </strong>or <strong>Time-boxes</strong>.</p><p>- The wording of <strong>commitments </strong>for <strong>artifacts </strong>has been removed. I remember how fiercely Scrum coaches argued before 2020 that there can be no commitments in Scrum.<br>Apparently Bas and Craig still hold this opinion.</p><p>- The <strong>Definition of Done</strong> has been separated into a separate section and is worded as an agreement, not a commitment.</p><p>- There are also some minor changes, more related to navigation. Speaking of navigation: the links in the table of contents does not work correctly in the PDF version. In the <a href="https://less.works/less/scrum-guide">online version</a> everything is fine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1689254005ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to sell OKR to employees?]]></title>
            <link>https://denistuchin.medium.com/how-to-sell-okr-to-employees-417246d63a8a?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/417246d63a8a</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[objective-and-key-results]]></category>
            <category><![CDATA[objectives-key-results]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Fri, 12 Jan 2024 15:35:42 GMT</pubDate>
            <atom:updated>2024-01-12T15:35:42.421Z</atom:updated>
            <content:encoded><![CDATA[<p>When my colleague and I started implementing the OKR goal-setting system in one company, we found that there are a lot of articles, books, and trainings on the market, that talk about the benefits of OKR for top management, but nothing about the benefits of OKR for middle and line management. And we had to invent our own training for them from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ATVEQJcJ-F8IfcmE.jpg" /></figure><p>Do you know what will happen if you try to tell the <strong>line management</strong> the same advantages of OKR as in a training for top management? We foolishly tried and got strong hate from Product Owners, who decided that now they would be forced to work 30% harder. Of course, we didn’t say anything like that, they just have a different prism of perception.</p><p>Exactly for the same reason why you tell why you are implementing any other change in the organization: if employees do not understand how this innovation will make their life easier, then they will actively or passively resist changes, even if it is obvious to you that the change will be useful for them.</p><h3><strong>Do you know why you need to sell OKR to employees?</strong></h3><p>To understand what OKR can be useful for middle and line management, we used the Design Thinking practice “stand in the customer’s shoes” and here’s what we got:</p><p><strong>1.</strong> <strong>Focus </strong>on a small number of goals and not run in 10 directions at once.</p><p><strong>2.</strong> Be able to <strong>adjust</strong> quarterly and annual <strong>goals</strong> if you guessed wrong when setting them.</p><p><strong>3.</strong> Have the opportunity to <strong>set goals</strong> for your department/product <strong>yourself</strong>, and not just receive them “from above”, as well as the opportunity to adjust the goals dropped from above, if they are too detached from reality.</p><p><strong>4.</strong> <strong>Understand the directions of business </strong>development in general and a specific product in particular.</p><p><strong>5.</strong> Plan work that depends on other departments of the company together with these departments to increase predictability and <strong>reduce stress from emergencies</strong>.</p><h3><strong>Especially for Product Owners, it was also:</strong></h3><p><strong>6.</strong> Move away from the race to achieve KPI and focus on <strong>generating ideas for multiple growth</strong>.</p><p>With such messages, the training went great. After that, we formulated OKR, initiatives, and noted dependencies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=417246d63a8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bonuses and OKRs]]></title>
            <link>https://denistuchin.medium.com/bonuses-and-okrs-99e736828b6?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/99e736828b6</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[objective-and-key-results]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Sun, 24 Sep 2023 14:05:18 GMT</pubDate>
            <atom:updated>2023-09-24T14:09:48.700Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the most often questions about OKRs is how to connect Performance Management and OKRs. Or even more straitly: how to pay bonuses according to achieving Objectives.</p><p><strong>OKR </strong>or<strong> Objective and Key Results</strong> are a goal-setting methodic which was invented by Intel in the 1970s. It has gone through two rebirths in 1999 and 2017 and is becoming a de facto standard of goal setting in companies worldwide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n9aHqQ99ZxIkveiN" /></figure><p>One of the main benefits of OKR is the <strong>inspiring effect</strong> of Objectives. Among other things, this is also achieved by the ambition of OKRs: when you set OKRs, you must be sure that you will reach the goal by 60–70% of the target value. That means if you achieved OKR by 60–70%, then you did your work well enough, and if achieved OKR by 100%, then you did your work exceptionally well.</p><p>💡 But the trick is that it’s always worth striving for better results, trying something new, and seeking beyond the familiar. And here we come very close to the issue of <a href="https://youtu.be/mw29EE2GWlg?t=1040">monetary motivation</a>.</p><p>We all know that if an employee’s <strong>bonus amount depends on</strong> <strong>how well the goals are achieved</strong>, the <strong>employee will</strong> consciously or unconsciously <strong>lower their targets</strong> to a comfortable level to ensure they reach them. Even if we tell them that they will receive a bonus if they achieve 60%, they will just normalize the goal to 60%. For example, if they know they can easily achieve revenue of 50 million and likely even exceed it, under classical KPI, they will set the goal at 50 million💰. However, under OKR, they will set their target at 84 million and easily achieve 60% of it (approximately 50 million). So, all the ambition we wanted is nullified when the bonuses depend on OKRs.</p><p>Some of you may argue, “Well, nothing stops them from trying to earn more!”</p><p>That’s true, but there are a couple of observations:</p><p>1. It really depends on the individual. If the person is naturally ambitious, they will strive for overachievement. Unfortunately, not everyone is like that; others may relax a bit and not aim for higher levels once they reach their target. In this case, overambitious OKRs serve as a psychological trick to stimulate the pursuit of higher achievements. It may not be a 100% foolproof trick, but it still helps.</p><p>2. A more critical point is that to achieve significantly more than what’s within the <strong>comfort zone</strong>, simply working harder is usually insufficient. It requires trying new approaches, taking risks with time and money, and consequently, in case of failure, one may not even achieve those coveted 60–70%.</p><p>Therefore, even if we have a highly ambitious employee who works diligently, they will consistently achieve around 80% but are unlikely to ever reach 100%. Simply because they will be afraid to take significant risks and try something new. So, in effect, instead of OKRs, you get the traditional KPIs, and bonuses you will pay for reaching 60%, not the usual 100%.</p><p>🏔 On the other hand, if we detach bonuses from the percentage of goal achievement, the same ambitious employees will be willing to take bold experiments. What can this lead to? Sometimes they may achieve only 40% of the OKR simply because not all their experiments will be successful, but other times they may skyrocket to <strong>180% due to growth-oriented approaches</strong>.</p><p>So, if we understand that it’s harmful to link monetary motivation to OKRs, two questions remain:</p><p>1. How do we motivate people to <strong>work most effectively</strong>?</p><p>2. How do we handle <strong>bonus payments</strong> then?</p><p>Researchers such as Peter Drucker, Carnegie Mellon University 🏛 , and many others already addressed both of these questions in their studies, even in the last century, but I’ll provide a brief summary.</p><h3>Motivation</h3><p>Studies have shown that monetary motivation works well only for tasks that are fairly mechanical and don’t require a highly creative approach. For example, it can work in assembly line work following instructions, or scripted sales. But when it comes to creating new products, conquering significant market parts, and similar cases, the approach “just work harder” unfortunately doesn’t work.</p><p>In such situations, non-monetary — intrinsic — motivation works better. In Dan Pink’s book 📕 “<em>Drive: The Surprising Truth About What Motivates Us</em>” identifies three major factors: <strong>inspiring purpose</strong>, <strong>autonomy</strong>, and <strong>mastery</strong>.</p><p>The OKR system indeed strongly supports the first two factors.</p><p>“🎯 <strong>OKRs</strong> <strong>should</strong> <strong>inspire employees to achieve</strong> and help them understand how and what their goals impact when achieved.</p><p>The approach of bi-directional goal-setting, where teams independently set 60% of their objectives, ensures the <strong>autonomy</strong> factor for these teams.</p><p>At this point, any experienced manager may wonder: “I’ve provided intrinsic motivation, but the <strong>employee still underperforms</strong>. How can OKR help me?”</p><p>OKR won’t help in such cases… However, the problem is that de-bonusing won’t help either.</p><p>In such situations, I always meet with the employee <strong>one-on-one</strong> and try to understand, in a trusting conversation, what the reasons might be. The reasons can be very diverse, but in most cases, it’s within your power to address these issues or assist the employee in resolving them. For one of my employees, a series of three conversations led to a <strong>20-fold increase in productivity</strong>, and this was a programmer, not a salesman.</p><h3>Bonuses</h3><p>If we’ve addressed motivation, how do we handle bonus payments?</p><p>According to research, the only way to pay bonuses that can increase motivation for creative work is to <strong>pay them immediately after the goal is achieved</strong>, without waiting for the end of the quarter. However, <strong>never promise bonuses in advance</strong>. In other words, if the employees’ work has generated some extra profits that weren’t anticipated beforehand, it’s worth rewarding that. In general, there are many successful companies on the market that never pay bonuses and still don’t face problems with employee motivation.</p><p>On the other hand, in some industries, regular bonuses are a part of the compensation package. If we say that we’re detaching bonuses from goal achievement, the simplest approach is to include bonuses in employees’ salaries and not bother either ourselves or the employees with it. One big European bank, for example, did just that in 2017.</p><p>📈 There’s still the <strong>annual bonus</strong>, which depends on the financial performance of the company. Here, too, it’s straightforward: some portion of the company’s profits is distributed among employees proportionally to their salaries.</p><p>I know that it’s challenging for many managers to embrace the approach of abandoning bonuses as a way to motivate employees, because it is so simple: you manage employee motivation by pressing buttons in an accounting program, almost like in a computer game 🎮</p><p>The problem is that such an approach is highly ineffective, and even if you see that an employee has become more efficient after de-bonusing, it could simply be a result of them learning how to <strong>manipulate the metrics</strong> you use to measure their performance. It’s essential to understand that knowledge workers are quite inventive and readily share hacks with each other on how to cheat the system, especially if they perceive the system as unfair.</p><h3>Conclusion</h3><p>💗 Without this bonus tool, more attention needs to be given to setting and communicating inspiring goals to employees, more one-on-one meetings, and enhancing communication and psychology skills. But it’s worth it. The results are genuinely qualitatively different.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99e736828b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spiral Dynamics Sprint Retrospective]]></title>
            <link>https://denistuchin.medium.com/spiral-dynamics-sprint-retrospective-d73ed6a1ef53?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d73ed6a1ef53</guid>
            <category><![CDATA[spiral-dynamics]]></category>
            <category><![CDATA[team-development]]></category>
            <category><![CDATA[sprint-retrospective]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile-retrospective]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Fri, 08 Sep 2023 17:28:02 GMT</pubDate>
            <atom:updated>2023-09-08T17:49:28.993Z</atom:updated>
            <content:encoded><![CDATA[<p>Did your team solve all the obvious problems? Or maybe there is a burning issue that can’t be solved? Try the <strong>Spiral Dynamic</strong> Retrospective.</p><p>Actually, this is one type of <a href="https://denistuchin.medium.com/agile-futurespective-546d206ccb38">Futurespecrives</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7_A_us9EdvlZxaKJ2Fv3Sw.png" /><figcaption>Image from <a href="https://tmetric.com/spiral-dynamics-theory"><em>tmetric.com</em></a></figcaption></figure><p>Spiral Dynamics is a model that describes what’s most important to people at different stages of their lives. It also helps to understand how you can make a team more productive and motivated.</p><p>Yes, the spiral dynamic is just another model with levels. You may have even come across interpretations of it, such as in <em>Frederick Laloux’s book “Discovering Future Organizations”</em>. But the point here is that the levels in this model are not about achievements, but rather the floors of a building. Each next floor builds on all the previous floors, so no matter how cool you build a new floor, if there are flaws in at least one of the lower floors, all the next floors will crack and crumble.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTXqofYGbdycwWAQDOELtQ.png" /><figcaption><em>The Spiral Dynamics metaphor of a building</em></figcaption></figure><p>These principles are the basis of the Spiral Dynamics retrospective.</p><p>To understand what levels have “cracks,” the team has a <a href="https://docs.google.com/spreadsheets/d/1OqEACxlITobBFZSgHlP5vWfbw28h67pN/edit?usp=sharing&amp;ouid=102729944004328538057&amp;rtpof=true&amp;sd=true">little questionnaire</a>. There are 21 statements that need to be rated on a scale of 0 to 10. In my experience, this questionnaire takes 10–20 minutes to complete.</p><p>It is better to fill it out before the Retrospective, for example, through Google Forms.</p><p>The layout of the retrospective is fairly standard:</p><ol><li>Any <a href="https://retromat.org/">warm-up</a> you know of that is appropriate for the occasion</li><li>Filling out a questionnaire by team members (if they haven’t done so beforehand)</li><li>Discussing problematic and controversial levels</li><li>Developing an Action plan (for example using <a href="https://denistuchin.medium.com/agile-futurespective-546d206ccb38#196d">Improvement Theme Toyota Kata</a>).</li></ol><p>To analyze the results we take the two most recognizable formulas from mathematical statistics: the average (arithmetic mean) and the standard deviation.</p><p>We will get a file like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CzLk_mILSuIMIHxAvRJ23g.png" /><figcaption><em>Spiral Dynamics Team Diagnosis</em></figcaption></figure><p>📈 The average is counted to see the lagging areas according to the opinion of the team as a whole. If the average is low on any of the questions, it’s worth discussing.</p><p>📊 The standard deviation is counted to see where there’s a big spread between team members. This is also something to talk about, even if the average score is high, as in line 14 in the picture.</p><p>To discuss the problem areas identified, you can again choose any facilitation format you know: brainstorming, stacking, 5 why, etc. In the end, be sure to record the first steps the team will take in the next sprint to change the most problematic areas.</p><p>⚠️ Warning: If the team is not very mature or suffers from learned helplessness syndrome for some reason, its members probably won’t be able to come up with solutions for the most problematic areas. And the Scrum Master needs on the one hand to try to encourage them to be more independent, and on the other hand, probably to take on the role of an impediment remover and help them solve some of the problems they discover.</p><p>⚙️ Example: In the <a href="https://docs.google.com/spreadsheets/d/1OqEACxlITobBFZSgHlP5vWfbw28h67pN/edit?usp=sharing&amp;ouid=102729944004328538057&amp;rtpof=true&amp;sd=true">file</a> on the first sheet the list of questions and fields for entering the results of the questionnaire, and on the second sheet the formulas that read the results from the first sheet.</p><p>📕 If you are interested in the topic of spiral dynamics, you can read more in <em>Don Beck’s book “Spiral Dynamics in Action: Humanity’s Master Code”</em>.</p><p>💬 I’d be glad if you’d write feedback after you’ve tried to host Retro in this format.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d73ed6a1ef53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From simple to complex:
a case study of OKR implementation in a big bank]]></title>
            <link>https://denistuchin.medium.com/from-simple-to-complex-a-case-study-of-okr-implementation-in-a-big-bank-8a716f941ec1?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a716f941ec1</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[okr]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[business-agility]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Sun, 03 Sep 2023 19:10:58 GMT</pubDate>
            <atom:updated>2023-09-03T19:12:40.891Z</atom:updated>
            <content:encoded><![CDATA[<p>We published with <a href="https://okrconsortium.com/">OKR Consortium</a> my <a href="https://okrconsortium.com/case-studies/okr-implementation-in-big-bank">OKR case study of a big bank</a> with 100 tribes and 1000 products.</p><p>This case study outlines the journey of a large universal bank that gradually implemented OKR practices over a period of two years.</p><p>This was a universal bank, which had already operated in an Agile context for four years. However, their goal-setting system lacked the necessary focus on metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oMVwBwz2PeFUGvTe2LZqJQ.png" /></figure><p><strong>Reasons for Adopting OKR:</strong></p><p>The bank decided to implement OKR practices to achieve the following goals:</p><ol><li>Measure progress effectively throughout each quarter.</li><li>Understand the correlation between product efforts and outcomes.</li><li>Establish a clear link between tribe backlogs and objectives.</li><li>Align tribe goals with the company’s overall objectives.</li></ol><p><strong>Sponsorship of the Implementation:</strong></p><p>The implementation of OKRs was sponsored by the Deputy President of the company.</p><p><strong>How were OKRs implemented?</strong></p><p>The implementation of OKRs occurred at four levels: the company level, the business block level, the tribe level, and the product level. The initial rollout of OKRs was focused on revenue-generating tribes. After two cycles, which demonstrated the approach’s effectiveness, the implementation extended to supporting tribes. Setting Objectives and Key Results for revenue-generating tribes was relatively simple, while for other tribes, a methodology was developed to measure their impact.</p><p><strong>Implementation Process:</strong></p><ol><li>Leadership Communication: The Deputy President addressed the entire company during a Town Hall, explaining the purpose of OKRs and the high-level roadmap for implementation.</li><li>Workshops by Agile Coaches: Agile coaches conducted workshops in each tribe, teaching them how to set OKRs using 1–2 product examples from each tribe.</li><li>Independent OKRs Setting: Subsequently, the tribes and the products, with the assistance of Agile coaches if needed, set their own OKRs.</li></ol><p><strong>Ensuring Alignment between OKRs:</strong></p><p>To maintain alignment between OKRs, the following synchronizations were carried out:</p><ul><li>Twice a year, OKRs were synchronized between business blocks.</li><li>Quarterly Business Reviews (QBR) were conducted in each business block to synchronize Objectives between tribes.</li><li>OKR-QBRs were held quarterly within each tribe.</li><li>Monthly OKR Check-Ins between products to ensure consistency not only within the same level but also with the higher-level goals.</li></ul><p><strong>Our Know-how:</strong></p><p>In the first year, a target was set to have at least 60% measurable Key Results. By year-end, direct coaching of the products resulted in achieving measurable Key Results ranging from 70% to 100% for different tribes.<br>The next step was to ensure that at least 60% of OKRs were aligned with the company’s objectives.<br>Finally, beyond the traditional OKR approach, efforts were made to measure the impact of initiatives linked to OKRs in monetary terms.</p><p><strong>Tools Used:</strong></p><p>All OKRs were stored in Jira as Epics.<br>Different levels of OKRs were linked together, and product-level OKRs were connected to real Epics (initiatives) of the products.<br>A dashboard was developed for a quick overview of tribes and products, highlighting cases where:</p><ul><li>Less than 60% of OKRs were linked with higher-level OKRs.</li><li>Less than 60% of the backlog was related to OKRs.</li></ul><p><strong>Challenges faced during implementation:</strong></p><p>During the OKR implementation, several products were discovered to be in development based on the request of some top managers. However, neither the Product Owner nor the Tribe Lead could formulate OKRs for these products. These problematic products were flagged on the dashboard, and after board inspection, OKRs were formulated for some of them.</p><p><strong>What Would We Do Differently?</strong></p><p>At the start of the implementation, we could dedicate more time to educating the board members on OKR principles and practices.<br>Also, we could provide more assistance in setting business block-level OKRs.</p><p><strong>Benefits of Implementing OKRs:</strong></p><p>The bank received the following benefits from the implementation of OKRs:</p><ul><li>Reduction in initiatives that were not aligned with the company’s objectives or lacked calculated business impact.</li><li>Enhanced focus of tribes and products on a limited set of goals.</li><li>Abandonment of products that were not aligned with the company’s objectives or had a lower business impact than their costs.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a716f941ec1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Futurespective]]></title>
            <link>https://denistuchin.medium.com/agile-futurespective-546d206ccb38?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/546d206ccb38</guid>
            <category><![CDATA[agile-retrospective]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Sat, 04 Feb 2023 16:08:31 GMT</pubDate>
            <atom:updated>2023-09-08T17:44:12.114Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile Futurespective</h3><p>Long-lived Scrum teams very often meet with the situation when they resolve all problems that they can. In this case, the team could be frustrated about the usefulness of Sprint Retrospectives because these don’t help and just waste time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*hm3jFeM2GcBkbtlqKhkY1Q.png" /></figure><p>When you have this challenge, you could try Futurespective instead of the Retrospective.</p><p>In Retrospective, you see back in past and try to understand what we can do better. Bun in Futurespective you see forward in the future and think about what you want to achieve in the effectiveness and quality of your work. It is a different perspective and it could uncover your team’s hidden potential.</p><p>Today I’ll give you a common plan for most Futurespectives and several Futurespective formats which I like</p><p>The common steps to conduct an Agile Futurespective are:</p><ol><li>Meeting check-in</li><li>Presenting the new format of Sprint Retrospective</li><li>Gathering data</li><li>Deciding what we want to improve</li><li>Improvements goal setting</li><li>Making an improvement plan</li></ol><p>Let’s consider all steps in detail</p><h3>1. Meeting check-in</h3><p>Usually, meeting check-in is quite similar to a simple Retrospective. You just have to ensure that every team member is willing to participate actively in the meeting. You could use almost any Retrospective check-in, for example, <a href="https://agilepinoy.wordpress.com/2020/02/18/everything-retrospective-check-in/#:~:text=Check%2Din%20activities%20are%20a,conversation%20starters%20for%20the%20group.">from here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*_wwtbs-uJjVEVs3Y-4ZOdw.png" /><figcaption>Associative cards check-in</figcaption></figure><h3>2. Presenting the new format of Sprint Retrospective</h3><p>This a very important step when you start any new Retrospective format with your team. You have to explain why you decide to use this format, what profit the team will get and what participants will do during the session. There is no rocket science, but many Scrum Masters forget to tell why he/she bring this new format and the team may have skepticism or even resistance against the new format.</p><h3>3. Gathering data</h3><p>Here are starting main differences in conducting Futurespective.</p><p>By and large, there are only two kinds of Futurespectives:</p><p>3.1. Any type of team assessments</p><p>3.2. Just free fantasy about the future</p><h3>3.1. Futurespective by assessment</h3><p>There any many variants of Agile team assessments. Here are just 5 examples that I like</p><ul><li><a href="https://engineering.atspotify.com/2014/09/squad-health-check-model/">Squad Health Check by Spotify</a></li><li><a href="https://denistuchin.medium.com/spiral-dynamics-sprint-retrospective-d73ed6a1ef53">Spiral Dynamics Sprint Retrospective</a></li><li><a href="https://www.teamretro.com/health-checks/team-radar-online-tool-teamretro">Team Radar</a></li><li><a href="https://agilityhealthradar.com/team-health-radar-assessment/">TeamHealth Radar Assessment</a></li><li><a href="https://www.thevirtualagilecoach.co.uk/post/the-5-dysfunctions-retro-patrick-lencioni">The 5 Dysfunctions Retro</a></li><li><a href="https://www.gallup.com/workplace/356063/gallup-q12-employee-engagement-survey.aspx">Gallup’s Q12 Employee Engagement Survey</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*qw_qEiev5N5LUrZX0kRVFw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*4fZ6nmn3x4FqyKf9oWnD2w.jpeg" /><figcaption>Squad Health Check by Spotify and Gallup’s Q12</figcaption></figure><p>You could collect data before Futurespective or directly during it. If you have enough time at the session it is better to gather data during it because you can explain some unclear questions and it will be guaranteed every team member participates in the survey. In case when you need to do some analyses after the survey of course you have to gather data before Futurespectivet.</p><h3>3.2. Just free fantasy about the future</h3><p>Actually, you can use any idea-generation technique, but for a fast start and structuring ideas, you may use one of the <a href="https://www.funretrospectives.com/category/futurespective/">Futurespective formats</a>. I use this type of Futurespective usually before Christmas:</p><ol><li>Team members write wishes about the work context. I ask them to imagine everything is possible. After that, they stick their wishes under the Christmas tree.</li><li>And at the Retrospective after Christmas team think about how to get closer to wish fulfillment.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*kOI9apYcN5lJe6r1DNzpjw.png" /><figcaption>Christmas Agile Futurespective</figcaption></figure><h3>4. Deciding what we want to improve</h3><p>When you get some data, the team has to decide what they what to improve for now. You could use any method of team decision-making: <a href="https://en.wikipedia.org/wiki/Dot-voting">dot voting</a>, <a href="https://patterns.sociocracy30.org/consent-decision-making.html">consent</a>, etc.</p><p>You could ask why not choose the worst metric from data gathering. Because it is not always the most terrible thing that could be resolved by the team. But you as a Scrum Master of course have to notice that and ask the team do they need help with this from management or someone else.</p><p>The team could choose 1–3 topics to improve. It is about focus because if you have a few things to improve, you will succeed faster.</p><h3>5. Improvements goal setting</h3><p>When have chosen what to improve you need to set goals about it. I like to make global goals for the year and mid-time goals for the quarter. Of course, you should do this with the team, precisely, you should help the team to do this by themselves. I love to use Improvement Theme Toyota Kata for goal setting. It also includes the next step of Futurespective (Making an improvement plan).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*XjRLau4G6m6vkpgx0daGZA.png" /><figcaption>Improvement Theme Toyota Kata</figcaption></figure><p>Here <br> <strong>Team Definition of awesome</strong> is the year’s goal, <br> <strong>Near targets</strong> are the quarter’s goals, <br> <strong>Next steps</strong> are the plans for the next Sprint.</p><p>Team selected three improvement areas: easy to release, quality, and health of codebase. And they set three year’s goals also — one goal per every area.</p><p>You can read more about Improvement Theme Toyota Kata in <a href="https://blog.crisp.se/2013/05/14/jimmyjanlen/improvement-theme-simple-and-practical-toyota-kata">Jimmy Janlén’s article</a>.</p><h3>6. Making an improvement plan</h3><p>Very many amateur teams forget this step and it is becoming the main reason that team starts to think that Retrospectives are useless, because “we only talk, but do nothing”.</p><p>For success you have to create a plan where every item has these four things:</p><ul><li><strong>What to do</strong> — starts from the verb</li><li><strong>Who will do this</strong> — here may be only volunteer from those present at the meeting</li><li><strong>When it will be done</strong> — sometimes you may skip it if the action will be done before the end of the Sprint</li><li><strong>How to check it</strong> — if “What to do” is quite abstract you have to write some acceptance criteria. For example, “Text and examples will be prepared at the end of the next Sprint”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*S1GqIl5p0Vee3amDa-vaiQ.png" /><figcaption>Next Steps*</figcaption></figure><p>* Names of responsible persons are covered up here</p><h3>After the Futurespective</h3><p>The best practice is to add the <strong>Next steps</strong> to your next Sprint Backlog. It helps to not forget it during a rash of the Sprint.s</p><p>And, of course, you must review the planned <strong>Next steps</strong> at the start of the next Retrospective like the next steps from any other Retrospective. You have to ask the team:</p><ul><li>Was every next step done?</li><li>Why it wasn’t done? (if “No”)</li><li>Did it bring us closer to the <strong>Near target</strong>? (if “Yes”)</li><li>What we should do next to achieve the <strong>Near targets</strong>?</li></ul><h3>Conclusion (of the article)</h3><p>I hope it was helpful to you.</p><p>In a nutshell, Futurespective is not so different from basic Retrospective. You should just use some special practices and tools and, of course, stop thinking that Retrospective is only about solving the problems 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=546d206ccb38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Как отличить красную организацию от оранжевой]]></title>
            <link>https://denistuchin.medium.com/%D0%BA%D0%B0%D0%BA-%D0%BE%D1%82%D0%BB%D0%B8%D1%87%D0%B8%D1%82%D1%8C-%D0%BA%D1%80%D0%B0%D1%81%D0%BD%D1%83%D1%8E-%D0%BE%D1%80%D0%B3%D0%B0%D0%BD%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D1%8E-%D0%BE%D1%82-%D0%BE%D1%80%D0%B0%D0%BD%D0%B6%D0%B5%D0%B2%D0%BE%D0%B9-b75c23fdaeda?source=rss-83fa96cd844b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b75c23fdaeda</guid>
            <category><![CDATA[спиральная-динамика]]></category>
            <category><![CDATA[офис]]></category>
            <dc:creator><![CDATA[Denis Tuchin, Agile Coach]]></dc:creator>
            <pubDate>Mon, 11 Jul 2022 07:30:14 GMT</pubDate>
            <atom:updated>2023-09-11T09:14:16.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*Yti6V1NFRZhsxo-tz3Aavw.jpeg" /></figure><p>Меня часто на тренингах спрашивают: «Чем отличается принципиально красные и оранжевые компании, ведь и те и другие ставят основной целью деньги и выжимают максимум из сотрудников?»</p><p>🔴 Красные выжимают из сотрудников максимум здесь и сейчас.</p><p>🟠 Оранжевые делают так, чтобы выжимать можно было как можно дольше и в рамках трудового законодательства</p><p>Понятно, что фразы несколько однобокие, поэтому давайте разберемся более детально.</p><p>Часто красные и оранжевые — это компании из разных отраслей, где больше применим какой-то один из этих типов управления.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65rT_DKJz3FwcIkt6BA1vg.jpeg" /></figure><p>В красных организациях лидер может начинать день с заряжающей речи, и все рвут когти пока не выгорят на сегодня. Это оправдано обычно в компаниях, где легко заменить сотрудника на нового: низкоквалифицированный труд и несложные (не очень дорогие) продажи. На фото, собственно, кадр из фильма «Волк с Уолл Стрит». Т.е. если сотрудник выгорел — пожалуйста уходи — на рынке труда полно желающих устроится именно в нашу компанию на нашу зарплату.</p><p>Ещё это может быть оправдано как краткосрочная мера, когда нужен мощный рывок на несколько недель или месяцев — тут уже на сколько хватит харизмы лидера и внутренней энергии конкретных сотрудников. Например, на первых этапах стартапа, когда нужно быстро с нуля создать первую версию, чтобы получить следующий этап инвестиций, который позволит уже расширить команду. Тогда высоко квалифицированные сотрудники ночуют в офисе, работают в выходные, забывают сходит на обед, перехватывая фастфуд на ходу. Главное после того, как стартап перешёл на следующий этап инвестиций, лидеру начать перестраивать компанию на синий уровень, чтобы этот рост компании не начал множить хаос отсутствия стандартов и процессов этапа «дикого запада».</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bKfGuiNPzjkUIxhiMqcERQ.jpeg" /></figure><p>В красный компаниях, как правило, чёрная или серая зарплата, потому что это более эффективно (меньше платить налогов), а кроме того, позволяет легко избавится от сотрудника — руководителю нужно просто нужно начать ему выплачивать только официальную мизерную часть з/п, и сотрудник очень быстро сам уйдёт.</p><p>Оранжевое управление распространено в компаниях, где затраты на наём и онбординг сотрудника сравнимы с его полугодовой-годовой зарплатой, а сама эта зарплата, как правило в разы больше зарплат рекрутёров, занимающихся их поиском. Обычно, это высоко квалифицированные специалисты. В таких компаниях применим и синий стиль управления, но здоровый оранжевый даёт, как правило, лучшие результаты. Например, Agile-манифест родился в ИТ-индустрии в 2001 году как раз, в больше степени, как призыв покончить с бюрократией и начать работать на результат.</p><p>С учётом того, что оранжевый лидер прожил синий уровень, он чтит трудовое законодательство и зарплата, как правило, «белая», по крайней мере сейчас в России, потому что это стандарт де факто в высоко квалифицированных индустриях. В 90-х начале 00-х было по-другому — просто государство было больше красное. Оранжевый лидер заботится о сотрудниках, потому что с одной стороны долго и дорого искать нового, если текущий уволится, а с другой стороны увольнение редкого специалиста часто может поставить под угрозу весь проект, на котором он работал.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*pE3XVOlFvjjmJAKM.jpg" /></figure><p>Но заряжающие речи не работают, как с неквалифицированным персоналом и продажниками. Оранжевый лидер вынужден использовать более сложные инструменты восстановления энергии. В офисах оранжевых компаний вы часто встретите кофемашины, спортзалы, а в соцпакеты включены ДМС и консультации психолога. Сотрудникам предлагают скидки на гостиницы, возможность удалённой работы, гибкий график, т.е. всё то, чтобы сотрудник мог как можно дольше отдавать свою энергию компании. Причём всё тоже самое можно встретить и в синих, и в зеленых, и, иногда, в жёлтых компаниях, потому что такие соцпакеты становятся стандартом в некоторых индустриях. Но этого вы обычно не встретите в красных организациях, их лидеры искренне недоумевают, зачем это делать, если можно просто платить сотруднику больше, чтобы он сам себе это всё позволил. Но беда в том, что сотрудники красных компаний загоняют себя так сильно, что у них не хватает времени даже подумать о том, что нужно позаботиться о своём самочувствии и психических силах.</p><p>Увольнение по инициативе руководителя в оранжевых компаниях проходит тоже, как правило, согласно трудовому законодательству. Кроме того, работодатель прежде делает несколько попыток всё-таки замотивировать сотрудника на продуктивность и профессионализм, понимая, что это проще и дешевле, чем найти нового. Может даже оплатить серию коучинговых сессий у внешнего коуча, если специалист действительно редкий и ценный. Обычно сотруднику даётся время на поиск новой работы с сохранением и стажем в трудовой. Такое человеческое отношение свойственно и зелёным организациям, но мотив другой. Оранжевые организации таким способом страхуют себя от скатывания сотрудника до красного уровня, где он может нанести вред бывшему работодателю типо кражи интеллектуальной собственности или негативных публикаций в соцсетях.</p><p>Надеюсь, этой небольшой заметкой смог объяснить основную и наиболее видимую разницу между красными и оранжевыми компаниями. Понятно, что под капотом там намного всё сложнее, начиная, от разницы в глобальных целях компаний, заканчивая системой мотивации, но об этом как-нибудь в другой раз 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b75c23fdaeda" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>