<?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 Brian Beavers on Medium]]></title>
        <description><![CDATA[Stories by Brian Beavers on Medium]]></description>
        <link>https://medium.com/@beaversdesign?source=rss-ff616dce445e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UkneXnouXKeVH8h10J2o8A.png</url>
            <title>Stories by Brian Beavers on Medium</title>
            <link>https://medium.com/@beaversdesign?source=rss-ff616dce445e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:39:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beaversdesign/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[Stress-Testing Designs]]></title>
            <link>https://medium.com/@beaversdesign/stress-testing-designs-f8176900e4d1?source=rss-ff616dce445e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8176900e4d1</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[cursor]]></category>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Brian Beavers]]></dc:creator>
            <pubDate>Sun, 26 Jul 2026 22:41:14 GMT</pubDate>
            <atom:updated>2026-07-26T22:43:00.519Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently with the surge of AI, I, like so many others in tech, have been wrestling with the beasts that are LLMs.</p><p>In the first quarter of this year, the internet was in awash of thinkpieces, hype, influencers, and sponsored plugs for different flavors of these LLMs.</p><p>There was a huge spike in content, media, youtube videos, how-tos, and the like. The hype was high.</p><p>Then like so many others, I jumped in to see how I could apply them to my workflow. I built a few proof-of-concept prototypes using MCPs and static Figma flows for projects I was working on. I built a couple of simple SwiftUI and Kotlin Android apps. Then some internal tools to interact with datasets to better understand the relationships among different internal company systems, dashboards, customer journeys, PRDs, production designs, and prioritized backlogs.</p><p>Don’t get me wrong — these are very powerful tools. Every company is figuring out how to use LLMs for decision-making, UI development, quarterly planning, dashboards, presentations, customer-facing features, chatbots, customer service triaging.</p><p>Speaking from my own experience, I’ve found the corners where LLMs can’t quite get to, yet. As a software designer, I’ve discovered the things these LLMs can do really well to moderately well to poorly to extremely poorly. They’re not perfect. I’ve treated them as tools and not replacements.</p><p>However, one way I’ve leveraged them is to help me be more inclusive in my design work solution. This skill I’ve uploaded to github today helps me uncover potential roadblocks, edge cases, or use cases I’ve not quite accounted for, yet.</p><p>I called it “Global Design Stress Test”.<br><a href="https://github.com/brianbeavers/global-design-stress-test-skill">https://github.com/brianbeavers/global-design-stress-test-skill</a></p><p>It allows me to put my designs — static Figma screens, userflows, Cursor or Claude prototypes — through the paces.</p><p>I encourage you to give it a try and see how it helps you and your teams deliver inclusive, accessible software to your customers.</p><p>Drop me a comment here if you have feedback.</p><p>Thanks!</p><p>Brian</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8176900e4d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips for guerrilla user research]]></title>
            <link>https://uxdesign.cc/tips-for-guerrilla-user-research-5fff52f30d0a?source=rss-ff616dce445e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5fff52f30d0a</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Brian Beavers]]></dc:creator>
            <pubDate>Mon, 01 Apr 2019 13:16:01 GMT</pubDate>
            <atom:updated>2019-04-11T00:36:45.023Z</atom:updated>
            <content:encoded><![CDATA[<p>Guerrilla user research, which is <a href="https://uxmag.com/articles/getting-guerrilla-with-it">conducting fast and low-cost</a> user testing, usability testing, or user interviews with random participants, is a valuable tool in every digital product designer’s toolbox. In this article, I’ll lay out a few tips to maximize your research when you are under time and resource constraints.</p><p>If you do not have the time or an extensive budget to set up screener surveys, coordinate and physically set up a research environment, or create a test on virtual usability testing service, guerrilla user research may meet your needs. And let’s be honest with ourselves: we should not be conducting frequent “user research” with fellow designers, engineers on your team, or co-workers. This results in biased answers, preventing you from getting the information that you need to improve your product.</p><h3><strong>Tip 1: Come to an agreement with your stakeholders.</strong></h3><p>Ensure that everyone understands the goals and anticipated outcomes from this type of research, which is not likely to result in significant product direction changes. The goal is to gather feedback quickly on userflows, page layouts, imagery, copywriting, and/or content. Be clear about the questions you and your team are attempting to answer.</p><h3><strong>Tip 2: Do a trial run in the office.</strong></h3><p>Your goal with this exercise is not to get feedback, but to be sure that your prototype or the build from the engineer is functioning, and that your questions are worded properly. You want to determine the problems that you need to address. Conducting actual guerrilla user research with your peers is counter-productive.</p><h3><strong>Tip 3: Recruit someone to go with you.</strong></h3><p>It is helpful to have someone who can help recruit participants and take notes on the insights you gather. Ideally, invite the engineer who is building the product or the skeptical product manager who is not quite sold on your design solution. I’ve brought both to help me do guerrilla user research and every time it has been a great experience.</p><h3><strong>Tip 4: Write and memorize a brief “elevator speech”.</strong></h3><p>You will use this description when you approach your potential research participants. The goal is not to have a one-minute conversation about who you are, what you are doing, who your participant is, and who designed the prototype. Instead, write a &lt;15-second approach that includes these key points for your possible participant:</p><ol><li>You’re going to pay them for their time. Tell your potential participant the specific dollar amount</li><li>Ask for a maximum of five to ten minutes.</li><li>Let your possible research participant know that you are not selling anything. You just want their feedback.</li></ol><p>Examples:</p><blockquote>“Hi, I just wanted to ask if you have a few minutes to spare. I’m looking for feedback on an app that our company is building. I’ll pay for your next coffee.”</blockquote><blockquote>“Excuse me, I’m looking for feedback on a website that my team built. Just wondering if you have five minutes to help me out. I’ll give a $10 Starbucks/Visa card for your time.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFLyXtlB5b_erXlot6-tNA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/pNIgH0y3upM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">RR Abrot</a> on <a href="https://unsplash.com/search/photos/cafe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Tip 5: Conduct your research at a busy coffee shop or in an area with high volume of foot traffic.</strong></h3><p>Don’t conduct your user research with your peers inside of the office. I prefer coffee shops, as they provide a more casual setting. Coffee store customers tend to be more open to reviewing your design over a cup of liquid caffeine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*30PE5Mzlk9DGxYuZqm2RAw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/B6-8HwbRJz4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sticker Mule</a> on <a href="https://unsplash.com/search/photos/notepad?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Tip 6: Avoid holding a notepad or clipboard.</strong></h3><p>If you are seen with either of these items, you almost certainly ensure that people will avoid you. When you are recruiting participants to give you feedback on your design, you want to look approachable, friendly, and casual. Notepads or clipboards make you look like you want something.</p><h3><strong>Tip 7: Be okay with “no.”</strong></h3><p>A lot of people are going to say “no”. It’s inevitable.</p><h3><strong>Tip 8: Have the gift card that you are offering in hand.</strong></h3><p>When you approach someone to ask for their feedback on your product design, it is important for them to see the compensation being offered. This demonstrates that you are serious about getting their input and not just asking for a signature or soliciting their political vote. An amount of $5–10 usually elicits a positive response.</p><h3><strong>Tip 9: Avoid revealing that you are the product designer.</strong></h3><p>This could create bias since most people will tend to praise the design if they know that it is yours and you will not get valuable feedback. Remain neutral or say that you are an independent researcher.</p><h3><strong>Tip 10:</strong> <strong>If possible, do your research on Thursday or Friday.</strong></h3><p>The most productive days for guerrilla user research became evident the longer I was involved with this process. People are generally in a better mood as it gets closer to the weekend. Avoid Mondays, if you can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r-n1bzh635gLSXRCqSo4xg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/tdlG1GIctfU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Holyoake</a> on <a href="https://unsplash.com/search/photos/cafe-people?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Tip 11: If a possible research participant looks busy, don’t approach them to ask for their help.</strong></h3><p>Solicit feedback from people who are clearly not in a hurry, on the phone, or with family. Use common sense and be respectful of others’ boundaries.</p><p>Conducting guerrilla user research is an excellent tool for eliciting feedback, which is important to the success of your product. Simply apply the basics, which include respecting the time of your participants, being prepared with your list of questions and a brief script, and offering compensation.</p><p>If you have additional tips or ideas that helped you conduct successful guerrilla user research, please leave your comment below.</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=5fff52f30d0a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/tips-for-guerrilla-user-research-5fff52f30d0a">Tips for guerrilla user research</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>
        <item>
            <title><![CDATA[Designing for real: tips for inclusive product design]]></title>
            <link>https://uxdesign.cc/designing-for-real-f907a66a34b6?source=rss-ff616dce445e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f907a66a34b6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Brian Beavers]]></dc:creator>
            <pubDate>Tue, 07 Aug 2018 11:59:31 GMT</pubDate>
            <atom:updated>2018-08-22T00:46:05.724Z</atom:updated>
            <content:encoded><![CDATA[<p>When designing for the real world, the key is to remember that we are different on many levels. <em>You</em> are <em>not</em> your product’s end user. We all have different philosophical, spiritual, and religious beliefs. We come from different communities, cities, regions, and countries. We all speak, write, and read in different languages, and in different dialects.</p><p>Therefore, as a professional product or UX designer, it’s important to design inclusively for all. This means that you will almost certainly need to work through several… perhaps many… iterations before you have your ideal design, one that comes closest to meeting your goals, which are ultimately your end users’.</p><p>This article presents some of the challenges you may encounter when designing for the real world and provides guidelines to help you develop the most valuable product for your end user.</p><h3><strong>Names aren’t always short.</strong></h3><p>Although last names such as “Smith,” “Johnson,” and “Davis” are common in the United States, this is not the case worldwide . It is essential to realize early in the creative process that there is a significant difference between designing for “pretty” or “perfectly-crafted” UI designs and what is realistic. Many less experienced product designers make this mistake, especially those who are transitioning from a purely UI or visual role to a product design role.</p><h4><strong>Tip:</strong> <strong>When you are designing a solution to a particular challenge or user pain point, use long names.</strong></h4><p>Instead of “Rebecca Smith” try “Rebecca Cohen Jamison”. Instead of “Chris Ocampo” try “Christopher M. Ordoñez”. Even if your designs may not be “pretty” or fit in the perfect design you created, you will position your developers and your end users for success. With this technique, you will see how your design might break when longer names are used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdtnoOdfivlGemdCplXRIQ@2x.jpeg" /></figure><h3><strong>There are over 7,000 languages.</strong></h3><p>While it is certainly easier to design for your native language and not consider other languages when you design, it is foolish to simply cross your fingers and hope for the best…and the clearest meaning for your end user.</p><h4><strong>Tip:</strong> <strong>Localize your designs.</strong></h4><p>When designing any high-value parts of the experience, or a design system for your company, consider how other languages might translate whatever you or your copywriter have written. It is not necessary to mock up your designs in <a href="https://www.ethnologue.com/">7,097 languages</a>, but be cognizant of your end users. Ask your data team or product manager to pull metrics on your user base. You might learn that ~21% are German, and therefore “Reserve now” in German is “Reservieren Sie jetzt,” which no longer fits in that small 200x40 pixel button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sc4JTOgGv7sMraOLKTdz7w@2x.jpeg" /><figcaption>My design for a fake travel app. The main CTA looks safe on the left but fails when translated to German in the middle; My modified design on the right.</figcaption></figure><h3><strong>Many people with different degrees of disabilities use your products.</strong></h3><p>Of course, it is easier and more fun to design an interface with a trendy, beautiful colors and splashy animations, but consider your end user. According to the <a href="http://www.who.int/disabilities/world_report/2011/report/en/">World Health Organization</a>, <strong>one billion people, or 15% of the world’s population, </strong>experience some sort of disability. iOS has many features to help those users who are visually-or hearing-impaired, including the ability to increase text size or read the interface to them.</p><h4><strong>Tip: Champion the underserved. Contrast and clarity are your friends.</strong></h4><p>When designing your new solution or when crafting your design system, run them through contrast simulators (like <a href="http://www.getstark.co/">GetStark</a>) and test them for visual or hearing impairments. Providing obvious hint text in form fields and employing clear contrasts between objects on a page can be effective.</p><p>When your engineers or developers begin coding the solutions, be sure there are alt tags for images on web (for screen readers), and make sure that the accessibility features on <a href="https://developer.apple.com/accessibility/ios/">iOS</a> and <a href="https://developer.android.com/guide/topics/ui/accessibility/">Android</a> are enabled. Test your designs to see how they scale up or down with <a href="https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/typography/">iOS’s Dynamic Type feature</a>. Talk with your engineers or product manager about including these in your acceptance criteria or product requirements document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HignQE8BnA0QnLXloUWu2w@2x.jpeg" /><figcaption>The design on left was sourced from <a href="https://dribbble.com/pixelzstudio">PixelsStudio</a>. It looks good, but it fails a color blindness test for Protanopia. My modified design on right with stronger contrast, bolder type weights, darker colors for categories, and clearly defined states for tab bar icons (filled for selected and hollow for unselected).</figcaption></figure><p><a href="https://medium.com/@benjamineevans">Benjamin Evans</a> from AirBnb gave a <a href="https://youtu.be/mV0lp5cJpBo">great talk on accessibility, inclusiveness, and bias.</a></p><p>The following are also good resources for additional information on designing for accessibility:</p><ul><li><a href="https://www.w3.org/WAI/fundamentals/accessibility-principles/">Accessibility Principles</a></li><li><a href="https://uxdesign.cc/designing-for-accessibility-is-not-that-hard-c04cc4779d94">Designing for accessibility is not that hard</a></li></ul><h3><strong>Numbers aren’t always clean.</strong></h3><p>For example, while “$100” might look neat and tidy in a mock-up of a user’s bank account balance, it is likely not representative of most people and will not present a complete picture that includes all possibilities.</p><h4><strong>Tip:</strong> <strong>When designing with numbers, think of edge cases.</strong></h4><p>Think of what might or probably will go wrong as it relates to them. Consider that most users will have fluctuating account balances. Prices on consumer goods and hotel bookings will change based on sales or discounts. Due to the many different currencies, work to break your design. See what would happen if you converted $300.00 USD to Japanese Yen (as of this writing, it’s 33,379.05 Yen).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HD4ESJ6xCFM2bjrK9-UYAg@2x.jpeg" /><figcaption>During my time at TripAdvisor, I worked on our list view pages. The left shows an early design with USD, which then fails when converted to Yen in the middle. The modified design on right shows the “worst case scenario” with a maximum character count.</figcaption></figure><p>Designing for the real world can be challenging, but by applying these simple suggestions, by viewing your work from the user’s perspective, and by considering all the possible edge cases or outcomes, you can increase your chances of delivering the most valuable product possible.</p><p>Drop me a comment below if you have other tips for “designing for real”. And please check out one of my recent articles on product and marketing design critiques:</p><p><a href="https://medium.com/@beaversdesign/how-we-do-product-and-marketing-design-critiques-at-stash-eb5ad67aa037">How We Do Product and Marketing Design Critiques at Stash</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%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/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f907a66a34b6" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-for-real-f907a66a34b6">Designing for real: tips for inclusive product design</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>
        <item>
            <title><![CDATA[How We Do Product and Marketing Design Critiques at Stash]]></title>
            <link>https://medium.com/stash/how-we-do-product-and-marketing-design-critiques-at-stash-1dea33c2a35f?source=rss-ff616dce445e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dea33c2a35f</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-critique]]></category>
            <dc:creator><![CDATA[Brian Beavers]]></dc:creator>
            <pubDate>Wed, 25 Jul 2018 13:56:41 GMT</pubDate>
            <atom:updated>2018-07-25T19:18:45.986Z</atom:updated>
            <content:encoded><![CDATA[<p>Brian Beavers + Christina Chang</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LO0LbLliyvZ_yb7AAuz9YA.jpeg" /></figure><p>Stash’s employee and customer base have been on a rocket ship with no signs of slowing down. As our design, research, and marketing team have continued to grow at Stash, we realized that we needed a new way of getting eyeballs on our work and getting timely critiques.</p><p>Like many product design teams, we use a combination of Sketch + Zeplin for design, feedback, and specs for engineering. But shoehorning feedback into Zeplin seemed like a misuse of the tool to us. We take vacations and sick days. We are often heads down busy with our own tracks of work on our squads. We’re in meetings or discussions throughout the building and can miss important threads on Slack or Zeplin. We often lack context behind certain projects, thereby missing the hypothesis and goals behind a particular solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n_LUjY2yQmeCN8OwYPcjyw.jpeg" /></figure><p>So my first pass at revitalizing how we do design critiques was by setting a standing one hour meeting every Wednesday afternoon (midway through the week to allow for time to prioritize design work and iterate within our squads) with the following mission:</p><blockquote><em>The purpose of this meeting is to have open and timely critique among team members and stakeholders. It is also to foster a more collaborative, human environment where we gather around, look at the work in-progress, and discuss our product solutions with each other </em><strong><em>in real life</em></strong><em>. The hope is that this will </em><strong><em>lighten some of the Zeplin discussions</em></strong><em>, give everyone a </em><strong><em>dedicated time</em></strong><em> to review work, push for more </em><strong><em>design consistency</em></strong><em> across squads and leave Zeplin for more engineering-based usage.</em></blockquote><p><strong>And this was the format:</strong></p><ul><li>1 hour long, 10–15 minutes each per squad or project (with timer)</li><li>Take the first five minutes of critique to walk around the room to look at the work printed</li><li>Write notes, questions, or feedback on stickies in relation to the project</li><li>To keep the meeting efficient and keep everyone’s attention, please take long discussions offline.</li><li><strong>No phones or laptops</strong></li><li>Stand up and discuss around each other’s designs</li><li>Attendees: All product managers and product designers from each squad, ux researchers, copywriters, and marketing designers</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*EiA0VtCBXNxEcw16" /></figure><p><strong>Designer:</strong></p><ul><li>Print out your flow or design(s)</li><li>Set the stage for the audience. Walk them through the challenge or problem statement, the goals, and the hypothesis.</li><li>Tell the audience what type of feedback you’re looking for (user flow, interactions, general UI, copy, etc.)</li><li>Tell the story. i.e. “The customer will be coming to this page from a button on home. Only customers who have a bank linked will see this.”</li><li>Tell the audience the goal(s) i.e. “We want to encourage customers to Auto-Stash more than $15/week.”</li></ul><p><strong>Coordinator + Timekeeper (Another designer or PM):</strong></p><ul><li>Focus the audience on the critique, the goals, the hypothesis, and the feedback the designer is looking for.</li><li>Please keep everyone’s time in mind so that all designers have enough time to present; especially if lengthy or non-relevant discussions come up</li><li>Make sure everyone has the opportunity to speak up. Oftentimes you’ll find the quiet ones provide the most valuable insights.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDUCENXylhUfA99hg4YFkw.jpeg" /></figure><p><strong>Audience:</strong></p><ul><li>Ask clearly defined questions i.e. “What were you trying to achieve with the placement of the icon there next to the headline?”</li><li>Be candid and honest. It shouldn’t be a compliment sandwich. Feedback should sound like, “Having Stash Cash preselected feels like an efficient way to move the customer through the funnel.” or “When you show too many payment options, it gets confusing and overwhelming, especially on mobile”.</li><li>Tie everything back to the goals and/or hypothesis. It should not be about liking or disliking the design. How is it meeting or missing the business and/or customer goals?</li><li>Provide directional suggestions, but avoid problem solving</li></ul><p>This product and marketing design critique format worked for awhile. Then we ballooned to 25+ attendees. Having 25+ people stand around an 11x17” print-out of a flow required magnifying glasses. After a few months of print-outs, we pivoted to a structured Google Slides format where the goals, the hypothesis(es), and link to the prototype or Zeplin were presented on a TV.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uC5qBsAhI3hiR8a86CmdXA.png" /></figure><p><em>*This image is for illustrative purpose only.</em></p><p>But we started to lose focus. Then attendance started to dwindle as work that was being presented became less relevant for some in the original meeting invite. And then we started to feel like the feedback wasn’t quite as timely or as focused as it had been in the earlier iterations with 10–12 people.</p><p>So we went back to the drawing board.</p><p>Christina Chang (one of our new Product Designers at Stash) had a friend that recommended an intriguing critique format called Tactical Design Critiques. The dramatically different approach convinced us this was worth trying:</p><ol><li>Small groups only — for us this meant only involving our small product design team of 6–7</li><li>One designer comes prepared with work to get critiqued, throws it up on a projector or large TV. The designer can’t say anything to explain their work to the rest of the group.</li><li>The rest of the group goes around the table, and one at a time says <strong>one</strong> point of critique or tension. Everyone is discouraged from giving compliments and building compliment sandwiches.</li><li>If you don’t have a point of critique, you can skip. If you don’t understand a person’s point of critique, you can ask them to clarify.</li><li>Most importantly, you cannot ask the designer any questions and they can’t jump in to respond and clarify.</li><li>At the end of 25 minutes of critique, the designer can take 5 minutes to summarize and explain how they will take the feedback into their designs.</li></ol><p>At first, this format felt like it was potentially limiting since designers are so used to providing context and defending their work. But, we quickly discovered that the designers became silent note-takers scribbling to capture feedback, and thereby less attached to their own work, able to step back and simply listen.</p><p>Because it often feels too intense in normal critiques to give so many suggestions, this format created the opportunity for comments on everything from copy to color to user flows to consistency. It’s a twist on user testing, except with users that happened to be designers you work with.</p><p>We’ve found it to be a very refreshing way to deep dive into one user flow at a time, and hone in on problem areas without involving egos.</p><p>Design critiques, much like design itself, can never truly be “perfected” or “done”, in our opinion. Audiences change, timelines change, team dynamics change, team needs or priorities are constantly shifting. As they say, change is the only constant. We’re still figuring out what works best for us.</p><p>If you have suggestions or have figured out what works for you and your team, drop a comment below.</p><p><a href="https://www.stashinvest.com/careers">P.S. Stash is hiring</a></p><p>References to design critique formats we used to iterate on ours:</p><p><a href="https://medium.com/@suelynyu/a-practical-guide-to-running-effective-design-critiques-c6e8166c9eb0">https://medium.com/@suelynyu/a-practical-guide-to-running-effective-design-critiques-c6e8166c9eb0</a></p><p><a href="https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4">https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4</a></p><p><a href="https://medium.design/tactical-design-critique-bb74d1a5e350">https://medium.design/tactical-design-critique-bb74d1a5e350</a></p><p><a href="https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c">https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dea33c2a35f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stash/how-we-do-product-and-marketing-design-critiques-at-stash-1dea33c2a35f">How We Do Product and Marketing Design Critiques at Stash</a> was originally published in <a href="https://medium.com/stash">stashinvest</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 Do Product and Marketing Design Critiques at Stash]]></title>
            <link>https://medium.com/@beaversdesign/how-we-do-product-and-marketing-design-critiques-at-stash-eb5ad67aa037?source=rss-ff616dce445e------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb5ad67aa037</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-critique]]></category>
            <category><![CDATA[critique]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Brian Beavers]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 20:59:54 GMT</pubDate>
            <atom:updated>2018-07-25T19:20:07.285Z</atom:updated>
            <content:encoded><![CDATA[<p>Brian Beavers + Christina Chang</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LO0LbLliyvZ_yb7AAuz9YA.jpeg" /></figure><p>Stash’s employee and customer base have been on a rocket ship with no signs of slowing down. As our design, research, and marketing team have continued to grow at Stash, we realized that we needed a new way of getting eyeballs on our work and getting timely critiques.</p><p>Like many product design teams, we use a combination of Sketch + Zeplin for design, feedback, and specs for engineering. But shoehorning feedback into Zeplin seemed like a misuse of the tool to us. We take vacations and sick days. We are often heads down busy with our own tracks of work on our squads. We’re in meetings or discussions throughout the building and can miss important threads on Slack or Zeplin. We often lack context behind certain projects, thereby missing the hypothesis and goals behind a particular solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n_LUjY2yQmeCN8OwYPcjyw.jpeg" /></figure><p>So my first pass at revitalizing how we do design critiques was by setting a standing one hour meeting every Wednesday afternoon (midway through the week to allow for time to prioritize design work and iterate within our squads) with the following mission:</p><blockquote><em>The purpose of this meeting is to have open and timely critique among team members and stakeholders. It is also to foster a more collaborative, human environment where we gather around, look at the work in-progress, and discuss our product solutions with each other </em><strong><em>in real life</em></strong><em>. The hope is that this will </em><strong><em>lighten some of the Zeplin discussions</em></strong><em>, give everyone a </em><strong><em>dedicated time</em></strong><em> to review work, push for more </em><strong><em>design consistency</em></strong><em> across squads and leave Zeplin for more engineering-based usage.</em></blockquote><p><strong>And this was the format:</strong></p><ul><li>1 hour long, 10–15 minutes each per squad or project (with timer)</li><li>Take the first five minutes of critique to walk around the room to look at the work printed</li><li>Write notes, questions, or feedback on stickies in relation to the project</li><li>To keep the meeting efficient and keep everyone’s attention, please take long discussions offline.</li><li><strong>No phones or laptops</strong></li><li>Stand up and discuss around each other’s designs</li><li>Attendees: All product managers and product designers from each squad, ux researchers, copywriters, and marketing designers</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*EiA0VtCBXNxEcw16" /></figure><p><strong>Designer:</strong></p><ul><li>Print out your flow or design(s)</li><li>Set the stage for the audience. Walk them through the challenge or problem statement, the goals, and the hypothesis.</li><li>Tell the audience what type of feedback you’re looking for (user flow, interactions, general UI, copy, etc.)</li><li>Tell the story. i.e. “The customer will be coming to this page from a button on home. Only customers who have a bank linked will see this.”</li><li>Tell the audience the goal(s) i.e. “We want to encourage customers to Auto-Stash more than $15/week.”</li></ul><p><strong>Coordinator + Timekeeper (Another designer or PM):</strong></p><ul><li>Focus the audience on the critique, the goals, the hypothesis, and the feedback the designer is looking for.</li><li>Please keep everyone’s time in mind so that all designers have enough time to present; especially if lengthy or non-relevant discussions come up</li><li>Make sure everyone has the opportunity to speak up. Oftentimes you’ll find the quiet ones provide the most valuable insights.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDUCENXylhUfA99hg4YFkw.jpeg" /></figure><p><strong>Audience:</strong></p><ul><li>Ask clearly defined questions i.e. “What were you trying to achieve with the placement of the icon there next to the headline?”</li><li>Be candid and honest. It shouldn’t be a compliment sandwich. Feedback should sound like, “Having Stash Cash preselected feels like an efficient way to move the customer through the funnel.” or “When you show too many payment options, it gets confusing and overwhelming, especially on mobile”.</li><li>Tie everything back to the goals and/or hypothesis. It should not be about liking or disliking the design. How is it meeting or missing the business and/or customer goals?</li><li>Provide directional suggestions, but avoid problem solving</li></ul><p>This product and marketing design critique format worked for awhile. Then we ballooned to 25+ attendees. Having 25+ people stand around an 11x17” print-out of a flow required magnifying glasses. After a few months of print-outs, we pivoted to a structured Google Slides format where the goals, the hypothesis(es), and link to the prototype or Zeplin were presented on a TV.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uC5qBsAhI3hiR8a86CmdXA.png" /></figure><p><em>*This image is for illustrative purpose only.</em></p><p>But we started to lose focus. Then attendance started to dwindle as work that was being presented became less relevant for some in the original meeting invite. And then we started to feel like the feedback wasn’t quite as timely or as focused as it had been in the earlier iterations with 10–12 people.</p><p>So we went back to the drawing board.</p><p>Christina Chang (one of our new Product Designers at Stash) had a friend that recommended an intriguing critique format called Tactical Design Critiques. The dramatically different approach convinced us this was worth trying:</p><ol><li>Small groups only — for us this meant only involving our small product design team of 6–7</li><li>One designer comes prepared with work to get critiqued, throws it up on a projector or large TV. The designer can’t say anything to explain their work to the rest of the group.</li><li>The rest of the group goes around the table, and one at a time says <strong>one</strong> point of critique or tension. Everyone is discouraged from giving compliments and building compliment sandwiches.</li><li>If you don’t have a point of critique, you can skip. If you don’t understand a person’s point of critique, you can ask them to clarify.</li><li>Most importantly, you cannot ask the designer any questions and they can’t jump in to respond and clarify.</li><li>At the end of 25 minutes of critique, the designer can take 5 minutes to summarize and explain how they will take the feedback into their designs.</li></ol><p>At first, this format felt like it was potentially limiting since designers are so used to providing context and defending their work. But, we quickly discovered that the designers became silent note-takers scribbling to capture feedback, and thereby less attached to their own work, able to step back and simply listen.</p><p>Because it often feels too intense in normal critiques to give so many suggestions, this format created the opportunity for comments on everything from copy to color to user flows to consistency. It’s a twist on user testing, except with users that happened to be designers you work with.</p><p>We’ve found it to be a very refreshing way to deep dive into one user flow at a time, and hone in on problem areas without involving egos.</p><p>Design critiques, much like design itself, can never truly be “perfected” or “done”, in our opinion. Audiences change, timelines change, team dynamics change, team needs or priorities are constantly shifting. As they say, change is the only constant. We’re still figuring out what works best for us.</p><p>If you have suggestions or have figured out what works for you and your team, drop a comment below.</p><p><a href="https://www.stashinvest.com/careers">P.S. Stash is hiring</a></p><p>References to design critique formats we used to iterate on ours:</p><p><a href="https://medium.com/@suelynyu/a-practical-guide-to-running-effective-design-critiques-c6e8166c9eb0">https://medium.com/@suelynyu/a-practical-guide-to-running-effective-design-critiques-c6e8166c9eb0</a></p><p><a href="https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4">https://uxdesign.cc/the-why-and-how-of-effective-design-critiques-944313947fe4</a></p><p><a href="https://medium.design/tactical-design-critique-bb74d1a5e350">https://medium.design/tactical-design-critique-bb74d1a5e350</a></p><p><a href="https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c">https://medium.com/@monteiro/13-ways-designers-screw-up-client-presentations-51aaee11e28c</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb5ad67aa037" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>