<?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 Sean Harris on Medium]]></title>
        <description><![CDATA[Stories by Sean Harris on Medium]]></description>
        <link>https://medium.com/@growthoutcome?source=rss-eff1c2e6679a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qREs7U2664AO2A2fhSNFlA.png</url>
            <title>Stories by Sean Harris on Medium</title>
            <link>https://medium.com/@growthoutcome?source=rss-eff1c2e6679a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 03:50:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@growthoutcome/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[Soft skills to empower any product or tech professional in their journey.]]></title>
            <link>https://medium.com/swlh/soft-skills-to-empower-any-product-or-tech-professional-in-their-journey-aa9be0b27286?source=rss-eff1c2e6679a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa9be0b27286</guid>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[experimentation]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[growth-design]]></category>
            <category><![CDATA[product-de]]></category>
            <dc:creator><![CDATA[Sean Harris]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 20:55:07 GMT</pubDate>
            <atom:updated>2020-06-12T17:13:27.445Z</atom:updated>
            <content:encoded><![CDATA[<h3>Soft skills to empower any product or tech professional in their journey</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ktKoQnQDyHmQCPFqtpe4fQ.png" /><figcaption><a href="https://unsplash.com/@lux17"><em>Photo by Lucas Clara at Unsplash</em></a></figcaption></figure><h3>Overview</h3><p>I’ve spent the last 8 years of my life working as a Digital Product Designer. This post organizes some of the soft skills I’ve cultivated over the years into a set of “core principles”. For me, these principles have provided a distinct advantage in my journey and have lasted the test of time. This post should be valuable to anyone in the design profession and or tech space.</p><p>I’m sharing these principles in hopes of helping others have success in their professional journey during these rapidly changing times.</p><h3>Background</h3><p>Over the last 8 years I’ve supported a variety of organizations including agencies, startups and the enterprise space across a variety of verticals. All organizations had made varying degrees of progress in their journey towards digital transformation. I’ve had amazing success as an agent of change in challenging enterprise cultures and have gotten my head blown off making a case for design more than once.</p><p>Last Thanksgiving (2019) I was laid off due to millions in reported losses and a massive reorganization. Since then I’ve been at home spending time with my family, building my professional portfolio (for the first time) and unfortunately like many of us, practicing social distancing due to the coronavirus (COVID-19). I’m smiling as I’m typing this, because all of these experiences helped me grow in ways I could have never imagined.</p><p>If you take the time to read this post, please consider leaving a comment. Any themes in feedback will be greeted with open arms and applied to my new portfolio to be released some time between Q1-Q2 this year (2020).</p><h3>The principles</h3><p>The soft skills that have helped me on my professional journey over the years can be categorized into the following “core principles”:</p><ol><li>Lead through inquiry.</li><li>Leverage the collective.</li><li>Know the organization.</li><li>Know the business.</li><li>Everything is an experiment.</li><li>Measure your outcomes.</li><li>Have heart.</li></ol><p>Ok, let’s dig in!</p><h3>1. Lead through inquiry</h3><p>No matter what your role or title, asking empowering questions as a primary means of getting things done, helps cultivate a safe space for creativity, communication and collaboration.</p><p>On the other side of the spectrum, telling people what to do, as a primary means of getting things done, most likely will diminish creativity, slow initiative progress and can have an extremely negative impact on your team’s morale. You may also stifle your own personal growth.</p><p>One of my favorite books “<a href="https://thewisemangroup.com/books/multipliers/">Multipliers</a>” digs into this in great detail.</p><h3>2. Leverage the collective</h3><p>Use your intelligence to amplify the smarts and capabilities of the people around you. You can have a resoundingly positive and profitable effect on organizations — getting more done with fewer resources, developing and attracting talent, and cultivating new ideas and energy to drive organizational change and innovation.</p><p>Participatory design is a great example of this i.e. <a href="https://www.gv.com/sprint/">Design Sprints</a>, <a href="https://www.nngroup.com/articles/facilitating-design-studio-workshop/">Co-Design Workshops</a> and <a href="http://www.liberatingstructures.com/">Liberating Structures</a>. Getting feedback from your team on your work is also a great practice and helps cultivate your own personal growth.</p><h3>3. Know the organization</h3><p>Understanding your organization’s level of commitment to modern design thinking, team structure, and its political landscape will help you optimize your efforts as a design professional. It will also help you avoid obstacles and in a perfect world could help you align with any organizational change before it impacts your role.</p><p>A good way to get started is to have coffee with organizational leaders to get a download of the landscape, gather advice and offer yourself as a friendly resource. Finding an executive sponsor can help you create change safely. Other steps include making sure you’re participating in regular 1:1s with your leadership and maintaining a high-level of awareness in all calls and organizational communications.</p><h3>4. Know the business</h3><p>Taking the time to understand the business drivers behind the service you support helps you make decisions that balance customer need with business goals. At the end of the day, everyone’s paycheck hinges on delivering value to the customer AND helping the organization generate revenue.</p><p>Regardless of your role, educating yourself on the different customer journeys across your organization’s portfolio helps you cultivate a holistic view that reveals how your team’s decisions may impact other parts of the service.</p><p>FYI — My choice method of visualizing the customer journey is <a href="http://www.practicalservicedesign.com/the-guide">Practical Service Blueprinting</a> because it marries the “front stage” customer journey with the backstage supporting “business processes” and it’s easily consumed by any stakeholder group. There is a great online course for this <a href="https://practicalservicedesign.teachable.com/p/intro-to-practical-service-blueprinting/">here</a>.</p><h3>5. Everything is an experiment</h3><h4>Experiments are already running. Reap the rewards.</h4><p>At this very moment, whether you are aware of it or not, your professional role, ideas, processes, and even your personal life are participating in experiments. Cultivating an awareness of your own assumptions and testing them, reduces risk, creates a safe space for feedback, room for pivots and will ultimately lead to growth. When an organization adopts a culture of experimentation it experiences these benefits as well.</p><h4>Growth begins with letting go of outcome.</h4><p>Experimentation aligns well with the Buddhist philosophy of “<a href="https://en.wikipedia.org/wiki/Detachment_(philosophy)">Detachment</a>” where suffering comes from attachment to outcome and or personal belongings. The inverse of this principle is best personified through the practice of “<a href="https://en.wikipedia.org/wiki/Dogma">Dogma</a>” which has the potential to stifle all of the positive outcomes associated with a culture of experimentation.</p><h4>Moving forward.</h4><p>Do you feel like you’re under constant pressure to come up with the “big idea”? Do you feel like you have a “safe space” to learn from experiences in your professional life? your personal life?? If this is a new concept for you, consider loosening your attachment to that “big idea” just enough to validate it and or make it better. You’ll be so glad you did!</p><h3>6. Measure your outcomes</h3><h4>Designing blind.</h4><p>Can you tell me if a customer has seen and or used the six-figure feature, multiple teams spent months to create? Is your team in a constant state of urgency working long hours focused on “just delivering”? Does your organization have a backlog of “big ideas” with little to no background data?</p><p>Do you see regular pivots on major initiatives, throwing multiple teams into confusion and frustration? Is a “reorganization” a common practice at your organization after a failed initiative, generating layoffs and turnover?</p><p>Does any of this sound familiar? These are all potential indicators that your organization may have inadequate means of measuring the impact of their work.</p><p>Your organization’s capacity to measure qualitatively and quantitatively is paramount. Metrics like “new users”, “page views”, “support contact” and “revenue” are extremely high-level and aren’t adequate for measuring the impact of design changes post release (ROI on design).</p><p>Telemetry tools like <a href="http://amplitude.com/">Amplitude</a> and <a href="http://mixpanel.com/">Mixpanel</a> have been around for years. Optimization tools like <a href="http://vwo.com/">VWO</a> and <a href="http://optimizely.com/">Optimizely</a> have also been around for years and yet today, many organizations still can’t measure the impact of their work post release.</p><h4>Risk vs. Reward.</h4><p>The expense associated with improving your ability to measure is a fraction of the expense associated with “designing blind” as an organization. Investing in your ability to measure will not only pay for itself, it will yield an exponential reward across the organization as a whole. It will help validate all those great ideas in your backlog, provide accurate reporting on the performance of your efforts and ultimately, lead to growth.</p><h3>7. Have heart</h3><h4>The unspoken war of the marketplace.</h4><p>Tech roles aren’t for the weary or faint of heart. We are the first responders in the unspoken war of the marketplace.</p><p>There are some unfortunate parallels between the average tech role tenure and how fast consumer markets change. Organizations are constantly “re-organizing” and in turn, generating significant layoffs. Meanwhile, employees AND consumers in the tech space are hiring and firing organizations at break-neck speed.</p><p>Organizations dump millions into contractor roles to move faster than their archaic HR process and as a result have grown a “gig economy” job market where the average tech contractor doesn’t get PTO (paid time off) when they are sick or burnt out. What? No summer vacation? The same applies to other “gig economy” roles outside of the tech contracting industry i.e drivers and food delivery services. “Gig economy” workers pay out of pocket for their time off. Many people are living hand-to-mouth these days and that IS an unfortunate situation, especially if you have a family to take care of.</p><p>Is contracting becoming “fast-food” labor for tech organizations, where the illusion of moving fast is prioritized over the long-term gains that come with investing in the the human? That depends on the organization and who you ask. Some orgs do convert their contractors to permanent roles. Many don’t. At the end of the day, contracting is a voluntary sport and some love it.</p><p>Regarding the design profession, depending on your organization’s culture and ability to measure it’s efforts, making a case for design can be just as traumatic as getting laid off — and sometimes, you do get laid off for making a case for design.</p><h4>Exploring the bright side.</h4><p>I love working in tech. I get to learn from brilliant people while solving complex challenges and driving business impact. It’s addictive and exhilarating. Do you like working from home? Many tech professionals have the luxury of working remotely and on a merits based schedule.</p><p>Depending on the organization and which path you choose you could get vested in an early stage startup and cash out big one day. You might land a permanent role that includes “retention bonuses” paying out an annual sum of $15,000 or more. The promise of a high paying tech salary is real, you just need to fight for it!</p><h4>Charging on!</h4><blockquote>“Life doesn’t get easier or more forgiving, we get stronger and more resilient.”</blockquote><blockquote>― <a href="https://stevemaraboli.net/">Steve Maraboli</a>, Life, the Truth, and Being Free</blockquote><p>For best results, listen and watch your step. Be brave and never stop challenging yourself. Every challenge you encounter will strengthen your armor, sharpen your sword and improve your overall contribution.</p><p>Focus on amplifying the efforts of others over yourself. Don’t be attached to outcome, because nothing is permanent in this fast paced world. Be gentle, have a empathy for yourself, your team members and the organization.</p><p>Be proud of your experiences and carry any scars like a badge of honor, they will serve you well!</p><h3>In closing.</h3><p>Have you leveraged any of these principles in past roles? Does your past experience point to other principles? I would love to learn what has guided you in your journey.</p><p>Feel free to comment here, or IM me at <a href="https://twitter.com/growthoutcome">Twitter</a> or <a href="https://www.linkedin.com/in/growthoutcome/">Linkedin</a>.</p><p>Stay safe and stay resilient!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa9be0b27286" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/soft-skills-to-empower-any-product-or-tech-professional-in-their-journey-aa9be0b27286">Soft skills to empower any product or tech professional in their journey.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to conduct design review meetings that don’t get derailed]]></title>
            <link>https://uxdesign.cc/how-to-conduct-design-review-meetings-that-dont-get-derailed-5807eeda2a63?source=rss-eff1c2e6679a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5807eeda2a63</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Sean Harris]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 00:16:24 GMT</pubDate>
            <atom:updated>2021-09-10T23:40:08.141Z</atom:updated>
            <content:encoded><![CDATA[<h4>Changing the round-table discussion.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YXBZuPsrz1BRZ1RUcSghwA.png" /></figure><h3>Overview</h3><p>This post outlines a great technique for conducting an efficient Design review meeting. I’ve leveraged this approach in startup and corporate cultures with C-Suite participants. In all situations, people have thanked me for the structured and collaborative approach.</p><p>This approach is not exclusive to the Product Design space and can be used to review any idea, process or concept you can think of. If you are facilitating, pitching, presenting or participating in a group review of any kind of content you may benefit from reading this post.</p><p>Quick shout out to Product and Technology leader <a href="https://www.linkedin.com/in/keren-nimmo-42141b/">Keren Nimmo</a> for sharing this technique with me years ago.</p><h3>Traditional design review example. The round-table discussion.</h3><p>Before getting in to the approach, let’s chat a little about traditional team reviews. In the design space, you’ll most likely find recurring team meetings where various cross-functional team leads all meet to review a new app design or design change.</p><p>The format you’ll see most of the time is a “round table discussion” which means anyone speaks up when they have something to say during the review. Participants may include multiple decision makers or maybe the decision maker isn’t present. The duration of the meeting is usually limited to 1hr at best. The lead designer will be facilitating the review and attempting to gather feedback on the design while it’s discussed.</p><p>The goal of the meeting is to generate a shared understanding of the design, identify challenges, opportunities and questions from the team. There also might be a goal of getting a final approval on the design.</p><p>This approach seems like a good idea, or does it? If your presentation skills are light and or you don’t feel like you have the confidence to guide the discussion you could be in trouble.</p><h3>Challenges with the traditional format.</h3><p>Have you ever presented a design or idea and within 5 minutes of kicking off the presentation a team member makes a comment like “from an engineering standpoint this just can’t be done” which led to more conversation and maybe derailed your entire agenda, including completing the actual review itself. Maybe if you had been able to complete the review the team member would have found their comment was unnecessary and accounted for had they waited a few minutes more. Maybe you left that meeting without the information you needed to move forward. Sound familiar?</p><p>I’m not saying the team member’s comment isn’t important. It’s crucial that information like that gets captured and the person citing the comment is rewarded for their knowledge. It’s even more important to thoroughly understand any problems before moving forward with more design work.</p><p><strong>Here are some of the challenges I encountered when conducting team design reviews using the traditional “round table discussion” format:</strong></p><ul><li>Participating in round-table discussion before completing the review can be wasteful. In many cases completing the review will answer questions and invalidate comments made.</li><li>Important discussions begin, but due to the open format it’s tough to capture all the feedback and truly understand the things that matter the most.</li><li>Highly Extroverted or “Bully” participants may keep other team members from being heard, thus limiting the knowledge in the room and putting the design at risk.</li><li>Introverted presenters or participants may have important comments but may not have the confidence to assert themselves.</li></ul><p>If you’re a product designer with at least 2 years under your belt, I’m sure you’ve witnessed these challenges first hand.</p><h3>Let’s try something different. Enter the “Feedback Workshop”.</h3><p>Ok let’s take a look at the approach I’ve been using to bring structure to the round table discussion and solve for the challenges mentioned above when reviewing designs or ideas. For the purposes of this post I’ll use the term “Feedback Workshop” to help differentiate this approach from the traditional “Design review meeting”.</p><h4>Feedback workshop goals:</h4><ul><li>Allow a full review of the design or idea before cultivating discussion</li><li>Create a “safe space” where all communication is welcome and feedback is captured from all participants</li><li>Give all participants a chance to speak</li><li>Reveal patterns in thinking and group consensus</li><li>Identify the basics questions, challenges, likes and ideas</li><li>Support remote participation</li></ul><h3>What you’ll need to conduct the workshop</h3><p><strong>Location: <br></strong>Find a comfortable meeting room with an open wall or whiteboard. For best results, conduct this meeting in-person. If some or all of your participants are distributed you can conduct this meeting remotely using a combination of screen sharing and collaboration tools like Mural, Realtime Board or even Slack.</p><p><strong>Participants:<br></strong>Perfect world, invite all of the people who have impact on the direction of the design. If people who have decision making authority over your design don’t attend the meeting they will have missed out on hearing the groups feedback and you risk having to repeat your efforts. If the key “Decider” can’t be present find their next in command and educate them thoroughly on the value of the Feedback Workshop agenda and its findings. That way they can communicate that to their leadership when the time comes.</p><p><strong>Time:<br></strong>The minimum amount of time needed for this approach is 1 hour. Scheduling 1.5 hrs will provide more time for group discussion. The number of people you include in the meeting will directly impact the amount of time it takes to complete the review. Try and keep the group under 7 people if possible if you want to complete the meeting in an hour. This is a great approach for a large crowd with 15–20+ participants but you’ll need to add time to complete the discussion. Worst case scenario for a large crowd and 1 hour is you capture segmented feedback from everyone but you may need to follow up with certain individuals to elaborate on their feedback.</p><p><strong>Supplies:<br></strong>You’re going to need a stack of post-its and a pen for each participant. That’s it. If your meeting room doesn’t have a big whiteboard pickup some <a href="https://www.amazon.com/Kraft-Paper-Roll-150ft-Brown/dp/B01N6584SD/ref=pd_lpo_vtph_328_bs_tr_t_1/147-1034899-7442603?_encoding=UTF8&amp;psc=1&amp;refRID=734JAGA3CF27FWRWYJKX">butcher paper</a> and tape it to the wall. Another replacement for the whiteboard is a <a href="https://www.amazon.com/Post-Tabletop-563R-Portable-Premium/dp/B00006IA99/ref=sr_1_7?ie=UTF8&amp;qid=1540256496&amp;sr=8-7&amp;keywords=post-it+super+sticky+easel+pad">Post-it Super stick easle pad</a>, the larger the better.</p><p><strong>Feedback Matrix:</strong></p><p>A couple min before the meeting get the “Feedback Matrix” diagram, shown below, up on the wall in the meeting room. You’ll need one of these diagrams for each separate idea or design concept. This diagram will hold the feedback post-its from your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x8EfkBWP6uvWarJKBr5Iwg.png" /><figcaption>Feedback Matrix</figcaption></figure><p>The Feedback Matrix is a simple way way of segmenting feedback into some predefined categories. Providing your participants with predefined categories can inspire different types of feedback and help keep everyone’s comments organized.</p><p><strong>Let’s take a quick look at the categories I‘m using’:</strong></p><ul><li><strong>Likes: </strong>Was there anything you liked about the design?</li><li><strong>Challenges: </strong>Is any part of the design not feasible?</li><li><strong>Questions: </strong>Do you have any questions regarding the design? Are you completely lost?</li><li><strong>Ideas: </strong>Do you have any ideas on how to make the design better? Changes?</li></ul><p>If you’re dealing with a big team you’ll need more room. If you have a large group or you’re just working with an empty wall and no paper you can use <a href="https://www.amazon.com/GripBlueTM-Multi-Use-Painters-Premium-Multi-Surfaces/dp/B0747YZ391/ref=sr_1_2_sspa?ie=UTF8&amp;qid=1540257365&amp;sr=8-2-spons&amp;keywords=blue+masking+tape+1+inch&amp;psc=1">blue masking tape</a> to create the diagram.</p><h3>How it works</h3><p>Here’s a quick overview of the approach:</p><ol><li>Each participant is given a stack of post-its and a pen.</li><li>The presenter will conduct a brief and hopefully un-interrupted review of the design while each participant is silently writing their feedback on post-its. Post-its should include the participant initials, the type of feedback from the matrix i.e. Ideas, Likes, Questions and Challenges.</li><li>After the review is complete the participants place their post-its on the wall in each Matrix category.</li><li>The presenter or facilitator quickly starts reviewing each post-it calling on author to speak to the feedback for a quick 1–2m max. The presenter clusters quickly in real-time during the review avoiding belaboring points. This process is fast, fast, fast. You’ll know you’ve done a great job when conversation is buzzing from all seats at the table.</li></ol><p>Once the shared brainpower of the team has been fully exposed through a collaborative exercise it’s time to determine next steps. Next steps may require additional discussion depending on the complexity of feedback and on if the decider was present. In those cases, entering the feedback into a spreadsheet may be helpful.</p><p>At this point, you should have complete and total permission to bask in the fact that you are a rock star at cultivating collaboration.</p><p><strong>Here are some photos of the Feedback Matrix in action:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*0rWiZwaCsDZnjf-XW4E_vw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*44AOq0rYAwx6tcdCMkdetQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*0ZidSNATwbQACRhLvkz8LQ.png" /><figcaption>FYI — You can experiment with different categories. Since the time these photos were taken, I’ve replaced the category “Changes” for “Challenges”.</figcaption></figure><h3>Sample Agenda</h3><p>Here’s a sample agenda using 1.5 hours of time to collect feedback from 5–7 people on a design that can be reviewed in 10–15m without interruption. For best results, educate your group on the agenda long before the workshop. Use this time to try and identify and solve for any friction from the participants before actually conducting the exercise.</p><p><strong>Overview — 5m:</strong> Briefly explain the workshop agenda and answer any quick questions.</p><p><strong>Background — 10m:</strong> Review the background data supporting the design or new idea. Perfect world, talk about your user, value of design to the user, business value and success KPIs.</p><p><strong>Conduct the design review — 15m:</strong> Presenters begin the review while participants capture segmented feedback on post-its</p><p><strong>Feedback lightning review and clustering — 30m:</strong> Presenter facilitates lightning reviews of the themes from the post-its. Fast, fast, fast.</p><p><strong>Prioritization &amp; next steps — 30m:</strong> The presenter guides the decider or decider’s proxy towards a decision on next steps.</p><p><strong>Retro — 15m (Optional):</strong></p><p>If this is your first time using this process with your team consider conducting a quick retro on the workshop. Draw the below image on the whiteboard, a smile for what went well, a flat facial expression for things that participants were unsure of and a frown for things we could have done better in the meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2V5JeXfewoRJWM7-bQjlA.png" /></figure><p>Let participants come and self-report in the moment how they felt about the exercise by writing feedback under each face. Whether startup or corporate culture this approach is your friend. Use it to create a safe space for communication and improve future workshops.</p><h3>In closing. Long-term rewards.</h3><p>While operating as a Lead UX Designer in one of my past roles, our team noticed a pattern of combative behavior in our reviews that would end up derailing the meeting before a review of the design work could be completed. All of the meeting participants were working against an aggressive deadline and tensions were high. In an attempt to resolve this toxic pattern, we decided to make the Feedback Workshop policy for all review meetings.</p><p>After leveraging the Feedback workshops for a few weeks the communication during meetings improved dramatically because people were no longer competing to have their voices heard. In general, this workshop agenda helped heal what had become a very challenging environment to discuss design in. After a while, we didn’t need the Feedback Workshop to review designs. Participants just carried themselves with empathy for the presenter and the group as a whole.</p><p>If you’re encountering challenges while conducting design reviews I encourage you to try this approach. If you do try it or have questions or comments please contact me on <a href="https://www.linkedin.com/in/seancharris/">Linkedin</a>. I’d love to hear how it went. Riff on this workshop. If you make a change or an improvement I’d love to hear about it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5807eeda2a63" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-conduct-design-review-meetings-that-dont-get-derailed-5807eeda2a63">How to conduct design review meetings that don’t get derailed</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>