<?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 Myroslava Zelenska on Medium]]></title>
        <description><![CDATA[Stories by Myroslava Zelenska on Medium]]></description>
        <link>https://medium.com/@myroslavazel?source=rss-6409ea8abc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qBPHodqXv345AQnI719VcA.png</url>
            <title>Stories by Myroslava Zelenska on Medium</title>
            <link>https://medium.com/@myroslavazel?source=rss-6409ea8abc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:51:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@myroslavazel/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[The Satir Change Model: Understanding Why Change Feels Like Chaos]]></title>
            <link>https://medium.com/@myroslavazel/the-satir-change-model-understanding-why-change-feels-like-chaos-af1e5a34c86b?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/af1e5a34c86b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Mon, 01 Jun 2026 14:45:40 GMT</pubDate>
            <atom:updated>2026-06-01T14:45:40.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="https://expertprogrammanagement.com/2018/10/satir-change-model/" src="https://cdn-images-1.medium.com/max/640/0*wS0aFKEnbPiW1oRi.png" /></figure><p>In a world that changes rapidly — and in an industry that changes even faster thanks to AI and everything that comes with it — managers spend more and more time looking for opportunities to improve, adapt, and evolve.<br>The challenge isn’t just recognizing the need for change. It’s understanding how to plan and implement change without descending into chaos, resistance, and frustration.</p><p>I’ve previously written about change management through the lens of <a href="https://medium.com/@myroslavazel/approach-to-changes-by-john-paul-kotter-71d62543a49a">John Kotter’s model</a>, but this time, I’d like to talk about another framework that I personally find fascinating. Unlike Kotter’s model, which focuses on the process of driving change, the Satir Change Model focuses on the human side of change — how people experience it and why their reactions often seem irrational from the outside.</p><p>Being a manager, understanding these reactions is critical. In some ways, the model reminds me of Tuckman’s stages of team development. There are also similarities to the Kübler-Ross Change Curve, although the Satir model differs in its ability to help predict how productivity is affected throughout the change process. If you’re familiar with either framework, the general concept will feel familiar.</p><p>The Satir Change Model was developed by family therapist Virginia Satir. Her core belief was that improvement is always possible. She created a transformation framework designed to help people improve their lives by changing how they perceive and express themselves. One element of that framework is a five-stage change model that describes the impact of change on emotions, thinking patterns, productivity, and even physiology.</p><p>Before diving into the stages themselves, it’s worth noting that the Satir model is primarily a tool for understanding and tracking the effects of change, rather than driving it. Without complementary change-management techniques, it becomes more of a measurement tool than a complete implementation strategy.</p><p>The five stages are:</p><ul><li>Late Status Quo</li><li>Resistance</li><li>Chaos</li><li>Integration</li><li>New Status Quo</li></ul><h3>Late Status Quo</h3><p>The first phase represents the current state — the way things are done today.</p><p>At this stage, people are generally not thinking about change because they don’t see a need for it. This is why organizations should encourage creativity, active listening, and continuous learning long before change becomes necessary. People need opportunities to think outside the box and identify potential improvements.</p><p>One helpful approach is storytelling: explain what the future could look like and why it matters. Show how the change aligns with company values. Prepare a communication plan that includes not only tasks and timelines, but also the reasoning behind them.</p><h3>Resistance</h3><p>Change is usually introduced through what Satir called a <em>foreign element</em> — a new technology, a new process, a reorganization, or a different way of working.</p><p>The introduction of this foreign element typically triggers the second stage: resistance. Resistance almost always causes a noticeable drop in productivity, both at the team and individual level. In many cases, this is the first visible sign that people are struggling with the change.</p><p>This is the moment when leaders need to clearly communicate the purpose of the change, define success criteria, and explain the expected value of the future state.</p><p>Listen without judgment. Fear cannot be solved through commands and presentations. Involve people in the process. Change is much easier to accept when people feel they helped create it rather than having it imposed on them from above.</p><h3>Chaos</h3><p>Chaos can occur whether the change is carefully managed or simply happens to people. The Satir model makes an important distinction between changes that are passively accepted — which often leave people stuck in chaos — and changes that are actively embraced and directed toward a positive outcome.</p><p>Regardless of the circumstances, this stage is emotionally intense. Negative reactions are normal. Productivity declines. Confusion increases. The only way forward is to create conditions where people can process what’s happening.</p><p>Ask questions. Listen. Consider introducing support systems such as mentoring, coaching, additional training, or regular check-ins. Acknowledge the difficulty of the transition. Don’t minimize the pain.Most importantly, establish priorities. During chaos, people cannot focus on everything at once. Concentrating on one or two critical areas often produces better results than attempting to solve every problem simultaneously.</p><p>If existing approaches aren’t working, encourage experimentation. At this stage, people need new ideas that help them make sense of the situation. They begin discovering ways to navigate the uncertainty and adapt to the new reality.</p><h3>Integration</h3><p>The recovery phase is called Integration. This is usually the point where productivity starts recovering.</p><p>People begin developing confidence in the new environment. Productivity improves, uncertainty decreases, and enthusiasm gradually returns. This stage requires continued support. Questions should be answered quickly, obstacles removed, and learning reinforced.</p><p>Practice is critical here. New habits and new knowledge only become permanent through repetition and application. Remember: support is more valuable than control. Give people additional time when needed. Allow mistakes. Encourage learning.</p><p>It can also be helpful to create visible rituals of progress: demos, achievement channels, retrospectives, small celebrations, or regular recognition of wins. These moments reinforce the feeling that the change is working.</p><h3>New Status Quo</h3><p>At this point, the change has become the new normal. Acceptance is widespread, teams operate comfortably within the new processes, and productivity should exceed previous levels if the change initiative was successful.</p><p>Celebrate the transition. Don’t immediately rush into the next transformation. Give the team time to enjoy stability and recognize what they have accomplished.</p><p>This stage is not the end of the journey, by the way! Leaders should evaluate the overall impact of the change, identify lessons learned, and create conditions that will make future changes easier.</p><p>Virginia Satir originally developed this model while working with families undergoing significant life changes. In our experience, however, the same dynamics appear in almost any group of people facing uncertainty and transformation.<br>Technology changes. Processes change. Organizations change. People, however, tend to react to change in surprisingly similar ways :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af1e5a34c86b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expectation management in a nutshell]]></title>
            <link>https://medium.com/@myroslavazel/expectation-management-in-a-nutshell-0e8e7ec77314?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e8e7ec77314</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[expectations]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 16:13:21 GMT</pubDate>
            <atom:updated>2026-04-02T16:13:21.477Z</atom:updated>
            <content:encoded><![CDATA[<p>They want something from me… again</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/0*EnaRbFjw17ms2xn2.jpg" /></figure><p>Our main goal as project managers is to <strong>align expectations with reality</strong> — to avoid conflicts and ensure satisfaction with the outcome.</p><p>Honestly, you could do nothing except manage expectations and still be a highly successful manager 🙂</p><p>Even employee motivation<a href="https://medium.com/@myroslavazel/motivation-in-goal-setting-how-it-actually-works-together-387b5726f9df"> (which we recently talked about) </a>— according to <strong>Victor Vroom’s Expectancy Theory of Motivation</strong> — is based on a rational evaluation of three factors:</p><ul><li>belief that effort will lead to results (expectancy),</li><li>belief that results will be rewarded (instrumentality),</li><li>and the value of that reward (valence).</li></ul><p>Even here, everything starts with expectations. As for clients and supervisors — and their expectations — that’s a whole separate story.</p><h3>How do you know you’re failing at this?</h3><p>The easiest signal that something went wrong: people start sliding down <a href="https://medium.com/@myroslavazel/delegation-everyone-knows-about-it-but-not-everyone-does-it-why-438bf0ae912e">the delegation levels</a> — micromanaging, double-checking, over-specifying tasks. If your client pings you for a status update — congratulations, you’ve already messed up.</p><p>One of the most common failures happens when someone clearly communicates their expectations, you don’t object, and they assume you agreed, but you… didn’t.</p><p>At that point, you’re already out of sync. Please, let them know if something is off.</p><p>Here’s a slightly controversial take: people often don’t actually care that much about the result — they care that you’re working <strong>according to their expectations</strong>. And if, from your perspective, those expectations “don’t exist” — your job is <strong>to find them or to create them</strong>.</p><h3>What does it mean to manage expectations?</h3><p>It means bringing someone’s assumptions as close to reality as possible. In practice, it means: think → clarify → understand → discuss → align → and double-check yourself.</p><p>To do that effectively:</p><ul><li>speak the person’s language,</li><li>use agreed terminology,</li><li>ask direct, open-ended questions (not yes/no ones),</li><li>make sure your questions have clear context and purpose.</li></ul><h3>So how do you actually manage expectations?</h3><p><strong>0) Identify expectations</strong> (yes, this is the hardest part — see above)</p><p><strong>1) Every task must have an owner and a clear responsibility area.</strong></p><p><strong>2) The next step must be explicit.</strong><br> Not “we’ll figure it out later”, but: <em>“Bring options to refinement on Tuesday — we’ll decide.”</em></p><p><strong>3) Set a specific time for discussions.</strong><br> Not “I’ll check later”, but: <em>“Let’s review this tomorrow at 10:30 during standup, okay?”</em></p><p><strong>4) Talk not only about what you WILL do, but also about what you WON’T do.<br></strong> This helps eliminate gaps and false assumptions.</p><h3>And the most important part</h3><p>Don’t forget: it’s not only you who has expectations of your team and company.</p><p>They have expectations of you too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e8e7ec77314" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Motivation in Goal Setting: How It Actually Works Together]]></title>
            <link>https://medium.com/@myroslavazel/motivation-in-goal-setting-how-it-actually-works-together-387b5726f9df?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/387b5726f9df</guid>
            <category><![CDATA[goals]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 14:50:48 GMT</pubDate>
            <atom:updated>2026-01-23T14:50:48.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*4FCuSPYChX9Fit1Q.png" /><figcaption><a href="https://blogs.illinois.edu/view/8816/1122591866#image-1">https://blogs.illinois.edu/view/8816/1122591866</a></figcaption></figure><p>Motivation is something we all struggle with. There are tons of trainings, frameworks, and all sorts of… questionable content around it. I’ve even written before about games like <em>Moving Motivators</em> (or maybe not — maybe I will later 😅), about goal setting, etc.</p><p>The real question is how all of this works together.</p><p>A quick reminder:<br> <strong>Management 2.0</strong> is about control and KPIs.<br> <strong>Management 3.0</strong> is about creating an environment where people work because they <em>want to</em>, not because they <em>have to</em>. Management 3.0 is specifically about <strong>intrinsic motivation</strong>, where the focus shifts from external incentives (2.0) to internal ones — a sense of purpose, mastery, autonomy, and satisfaction from the work itself.</p><p>With <strong>mastery &amp; autonomy</strong>, things are more or less clear: give people opportunities for professional growth (courses, KPIs used properly, a safe environment, mentoring etc. etc.), and give them independence (delegation at the level they need — <a href="https://medium.com/@myroslavazel/delegation-everyone-knows-about-it-but-not-everyone-does-it-why-438bf0ae912e"><em>here’s a link to my article about delegation levels</em></a>).</p><p>But <strong>goals</strong> are a source of motivation too. They can trigger powerful self-organization processes, mobilizing both visible and hidden personal resources. Goal setting helps people focus their efforts and create a clear path toward achieving outcomes. Another key motivational aspect at the intersection of <strong>autonomy and goals</strong> is a sense of control. When a person feels they control their life and can make decisions that influence their future, they are far more likely to stay motivated.</p><p>That said, it’s crucial <strong>not to impose goals</strong>, but to involve employees in defining them — or at least to “sell” the goal properly. Otherwise, motivation becomes external rather than internal. That’s not necessarily terrible, but we <em>are</em> talking about modern management practices here, right? 🙂</p><p>That’s why it’s useful to involve teams or individuals in setting goals from the start. This not only helps formulate clearer and more valuable goals by incorporating different perspectives, but also increases motivation and ownership.</p><p>So how do you actually set a motivating goal? In 1990, years after publishing his first article, Edwin Locke teamed up with psychologist Dr. Gary Latham, and together they published the book <a href="https://www.amazon.com/Theory-Goal-Setting-Task-Performance/dp/0139131388"><em>“A Theory of Goal Setting and Task Performance.”</em></a></p><p><strong>Specific and measurable</strong><br>Goals must be clear and measurable (for example, “learn SQL basics in one month” instead of “improve programming skills”). I think you already know <a href="https://medium.com/@myroslavazel/goal-setting-acronyms-do-you-know-all-of-them-smart-pure-clear-smeac-e7afb04d4154"><em>SMART goals (and other helpful acronyms).</em></a></p><p><strong>Defined constraints</strong><br>Clearly define the “rules of the game” and boundaries within which the team can operate.</p><p><strong>High but achievable level</strong><br>Challenging goals are more motivating than easy ones — as long as they don’t feel impossible. Frame the goal as a stretch, but don’t overdo it, or you risk failure. And honestly, the simpler the goal is, the better.</p><p><strong>Confirmation and milestones</strong><br>If a goal is large, distant, and feels like rewards are far away, break it into smaller stages. This makes wins more achievable and allows people to feel proud of progress more often, helping sustain motivation over time.</p><p><strong>Focus on the desired outcome</strong><br>Understanding <em>why</em> (meaning) is more important than <em>how</em> (process).</p><p><strong>Feedback</strong><br>Regularly acknowledging progress reinforces motivation. When reviewing results, always try to identify how even greater progress can be achieved next time.</p><p>Finally, effective goal setting means defining clear, specific, and achievable objectives that align with personal values and long-term aspirations. Setting personal goals increases the likelihood of success and helps maintain motivation. <strong>BUT</strong> — don’t forget to align your motivation system with the company’s strategy and structure. A motivated person is a great player, but if everyone starts pulling the team and/or company in their own direction, things will go south very quickly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=387b5726f9df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Graham’s Hierarchy of Disagreement in Management: Turning Arguments into Useful Feedback]]></title>
            <link>https://medium.com/@myroslavazel/grahams-hierarchy-of-disagreement-in-management-turning-arguments-into-useful-feedback-dc8e6c1f9bc8?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc8e6c1f9bc8</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Wed, 01 Oct 2025 16:25:18 GMT</pubDate>
            <atom:updated>2025-10-01T16:25:18.041Z</atom:updated>
            <content:encoded><![CDATA[<p>Some of you may have seen <strong>Graham’s Hierarchy of Disagreement</strong> before (the pyramid below). It’s usually used to analyze internet debates (aka: comment-section battles), but it’s surprisingly useful in management too. Specifically, in the <strong>feedback process</strong>. The higher up the pyramid you go, the more constructive your disagreement becomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*fSoPnG5Q8280OFM5.png" /><figcaption>From themindcollection.com</figcaption></figure><p>And let’s be real: giving constructive feedback is tricky. Sure, most of us know the difference between a cheap insult and a well-reasoned critique. But the in-between levels? That’s where managers often slip. So let’s break them down:</p><h3>Level 0: Name-Calling</h3><p>Feedback like: <em>“You’re an idiot, I can’t even talk to you.”</em><br> Hopefully, this kind of thing is extinct in our industry. (If not… we need to have another conversation.)</p><h3>Level 1: Ad Hominem (Attacking the Person)</h3><p>A little more sophisticated than name-calling, but still weak. Example:</p><ul><li>Developer: <em>“This isn’t a bug, it’s a feature.”</em></li><li>Response: <em>“Of course he’d say that, he’s the developer.”</em></li></ul><p>Yes, it might feel relevant, but it’s not. If the developer’s reasoning is flawed, point out the flaws. If it’s not flawed, then who cares what their job title is?</p><p>Another classic: dismissing someone because they’re “not senior enough.” But the real question is: <em>Are they right or wrong?</em> If they’re wrong due to lack of experience, highlight the mistake. If they’re right — then seniority doesn’t matter.</p><h3>Level 2: Responding to Tone</h3><p>This is where people start reacting to <em>how</em> something was said instead of <em>what</em> was said. Example:<br> <em>“How dare you speak so arrogantly about our release plan?”</em></p><p>Better than personal attacks, but still weak. The issue isn’t whether someone is blunt — it’s whether they’re correct. I’d rather have a rude-but-right colleague than a polite-but-wrong one.</p><h3>Level 3: Contradiction</h3><p>Finally, we’re addressing content. But the weakest form of it is just saying the opposite without support. Example:<br> <em>“I can’t believe John rejected our release plan so arrogantly. It’s approved by stakeholders and is perfectly fine.”</em></p><p>Contradictions <em>can</em> be useful, but without reasoning they add little.</p><h3>Level 4: Counterargument</h3><p>Now we’re talking! This is where disagreement starts being useful. Counterarguments are contradictions <em>plus reasoning or evidence</em>.</p><p>But here’s the catch: often, people argue about slightly different things. Two team members might be passionately debating, yet they’re not even on the same topic. Sometimes they even secretly agree but are too locked into the “battle mode” to notice. (Hello, conflict management!)</p><p>Pro tip: if you’re shifting the discussion to something else you feel is more important, make that explicit. And please, no <em>“Wikipedia says you can’t release like that”</em> arguments. You’re a manager, not a freshman in debate club.</p><h3>Level 5: Refutation</h3><p>This is where <strong>constructive feedback truly begins</strong>.<br> At this level, you quote or reference the specific behavior/action/decision you disagree with, and then explain <em>why</em> it’s a problem.</p><p>Example: <em>“In last week’s sprint, you skipped peer review on ticket #123. That’s risky because bugs slip through without review. Please make sure we always peer-review before merge.”</em></p><p>Notice: concrete, actionable, evidence-based.</p><h3>Level 6: Refuting the Central Point</h3><p>The most powerful form of feedback is addressing the <strong>core intention</strong> or the root issue.</p><p>Weak refutations often nitpick irrelevant details (formatting errors, typo-hunting, pedantic corrections) just to discredit someone. That’s not helpful.</p><p>Strong feedback identifies the <strong>main problem</strong> and addresses it with specifics.<br> For example:<br> <em>“The main problem with our release plan is that it’s missing rollback steps. Without those, any failure will cause extended downtime. We need to add contingency planning.”</em></p><p>This way, you’re not fixing symptoms — you’re addressing the root cause. That’s how feedback helps people grow, teams improve, and projects actually succeed.</p><h3>So what’s the takeaway?</h3><ul><li>Don’t waste time at the bottom of the pyramid.</li><li>Feedback isn’t therapy, venting, or tone-policing — it’s a tool to fix real issues.</li><li>The higher up you climb, the more valuable your feedback becomes.</li></ul><p>So next time you’re about to say <em>“I can’t believe she said that in such a rude tone”</em> — stop. Take a breath. Quote the actual behavior, find the root issue, and explain <em>why it matters</em>. That’s real feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc8e6c1f9bc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If You Delegate Tasks but Not Power, You’re Doing It Wrong]]></title>
            <link>https://medium.com/@myroslavazel/if-you-delegate-tasks-but-not-power-youre-doing-it-wrong-10b82df39df7?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/10b82df39df7</guid>
            <category><![CDATA[delegation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Sat, 29 Mar 2025 21:39:01 GMT</pubDate>
            <atom:updated>2025-03-29T21:39:01.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/225/0*XVycY6z8uVw4UVbk" /><figcaption><a href="https://www.instagram.com/prthebuilder/p/C17cZfjxgzt/?img_index=1">https://www.instagram.com/prthebuilder/p/C17cZfjxgzt/?img_index=1</a></figcaption></figure><p>I’ve written about <a href="https://medium.com/@myroslavazel/delegation-everyone-knows-about-it-but-not-everyone-does-it-why-438bf0ae912e">delegation</a> before, but I want to highlight one crucial point.</p><p>Some <em>very smart</em> managers claim that you can only delegate tasks. They insist that you don’t delegate authority, responsibility, or problems — just the tasks that previously fell within your area of responsibility.</p><p>That’s simply <strong>not true</strong>. Delegating authority is essential. If you delegate a task, you should also delegate the right to decide how to complete it (assuming you’re working at <a href="https://miro.medium.com/v2/resize:fit:4800/format:webp/1*lLjK1ZJgGjOcB6E0IAD95A.png">delegation levels 5–7</a>, of course).</p><p>Otherwise, giving someone responsibility without authority leaves them unmotivated and powerless. And to me, that’s every manager’s worst nightmare — being held accountable but having zero control. Imagine being responsible for a project but unable to manage people (hire, fire, decide on compensation), set the budget, or define processes. At that point, you’re not a manager — you’re a blindfolded monkey randomly pulling strings, hoping something works.</p><p>Moreover, if you don’t give people authority and decision-making power, they will never grow. Let them learn to communicate, research, and allocate resources. Completing a task with predefined data, distributed resources, and strict constraints doesn’t require much brainpower. Of course, people will mess up at some point — that’s normal. Who hasn’t made mistakes while learning? But that’s the only way to develop real talent. A mid-level employee will never become a senior in a ‘safety net’, senior won’t evolve into a leader, and a leader won’t be able to scale their impact.</p><p>That said, delegation doesn’t mean giving up all your power — you’re simply distributing the <strong>necessary</strong> responsibility and authority required to complete certain tasks <strong>within the organization’s policies and regulations</strong>. And obviously, you can’t delegate authority that you don’t have in the first place. Oh, and the best part? You’re still ultimately accountable!</p><p>So use <strong>common sense</strong>, but don’t be afraid to upskill your teammates!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10b82df39df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Approach to changes by John Paul Kotter]]></title>
            <link>https://medium.com/@myroslavazel/approach-to-changes-by-john-paul-kotter-71d62543a49a?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/71d62543a49a</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Tue, 11 Feb 2025 17:24:24 GMT</pubDate>
            <atom:updated>2025-02-11T17:24:24.232Z</atom:updated>
            <content:encoded><![CDATA[<h4>Let’s start with what change is. As the definition tells us, it is a transition from a certain current state to a certain future state (not always a desirable one, by the way :) ).</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/0*WuPS3_SSFtaffPAw.jpg" /></figure><p>The <strong>reasons for the change desire</strong> in an organization can be different — internal needs, external feedback, the need to respond to market/legislation changes/etc.</p><p>However, <strong>people usually do not like change</strong> (does everyone know that we work according to patterns wherever possible? Daniel Kahneman surely did!). <br>Swiss psychiatrist, Kübler-Ross first introduced her five stage grief model in her book “On Death and Dying”. Everyone knows these stages — denial, anger, bargaining, depression and acceptance. When implementing change, people often experience the same. These stages are not linear and some people may not experience any of them. Yet and still, others might only undergo two stages rather than all five, one stage, three stages, etc.</p><p>Actually, this post is about how to deal with it, or at least alleviate the symptoms for people who are facing change.</p><p>First of all, when you do the transformation — consider that it should be holistic, sustainable, moreover, it should affect the entire organization, changes mindset, change company culture. Tiny pointy changes within one team may work… But only within minor processes and in the case when your team is pretty much isolated. And we are talking about biiig transformation here!<br><strong>What are your main pillars? </strong>Authority, vision, employees and agility. Logically — you need to be authoritative enough and have enough power to implement changes, have a vision for these changes (hopefully everyone remembers <em>“Begin with the end in mind”</em>), involve your employees and be agile if the plan needs to be changed or if something goes wrong.</p><p>There are many transformational models, but I personally like <strong>the model of Professor John Kotter. </strong>He talks about more specific steps on the path to organizational transformation, proposing an 8-step change model. Let’s talk about it in a little more detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/0*AUOdfvuZfcTycdIh.png" /></figure><p><strong>Step 1: Establish a Feeling of Urgency.</strong> According to Kotter, the first step is the most important. The process must begin by creating a sense of urgency among both managers and employees. Everyone involved must feel that change is necessary and that it is critical to organizational growth. If employees are satisfied with the current state of things, it is almost impossible to convince them that something needs to change. Without their support, it will be difficult to maintain the momentum of the change initiative and achieve long-term transformation.</p><p><strong>Step 2: Formulate a guiding coalition. </strong>To do this, it is necessary to identify employees who are most loyal to changes, who have management skills and a similar vision of the future. Ideally, team members should be from different departments and at different levels so that the change leadership team can communicate effectively with multiple employees.</p><p><strong>Step 3: Develop a strategy to bring about change. </strong><em>Begin with the end in mind,</em> again. Important — managers must maintain the execution strategy in line with the company’s vision to help employees achieve their goals. A clear vision of the prospects allows you to quickly make hundreds of intermediate decisions, for which you might have spent an unreasonable amount of time. Vision alleviates the suffering of employees at the initial stages, and charges the energy of the final goal. Vision significantly increases the efficiency of employees, simplifying their coordination. <br>Just remember — clear and realistic goals must be defined that will help to easily measure success and will interest the company’s stakeholders (you might use <a href="https://medium.com/@myroslavazel/goal-setting-acronyms-do-you-know-all-of-them-smart-pure-clear-smeac-e7afb04d4154">SMART or other similar tool</a>, by the way).</p><p><strong>Step 4: Communicate the vision for change. </strong>Communicate vision and strategy as often as possible, incorporating them into daily decision making, problem solving, and action. Your own example + continuous repetition should help! Encourage feedback from employees and address their worries, problems, anger and fears openly and honestly. Stimulate dialogue between managers and employees, as far as dialogue is much more effective than simply accepting information.</p><p><strong>Step 5: Empower employees for taking action to incorporate changes.</strong> Remove barriers and impediments! Barriers can be in the form of insufficient processes, resistance to change from employees, powerless managers, organizational policies and structures, etc. Ensure that organizational processes, structures, policies, reward systems, etc. are aligned with the new vision for change. Recognize and reward employees who actively work to implement the change. Empower employees to do their best and successfully overcome challenges by providing them with the necessary training, coaching, and mentoring.</p><p><strong>Step 6: Formulate and generate short-term goals. </strong>Achieve quick wins. Managers can set short-term goals, and when employees achieve them, they can reward them for their participation in the change process. Nothing changes the history of change as much as specific positive results. In addition, there is a risk of initiating and getting sign-offs for changes if you do not immediately demonstrate positive things.</p><p><strong>Step 7: Capitalize of wins or gains in order to produce bigger results.</strong> Evolve the change. Kotter noted that many changes fail because companies declare success too early, and change is a slow process. The short-term goals set in the previous step are only short-term wins, and the company must continue to adjust the new plan until the vision is realized. It is not enough to change part of the system. It is necessary to change the whole system. Therefore, the change process may require additional activation of the manager’s skills and may stretch over many years.</p><p><strong>Step 8: Incorporate new and better changes in workplace culture.</strong> No matter how successful the changes are, they will degrade to nothing if they are not embedded in the corporate culture. To do this, it is necessary to formalize the norms of behavior, to form a relationship between achievements and rewards. It also involves changing organizational norms and values, processes, reward systems and other infrastructure to ensure that everything is in line with the new direction.</p><p>Changes are inevitable, and it’s up to you whether to embrace them!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71d62543a49a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retrospective - why don’t we like it and how can we love it?]]></title>
            <link>https://medium.com/@myroslavazel/retrospective-why-dont-we-like-it-and-how-can-we-love-it-8813598cbf93?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/8813598cbf93</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[retrospectives]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Thu, 23 Nov 2023 18:43:16 GMT</pubDate>
            <atom:updated>2023-11-23T18:43:16.501Z</atom:updated>
            <content:encoded><![CDATA[<h4>Retrospective — useful thing or useless bullshit?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/174/1*JvwY0LrhLNovtAVv6dRphw.jpeg" /></figure><p>What is a retrospective in general — I won’t describe it now. You can Google it very quickly and from different angles. I’d like to discuss <strong>why your team doesn’t like retrospectives</strong>. Where do these Prisoners come from, <a href="https://www.funretrospectives.com/esvp-explorer-shopper-vacationer-prisoner/">if we take ESVP?</a></p><h4>From my experience, it’s usually <strong>one of the following reasons</strong>:</h4><p>- The team <strong>was given responsibility and not given relevant authority</strong>. They complain about the lack of authority, which becomes an impediment. There is a feeling that either you do write points or don’t do that, nothing changes.<br>- There are<strong> no action points</strong> or they are not done/worked on, the team considers the meeting to be a useless talk, a wasted time.<br>- The team <strong>forgets all the points during the sprint</strong> (before the start of the retrospective). What happened on the third day of the sprint, no one remembers till the 10th day.<br>- The team thinks that all the <strong>retrospective is about complaining</strong>.<br>- <strong>The team does not trust each other</strong> and the scrum master; the customer is present at the retro and the team does not know what can and cannot be said in their presence.</p><h4><strong>What are we able to do with these?</strong></h4><p>- Try<strong> </strong><a href="https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/"><strong>ice breakers </strong>and interactive exercises</a>. When people are willing to have a conversation, it will happen.<br>- <strong>Anonymity</strong> of points helps sometimes (especially when there is a lack of trust in the team).<br>-According to the rules, there should be <strong>no customers or other teams</strong> at the retrospective, such meetings with them can be held separately if necessary (like scrum of scrums, but retro of retros).<br>- Emphasize that <strong>retrospective is not just about complaining</strong>. Start introducing the practice of Kudos, of what went well. Write down these points yourself the first 2–3 times.<br>-Create a <strong>board for the next retrospective right after the previous one</strong>. When something happens (good or bad), remind the team to put a point on the board right away, so they are able to get used to it.<br>- Do not forget about <strong>action points</strong> (use SMART if you can). They should be recorded, and like any task, should have a responsible person and a deadline. At each subsequent retrospective, give the team a report on the action points of the previous retrospective, even if the point is not closed (like what was done there to make progress).<br>- The <strong>SM herself must be emotionally and procedurally involved</strong> in the process. If the team sees that she wants to end the rally as soon as possible, then he will react in the same way.<br>- No one forbids <strong>asking the team on one-on-one what is wrong</strong>, how it can be improved, why they don’t like the meeting or don’t see the point in it. The team will tell you better than any articles here ;)<br>- During the retrospective itself, it is advisable <strong>not to be in rush</strong>. Try to motivate team to vote for the best points. It is better to discuss 4–5 points qualitatively than to run through ten of them, especially if you exceed the time limit and the team starts to get annoyed and tries to finish it quickly.<br>- If the points above still do not help, <strong>get involved</strong>! Try to add the points by yourself without relying on the team. Try to give the floor to everyone in a circle, so that the team answers already prepared questions, such as:<br>Is the sprint goal achieved? Was too much work committed? Any impediments during the sprint? What did we expect the teams/people would do? Are those teams/people aware of our expectations? Are our expectations correct? What can we learn going forward?</p><p>As it is written in one article, <em>when I picture Retrospectives I always think of a dressing room after the football match is over where coach and team sits together and talk constructively for the next improvements and learning they took.</em></p><p>Be your team’s Ted Lasso and bear in mind that for him it didn’t work at once as well :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8813598cbf93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chat GPT for non-technical IT people (PM/QA/BA/PO).]]></title>
            <link>https://medium.com/@myroslavazel/chat-gpt-for-non-technical-it-people-pm-qa-ba-po-eeee1778a178?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeee1778a178</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Mon, 30 Oct 2023 14:43:10 GMT</pubDate>
            <atom:updated>2023-10-30T14:43:10.240Z</atom:updated>
            <content:encoded><![CDATA[<p>How non-technical IT guys are able to use this instrument?</p><p>When we tried this with the team, we were really excited about how it can help us in our daily routine. So, if you are a PM/PO/BA/QA — you might find this article really useful.</p><p>There are tons of articles which show that Chat GPT can be used for the idea brainstorming (from choice of library that does the best csv files for your stack, to inspiration for the roadmap ideas); information gathering and research; market analysis; customer feedback analysis and what not. But our goal here is to show you how chat GPT can be your little Santa’s helper in your daily routine.</p><p>Let us start with more or less occasional tasks. For example, you need to <strong>compose a letter to the customer/team </strong>(not so occasional for PM). Just try this!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/0*AORdhU212nzDbhVH" /></figure><p>In other examples that I’ve tried, sometimes I deliberately had to ask the Chat to keep it short, otherwise it’ll create a huge email with detailed explanations and analysis (it might be better for your case tho).</p><p>Let us go further and ask it to<strong> create a risk assessment </strong>for the same solution. It had 10 points in it! Let me show you the first four:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/0*AiSsAU_mNgiRpNrf" /></figure><p>GPT did a great job here. Certainly, the list should be analyzed and customized, but still it’s a big step ahead. And I even didn’t ask it to include mitigation strategies!</p><p>Ok… Imagine that a delivery manager wants to have a meeting on this (they usually do). As a diligent PM, we have to <strong>create Meeting minutes </strong>afterwards to show what decisions were made and action items planned. I told the chat that the PM had a meeting with the delivery manager on the ‘Stories’ feature, discussed all the risks, but the DM is still going to include this feature into the release, absorbing the risks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/0*w6l2PaWtLf574uoT" /></figure><p>Actually, I think those are a little bit redundant, but can be edited and adjusted easily. Though, some of you might say that nothing is redundant in terms of risks and deadlines (and I cannot agree more).</p><p>So, we still have to implement this feature. GPT can help us with <strong>creating a PBI </strong>as well!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*ERJaN9UODWqnfLVY" /></figure><p>It even didn’t forget to include possible engagement features, discoverability (how you can get to the feature from the login page), performance and scalability, quality assurance, dependencies and even Definition of Done!</p><p>Ok, great, now we have the PBI and need to <strong>write a User Story with all the needed Acceptance Criteria</strong> (we do not want to miss anything, do we?).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/0*hsXXk21Fc_lIhW4X" /></figure><p>So we have seven scenarios created. Certainly, they need to be shortened and we might want to add error-handling, alternative and exception scenarios there as well (just try it by yourself ;)).</p><p>But what about Quality Assurance, especially<strong> test design documentation</strong>? One moment, please..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/0*fwgn8tdDie50p9Px" /></figure><p>Voila — seven detailed test cases for each scenario! But what’s that? We cannot create a story because the image cannot be added to the story? Let Chat GPT deal with the<strong> bug report </strong>as well!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/0*zVLnfh1xlzjWgaR8" /></figure><p>It also didn’t forget about attachments, environment, bug priority, bug severity, resolution status etc. Very helpful if you are working not in some task manager, but in some kind of document or Excel :)</p><p>Ok, so we have developed and tested this feature (yaay!), but how can we explain to the user how to actually use it? Let us check how GPT deals with <strong>user guides</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/0*1RvB9S9Z5QVLEmyu" /></figure><p>As you can see, it was not THAT short :) Though, we managed to include reacting and sharing, discovering new stories etc — everything that a zoomer needs!</p><p>And the last, but not the least point — we have to somehow praise our team for the great job (yes, we can compose a praising letter using the same instrument as well). It’s<strong> performance review</strong> time! Let us assume that I need feedback for my Senior React dev, who did a great job here — they communicated with stakeholders in a timely and effective manner, set up all the dev processes, met their commitments and inspired all the team to achieve the goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/797/0*JmM8_DgDnH802bLF" /></figure><p>Looks good enough, maybe a bit too formal — but we can always ask it to be less formal (I tried this and it was amazing). On the other hand, at each good review, we need to <strong>set goals for our team members</strong>. I can’t think of a way how Chat GPT can do this (but you may certainly try), but for sure it can re-formulate that in a nice and clear way. This Senior React dev needs to practice more on giving feedback to other team members and delegating non-urgent assignments. So I asked Chat GPT to set goals for them using the OKR technique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/859/0*w_eAeCpszbPlyp5u" /></figure><p>Frankly speaking, I couldn’t do better :)</p><p>They say — work smart, not hard, and Chat GPT is definitely one of the tools that will help you in this journey!</p><p>**Disclaimer — all cases used above are fictional and do not violate any NDA :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeee1778a178" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to reduce onboarding time and communication issues on your project?]]></title>
            <link>https://medium.com/@myroslavazel/how-to-reduce-misunderstandings-and-onboarding-time-on-your-project-a8444774c1ff?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8444774c1ff</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Thu, 10 Aug 2023 13:46:44 GMT</pubDate>
            <atom:updated>2023-08-10T13:47:36.384Z</atom:updated>
            <content:encoded><![CDATA[<h4>Always make yourself clear!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*togowrM2jnxNW0vCpWVUFA.jpeg" /></figure><p>I guess that almost every gamer knows <strong>“The Tale of Eric and the Dread Gazebo”</strong>. Let me remind it here in case that someone isn’t that fond of games 🙂</p><p>Guy named Eric was playing a Neutral Paladin in a game. He was on some lord’s lands when the following exchange occurred (GM — game master):<br>GM: You see a well groomed garden. In the middle, on a small hill, you see a gazebo.<br>ERIC: A gazebo? What color is it? How far away is it?<br>GM: (Pause) It’s white, Eric. About 50 yards.<br>ERIC: How big is it?<br>GM: (Pause) It’s about 30 ft across, 15 ft high, with a pointed top.<br>ERIC: I use my sword to detect good on it.<br>GM: It’s not good, Eric. It’s a gazebo.<br>ERIC: (Pause) I call out to it…I sheathe my sword and draw my bow and arrows. Does it respond in any way?<br>GM: No, Eric, it’s a gazebo!<br>ERIC: I shoot it with my bow. What happened?<br>GM: There is now a gazebo with an arrow sticking out of it.<br>ERIC: (Pause) Wasn’t it wounded?<br>GM: OF COURSE NOT, ERIC! IT’S A GAZEBO!<br>ERIC: (Whimper) But that was a +3 arrow!<br>GM: It’s a gazebo, Eric, a GAZEBO! If you really want to try to destroy it, you could try to chop it with an axe, I suppose, or you could try to burn it, but I don’t know why anybody would even try. It’s a @#$%!! gazebo!<br>ERIC: (Long pause. He has no axe or fire spells.) I run away.<br>GM: (Thoroughly frustrated) It’s too late. You’ve awakened the gazebo. It catches you and eats you.</p><p>At this point, the increasingly amused fellow party members explained to Eric what a gazebo is. <br>Fun story is when I told this tale to my friends, I was 100% sure they knew what a gazebo was. It turned out that 4 out of 6 people just didn’t. And I had a big insight there —<strong> nothing that seems to be obvious is really obvious.</strong> And that can be a huge issue in your project.</p><p><strong>First point related to this —always explain the terms</strong>, even if they seem obvious to you. Better ask your team member if they really understand what does that mean. Avoid complex and technical expressions and do not use vague expressions, especially on onboarding and knowledge transfers.<br>They say that if you’re hesitating about whether it’s obvious, then it’s not obvious. Don’t be the game master or me in that case :)</p><p><strong>My second ‘favorite thing’ here is abbreviations.</strong> You might check the Youtube video <a href="https://www.youtube.com/watch?v=igPIk79wAPg">“The problem with workplace jargon” </a>from my favorite “Viva La Dirt League” team (go gamers!). How do you like it when your leader says something like “I’ve got the OTC MOM TBA. Then the CFO asked me to get on the EDS on EST ASAP”. Yes, most of those abbreviations might seem familiar. But imagine if they were not.<br>Please, use only commonly accepted abbreviations and acronyms in the project. Commonly accepted are the ones that are easily googled (in their first meaning), like AFK. Take other abbreviations only from the project glossary and only for the oldies of your project! During onboarding, it is better to avoid project- or domain-specific abbreviations, even if they might be easily googled, because you newbie will waste time and be in doubt (did they really mean it?). <br>To cut long story short, avoid unnecessary and/or extensive abbreviations.</p><p>If your domain or project is very specific, compile a<strong> glossary of terms and abbreviations.</strong> You might think that the need for a document with the title “Project Glossary” is very exaggerated — you can just opened google and write “what is AWS”. Though, a compiled glossary helps to avoid misunderstandings and to reduce the need of guessing games, which speeds up the process and makes work more efficient. Due to the glossary, key terms are always understood correctly, even if many teams work on a certain project or domain (consistency is a key).<br>It is very convenient to update the glossary in the regular working process: when we notice a repeated term — we add it to the glossary. But don’t forget to check that terms are not duplicated. Double terminology can confuse you and cause errors in the text. That is why it is desirable to supplement the terms with definitions, explanations and context.<br>And the last point here— glossary should not be redundant. Here, if you are practicing in the Healthcare domain, it is normal to assume that the HIPAA abbreviation, or the term “medical insurance” is more or less known to everyone who used to work in this domain.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8444774c1ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Constructive resolution of conflicts and problems]]></title>
            <link>https://medium.com/@myroslavazel/constructive-resolution-of-conflicts-and-problems-85411e39ec14?source=rss-6409ea8abc------2</link>
            <guid isPermaLink="false">https://medium.com/p/85411e39ec14</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[conflict-resolution]]></category>
            <category><![CDATA[conflict]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Myroslava Zelenska]]></dc:creator>
            <pubDate>Tue, 01 Aug 2023 08:35:31 GMT</pubDate>
            <atom:updated>2023-08-01T08:35:31.660Z</atom:updated>
            <content:encoded><![CDATA[<h3>Constructive resolution of conflicts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/419/1*s9XdBMjc-ag68TomEIq9oA.jpeg" /></figure><p>To begin with, let us look into the structure of conflict. What do we have there?</p><blockquote>- <strong>Two sides </strong>(usually); sometimes we would have 3rd side as moderator, but we still would have two conflicting sides and/or opinions;<br>- (External) <strong>incompatibility of values and/or intentions</strong>; often it’s just external due to miscommunication or language barriers;<br>- <strong>Opposition of one side to another</strong>;<br>- <strong>Actions are aimed at disrupting the plans and intentions</strong> of the other party.</blockquote><p>It seems pretty straightforward. Though, it’s more important to know what we should do to make them constructive and help us solve issues and endure challenges.</p><h3>Rules of constructiveness</h3><h4>1. Timeliness</h4><p>There is one problem with the past — it cannot be changed. So, if you talk to your team about something they haven’t (or have) done in the past, it’ll not help. Though, usually this talk is meant to solve some issue in the current moment, so focus on here and now. And when it is resolved — this is when you can look into the future: how would we make such situations not to happen anymore.</p><h4>2. Talk to someone who is able to resolve it</h4><p>It will not help to spread hatred for your leader somewhere in the kitchen with colleagues, if he/she is not there. Go and talk to them personally (or set up a meeting). If the potential problem solver does not know about your issue, they will not be able to help you.</p><h4>3. Solve the problem, not the person</h4><blockquote>When it hits, it’s tempting for us to see the person with whom we’re in conflict as the “bad guy”, and to create a “You Against Me” scenario.</blockquote><p>It’s not a great idea to play blaming games. We are trying to solve the issue, not to attack our team or colleague, so we should concentrate on the issue itself. Not “Why haven’t you send a report to the client, you should be ashamed of yourself!”, but rather “We should have sent a report to the client yesterday, and we missed the date. Client needs that for his board meeting today in 2 hours. What should we do to fix this?”.</p><h4>4. Be specific and objective</h4><p>Try not to operate with some abstract stuff like ‘team spirit’ or ‘because Ken Schwaber says so’. Your statement must be specific and well defined. Like not ‘we should do refactoring every sprint because it’s what everyone does’, but ‘we should take tasks for 3 story points for refactoring each sprint to improve the performance for our landing page because conversion in this quarter fell to x% due to poor performance’. Your team/opponent will be more motivated and eager to help if you talk data and not some value judgments.</p><h3>Steps of conflict resolution</h3><h4>1. Preparation</h4><p><strong>1a. Identify the issue.</strong><br> What is the issue in this situation? And is it really a problem?<br>Does it affect work? Why should I solve it? If I don’t solve it, what will go wrong?<br>What do I want to achieve as a result (remember — we always begin with the end in mind)?<br>If something personally annoys you, but it does not and cannot affect work, then who/what is the problem? Who should resolve it?</p><p><strong>1b. Plan the approach.</strong><br>Some books claim that you should communicate with people the way you would like to be communicated with. Nope. You need to communicate with people the way they would like to be communicated with.<br>Think over your presentation in advance, rehearse if needed. Be objective.<br>Operate with facts and data that are interesting to a person. Prepare <strong>several</strong> arguments.<br>Determine the right time and place.</p><h4>2. Discussion</h4><p><strong>2a. Come to an agreement on the issue.</strong><br>We see the issue, understand why this is problematic and then select arguments/solutions that would solve the issue. For us. But are you sure that our problem is also a problem for another person/team?</p><p><strong>2b. If you are out of arguments— leave the conversation.</strong><br>If you are out of arguments — take a break, think and come back to the conversation a little later with new facts and arguments. If we push a solution without agreeing to the issue, the person fights back, sabotages the solution, and moreover, it might turn to a huge conflict with them.</p><p><strong>2c. Listen to a person (team/other side).</strong><br>Think — which arguments do people listen to better? To those that show that you have a problem, or to those that show that they have a problem?<br>Listen to the other side’s point of view, ask open-ended questions like “What do you think about it? How does it look to you?”.</p><p><strong>2d. Make a consolidated decision.</strong><br>Ask a person/group to suggest a solution. Listen to it.<br>Suggest and explain your solutions.<br>Write down the reasons, pros &amp; cons as a checklist for other options.<br>Consider solution options; choose one of them.<br>Ask: “Do you think we’ve considered all options”?<br>Test selected solution for sustainability (look into the future).</p><p><strong>2e. Make MoMs (specify the timelines and responsibilities).</strong><br>Be sure to record what will be done, like a list of actions, timelines, and necessary resources. A good form of recording decisions: WWW = Who, What, When.</p><h4>3. Control</h4><p>Set a date to discuss progress. Establish a feedback system, for example, an action plan in the form of a checklist.<br>And the most important thing — make sure that the process works for all sides and participants.</p><p>If a person/group has started to work on the agreed solution, and even the affected people confirm the improvement — you should thank them. If you don’t do this, a person may think that you didn’t notice and will be demotivated. <br>If a person/group has started the work— this is a reason to ask: “What has happened?” And either it turns out that the person has forgotten about it (in which case it is probably necessary to re-work your feedback and control system), or it turns out that the solution does not work for them. In this case you will have to return to the previous stage and refine the solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85411e39ec14" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>