<?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 Osama Al-Eryani on Medium]]></title>
        <description><![CDATA[Stories by Osama Al-Eryani on Medium]]></description>
        <link>https://medium.com/@osama.eryani?source=rss-68dc94e06222------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Wq23_xmNQGFhkBO5rrKKLw.jpeg</url>
            <title>Stories by Osama Al-Eryani on Medium</title>
            <link>https://medium.com/@osama.eryani?source=rss-68dc94e06222------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:33:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@osama.eryani/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[Transitioning From Online To In-Person & Back, One Cohort’s Experience Developing a Workshop on…]]></title>
            <link>https://medium.com/@osama.eryani/transitioning-from-online-to-in-person-and-back-again-one-cohorts-experience-developing-a-94f5ad0dd203?source=rss-68dc94e06222------2</link>
            <guid isPermaLink="false">https://medium.com/p/94f5ad0dd203</guid>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[online-workshop]]></category>
            <category><![CDATA[concordia-university]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Osama Al-Eryani]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 20:00:03 GMT</pubDate>
            <atom:updated>2021-11-08T22:32:44.034Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transitioning From Online To In-Person and Back Again, One Cohort’s Experience Developing a Workshop on Change</h3><p><em>Written by </em><a href="https://medium.com/u/5fdf7f313b0b"><em>Kyle Wilson</em></a><em> (data visualizations by </em><a href="https://medium.com/u/68dc94e06222"><em>Osama Al-Eryani</em></a><em>), for the </em><a href="https://www.concordia.ca/academics/graduate/human-systems-intervention.html"><em>Human Systems Intervention</em></a><em> Masters Class of 2022, Concordia University.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5aZyV4XSR6bsflDTZeRZyg.png" /><figcaption>Hand-Drawn Timeline created by the cohort</figcaption></figure><p>What happens when you form a cohort of diverse organizational and cultural backgrounds in a purely online environment, and after a year in that setting, have them come together to co-create an experiential online workshop on change and transition? Well, you get a fascinating, messy, chaotic, and beautiful exploration into human experience, group dynamics, development, and facilitation.</p><p>In this blog post, we offer you a window into this journey.</p><p><strong>HSI 2022</strong></p><p>Our cohort is comprised of students in the 2022 Human System Intervention (HSI) Master’s program at Concordia University, Montreal. The HSI program focuses on developing skills to help facilitate positive change in groups and organizations, with a focus on looking at the group as a whole, as opposed to a collection of individuals. Typically this program would be in-person, however given the context of the COVID-19 pandemic it shifted to being completely online. Our group was initially thirteen individuals, about half the typical HSI cohort size, however over the course of the year we lost three members for various reasons. Each time a group gains or loses a member the dynamic changes, and we want to recognize the contributions of those members during the first year of our experience, and the impact that losing them had on the whole.</p><p><strong>Intensive Week</strong></p><p>The adventure of developing an online experiential workshop began in early September, with an in-person, week long intensive course. This was the first time the cohort had been present together in its totality in the “real world”. It was a fascinating and exhausting week, filled with trust exercises, personal reflections, theoretical frameworks, and workshop design. It was also during this time that we realized we might not be as developed a group as we had imagined. The simple task of splitting into five pairs to facilitate the workshop turned into a much longer and more stressful experience than we might have anticipated, with one cohort member in particular being thrust in a direction not of their choosing. Here we came to learn that we lacked clear processes for decision making, and did not take the time to create true consensus within our group. For all our time together as an online cohort, we might only be in what Tuckman¹ describes as the “Storming” phase of group development. This resulted in our group taking some time to have some real and vulnerable conversations, which marked an important shift in our dynamics as a cohort.</p><p>The final day of our week-long intensive marked the beginning of our program design, with the cohort dividing into sub-groups or committees to tackle the various roles and responsibilities of the workshop. The committees formed were Registration &amp; Promotion, Coordination, Design, and Record of Work &amp; Project Celebration. This process was done relatively quickly, and at the time we did not establish clear mandates for each working sub-group.</p><p><strong>Bridges Change &amp; Transition</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xhG2-GstYr724GVq.jpeg" /><figcaption>Bridges Model of Transition</figcaption></figure><p>The goal the cohort was tasked with was to:</p><blockquote>Build a team that masters the conceptual and practical underpinnings of interdependently implementing an experiential workshop tailored to a client system using the Bridges Model of Transition².</blockquote><p>The vision the cohort developed to achieve this goal was:</p><blockquote>To create an individual and collective experience where we explore new ways of seeing and understanding change and transition with curiosity and care.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*KCAFPcPjbL5SqghH9zKNlQ.jpeg" /><figcaption>Initial Workshop Design</figcaption></figure><p>The basic format we followed was to have an opening session with all members of the workshop, after which the participants would be split into smaller groups, with each smaller group co-facilitated by two members of the cohort. After the small group experience, everyone would return together for a plenary discussion and closure to the workshop. The goal of the opening section was to welcome the participants, introduce the Bridges model on Transitions, and effectively prepare the participants for a deeper exploration into change and transition in their small groups. Aside from that more in-depth exploration, the small groups were intended to prepare participants for the larger plenary discussion in the closing. The closing was an opportunity to cross pollinate between the various small-group experiences, and engage in collective sense-making.</p><p><strong>Too Much Information</strong></p><p>In the ensuing weeks, the various committees each worked on their appointed focus for the workshop, and the co-facilitating pairs developed their design for the smaller groups. It should be noted that the co-facilitating pairs all created unique designs, independent of the others. This ensured the small group designs were tailored to the specific facilitators, and also allowed for a wider variety of experience to be explored in the final plenary session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_5nsHU0q8dSyEvRH2zX4Q.gif" /><figcaption>Miro Board Evolution</figcaption></figure><p>The cohort used a collective Miro board with design plans, drafts, and notes. The various committees and pairs held meetings, most of which were online. Updates from each committee were posted in a communal Slack channel so cohort members could stay informed on what was transpiring in the other sub-groups. And while the sharing of data is all well and good, in this case it became a bit of information overload. The sheer amount of updates and the details therein made it difficult to retain, or even keep track, of all the information. Here we saw a siloing effect, where the asynchronous updates were being shared, but not necessarily seen or understood, with very little dialogue between the committees. We call this time the Slack Overload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXtVan5Pk2g24Brj-8KySA.png" /><figcaption>Slack Traffic</figcaption></figure><p><strong>English? French? Both?</strong></p><p>Partway through the process of creating this workshop, one cohort member raised concerns about inclusivity, in particular regarding accessibility to francophones. This became a major point of debate and discussion within the cohort, on if we could accommodate French-speaking participants, and if we chose to, how to design a francophone or bilingual workshop. Throughout the process of this dialogue, a new committee was formed, Language &amp; Inclusion. After some deliberation, we chose to do what no other HSI cohort had done before; offer a workshop accessible to anglophone, francophone, and bilingual participants. This involved modifying our basic design to include a bilingual plenary opening, leading into two simultaneous workshops, occurring side by side, to accommodate speakers of both languages. A major consideration for this to function was how many members of the cohort felt strong enough in French to facilitate the francophone version of the workshop. Consequently, we also needed to monitor and adjust the number of anglophone, francophone, and bilingual participants our workshop could accommodate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sakWvccI8AZsn082hfa7TA.jpeg" /><figcaption>Final Workshop Design</figcaption></figure><p><strong>Technology</strong></p><p>Given the complexity of beginning a bilingual workshop, splitting it in two (English and French) then dividing it further into small groups, and many of those groups dividing into pairs (all the while online!), we had some technical logistics to consider. Our solution was to begin the workshop on a Zoom call, and then have a series of well organized breakout rooms for the various subdivisions.</p><p><strong>Participants</strong></p><p>In the past this kind of workshop would be done in a client organization, with all the members a part of the larger system. This year was a bit different. Given the online nature and the COVID-19 context, our workshop was not with a client organization, but instead open to the public. This meant that our cohort reached out to friends and family, our various networks, and social media to get the word out and acquire our participants. This offered a very diverse group of participants, and also made it challenging to predict what kind of group we would be working with before meeting them for the first time.</p><p><strong>Maintenance Needs</strong></p><p>In the weeks leading up to the workshop, there was a build-up of stress, exhaustion, and a continuation of siloed work. Up to this point, the task of creating the workshop had been the primary focus. A few key members of the cohort took it upon themselves to generate spaces for team maintenance, as well as more communal online work spaces to cross-pollinate between the various committees. It was undeniably difficult to shift from the task mindset into that of group maintenance, particularly with the deadline of the workshop approaching.</p><p>The final design for the workshop was generated as a precisely laid out script. The cohort had a few practice run-throughs of some key segments, the opening in particular. The day before the workshops, the cohort met in person to go over everything and address any last minute apprehensions. This was a particularly stressful day for our group, with numerous concerns and possible modifications being raised, and little time or energy to adjust to them.</p><p><strong>Showtime</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S4I4wzVL01ibiGPPrX-siw.jpeg" /><figcaption>Participant Distribution</figcaption></figure><p>After weeks of preparation and stress, we had the public workshops with our participants on the 16th and 17th of October. On Saturday we ran simultaneous English and French workshops, and Sunday only in English, due to a lack of francophone participants. It was an exciting and stressful time for all of us. Both workshops resulted in rich and insightful reflections by the participants, who expressed gratitude for the collective sense-making and openness of the spaces that were created. Some themes that emerged from our workshops were the importance of allowing ourselves to be in transition, trusting in the process, creating space to reflect, and creating safe spaces to share and dialogue, just to name a few.</p><p><strong>Feedback</strong></p><p>We were also fortunate enough to have HSI alumni in each of the smaller co-facilitated groups during the workshops. Their presence allowed us to get constructive feedback on the workshop and for our co-facilitation pairs just after its completion. Each of the pairs made their own adjustments, and we made a minor tweak or two to our overall design for Sunday. Aside from the HSI alumni, we were also very grateful to receive feedback from several participants in the form of questionnaires, completed after finishing the workshop. By and large the feedback was incredibly positive, with most participants enjoying the pace, facilitation style, small group experiences, space to be vulnerable, and generative dialogue. We also received some critical feedback about the length of various sections, and some design considerations like the order of some experiences, and the purpose and timing of certain components.</p><p><strong>Reflections &amp; Learnings</strong></p><p>Developing and running these workshops was a wild, and sometimes messy, ride. After having a chance to decompress and reflect, our cohort has some reflections and learnings on the process we went through, and some considerations both for ourselves and any others engaging in a similar experience.</p><p><strong><em>Go Slow to Go Fast</em></strong></p><p>We rushed out of the gate a bit trying to jump into work mode, but hadn’t clearly defined so many elements. How were we going to make decisions? What processes were we going to use? What were the mandates of the committees? Taking the time earlier on to clarify key elements might have saved us a great deal of time and effort in the long run. If, for instance, we had discussed inclusion and language early on, we might have avoided a complex redesigning of our workshop later in the game. Instead of jumping directly into work groups at the end of our intensive week, we could have taken a week off to consider these elements.</p><p><strong><em>Everything Needs a Purpose, and It Has to be Clear</em></strong></p><p>Taking the time to figure out what we’re doing is important, but if it isn’t clear, what good is it? Clearly defining the goals of the workshop, the pairs, the committees, and so on helps remove ambiguity from the process. If we get lost in what we’re doing, it’s so much easier to re-orient when there’s a clearly defined goal on the board. Intentionality is incredibly important, especially in an online setting. Many of the tiny elements that organically occur in group interactions are lost behind the screen. We need to intentionally create those elements through the design and experience. With that in mind, there’s also no need to overengineer a design! We might have taken the notion of using a script a little too far, for instance. Including the key and necessary components for the workshop, and leaving the space for emergence might create a better container for the transformative work we set out to do. Bells and whistles are nice, but if they are not intentional, may detract from the purpose.</p><p><strong><em>Maintenance</em></strong></p><p>Don’t skimp on group maintenance people. The task always seems of the utmost importance, and in a way it is, but if your team doesn’t make time to take care of itself they’ll be less equipped to tackle the work. Retrospectively, our group would have benefited greatly by creating intentional spaces for maintenance from the very beginning of our process, as opposed to reactively trying to make those spaces partway through.</p><p><strong><em>Team Capacity &amp; Timing</em></strong></p><p>Another thing to consider is the capacity of your team, and the timing involved in meetings, adjustments, and feedback. When we set about forming our various committees, as a group we were exhausted, and that impacted the way we planned for the following weeks. We could easily have pushed that meeting a week to develop those clearer mandates and processes. Similarly, our Friday session just prior to the workshops was poorly timed. The stress level in the group was too high, and there were too many questions and possible modifications raised with too little time to adequately adjust. Retrospectively that session would have probably been much more impactful if it happened a week prior. Finally, when we consider the feedback we received, many cohort members felt we had little capacity to hear it. While running a live workshop can often be invigorating, in our experience the online version is exhausting. The screen fatigue is real! If we had taken a longer break after the end of the workshops, as opposed to hearing feedback right away, we may have been in a better space to hear and absorb it.</p><p><strong><em>Too Many Cooks?</em></strong></p><p>Co-designing a workshop with ten people is a pretty complex endeavor. Many members of the cohort have expressed how much simpler this would have been with two or three people, or even alone! And ten is a peculiar number as well. Had we been a group of five, all members could have worked closely on everything, communication would have been relatively straightforward. If we had a much larger group typical to the program, say twenty-five, then we would have had to create those clear tasks and boundaries, otherwise it would be utter chaos. Being in the middle, it seemed like we tried to flip flop back and forth between involvement in all the decisions, and the siloing of the committees. Once again, having clear processes for working together and making decisions is key. Stakeholders should be involved in those decisions that directly impact them, however tasks should also be clearly delegated, and group members should trust one another to act in the best interest of the team. Again, this is supported by having clear and explicit goals and mandates.</p><p><strong><em>Group Development Online</em></strong></p><p>A final consideration is the way our group developed in our online setting. We studied and worked together in various capacities for over a year, however once we got down to brass tacks, it seemed like our group was in its infancy. Our online experience was simply not the same as working together in person. Here we come back to intentionality. We need to be extremely intentional in creating the spaces and types of interactions that foster dynamic group development. During our first year together, we did almost no work together as an entire cohort, and for the brief activities we did, the stakes were incredibly low. Looking back, we might have benefited from doing more work together as an entire cohort. Being thrown into some interesting, dynamic, or just plain difficult situations might have let us hash out more of our groups norms, decision making processes, communication, maintenance, and feedback.</p><p><strong>Now What?</strong></p><p>This blog marks the end of our cohort’s strange, stressful, and exciting adventure co-creating and facilitating these workshops. These are only a few key reflections on our process, and we suspect that a deeper understanding of our learnings will emerge as we take more time to process this experience.</p><p>Our cohort is unlikely to go through this process again, at least not all ten of us together, but we hope that our experience can help inform our group work and designs for the future, as well as that of any participant, reader, or facilitator. As we continue in a world that has become increasingly remote, whether fully online or hybrid, how can we intentionally create meaningful group experiences for both participants and facilitators?</p><p>References</p><p>(1) Kass, R. (2015). <a href="https://www.concordia.ca/artsci/chrcs/publications/featured/theories-small-group-development.html"><em>Theories of small group development</em></a> (5th ed.). Concordia University.</p><p>(2) Bridges, W. (2019). <a href="https://www.amazon.ca/Transitions-Making-Sense-Lifes-Changes/dp/0738285404/ref=sr_1_2?crid=1AUCZJNQHXTYE&amp;keywords=transitions+making+sense+of+life%27s+change&amp;qid=1636395782&amp;sprefix=transitions+making+sense+of+life%27s+changes"><em>Transitions: Making sense of life’s changes</em></a> (40th anniversary ed.). Lifelong books.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94f5ad0dd203" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fire, Water, and Retrospectives]]></title>
            <link>https://medium.com/ssense-tech/fire-water-and-retrospectives-140c5c40e77b?source=rss-68dc94e06222------2</link>
            <guid isPermaLink="false">https://medium.com/p/140c5c40e77b</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Osama Al-Eryani]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 14:01:01 GMT</pubDate>
            <atom:updated>2021-09-21T23:20:00.483Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Fire, Water and Retrospectives</h3><p><em>What I learned from starting and facilitating retrospectives for 9 teams.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PPPMfN6ZiRmtWMmVGrSOZg.jpeg" /><figcaption>A simple retrospective with a clear grouping and an action item proposed by a new team member</figcaption></figure><p>Retrospectives, or simply retros, are structured conversations in which a team inspects and adapts how they work together.</p><p>My context is working in Tech teams, but retrospectives can just as well be used for HR, Accounting, Sales, Marketing, C-Level teams, or even in a family setting.</p><h3>Background</h3><p>I used to work in a large team as an individual contributor. It was less of a team and more of a group of individuals, each working on their respective tasks, with a coordinator managing the integration of their work. Plans were drafted, with hourly precision for the different phases.</p><p>Thanks to the notorious unpredictability of our line of work, it was common to be behind schedule by months. By the end of the project — say a year later — we would all sit together to discuss how things went.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*i1osFW-iw7XdUH3a" /><figcaption>A special retro for a new team, with framing questions designed to anticipate further problems down the line</figcaption></figure><p>Reflecting upon this, I figured there must be a better way to reduce, or at least acknowledge, this uncertainty.</p><p>I proposed that we split our group into three smaller teams and gradually shift from monolithic releases every six to nine months, to monthly, and finally to bi-weekly. This required adjustments at all levels: our stakeholders realized they did not need to squeeze in all their requests before we started; rather, they could wait for the next cycle. The group members realized they were now a team. They knew each other’s names, what everyone worked on and how they could support one another. Lastly, our managers gradually let go of chasing specific dates, in favour of a more constant stream of value addition.</p><p>In this dynamic setup, we found ourselves adjusting how best to work together, which did not always go smoothly. The managers set the overall constraints but we still needed a lightweight mechanism for resolving disputes and continuously evolving as a team.</p><p>Enter Retrospectives.</p><blockquote><em>Retrospectives = Process Kaizen + Team Therapy</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zUm02p5jMQ_rmt5a" /><figcaption>Praise section makes an appearance</figcaption></figure><p>Here is what I learned from facilitating retrospectives for nine teams over a three year period:</p><h3>1. Get Management’s Blessings</h3><p>Introduce the concept of retrospectives to the team’s managers.</p><blockquote>Retrospectives are a mechanism to increase the team’s autonomy. It does that by surfacing and addressing disputes — before they escalate — revisiting working arrangements as needed, reinforcing the good stuff, and continuously improving how the team works.</blockquote><p><em>Note to my early self: managers are not the enemy. They provide care and support that nurtures the team, help with what is out of their control, and bring in strategic work that keeps the team engaged.</em></p><p><em>Note to my current self: be wary of too much autonomy in teams with limited technical expertise or an unclear business vision.</em></p><h3>2. Find Time in the Team’s Schedule</h3><p>I have observed that teams cancel retros when they need them the most. Here are a few ways of mitigating this problem:</p><ul><li><strong>Mandate it</strong> as part of your engagement as a facilitator. Note that, depending on your environment, this might be a bit too coercive.</li><li>Embed a small slice into existing meetings, <strong>show value</strong>, then expand. This works almost everywhere, but with a slower ramp up.</li><li><strong>Channel </strong>the team’s process changes and points of contention to the retro forum.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kG-tkzozE4bjYmCM" /><figcaption>A timer proves super handy for speedy retros</figcaption></figure><h3>3. Find a Facilitator</h3><p>If you are a manager interested in starting retrospectives in your team, it helps to pick a facilitator from outside the team who is detached from the specific outcomes of the discussion.</p><p>We tried having team members facilitate their own team’s retro, but they often found themselves torn between the requisite neutrality of facilitating the discussion and their desire, as a contributor, to push for certain outcomes.</p><p>We have since experimented with having team members facilitate retros for other teams, and the early results are promising.</p><p>The facilitator’s role:</p><ul><li>Invites as many <strong>different views </strong>as possible into the discussion</li><li>Ensures <strong>procedural fairness </strong>during the discussion</li><li>Helps the team <strong>converge </strong>towards specific and previously undetermined outcomes</li></ul><h3>4. Design a Framing Question</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*Q5g6DAsQrtn7oILl" /><figcaption>Freshening up the framing question</figcaption></figure><p>The purpose of the framing question is to gather facts and sentiments regarding different events that transpired during the period in question.</p><p>Examples:</p><blockquote><strong>⎢</strong>What went well? <strong>⎢</strong>What didn’t go so well? <strong>⎢</strong>Ideas for Improvement <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>Good <strong>⎢ </strong>Not So Good<strong>⎢ </strong>Ideas <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>Start<strong>⎢</strong>Stop <strong>⎢</strong>Continue <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>😊 <strong>⎢</strong>😣 <strong>⎢</strong>💡 <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>👍 <strong>⎢</strong>👎 <strong>⎢</strong>🌷 <strong>⎢ </strong>💡 <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>Who are we as a team? <strong>⎢</strong>What is the objective of the team? <strong>⎢</strong></blockquote><blockquote><strong>⎢</strong>Great <strong>⎢</strong>Not So Great<strong>⎢</strong>Thank You’s <strong>⎢</strong>Help Requests<strong>⎢</strong></blockquote><p>A good facilitator will pay special attention to how the team speaks, and<strong> </strong>choose language attuned to the team’s culture<strong>.</strong></p><p>Asking “What was bad?” versus “What was not so good?” could be the difference between a lively discussion and silence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/0*j9q5PCDZL66sOmld" /><figcaption>New grouping “Help Requests” emerged during the retro</figcaption></figure><p>Lastly, avoid defining your question too narrowly. Doing so could exclude topics wherein the real problems reside.</p><h3>5. Conduct the Retro</h3><h4>Reflection</h4><p>Ask your framing question to the group, hand out post-its, and encourage silence. Observe body language cues, this can help anticipate what is to come. If you have new team members, take advantage of their fresh perspective and encourage them to write.</p><h4>Presentation</h4><p>Once everybody has written on their post-its, announce “the floor is now open, for whoever would like to start”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*khpdAcQ38wrS9W-F" /><figcaption>A retro examining a specific incident which, after gathering all the information and generating multiple hypotheses, led to an unexpected solution</figcaption></figure><p>At this point, the team members will take turns to stick their post-its to the wall, read them aloud and explain their significance. Be wary of people sticking up their post-its all at once before explaining them, this makes it harder to refer to them later for further treatment or prioritization. Another thing to watch out for is back and forth discussions, other than clarifying questions, before everybody has presented. This is the fastest way to derail a retro with potentially less important topics. The team’s energy is finite, save it for the most important topics.</p><p>If an emotional presenter looks at you, nod and acknowledge, but avoid engaging just yet. Once everybody has presented, you will have the full picture including everyone’s feelings, observations, and suggestions.</p><p>This is your raw material.</p><h4>Grouping</h4><p>As a facilitator, having listened to the group, and read the post-its; try to identify clear patterns. Are there different post-its branching from the same theme? If yes, ask the group to confirm. If they agree, group the post-its by themes and draw labelled circles around each group.</p><p>The theme labels can influence the forthcoming discussion, so choose them carefully, and remain open to changing them. You could also ask the team to help you name the themes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J8l9OT5z_p5-T8_u" /><figcaption>While not always necessary, you could create themes for “good things” as well. Especially if it is recognizing someone!</figcaption></figure><p>Once the biggest themes have been identified, you could ask the group to come closer to the board, and do the same for the remaining post-its. By engaging the team in this way, it does three things for them: firstly, they practice creating order out of chaos; secondly, they learn to deprioritize that which doesn’t align with any of the main themes; lastly, it gets them warmed up for the next stage — discussing solutions for the themes identified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/857/0*67KhfVb2FyAC5ndE" /><figcaption>Creating order out of chaos</figcaption></figure><p>At the end of this phase, your board should be shaping up, and themes about the major pain points should be emerging.</p><p>If you were to stop right here, it would already be an achievement. You have a holistic view of the problems, with an energized team, invested in solving them. This level of understanding may not have existed before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OLE3R78fiJ8fHd5_" /><figcaption>A complicated retro, with the same theme generating opposing sentiments (notice the lack of written action items)</figcaption></figure><h4>Spark the Fire 🔥</h4><p>You have the haystack (the themes) and the matches (the people), all that is missing is a little controlled fire.</p><p>Sometimes it is helpful to start with an uncontroversial and large theme first to get the team comfortable with the discussion.</p><p>For this, you could select the largest theme and ask your team what they think can be done to resolve the problem at hand. If this is followed by silence, remain patient. The longer the silence, the deeper the thoughts.</p><blockquote>Delay the attack until the team is intimate with the problem.</blockquote><p>Eventually, somebody will make a proposal. If it is directed at you, subtly redirect the question to the team. Give the team a moment to react. If nobody does, pick someone at random, and provoke a response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*UBwiib9vmwxNcY4e" /><figcaption>Mixing elements from different retros, for a squad reboot</figcaption></figure><p>It is unlikely that the second person will agree with no further additions. They will likely add their own insights, which will sharpen the initial proposal, or create stronger alternatives.</p><p>Once the second person has spoken, usually the rhythm of the exchanges will pick up pace.</p><p>The fire is now lit.</p><blockquote>The goal of the fire is to spark multiple points of view, and forge them in the heat of conversation.</blockquote><p>Your job is to keep the fire burning at the right intensity. If it is too weak, nothing of significance will be discussed; if it is too strong, team members might become wary of opening up in the future.</p><p>This exercise allows team members to openly discuss volatile matters that might otherwise lead to more toxic outcomes. It also makes them more likely to adhere to resolutions that were reached by consensus. Lastly, if the fire does not light for a particular topic, give it a rest. Maybe it is not that important after all. Or maybe the team is not ready to discuss it yet.</p><h4>Action Items — Quell the Fire 🌊</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0IX0eWgxuhkhOmwH" /><figcaption>Clear links leading to action items, and named owners</figcaption></figure><p>If you channel the conversation well, there will be an idea for each theme that gathers the most momentum. As time runs out, grab onto that idea and ask the team what they think is the smallest step they can take towards it. Write it on the board, and confirm with the team if they are willing to commit to it. For those who remain hesitant, reassure them that the action item and its impact will be revisited in the next retro. Once everyone is on board, your job is done.</p><h4>Conclusion</h4><p>The trick to a successful retrospective is to delay judgement until a holistic picture emerges (via the reflection and presentation sessions), and the team collectively deduces the themes in this picture (via the groupings). Then, and only then, should you ‘spark the fire’ to invite judgement, analysis, and finally, plans of action.</p><p>This ends the retro with a sense of continuity in the team’s experience, a holistic understanding of the major challenges, a collectively agreed upon plan of action, and the promise of accountability in the next retro.</p><p>And that is the magic of retrospectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*LmEkBkA74uEUCuXG" /></figure><p>Editorial reviews by <a href="https://medium.com/@deanna.chow">Deanna Chow</a>, <a href="https://medium.com/@lielatoure">Liela Touré</a> &amp; <a href="https://medium.com/@sanyal.prateek">Prateek Sanyal</a></p><p>Want to work with us? Click <a href="https://www.ssense.com/en-ca/careers">here</a> to see all open positions at SSENSE!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=140c5c40e77b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ssense-tech/fire-water-and-retrospectives-140c5c40e77b">Fire, Water, and Retrospectives</a> was originally published in <a href="https://medium.com/ssense-tech">SSENSE-TECH</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>