<?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[Bleacher Report Design - Medium]]></title>
        <description><![CDATA[Thoughts from the B/R Design Team - Medium]]></description>
        <link>https://medium.com/bleacher-report-design?source=rss----bfa662314d5b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Bleacher Report Design - Medium</title>
            <link>https://medium.com/bleacher-report-design?source=rss----bfa662314d5b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:35:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/bleacher-report-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Meet Thomas Lei, our Senior Product Designer at Bleacher Report]]></title>
            <link>https://medium.com/bleacher-report-design/meet-thomas-lei-our-senior-product-designer-at-bleacher-report-318f27f6797c?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/318f27f6797c</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Marie Shatara]]></dc:creator>
            <pubDate>Wed, 24 Aug 2022 13:02:58 GMT</pubDate>
            <atom:updated>2022-08-24T14:32:00.430Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fEuw0ZyMfSWJezOT4ICQ8Q.png" /></figure><p>Meet Tom — our veteran Senior Product Designer at Bleacher Report. He’s an esquire-turned-designer who loves to mentor, travel, and is making a big impact on sports culture.</p><h3>So Tom, where are you from?</h3><p>NYC born, SF harvested, currently hustling in LA. And no, I don’t miss east coast winters.</p><h3>How did you get into design?</h3><p>Before transitioning to design, I had been practicing law as a corporate attorney in a previous life. You wouldn’t know it by the man bun, but I used to live in a suit. While I was good at it, it was also sucking the creative soul out of me. I was an esquire by trade, but a creative at heart. As I began to appreciate the person I really wanted to be, my focus became more about pursuing my passions and less about what I thought society’s perception of me should be.</p><p>That being said, I’d been a closet creative for as long as I could remember. As a child, I was a curious, visual learner. I’d marvel at the colorful branding of team uniforms in <a href="https://www.slamonline.com/the-magazine/oral-history-of-the-legendary-slam-15-cover-shoot/">Slam</a>. Playing organized baseball in my formative years, I was fascinated by the nuanced designs of <a href="https://thomasvonlei.com/wp-content/uploads/2017/07/baseball-gloves.png">mitts</a> for the needs of each position. And as a competitive <a href="https://thomasvonlei.com/wp-content/uploads/2017/07/b2b-champs.jpg">runner</a>, I found it remarkable how the innovative <a href="https://www.businessinsider.com/nikes-first-running-shoes-were-made-in-a-waffle-iron-2015-7">pattern</a> of my track flats translated into better performance. In high school, I would express myself through digital mediums like MS Paint and then PS, Illustrator, and HTML/JS later on as my college fraternity’s webmaster.</p><p>I think I always knew I’d somehow end up in some kind of creative space. It just took time to build up the confidence to do it (also, I just ran out of excuses). The leap from law to design was both exciting, challenging, and rewarding all at once. Fortunately, my background provided a tremendously beneficial skill set that helped bridge the gap. As a former attorney, I was required to understand what drove my clients. As a young UI/UX designer, I used that critical thinking to harness the user’s feelings, thoughts, and needs. In both professions, there was a hypothesis to prove, a commitment to research, and a carefully painted story containing facts to support the solution.</p><p>When I’m immersed in design, it is without a doubt the best version of myself. If something is important enough to you, you’ll eventually find a way to dedicate the time and energy to making it happen.</p><h3>What’s your role at Bleacher Report?</h3><p>I’ve been at Bleacher Report for 5 years now. In that time I’ve worked on our Scores, Stats, Games, and News experience, shifted over to Sports Betting, then some parts Growth, some parts Revenue, and was previously on our Live Video, Connected Devices, and PPV experiences.</p><p>Currently, I’m on the amazing team that works on Community Activities and Roles. I focus on better ways to organize and create structure and safety for our communities while spotlighting the best conversations to elevate healthy, passionate discussions. I also develop features that empower our content creators while promoting fanbase UGC and the users behind them. Finally, I continue to support our Sports Wagering initiatives by educating our fans in the betting space as well.</p><p>At the end of the day, it really just comes down to figuring out what is the best possible journey for the user to really drive the conversation around those sports moments that matter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pn8cDfZtLw_ONOIHQ-Di9A.png" /></figure><h3>What made you want to join Bleacher Report?</h3><p>I was hired as designer #4 back in 2017 when the company had just been acquired by Turner and they were doing a complete rebrand of the app. I think back then what drew me to the team was that we were a small, scrappy band of talented misfits that weren’t afraid to be bold or brash with the opportunity to create and design things that didn’t exist. It had a start-up-type excitement to it and all of that fostered a tight-knit familial bond that I still cherish to this day.</p><h3>What’s a guilty pleasure right now?</h3><p>I recently came back from a trip to Northern Italy where I learned how to make fresh pasta in Florence. So I’ve been trying to get better at that. Guilty pleasure? Maybe more a labor of love right now. <em>Channels inner Aziz Ansari.</em>👨‍🍳</p><p>I also take building Legos very seriously and am a bonafide AFOL (Adult Fan of Lego). Credit my parents for this as it most likely promoted visual thinking and spacial development at an early age. That interest graduated into a hobby/passion where I now have roughly over two thousand Lego sets. And if I wasn’t in the process of moving all of them to a dedicated room in our new house at the moment, you bet I’d be sharing photos of them here. But I’m always building! 😊</p><h3>How do you spend your free time?</h3><p>It’s got to be traveling right? I’ve been to six continents and am looking to visit Antarctica this year for my birthday to make it all 7! My favorite experiences are probably ones that are more off the beaten path. Living in a felucca on the Nile, breaking bread with locals in Aswan, watching the sunrise in Angkor Wat, and swimming in the Grotta Azzurra in Capri come to mind.</p><p>There’s something about meeting people from different far reaches of the world and realizing we’re all just really trying to figure this thing called life out. Oftentimes in my travels, the happiest individuals I’ve come across also just so happened to have the least. Rephrased, their wealth wasn’t necessarily defined or measured by traditional means or material possession. I’ve found that it’s given me a more humble, appreciative, and empathetic outlook on life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ALPCZMuSgWnVDB1uuzoE7A.png" /></figure><h3>What’s your favorite thing about living in Los Angeles?</h3><p>The food scene here is second to few. The arts and music scene is great too if you’re into that, which I am. Also the beaches. I’m still a city boy through and through, but there’s something about being twenty minutes from the Pacific Ocean and spending a day there just to reset. My dog Sir Bixby loves the beach. It might just be his happy place.</p><h3>What would your walk-up song be?</h3><p><em>Uproar</em> by Lil Wayne. Not coincidentally, it’s also the song my wife and I entered to for our wedding 😂</p><p><em>Ima Boss</em> by Meek Mill would be the guilty pleasure walk-up song. It’s a lot of bravado though. You have to come correct for that one.</p><h3>What’s one thing you wish more people knew about you?</h3><p>I find mentorship incredibly fulfilling. I try to mentor young designers who made a career switch like myself as much as possible outside of work. I had great mentors coming up and in some twisted, cathartic and self-enriching, guilt-laden way feel the need to give back and pay it forward however I can.</p><p>Also if I wasn’t a product designer I’d probably want to open my own sneaker store. That or an artisanal ramen shop.</p><h3>What’s your favorite thing about Bleacher Report?</h3><p>While Bleacher Report is a sports media company at its core, it’s really so much more than that.</p><p>I’ve always seen it as this innovative intersection of sports, music, fashion, and social justice issues, catered towards Gen-Z and millennials and their consumption behaviors. So it really is a reflection of popular culture through the lens of sports for the scrolling generation.</p><p>I also feel blessed to work with such talented designers that I get to call my peers and continue to get inspired by them every day. It’s what keeps me motivated. One thing we’ve always advocated and continue to is, that in order to thrive and succeed as a designer, you have to be able to show up as your authentic self.</p><p>Finally, I’m proud to be part of a diverse team of designers that collectively hail from all genders, races, backgrounds, and walks of life. This isn’t always the case or easy in a traditionally male-dominated environment that is the sports industry.</p><p>It’s always been important to us that our team represents and reflects the diversity of our fans.</p><h3>How can designers find out more about Design at Bleacher Report?</h3><p>There are a lot of exciting new features we’re currently working on that I think will really take what the app is at the moment to the next level. One thing I can say is that behind the scenes we do a lot of listening with our fans. The great thing about B/R users is that they are wildly loyal and we make the extra effort to make them feel like they’re involved and a part of what we do.</p><p>We’re always looking for talented, passionate designers. And not just for Product Design roles but for Motion, Content, and Innovation design as well. It’s a great culture and environment. We work hard and we play hard because at the end of the day it’s sports, right? You’re supposed to have fun!</p><p>If you’re curious about learning more about Design at Bleacher Report and what we do, a good place to start is <a href="http://design.bleacherreport.com/">design.bleacherreport.com</a> and <a href="http://brand.bleacherreport.com/">brand.bleacherreport.com</a>.</p><p>As for me, I’m always happy to talk shop. Feel free to reach out at <a href="/service/mailto:thomas.lei@warnermedia.com">thomas.lei@warnermedia.com</a> ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=318f27f6797c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/meet-thomas-lei-our-senior-product-designer-at-bleacher-report-318f27f6797c">Meet Thomas Lei, our Senior Product Designer at Bleacher Report</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet Cameron Cline Martinez, our Senior Product Designer at Bleacher Report]]></title>
            <link>https://medium.com/bleacher-report-design/meet-cameron-cline-martinez-our-senior-product-designer-at-bleacher-report-873cce374f13?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/873cce374f13</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Marie Shatara]]></dc:creator>
            <pubDate>Thu, 28 Jul 2022 13:03:06 GMT</pubDate>
            <atom:updated>2022-07-28T16:00:32.375Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eptOVPjqAIC14TOzJsXnFw.jpeg" /></figure><p>Meet Cameron— our new Senior Product Designer at Bleacher Report. She’s an outdoor enthusiast and a developer turned designer, who brings a unique perspective to B/R.</p><h3>So Cameron, where are you from?</h3><p>I grew up on the California Central Coast, graduated from San Diego State, and now live in Los Angeles. I moved to LA right after graduating when I joined AmeriCorps. During my year of service, I grew to really love the city and decided to stay.</p><h3>How did you get into design?</h3><p>After graduating from college with a degree in International Security and Conflict Resolution, I started work at a non-profit organization as a grant writer. They also needed design help for events, mostly print materials like invitations, posters, etc. Growing up I always had a creative side, so I volunteered to help and it ended up being the most enjoyable part of my job. Eventually, I was also tasked with creating their event websites so I taught myself to code and it eventually became my full-time job.</p><p>After leaving the non-profit, I worked as a designer and front-end developer for freelance clients and then eventually a design agency. I liked coding but felt something was missing. When I started working at Warner Bros. as a designer and developer, I worked under a fantastic mentor who taught me everything she knew about UX design. I had the freedom to experiment with ideas and learn from my colleagues and it led me down the path to product design.</p><h3>What’s your role at Bleacher Report?</h3><p>I am a Senior Product Designer for the Activities &amp; Roles team. So far, my projects have been centered around building upon the community that exists in the app with the goal of making it easy and enjoyable for fans to experience sports moments together.</p><h3>What made you want to join Bleacher Report?</h3><p>Bleacher Report as a brand always stood out to me as having a unique voice in the sports world. I was really interested in how this was translated into the UI of their digital apps. I also have an interest in analytics and user research and thought an application with a large user base like BR would be a good way to gain more experience in this field.</p><h3>What’s a guilty pleasure right now?</h3><p>Reality TV is my top guilty pleasure now and always. My favorite is Real Housewives, I watch every city 😬</p><h3>How do you spend your free time?</h3><p>I love being outdoors — camping and hiking. I also love watching movies, gardening, and gaming. My husband and I are also big LA Clippers fans and enjoy going to the games.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rt0atR9fekMyfu2Nw_oQpw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRYYE6HUd2nUrvWrz0vGaA.jpeg" /></figure><h3>What hidden talent do you have?</h3><p>I’m pretty good at racket/paddle sports — tennis, pickle ball, ping pong.</p><h3>What’s your favorite thing about living in LA?</h3><p>The restaurants and easy access to nature. I think if I ever were to move out of LA the restaurants would be what I miss the most. I love that you can find basically any type of cuisine here. Also, I love that you can choose to be in the desert, the mountains, or the ocean within basically 2 hours.</p><h3>What would your walk-up song be?</h3><p>My walk-up song would be “Like a Girl” by Lizzo.</p><h3>What’s one thing you wish more people knew about you?</h3><p>I take composting very seriously. It’s something that’s relatively simple and can potentially have a large impact on the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BuOD5RHier797eSx3qfIdQ.jpeg" /></figure><h3>What’s your favorite thing about Bleacher Report?</h3><p>I appreciate the value that’s placed on discovering how we can work best both individually and as a team. There is a lot of consideration around how to optimize communication and create an environment where we can do our best work. There is also a lot of emphases placed on design exploration. We’re encouraged to explore potentially unconventional solutions and given the time and space to do so.</p><h3>How can designers find out more about Design at Bleacher Report?</h3><p>I’m always open to chatting. Feel free to reach out to me at <a href="/service/mailto:Cameron.martinez@warnermedia.com">cameron.martinez@warnermedia.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=873cce374f13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/meet-cameron-cline-martinez-our-senior-product-designer-at-bleacher-report-873cce374f13">Meet Cameron Cline Martinez, our Senior Product Designer at Bleacher Report</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Created More Inclusive and Efficient Design Critiques with Round Robin]]></title>
            <link>https://medium.com/bleacher-report-design/how-we-created-more-inclusive-and-efficient-design-critiques-with-round-robin-f1e12a7dea31?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/f1e12a7dea31</guid>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-critique]]></category>
            <category><![CDATA[design-feedback]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Marie Shatara]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 12:52:58 GMT</pubDate>
            <atom:updated>2022-07-21T12:52:57.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iCQoPlFF083T97DJuHsnRA.jpeg" /></figure><p><strong>Round Robin</strong> is an inclusive feedback method that allows participants to share their perspectives one by one, making their way around the (virtual) table. This method provides two clear advantages:</p><ol><li><strong>Everyone contributes.</strong> People are no longer overshadowed by one or two dominant voices in the room, but instead given an equal opportunity to speak.</li><li><strong>More feedback in less time</strong>. The rapid-fire feedback cycle allows presenters to gather as much feedback as possible in as little time as possible so that they can keep iterating on their projects. This also allows more people to present in the allotted time.</li></ol><h3>How it Works</h3><h4>1. Presentation</h4><p>A designer will first present their work to the group which helps set the stage for the rest of Round Robin. Their goal is to collect as much feedback as quickly as possible in order to continue to iterate on their designs. This means preparation and brevity are key so the emphasis of Round Robin is placed on the feedback.</p><p><strong>A successful presentation will outline the following:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HdfQjA4izF_qae62NmIn8g.jpeg" /></figure><p><strong>Some tips to prepare for Round Robin:</strong></p><ul><li>Utilize asynchronous tools to communicate your work ahead of the meeting. This could be putting links to your Figma in Slack with a brief project overview or perhaps making a Loom video walking everyone through your file. Give enough time for everyone to participate ahead of the meeting so that the time in Design Critique can be better spent on feedback.</li><li>Practice listening and hold back the need to rebuttal. Rather, listen and ask clarifying questions. Remember this is an opportunity for you to collect valuable feedback, so be sure to take notes. You will have an opportunity to share additional thoughts about your project once everyone has a chance to give their feedback.</li><li>The feedback should be helpful in order for you to continue to iterate on your project. If conversations get sidetracked or feedback isn’t what you are looking for (e.g. talking about visual design when you are only in the wireframe stage), then steer the conversation back by gently reminding everyone what to focus on or by tabling a topic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NYRKLwJR_DetOVsyzz9YZw.png" /><figcaption>Using Loom is a great way to explain your work asynchronously</figcaption></figure><h4>2. Round Robin</h4><p>After the presenter is finished, participants will share one piece of feedback until everyone takes a turn. This process can repeat until there is no new feedback left. The objective is to include as many perspectives as possible and allow everyone the opportunity to speak.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCfbWWESJCgh_OEJOaZpow.jpeg" /></figure><p><strong>Best practices for feedback:</strong></p><ul><li>Not everything needs to be feedback, you can also ask questions or make a comment.</li><li>If someone says something that you agree with, you can simply say “+1” to reinforce the message and leave a separate comment.</li><li>If you have gone around more than once and you have nothing new to add, then say “pass,” until no one has anything left to add.</li><li>Minor notes can be left as comments in Figma after Round Robin.</li></ul><h4>3. Wrap-up</h4><p>After Round Robin is complete, the presenter can recap or comment on the feedback. This is simply to wrap up any final thoughts before moving on to the next presenter.</p><p><strong>Here’s an example of what a Round Robin could look like:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*af6rM3SYgbwYkJpKKpb8pQ.jpeg" /></figure><h3>Trying it Out</h3><p>If you’re thinking to give Round Robin a try, we’d love to hear how it’s worked for you. Feel free to let me know in the comments or email me at <strong>marie.shatara@warnermedia.com</strong>. We look forward to hearing from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1e12a7dea31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/how-we-created-more-inclusive-and-efficient-design-critiques-with-round-robin-f1e12a7dea31">How We Created More Inclusive and Efficient Design Critiques with Round Robin</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Effective Teams with Leadership Philosophies]]></title>
            <link>https://medium.com/bleacher-report-design/building-effective-teams-with-leadership-philosophies-a3ef07361bcb?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/a3ef07361bcb</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Marie Shatara]]></dc:creator>
            <pubDate>Tue, 13 Apr 2021 17:38:58 GMT</pubDate>
            <atom:updated>2025-08-05T20:38:50.703Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*agyIWFqXS07p-9CK058Etw.jpeg" /><figcaption>Illustration by Cynthia Kittler</figcaption></figure><p>Design teams thrive when leaders establish the right conditions for designers to find inspiration, purpose, and motivation. Leadership is not about power, followers, or getting your way. It’s about creating an environment where designers eventually grow into leaders themselves. Bringing out the best in our designers doesn’t happen by accident. It comes with deliberate intention and careful planning. That’s why we established our Product Design Leadership Philosophies at <a href="https://design.bleacherreport.com/">Bleacher Report</a>, a set of guiding principles for how we lead our design team.</p><p>Leadership philosophies are like cooking. Just like managing, cooking can be done in a variety of personal styles. But no matter what, you need the right ingredients and tools to lead to create a successful outcome. So imagine if you were asked to make the perfect meal without a recipe. You might understand all the basic ideas, but at the end of the day, you make a lot of missteps that lead to a less than desirable outcome. We can’t expect the best outcomes for our teams if we don’t understand how we are going to get there.</p><p>Now imagine adding multiple cooks to the kitchen. Each cook brings their own personal flair, experiences, and habits. The result could be a meal that lacks cohesion. This is why it’s important to establish consistent manager expectations throughout the department so it doesn’t feel like there are too many cooks in the kitchen with vastly different styles. Designers, just like most people, crave stability. They need to know that they will be coached the same way and are heading in the same direction regardless of who their manager is. Leadership philosophies help make that happen by bringing in that needed consistency.</p><p>We’ve identified four main ingredients that are key to happier teams and better outcomes: Trust, Support, Growth, and Inspire. This led us to perfect our recipe for success by writing our Product Design Leadership Philosophy. Let’s take a closer look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wvhj92ISDcaYtRoDFMXxJA.jpeg" /><figcaption>Illustration by Cynthia Kittler</figcaption></figure><h3>TRUST</h3><h4><strong>Optimism</strong></h4><p>We believe optimism can change everything. Making negative assumptions and defaulting to the worst-case scenario can not only be frustrating but make people unhappy and unmotivated. Instead, we trust that people have the best intentions. We do this by thinking the best of people, actively listening, practicing empathy, and asking clarifying questions.</p><h4><strong>Trust by Default</strong></h4><p>We treat people like professionals who are capable of doing their job and making good decisions. We don’t tell people what to do while ignoring their skills. After all, everyone comes to the table with a unique set of skills and perspectives we rely on to drive the process forward. When they prove themselves otherwise through their performance and behaviors, we course-correct by retrospecting to identify necessary adjustments to learn and avoid similar missteps in the future.</p><h4><strong>Embrace Risk-Taking</strong></h4><p>We empower our team to embrace risks and treat any shortcomings as learning opportunities regardless of the outcome. Creating a safe space to get messy, trying new things, and making mistakes help strengthen our team’s trust. It also helps make going into uncharted territory feel exciting rather than paralyzing. We praise risk-taking and learning opportunities publicly or privately to help the team learn from others’ accomplishments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VIcLh0EtSe8NksRl_asI7g.jpeg" /><figcaption>Illustration by Cynthia Kittler</figcaption></figure><h3>SUPPORT</h3><h4><strong>Invisible Partner</strong></h4><p>By influencing in an undetectable way, we allow the efforts of others to become more visible so that new leaders can emerge. We stay in close communication with the team and partners so we have a better idea of what’s going on which helps us anticipate or triage problems. By working behind the scenes, we can remove obstacles so our team can do their best work. We do this by allocating budgets and resources, creating alignment with partners, and advocating for the team and their ideas with stakeholders.</p><h4><strong>Air Cover Leadership</strong></h4><p>We have an eagle-eye view of the organization to boost our strategic and holistic understanding of every project. Instead of directing the work or providing solutions, we use our knowledge to ask questions, identify holes in logic or unseen opportunities, and foresee potential overlaps with other projects when reviewing the work of our team. Our role is to be supportive, enrich proposed solutions, or help the team decide when it’s time to let go of an idea not worth exhausting.</p><h4><strong>Empathetic Leadership</strong></h4><p>We care personally about our team’s needs, hopes, and dreams. That’s because we treat individuals as people, not as interchangeable objects. We practice vulnerability to show our team that it’s safe to be vulnerable back. We apply empathy so we can approach situations thoughtfully by understanding their point of view before jumping to conclusions. We demonstrate a willingness to help and provide proper support regardless of it being a personal or work-related problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FafG5yoth8A18du8FRxjA.jpeg" /><figcaption>Illustration by Cynthia Kittler</figcaption></figure><h3>GROWTH</h3><h4><strong>Growth Mindset</strong></h4><p>We believe that talent can be developed through hard work, good strategies, and input from others. When we transform challenges into opportunities, we become more resilient and self-motivated. Our teams are focused on getting better at what they do by striving for their personal best. Even when it’s difficult, we encourage them to keep trying and not give up because we know this process will lead to their success. By continually learning from feedback, achieving what they set their minds to, and seeking inspiration from others, our team becomes a force to be reckoned with.</p><h4><strong>Promote Radical Candor</strong></h4><p>We apply radical candor because we believe candid and constructive feedback is core to our team’s growth. While we challenge directly, we do so with genuine care for each individual. We do this by providing personal and private feedback to avoid misinterpretations or hurt feelings. When an issue arises, we give timely feedback so no one is caught off guard. We deliver concrete feedback that supports our rationale, listen thoughtfully, and proactively set clear expectations with the next steps for ourselves and individuals.</p><h4><strong>Adaptability</strong></h4><p>We actively seek management feedback to understand how we positively or negatively impact our team, both publicly and privately. Being humble and open to criticism creates safety and trust essential to a healthy working relationship. We listen to the true intent of their perspective and challenge our assumptions before jumping to conclusions. When we make mistakes or make things more difficult, we have humility, self-reflection, make necessary adjustments, and follow up accordingly. We recognize that our strengths and weaknesses can affect others. We adjust our style based on the impact we may have on each individual. For some, a hands-on approach can be frustrating, while others welcome extra guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iZ67W-I-LmdaBJtbwOMkYw.jpeg" /><figcaption>Illustration by Cynthia Kittler</figcaption></figure><h3>INSPIRE</h3><h4><strong>Creating Purpose</strong></h4><p>When portfolio-worthy Product Design projects don’t go to plan or even ship, it leaves employees feeling unsatisfied, unmotivated, and makes retention difficult. Rather than relying solely on these projects for fulfillment, our team finds opportunities that align their career goals with impactful and inspiring initiatives. By pursuing passion projects, our team develops a sense of purpose while mastering the skills they need to level up. Our role as managers is to provide the necessary time, resources, and support to achieve the desired outcome.</p><h4><strong>Future-Focused</strong></h4><p>We look beyond today’s status quo and perils by providing an inspiring vision for the team to rally behind. Instead of being reactive to frustrating daily situations, we are future-focused by being proactive and action-oriented to get ahead of these challenges. When we hear “this is how it’s always been done,” we challenge ourselves to think beyond the limitations of today so we can achieve a greater goal. We view our work, tools, processes, and vision as an evolution to help us focus on the future.</p><h4><strong>Lead by Example</strong></h4><p>We strive to be a source of inspiration for our team by setting the right example. We do this by keeping our promises, building trust, and gaining respect to motivate our team toward good results. We show our team what it’s like to have a good work ethic while caring for our mental health and work/life balance by taking time off. We don’t place expectations on the team without living it ourselves, which is why we embody our principles. We know that our team will be willing to go the extra mile when we’re not afraid to get our hands dirty and help out. By leading by example, we hope to be the people that will inspire them in their careers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3ef07361bcb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/building-effective-teams-with-leadership-philosophies-a3ef07361bcb">Building Effective Teams with Leadership Philosophies</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Crit Playbook]]></title>
            <link>https://medium.com/bleacher-report-design/the-crit-playbook-e9fbb957bc07?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/e9fbb957bc07</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:42:04 GMT</pubDate>
            <atom:updated>2023-07-17T15:53:34.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9S2vG81KQCPIoNzWIypYUA.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>A Four Part Series</h4><p>Welcome to the Crit Playbook! Feedback on your work is important for every designer. We’ve written about some of the ways our team makes our Design Critiques the most effective. Each part of this series offers guidance and best practices on the different aspects of a design critique meeting.</p><ul><li><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1: Introduction</a></li><li><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a></li><li><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a></li><li><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9fbb957bc07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/the-crit-playbook-e9fbb957bc07">The Crit Playbook</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 4: The Role of Design Critique In Decision-making]]></title>
            <link>https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/33170d9599a1</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[critique]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:37:10 GMT</pubDate>
            <atom:updated>2019-09-24T17:37:10.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUxsKPccU3HW8DRanFdf_g.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p>The final part of this series will talk about the attitude and approach to take toward design critique within the larger context of your team and the impact it has on your day-to-day decision making.</p><h3>Attitudes Toward Critique</h3><p>As a designer, your team is trusting and relying on you to be a decision-maker for your project. You should not lean on Crit as a place where you get direction. Your team can’t make your decisions for you!</p><p>Conversely, a team should not expect the feedback from Crit to dictate the final solution. Even if the director of product is in attendance and providing input, in Crit everything is take-it-or-leave it feedback.</p><h3>Crit Is Not An Approval Process</h3><p>Crit shouldn’t feel like a committee of art directors reviewing and approving work. It’s meant to provide healthy discussion and outside points of view. Crit should not be where decisions are made, debated, or approved. Crit is a place for open-minded discussion.</p><p>Following a style guide or brand standards is likely a constraint of your work. Some teams may need an approval process to make sure designs comply with pre-set guidelines. These evaluations and approvals should happen in a dedicated meeting. The outcome of an approval meeting is similar to a pass or fail test while the outcome of Critique is take it or leave it feedback.</p><h3>Crit Is Not For Strategy Pivots</h3><p>The process of setting a strategy for an area of work involves many layers of decisions, multiple people, meetings, and discussions. Designers should be actively involved in helping shape the strategy for their area of work.</p><p>In Crit, it can be helpful to include details on how the work you’re presenting connects to the roadmap for your team or broader product vision. But the strategy has likely been through rounds of feedback before you began producing work. This makes it difficult to discuss changes in strategy without the right stakeholders in the room. But it’s possible for input on strategy to come up in Crit that needs consideration. In that situation, you could choose to:</p><ul><li>Take down a note about the feedback and ask to follow up in a separate meeting. This ensures the feedback is heard, provides a dedicated time for discussion with the right set of people, and keeps the rest of Crit on track.</li><li>Timebox the conversation during Crit. Offer to take the next 5–10 minutes to discuss the feedback so the entire group is included in the conversation. Remember, you still need to use the rest of your time to get the feedback you specified. If the discussion goes beyond the timebox, the conversation probably merits a separate meeting.</li></ul><h3>Crit Is Not Show and Tell</h3><p>Part of your responsibility as a designer is to keep your design team aware of your progress, and it’s tempting to use Crit as a way to socialize work. The whole design team is conveniently in the room, you can show your progress and let everyone know that you have<em> in fact</em> been busy working. It can feel easier than documenting your progress. However, this isn’t the best use of everyone’s time.</p><p>The purpose of Crit is to receive input. If you aren’t looking for input and just want to share, it’s best to publish your work to message boards or share your progress during meetings meant for status updates.</p><h3>Keep Your PM In the Loop</h3><p>It doesn’t happen often, but it’s possible that in a <em>single </em>Crit, the team has helped you realize you’ve been going about your solution all wrong. Maybe you’ve done too much! Or too little… or drifted from the original problem. You might be thinking, “My PM is gonna freak out if we change direction.” or “I’ve invested so much time in my current solution… I’ll slow down the team if I pivot now.”</p><p>PMs are great thought partners! If you feel you need to explore a new direction, discuss the points raised in Crit with your PM. Help them understand why you think making a significant change is important to the user experience and the goals your team has set. Ask for their input, and their help in figuring out how to execute on the ideal solution while managing the team’s timeline. Even if they’re not in Crit, they still need to be part of the conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35jzQwqwCn0uu34RLLMCGw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>Get Feedback Outside of Crit</h3><p>Most teams have a weekly Crit. Waiting until the next meeting to get feedback can slow down progress on your work. It’s helpful to have tools to get input throughout your process.</p><h4>Asynchronous Feedback</h4><p>Exploring button styles? Typography? Or specific visual design choices? Decisions that are more tactical or small in scope don’t require a meeting. Tools that enable asynchronous design feedback can help you get input from your team as they have time throughout their day.</p><h4>In-person Meetings</h4><p>Maybe you could use a second pair of eyes on a problem that’s a bit larger in scope or hard to explain if you’re not doing it in person. Set up one-on-one time with a teammate or ask if you can stop by their desk for their input. Ask another designer, a PM, an engineer, or anyone who you think might have a helpful point of view!</p><h3>In Conclusion</h3><p>Overall, design critique is meant to be a place where designers can come together and offer helpful input on each other’s work. Maybe more than other roles and professions, designers recognize that good design can’t be made in solitude. You’ll never get it exactly right on your own. The best work comes from creativity, open-mindedness, and scrutiny.</p><h3>See Full Series: The Crit Playbook</h3><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33170d9599a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 3: Feedback]]></title>
            <link>https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/c7eac60d878d</guid>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:50 GMT</pubDate>
            <atom:updated>2019-09-24T17:39:29.587Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qzuN-mFRk1wT70ICp0fuAQ.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p>So far in our series we’ve focused on being prepared, individually, for Crit. Part 3 will dive into the conversations during the meeting and offer guidance on how to make sure we’re supporting each other while also being honest and direct with our feedback.</p><h3>How To Approach Feedback</h3><p>During design critique, all input should be taken with a grain of salt. Feedback in Crit should never be considered mandatory changes. As the designer, you’re the owner of the decisions you make. Critiques on the work aren’t a reflection on you or your abilities. It’s only about the current status of the design.</p><h3>When You Are The One Receiving Feedback</h3><h4>Assume Good Intentions</h4><p>Some people struggle to phrase feedback well while others can be great at it. Assume that your teammates are doing their best to be honest and helpful, regardless of how the wording comes out. If something doesn’t feel quite right, use your best judgement in the meeting and lean on your manager to help you and your teammates to make sure everyone feels respected.</p><h4>Appreciate The Feedback</h4><p>Non-verbal communication is the most effective way to let someone know you’re listening and encourage them to express their thoughts. When your teammates are talking, make eye contact! Show appreciation by saying things like, “I hadn’t thought of that thank you!” or “I hadn’t noticed until you said it, I’ll think about that.”</p><p>If you get feedback you don’t agree with, ask clarifying questions to make sure you understand the intent behind the feedback. Be careful not to debate their suggestions or their point of view. Take note of all the input and keep the conversation moving. What you do with their feedback after the meeting is up to you.</p><h4>Make A Decision</h4><p>Think about how you are going to use (or not use) the feedback to move your project forward. Making a decision can be the most difficult part of being a designer. No matter how experienced you are, you never know for sure how people will interact with a design until you get something out there. The key to getting better as a designer is seeing how people respond to a design and learning from your own mistakes. It’s better to be wrong and learn how to improve the design, than to be indecisive and delay progress.</p><blockquote>I’ve missed more than 9,000 shots in my career. I’ve lost almost 300 games. 26 times I’ve been trusted to take the game winning shot and missed. I’ve failed over and over and over again in my life. And that is why I succeed.</blockquote><blockquote>- Michael Jordan</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifdgYbWk6K-EVli3noQDAw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>When You Are The One Giving Feedback</h3><p>As much as we want to be direct and focus on the work, Critique is still a vulnerable place. Always focus feedback on the work, and not on the designer. Remember that people receive communication differently. A little warmth and patience goes a long way.</p><h4>Positive Feedback</h4><p>As designers, we have to be self-critical of our choices in order to create good work. Crit isn’t just about pointing out what needs improvement. It’s just as important to know what’s working. Even if the presenter doesn’t directly ask for it, calling out what is good or just <em>cool</em> about a design can go a long way toward helping each other create good work.</p><h4>Show Confidence In Each Other</h4><p>When suggesting a new idea or approach, you can show confidence in the presenter by starting with a phrase like, “You may have already thought of this…” This shows respect by acknowledging that an idea you <em>just</em> came up with may be something they already considered, since they’ve been thinking about the problem longer than you.</p><h4>Don’t Ask Leading Questions</h4><p>It’s natural to want to deliver critical feedback in a diplomatic way. It’s common to hear feedback in phrases like, “Do you think the design is a little noisy with that graphic?” or “Do you think it would be better if the text was bigger?” These are leading questions. A leading question is when you ask a question and secretly insert the answer you want. This phrasing reveals that the person <em>asking</em> the question holds an opinion, but maybe doesn’t want to come off too strong when expressing it. However, this puts the person receiving the feedback in a position of having to answer a leading question without knowing the motivation behind it. Even if the intentions are good, it can feel manipulative and inadvertently lead to arguments.</p><p>There are much better ways to express feedback directly without masking the opinion in a question. A few phrases you could use:</p><ul><li>I think that….</li><li>In my opinion…</li><li>If you ask me…</li></ul><p>So instead of “Do you think it would be better if the text was bigger?” you could say “In my opinion, the text is a bit hard to read. Making the text bigger could improve the legibility.”</p><h4>Be Specific</h4><p>Always explain why you’re giving the feedback so that the presenter understands what they can improve in the design.</p><p>For example, simply asking:</p><blockquote>Have you thought about moving that button to the bottom of the screen?</blockquote><p>This is just a yes or no question (and a leading question). It doesn’t convey a point of view or an opportunity to improve the design. If you really just want to know if they’ve thought about moving the button, the answer is probably yes! So what?</p><p>Asking a general question:</p><blockquote>What if you move the button to the bottom of the screen?</blockquote><p>This is a suggestion for a different approach, however, you haven’t conveyed why this approach improves the design. Let’s say we move the button to the bottom of the screen. So what?</p><p>If you were to say:</p><blockquote>I feel like the button on top throws off the visual hierarchy. As a user, it might make it hard to know what I should do. What if the button was at the bottom of the screen?</blockquote><p>Aha! This is great! You’ve specified what might be causing the design to struggle. You’ve helped identify a possible solution. These are the types of things that sometimes take multiple points of view to uncover. This is why we have Crit!</p><h4>Feedback That’s Out of Scope</h4><p>If you want to give feedback outside of what the presenter asked for, ask yourself how your feedback might impact the process of their work.</p><p>Notice a few small things that might be worth flagging in this meeting? Write it down. Mention it at the end of the presenter’s time allotment or mention it to them separately after the meeting.</p><p>Have concerns at the strategy level and feel the work might need to course-correct? Wait until the presenter has specified what feedback they’re looking for (presenter: be concise!). Let the presenter know you have a question that is outside of the scope and need clarity before the conversation moves forward. From here, the group should be able to discern if it merits pivoting the conversation to a different scope or if it is best to set a follow-up meeting.</p><h3>What If I Don’t Know How To Give Feedback?</h3><p>If you’re just getting started in your design career or you’re not a designer, it can be hard to know what details to look for in order to offer critique. If you’re feeling a little lost or unsure of how to contribute in Crit, start by asking yourself:</p><ul><li>Is there anything about the work being presented that is confusing to me?</li><li>Could the work being presented be simplified? Are there any elements or screens that could be removed or taken away?</li><li>How does the work being presented impact the way the user experiences the product as a whole?</li></ul><p>If these questions trigger thoughts or feedback in your mind, share that out loud with the group. There’s no right or wrong answer!</p><h3>Coming Up Next</h3><p>Part 4 of this will dive in to the actual conversations in design critique, how to give feedback and how to receive it.</p><p><a href="https://medium.com/bleacher-report-design/part-4-the-role-of-design-critique-in-decision-making-33170d9599a1">Part 4: The Role of Design Critique In Decision-making</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7eac60d878d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2: Presenting Your Work]]></title>
            <link>https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/42527be7cfb4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[critique]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:33 GMT</pubDate>
            <atom:updated>2019-09-24T17:38:38.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkvb4tv1_Xp2sRSAB-0gSw.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><p><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1 of this series</a> covered why critique is important and how to decide when you’re ready for feedback. Part 2 offers guidance on how to present your work once you’ve decided you’re ready for feedback from a group.</p><h3>Presenting</h3><p>Even in Crit, people can suffer from information overload or get easily distracted. When you’re presenting, you can do a lot to make your work easy to follow. This will help everyone be able to participate and makes sure you get the most benefit out of everyone’s time.</p><h3>Set Context</h3><p>When you’re presenting, always start by giving a little background on your work. This should only take 2–3 minutes. To being concise when you’re setting context, it helps to know what <strong>type feedback you need</strong>. Then ask yourself, what is the minimum context necessary to enable others to provide feedback? Try presenting only that context. Leaving more time for others to talk means you’ll get more feedback or more specific questions on what type of context they might find helpful.</p><p>If you think it will take longer than 2–3 minutes to set the context, you might be sharing too much at once. The full context of your work is not needed in order to get input. Focusing on a specific portion of your work will help you get actionable feedback.</p><p>Here are some details that are usually helpful to include for any project:</p><ul><li>The problem you’re trying to solve</li><li>The outcome you’re hoping to achieve for the user</li><li>Constraints you’re designing within (such as timelines, scope, resources, technical limitations, etc.)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PWRa3JcanCUk2NNI7oexBA.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>Show. Don’t Tell!</h3><p>Our brains process images faster than text. Less effort is required of an audience when pictures <em>support</em> a message. A good rule of thumb for any presentation is to ask the audience to read OR listen, but not both. Use visuals (like sketches, wireframes, mockups, screenshots, etc.) to illustrate your points while you talk.</p><h4>Things you can say without showing it:</h4><ul><li>The problem you’re solving</li><li>The type of feedback you need</li><li>Constraints (e.g. deadlines, resources)</li><li>Goals, hopeful outcomes, metrics for success</li></ul><h4>Things you can show through visuals:</h4><ul><li>Complex details that help illustrate context</li><li>What the current solution looks like (assuming you’re improving an existing feature)</li><li>Ideas you previously tried that you already ruled out</li><li>The specific part of the design that needs feedback</li></ul><p>It’s important for your visuals to be easy to digest. Avoid putting a bunch of words on the screen. People will naturally try to read and listen at the same time, which distracts from actually processing the information.</p><p>Avoid small labels or arrows through flows that can’t be quickly understood. A better approach for feedback on flows is to show a before and after visual. This makes it more clear how your work is different from what currently exists, and where you need feedback.</p><p>People see and interpret almost everything through contrast and comparison. The contrast between before and after helps separate your work from what currently exists, and highlights the differences where you need input.</p><h3>Facilitate The Conversation</h3><p>As the presenter, it is your job to facilitate the conversation you want to have. To do that, you need to be solid on two things:</p><ul><li>The goals of your project</li><li>The type of feedback you need</li></ul><p>It is your responsibility to keep the conversation focused on the feedback you need. If someone is giving feedback that is off topic or out of scope for the conversation you want to have, it’s your job to point this out. It can be as simple as letting them know, “I see what you’re saying. Right now, I could use more feedback on [reiterate what you need feedback on] first before we have that conversation.”</p><p>It only takes one person to break the seal for off-topic feedback to change the conversation for the whole group. It’s important to keep the conversation on track. In the end, you’re responsible for making sure you get the feedback you need.</p><h4>Talk Less And Listen More</h4><p>Remember, you came to Crit to hear from others! If you find yourself doing most of the talking during your time allotment, you should switch gears and offer the floor to the group.</p><h3>Coming Up Next</h3><p>Part 3 of this series will dive in to the conversations during design critique; how to give feedback and how to receive it.</p><p><a href="https://medium.com/bleacher-report-design/part-3-feedback-c7eac60d878d">Part 3: Feedback</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42527be7cfb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: Introduction]]></title>
            <link>https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/2282140ddf0b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Carolann Merchant]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 17:36:10 GMT</pubDate>
            <atom:updated>2019-09-24T17:37:23.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vnwe4bpiRmOSNI_vON9m5w.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h4>The Crit Playbook</h4><h3>What is Design Crit?</h3><p>There are many different ways to get feedback on design work: one-to-one conversations, formal reviews, user research, data analysis, the list goes on. This series will focus on how designers can best get feedback during a design critique.</p><p>Most design teams have a weekly critique meeting to make sure designers get the feedback and support they need. This meeting is where designers share unfinished work. We ask to be challenged and to have the successes and flaws in our work pointed out. At times, these conversations can be challenging and sometimes uncomfortable, but the more you open up in Crit the better designer you’ll be.</p><h3>Always Come With A Point Of View</h3><p>The number one rule of Design Critique is to always come with a point of view. Even if it’s a loosely held point of view or an opinion you’re not confident in, you have to come with one. To make products, you have to make decisions. To make informed decisions, you have to form an opinion. As a designer, this is what you’re getting paid for!</p><p>Crit should be a casual environment. But no matter how casual the conversation or the meeting, everyone’s time is important. Coming prepared shows respect for your teammates.</p><h3>Know What Type of Feedback You Need</h3><p>Always communicate what type of feedback you need to the group. This helps everyone focus their input on the details that are most relevant. It also ensures that you get the input you need, rather than input that might be out of scope or jumping ahead of where you are in the process.</p><p>A good place to start is letting people know which aspect of design you’d like input on:</p><ul><li>Visual design</li><li>Interaction design</li><li>User experience</li></ul><h4>Prepare Ahead of Time</h4><p>Spend a few minutes before Crit to prepare. A good practice is to create a separate space or page in your design tool just for that day’s Crit. Only copy/paste in the visuals you need feedback on and the visuals you might need to include for context. This prevents scrolling around in big design files (jarring for everyone) and forces you to narrow down <em>only</em> the information needed for feedback and how best to present it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UiPM8dVuPO1Wx86bcUc3EQ.png" /><figcaption>Illustration by Kelsey Rushing</figcaption></figure><h3>When To Show, When Not To Show</h3><p>It can be hard to know when is the right time for outside input on your work. At times it’s helpful. Other times it can introduce confusion. There are a few ways you can decide whether you should present your work in Crit.</p><h4>You should present in Crit when:</h4><ul><li>You’re blocked; you’ve explored all the possible or reasonable options but could use some extra brain power to make sure you’re not missing an opportunity.</li><li>You need input on something specific to refine your current solution. Maybe an extra pair of eyes could help identify improvements you hadn’t thought of yet.</li><li>You feel like you’ve landed on the right design, but want a gut check. You want your thinking challenged to make sure you’ve come to the best solution.</li></ul><h4>You should NOT present in Crit when:</h4><ul><li>You haven’t developed your own point of view on the problem you’re solving. You haven’t had a chance to fully understand the goals of your project yet.</li><li>You haven’t had a chance to explore different approaches on your own. There’s still a lot of low-hanging fruit or obvious ideas to try out first before getting feedback.</li><li>Your mockups are a mess and you don’t have any digestible visual assets prepared. You won’t be able to facilitate a productive conversation.</li><li>You have new work you’ve completed but you don’t really need feedback.</li></ul><h3>Tips For Organizing the Meeting</h3><h4>Have An Agenda</h4><p>All meetings should have an agenda. It helps the meeting stay on track and ensures everyone gets the amount of time they need to present. Keep an eye on the time during the meeting and provide reminders when it’s time to switch presenters. The goal is to keep conversations focused and helpful.</p><h4>Laptops Down</h4><p>At the beginning of the meeting, remind everyone to close their laptops and phones when they’re not presenting. It’s better to skip Crit if you need to focus on other work or conversations than to try to multitask during the meeting.</p><h3>Keep An Open Mind</h3><p>No one has all the answers. We need outside points of view to make our best work. Crit is one of the places where that happens. Being in situations where you have to explain the reasoning behind your decisions ensures good design. Others can learn from your decision-making and you learn by having your decision-making challenged!</p><p>It’s always okay to say “I don’t know” or “I’ve tried everything and I <em>still</em> haven’t found a good solution. I need help!” It doesn’t make you seem inexperienced or like you don’t know what you’re doing. It happens to all good designers.</p><h3>Coming Up Next</h3><p>In Part 2 of this series, we’ll cover best practices for how to present your work in crit and how to facilitate the conversation to get the feedback that you need.</p><p><a href="https://medium.com/bleacher-report-design/part-2-presenting-your-work-42527be7cfb4">Part 2: Presenting Your Work</a></p><p><strong>Want to be part of our product design team? We’re hiring! Reach out to learn more. carolann.merchant@bleacherreport.com</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2282140ddf0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/part-1-introduction-2282140ddf0b">Part 1: Introduction</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How We Switched from Sketch to Figma]]></title>
            <link>https://medium.com/bleacher-report-design/how-we-switched-from-sketch-to-figma-78fab13eac2c?source=rss----bfa662314d5b---4</link>
            <guid isPermaLink="false">https://medium.com/p/78fab13eac2c</guid>
            <category><![CDATA[design-tools]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[decision-making]]></category>
            <dc:creator><![CDATA[Marie Shatara]]></dc:creator>
            <pubDate>Wed, 28 Aug 2019 19:17:49 GMT</pubDate>
            <atom:updated>2019-08-28T19:17:47.998Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our decision-making process to a better design tool</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7r3LhADujFakji-ql34dxA.png" /></figure><p>When I was 7 years old, my dad brought home our first family computer. Not knowing what to do with this fancy new toy, I played around with different programs on the computer and discovered Microsoft Paint. I was amazed I could create anything I imagined. I would come home from school, turn on the computer, and create my next masterpiece (none of it was ever really good but I did paint a cool manatee once). This was an early introduction to my career working with design software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2hmdf1hQXmB01iV5MwE_JA.png" /></figure><p>Design software is constantly evolving with the needs and demands of the industry. Designers might have never imagined what innovations would lie ahead before the evolution of the Web in the ’90s. As the digital landscape evolves to meet the needs and demands of the industry, we are able to push the limits of how we create, thus propelling us to constantly learn, grow, and adapt.</p><p>Photoshop was my go-to tool for Product Design until Sketch came along. Sketch changed the way we worked because it was lightweight and efficient, which made a world of a difference in my workflow. However, our team at <a href="https://dribbble.com/bleacherreport"><strong>Bleacher Report</strong></a> was quickly growing, so we needed to find ways to increase our performance, transparency, and collaboration across the product team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLgJbHVhg33NykxU8i82BQ.png" /></figure><p>In total, we used 8 separate tools to design, prototype, deliver specs and get feedback. Although each tool by itself was purposeful, key problems began to surface when we switched between multiple tools to complete a single project.</p><p><strong>Key Problems</strong></p><ol><li>While each tool would generate a ton of feedback, communication would get lost between tools, making it difficult to keep track.</li><li>Designers would have to export and upload files to get feedback in Basecamp or Wake, which meant designers couldn’t get feedback as quickly or efficiently as possible.</li><li>We didn’t have an efficient way to do real-time collaboration and brainstorming with our remote team.</li><li>Depending on the design phase, multiple artifacts were generated for a single project, so it was difficult to know where the single source of truth was.</li><li>Design iterations meant the uploaded files and links became lost or obsolete, so stakeholders didn’t know if they were looking at the most up to date version.</li></ol><p>Needless to say, we needed a tool that was more agile so we could streamline communication between the team and stakeholders, tighten our feedback loops, and reduce the number of overall tools the team used.</p><blockquote>Once we began to explore Figma as a possible tool replacement, we quickly realized that Figma was like the Emerald City of design tools.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U1Xk-Sch1MKdJxeGu50j-Q.png" /></figure><p><strong>What caught our attention</strong></p><ul><li>Real-time collaboration</li><li>Instant feedback loops</li><li>Smarter design system libraries</li><li>One tool to rule them all (you can design, prototype, and spec in Figma)</li></ul><p>We knew Figma had a lot to offer, but switching design tools is a serious thing to consider because it disrupts your teams’ workflow and can be costly. We wanted to make sure that we were replacing our design tools for the right reasons. Thus we began our journey into exploring whether Figma was the right tool for our design team at Bleacher Report.</p><h3>Here’s how we decided if Figma was right for us:</h3><h3>Start with Why</h3><p>Understanding why your team needs new tooling is crucial. Is there something in your process that is lacking or creating obstacles that this tool will fix? Is your current tool working, but you just need to improve your process?</p><p>For our team at Bleacher Report, we needed to close those feedback loops quicker, consolidate our tools so we didn’t have to figure out where to go to review work and be able to produce work with greater velocity. Consider what your team needs, how the tool might fit, and what you are looking to gain from a new design tool that you don’t already have.</p><h3>Know Your Players</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mxzf3vmYTlRvoDNXvI3Pxg.png" /></figure><p>Changing a tool for your design team affects more than just designers since PMs, Engineers, and Key Stakeholders are integral to your process. How is a Product Manager going to give quicker feedback in Figma versus the tools we already use? Would switching to Figma impede an Engineer’s ability to code based on our specs?</p><blockquote>Design is a team sport and knowing who your players are will help your evaluation stay on track.</blockquote><p>By involving others in the evaluation process, you develop an environment for co-creation. This will increase the likelihood of buy-in and acceptance once the tool change is officially made. Get the design team involved, but involve other stakeholders and contributors who may be interacting with the tool as well.</p><p><a href="https://docs.google.com/spreadsheets/d/1Pm-I9RSZ3BcTNR9KzPccefYmrSrMhDW8fyoOZA9zxxY/edit?usp=sharing"><strong>Find our Design Tool Evaluation Template here</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*axXLcq6_GDtw7-opzTfwPg.png" /></figure><h3>Evaluating Different Features</h3><p>I set up an initial evaluation to dig into Figma’s features with the Product, Design, and Engineering teams. We compared Figma to the tool counterpart that we were already using. For example, comparing Figma to Sketch when evaluating it as a design tool and comparing Figma to InVision when evaluating it as a prototyping tool. Each member of the team was assigned a different aspect of Figma’s features.</p><h4><strong>Features we wanted to learn about:</strong></h4><ul><li>Styles, including Design System Management, and Component Libraries</li><li>Design Tools</li><li>Prototyping</li><li>Streamlining Communication</li><li>Developer Tools</li><li>API, Plugins, and Integrations</li></ul><h4><strong>What we considered when evaluating:</strong></h4><ul><li><strong>Reliability — </strong>How reliable is this tool?</li><li><strong>Ease of Use </strong>— How intuitive is the tool or is there a learning curve?</li><li><strong>Velocity </strong>— How quickly can I get the typical tasks done?</li><li><strong>Features</strong> — Does it have the minimum features compared to the current tool? What can’t we live without?</li><li><strong>Utility</strong> — What are the features we can utilize to improve our process?</li></ul><h3>Putting it to the Test</h3><p>Once we got a bird’s eye view of how Figma compared to our other tools, it seemed promising. As Product Designers, it made sense for us to set up a usability test for Figma. Our goal was to design a new module while using existing elements of design from Sketch to understand how easy Figma would be for designing, prototyping, collaboration, and development. Designers were given a scenario and 12 tasks to complete in addition to some follow-up questions on whether or not we should move forward with Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cWMulwS36cT32g0G37H8TQ.png" /></figure><p><a href="https://docs.google.com/document/d/1aKCI_qpsVHmg9E7XtnKfe_gKM8vvIhzCaH_tXyPJh94/edit?usp=sharing"><strong>Find our Figma Test Plan Template here</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhGixTHHhAYScQupegtDiQ.png" /></figure><p><strong>Some of the tasks performed:</strong></p><ul><li>Importing fonts and Sketch files</li><li>Using the design and prototyping tools</li><li>Completing tasks offline</li><li>Using the component library</li><li>Getting feedback</li><li>Delivering to engineers</li></ul><p><strong>And finally we wanted to know:</strong></p><ul><li>Overall thoughts on the tool?</li><li>What would you change, add, or improve about Figma?</li><li>Did you find any workarounds for problems that came up?</li><li>Final thoughts on moving forward with Figma?</li></ul><h3>Synthesize Results</h3><p>I synthesized all the tests from 6 designers and 5 product managers and added insights into a key findings report. I thought after both the tool evaluation and test plan we would have a clear answer as to whether we should adopt Figma. However, that was not the case. When it came to whether or not we should move forward with Figma, results were not100% conclusive, but I felt like we were getting closer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rN1eLv4znYk84kmIlQA95A.png" /></figure><h3>Weigh your Pros and Cons</h3><p>Go back to “why.” Why are you considering adopting a new tool and what’s really important to you and your team? Take a look at the trade-offs of what you will be gaining or losing by transitioning to a new tool.</p><p><strong>The bottom line is:</strong></p><ul><li>If you care about maturity, stick with Sketch.</li><li>If you care about collaboration, velocity, and an all-in-one tool, use Figma.</li></ul><p>That being said, Figma has made great strides improving their product by adding new features constantly and launching Figma plugins! Game changer!</p><h3>Ask Around</h3><p>Figma has been adopted by various companies such as Twitter, Dropbox, Zoom, GitHub, and Square, to name a few. Reach out to folks who have experience using Figma and ask why they decided to make the switch and how they use it on their team.</p><p>We met with the Design Manager at Asana who recently transitioned her team from Sketch to Figma. We wanted to find out how her team used Figma and what pain points they encountered. It was so helpful to hear Asana’s experience with Figma because after knowing how much it improved their team and workflow, it really cemented our decision to move forward.</p><h3>Moving Forward</h3><p>We’ve done our homework and now it was time to make a decision. Did our pros outweigh the cons? The answer was an enthusiastic yes! We loved Figma and how much more efficient it was at getting the job done. It seemed like a no-brainer. Once we knew we wanted to move forward with Figma, we began drafting a plan on how to transition from Sketch to Figma.</p><p>Some things you might consider are whether to rebuild your component library in Figma before transitioning. This will help expedite design because not every Sketch component, icon, or vector will import correctly. Think about what the bare minimum is needed to get your team to start taking on projects in Figma. You can always build more on top of that while designers are adjusting and learning the tool.</p><p>While the process we set up has worked for our team at Bleacher Report so far, we are still learning and evolving. Going through each step of our tool adoption evaluation was very helpful in ensuring we did our due diligence and incorporated key stakeholders. However, each design team will have different needs for their own team. Perhaps you are working as a consultant or at a start-up. You might not need to review with as many stakeholders and therefore can make a decision in fewer steps. Pick and choose elements of this process that make the most sense for your team.</p><p>As our team continues to grow and evolve, we know now that Figma is the tool that is built to help us scale. If you’re in the process of switching your team’s design tools or are considering adopting Figma, we’d love to hear how you’re doing it.</p><p><strong>Want to be part of our squad? We’re hiring! Reach out to marie.shatara@bleacherreport.com to learn more.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78fab13eac2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bleacher-report-design/how-we-switched-from-sketch-to-figma-78fab13eac2c">How We Switched from Sketch to Figma</a> was originally published in <a href="https://medium.com/bleacher-report-design">Bleacher Report Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>