<?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 Zeba Avera on Medium]]></title>
        <description><![CDATA[Stories by Zeba Avera on Medium]]></description>
        <link>https://medium.com/@zebaavera?source=rss-34f0cdafa0ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*VD4Qk-QC8rSL1xVVcvpCMQ.jpeg</url>
            <title>Stories by Zeba Avera on Medium</title>
            <link>https://medium.com/@zebaavera?source=rss-34f0cdafa0ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:33:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zebaavera/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[Fear of Change: Let’s Talk About It]]></title>
            <link>https://medium.com/@zebaavera/fear-tied-to-change-that-we-dont-talk-about-enough-e085b7b3354?source=rss-34f0cdafa0ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e085b7b3354</guid>
            <category><![CDATA[alignment]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Zeba Avera]]></dc:creator>
            <pubDate>Sun, 12 Apr 2020 06:57:36 GMT</pubDate>
            <atom:updated>2022-11-02T23:01:30.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hy26IwILXLk3IYJc8sjhLQ.jpeg" /></figure><p>I’ve been reflecting on how people behave when change confronts them, leaving them feeling out of control. Experiencing change is not foreign to us; we deal with it daily in small doses. Yet our immediate responses to change often come from instinct. Instinctual responses put us in a fight or flight mode and leave us feeling as though we have little time to think something through. Maybe that moment is when we should pause before responding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*QCTgTPinLeqNejs4Mc5hGg.png" /></figure><p>Over the past few years and especially months, a lot of us have experienced changes in the workplace, and as we know, with the pandemic, the changes will most likely continue. How we respond to change is what will allow us to rise above the challenges.</p><blockquote>“The world is becoming more technologically complex, interdependent, and culturally diverse, which makes the building of relationships more and more necessary to get things accomplished and, at the same time, more difficult. Relationships are the key to good communication; good communication is the key to successful task accomplishment; and Humble Inquiry, based on Here-and-now Humility, is the key to good relationships.” <a href="https://www.amazon.com/Humble-Inquiry-Gentle-Instead-Telling/dp/1609949811/ref=sr_1_1?dchild=1&amp;keywords=humble+inquiry&amp;qid=1586705071&amp;sr=8-1">Edgar Schein, Humble Inquiry</a></blockquote><p>One of the hardest things with which to contend within a group is change. Responses to fear can come through in challenging ways. Overreacting to something that appears benign on the surface. Resisting collaboration. Answering questions with fear-based responses, inadvertently creating confusion that isn’t useful.</p><p>I’ve responded in fear before. It’s in those moments that I feel confused: Why did I react that way? How could I have done things differently? The key is not giving yourself a hard time, but making sure we have space to reflect and learn. It’s also important to avoid judging others if they have a fight or flight response due to fear. We are human, after all.</p><p>A quote from Rumi seems appropriate here:</p><blockquote>“Out beyond ideas of wrong doing and right doing there is a field. I’ll meet you there.”</blockquote><p>You can see how powerful fear can be when you look at examples in the world that produce adverse outcomes — for example, hoarding during the pandemic despite understanding that it impacts the supply chain industry negatively. Seems obvious, right? But emotions change our response before we even realize we are in autopilot mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tkVwFGQqq2x8ErTkxjWJhw.png" /></figure><p>The Kubler-Ross Change Curve highlights our emotional responses to change and how to tackle the downward curve for the best outcomes. I don’t think it’s a coincidence that the stages are similar to dealing with grief. The five steps that I’ll be reflecting on as change continues:</p><ol><li><strong><em>Creative Alignment: </em></strong>Are we aligning ourselves and communicating why a particular change is happening? Explaining who will be impacted by the change and what the benefits are? I’ve heard of some groups designating a space to write up details around an initiative and team members entering the area to take in the information, then sharing anonymous feedback for leadership review.</li><li><strong><em>Maximize Communication:</em></strong> Are we creating informal communication (“lean coffee”) sessions to establish an honest dialogue about a change? Team members should be able to vent and share their complaints in a safe space.</li><li><strong><em>Spark Motivation: </em></strong>Do we understand what is hindering someone from trying a new process or practice? Setting up some time for training or coaching could be a constructive endeavor.</li><li><strong><em>Develop Capability: </em></strong>Are we allowing people to practice the new skills they are learning? Are we helping them to feel safe in failing? Leaders and coaches should set some guardrails and create opportunities for teams to innovate and collaborate.</li><li><strong><em>Share Knowledge:</em></strong> Are we sharing our stories? Are we encouraging the team to learn from one another? It’s vital to allow teams to come together and showcase their work.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UD3kBwW8DWAq5xF1D1AxbA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e085b7b3354" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 11 Mistakes I’ve Made and Learned From]]></title>
            <link>https://medium.com/@zebaavera/top-11-mistakes-ive-made-and-learned-from-608756364b8b?source=rss-34f0cdafa0ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/608756364b8b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[learning-from-mistakes]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Zeba Avera]]></dc:creator>
            <pubDate>Sat, 28 Mar 2020 17:01:14 GMT</pubDate>
            <atom:updated>2022-02-25T17:14:09.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ApNWVKS_xHkjle2nQUrsOA.jpeg" /></figure><p>I’ve worn lots of hats and continue to juggle between them as many of us do. Through the process of working on traditional waterfall projects, transitioning to a product, agile and lean mindset I have been able to manage the flow of work and support my teams and customers better. It’s clear to me that making mistakes and learning from them has been integral to my growth. Below is a list of the top 11 mistakes I’ve made over the years and what I learned from them.</p><p>Can you relate to the items below? Would you be willing to share your mistakes and lessons learned? Let me know what you think or feel free to reach out if you want to chat about similar topics.</p><ol><li><strong>Working on requests from the business immediately without thinking through the outcomes and value they are looking for. </strong>Service and support incidents and new customer requests should be managed differently. We should jump on high impact support and service incidents and resolve them. But there’s a delicate balance between figuring out what to work on and what not to work on for a new customer request. Collaborating as a team along with the business to understand the outcomes we are trying to achieve and the value they will bring is integral to the discovery process. Writing up use cases and outputs are also valuable, but focusing on outcomes first helps the team work on the most important things. Check out Jeff Gothelf’s <a href="https://jeffgothelf.com/blog/leanuxcanvas-v2/">Lean UX Canvas</a> for an approach that has been successful for me with regard to discovery, collaboration, and decision making.</li><li><strong>Completing ROI Analysis for every request.</strong> ROI Analysis is important and extremely helpful for larger initiatives as they have higher costs. Understanding the amount of effort an initiative will require will help you decide when to scrutinize and when not to. Douglas Hubbard’s <a href="https://www.amazon.com/How-Measure-Anything-Intangibles-Business/dp/1118539273"><em>How to Measure Anything</em></a> is a fantastic book that highlights some great approaches to such topics.</li><li><strong>Brainstorming solutions before understanding the business problem. </strong>Understanding the problem we are trying to solve (thoroughly) is most important, and often times helps with finding the right solution with minimal waste. This one is related to #1. The discovery process should include the problem statement. Joshua Seiden’s book, <a href="https://www.amazon.com/Outcomes-Over-Output-customer-behavior/dp/1091173265"><em>Outcomes over Output</em></a> is a quick 45 minute read that helps uncover the discovery process.</li><li><strong>Moving forward with the first solution mentioned, without collaborating and discovering more ideas/solutions with the team.</strong> Facilitating techniques to help draw out solutions from the team helps to keep biases at bay. Making sure the team gets a chance to share their ideas and thoughts, writing them on a common and visible board to help with taking information in as a group. Weighing the pros and cons, the effort it would take to implement and deciding how the new information aligns with our goals — helps us to select the right solutions and experiment.</li><li><strong>Keeping the customer from joining us in collaborative discussions because they may derail the meeting.</strong> Getting the customer to join us in collaboration, writing business problems, and discovery sessions are important so that the whole team not only builds a relationship with the business but can clarify unknowns during the session so shared understanding is immediate. Customers should be included in all our Agile related events during a project so that communication and collaboration are constant. It may help to set some ground rules before a meeting begins so that we allow all team members to speak and avoid disruptions.</li><li><strong>Not completing risk analysis before a large initiative begins. </strong>Understanding the risks tied to a project failing upfront and writing up how to mitigate them lowers stress levels when pitfalls arise. Has helped with better decision making as well.</li><li><strong>Not completing stakeholder analysis before a large initiative begins. </strong>Understanding who is impacted by a project or change and how to communicate with them to get feedback is integral for project success. Stakeholder buy-in and a communication plan around that helps. Teams, Yammer, Face to Face meetings, Emails can all be a part of the communication plan.</li><li><strong>Prescribing how to work once team members have learned the fundamentals. </strong>Think <a href="https://www.solutionsiq.com/resource/blog-post/shuhari-agile-adoption-pattern/">Shu, Ha, Ri</a>. It’s important to inform team members that are new to a process or the team and help with training around Agile methods and frameworks. Once they understand the full process and have been a part of a few projects using the methodology and frameworks, give them room to breathe. Allow them to learn from others and through their own mistakes. Keep the communication line open so they can lean on you for guidance when they need it and let them fly and grow on their own.</li><li><strong>Avoiding progress, due to difficulty with letting go and embracing change. </strong>Growth can be painful especially when letting go of the past or changing how we do things in the present. It’s hard to find the courage to take the leap at times. For me, it is the unknown that inspires me and what scares me at the same time. When things get uncomfortable I try to lean in and understand why and talk through it with a trusted colleague or friend.</li><li><strong>Keeping quiet when I have a question or thought. </strong>You know the saying there isn’t a stupid question, just ask. In my experience, there are often other folks thinking the same thing I am or require further clarification but they are often afraid to ask. I can’t think of a question that was asked that made me think it wasn’t worth answering. Often times it helps the team with the ideation process. Seems obvious but I still see the apprehension in sharing among teams and maybe a sign that more trust-building is necessary.</li><li><strong>MVP (Minimum Viable Product) is a process, not a product.</strong> I read <a href="https://www.jpattonassociates.com/user-story-mapping/"><em>User Story Mapping</em></a> by Jeff Patton and something he shared that really stuck with me: “deliver half a baked cake, not a half baked cake”. Half a baked cake may not be enough to feed a wedding party, but it is enough to taste and leave everyone looking forward to the rest of the cake. The MVP process helps us experiment and prove or disprove an assumption so that we can learn and pivot.</li></ol><p>I’ll leave you with a quote from Ray Dalio because the decision-making process is important and helps us to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ermp9JETHfIYA5p7vTqJw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=608756364b8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>