<?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 Mikail Gündoğdu on Medium]]></title>
        <description><![CDATA[Stories by Mikail Gündoğdu on Medium]]></description>
        <link>https://medium.com/@mikailmikhail?source=rss-4b1c7b10cc12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1KxQd_xZBnb81n9PmihfdA.jpeg</url>
            <title>Stories by Mikail Gündoğdu on Medium</title>
            <link>https://medium.com/@mikailmikhail?source=rss-4b1c7b10cc12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:38:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikailmikhail/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[Four collaboration lessons from the Jacobi Design System]]></title>
            <link>https://medium.com/clover-health/four-collaboration-lessons-from-the-jacobi-design-system-6d6ccfd5c8c8?source=rss-4b1c7b10cc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d6ccfd5c8c8</guid>
            <category><![CDATA[healthcare-technology]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mikail Gündoğdu]]></dc:creator>
            <pubDate>Wed, 18 May 2022 18:55:33 GMT</pubDate>
            <atom:updated>2022-05-19T19:08:23.959Z</atom:updated>
            <content:encoded><![CDATA[<p>The Jacobi Design System exists to connect all of our teams working on different components, functions and stages of the Clover Assistant’s product development. That, of course, means collaboration is essential to design system success. So for our first deep dive, let’s talk about some of the lessons we learned working together.</p><h3>Lesson #1: Dedicate time and space for your design system</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FNi3TgZt5r0mT4hN3YulJw.png" /><figcaption>I will admit, I love using the #design-system channel to unleash my Figma fanboy</figcaption></figure><p>Like many design system owners on growing teams, I am responsible for so much more than the design system. At any given moment, feature-related work is usually my highest priority. That’s all the more true for other design system collaborators. Before even getting to work on Jacobi, overcoming everyone’s higher priorities ended up being our first lesson.</p><p>For myself, meaningful progress on the design system every week meant blocking out my calendar. For the team as a whole, that meant running a weekly design systems meeting block. Create the expectation with yourself and your team that regular design system work is a routine aspect of work.</p><p>Meeting blocks with the wider team proved effective, but collaboration still had to happen between meetings. Clover always had a Slack channel for Jacobi, but participation was initially lacking; posts were far and few between. One trick that proved useful: designating our #design-system Slack channel for all design and engineering collaboration. Since our scrum teams lacked a shared channel for communication across teams, async design system collaboration went through the roof.</p><p>Still, nothing proved as effective in engineering collaboration as our next lesson.</p><h3>Lesson #2: Find a design system engineer</h3><p>When I first started at Clover, I did what I could as a designer to deliver system improvements. The result was our design work moved faster and our design specs were consistent. Yet the product we shipped still suffered from inconsistency and repeated work.</p><p>Unfortunately, the engineering team had a long list of feature-focused priorities that got in the way of requisite, up-front design system work. Familiar story, I know. But we’ve since created a robust engineering-side design system despite continuing to have high-priority engineering work. So what changed?</p><p>Clover found Peter Agar, a front-end developer with a wealth of experience in design systems. While I was initially most excited for Peter’s expertise, his enthusiasm was what brought about the most effective change to Jacobi’s engineering side. Before, when a design system improvement was decided upon, it would disappear into the JIRA abyss. Now, Peter jumps at the opportunity to contribute and finds time to sneak in our improvements.</p><p>It goes both ways. As a design system power user deeply embedded in engineering territory, Peter is the ambassador of a key design system user base. Peter’s feedback, sourced from the engineering team as a whole, has allowed us to create system pieces and processes that better integrate across our teams. Bringing us to lesson #3.</p><h3>Lesson #3: Feedback is the #1 measure of design system success</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dB-4nYPDd8PFJYCFtLmg9g.jpeg" /></figure><p>Another misstep in my early days at Clover: trying to create a fancy system for design system analytics. The reality was that maintaining (accurate) metrics was a manual process that only uncovered problems already being brought up by stakeholders. At that early stage, I learned that my effort building out analytics would be better spent tracking internal and external feedback and streamlining our collaboration with engineering. Especially as a design system owner working so closely with product development.</p><p>To design folk, listening to user feedback may sound obvious. On a design system, though, where feedback needs to continuously come from the same people, we learned that users also need to feel listened to. Initially, each piece of feedback would go straight into a prioritized list of design system to-dos; these days, we immediately close the loop on new feedback if possible.</p><p>Our last lesson gets into how feedback isn’t always so direct.</p><h3>Lesson #4: Leverage desire paths</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WX5ML1lhRO9-Mqhi.JPG" /><figcaption>This Wikipedia photo of a desire path of clovers felt especially Clover-y</figcaption></figure><p>One of my first projects for Jacobi was establishing a component process. The first pass was a long and in-depth Confluence page covering all of our requirements and scenarios, while ensuring that all system additions would pass through the necessary stakeholders. I don’t think anybody actually read it.</p><p>If they did read it, it certainly didn’t show. For example, the process outlined that every new UI component needed to pass through a review panel with the design system owners and design manager to determine whether it should be systematized and documented as a Jacobi component. But because the team was accustomed to simply Jacobi-fying every time we used a component more than once, the process was forgoed in favor of what best fit our workflow.</p><p>Even I will admit to having skirted the process. Maybe more than once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6G-EqMoKdM98XImbURo1w.png" /><figcaption>Our new process flowchart</figcaption></figure><p>Revamping our component process, we learned to align with the team’s <a href="https://en.wikipedia.org/wiki/Desire_path">desire paths</a>. Our new documentation even added a flowchart to reach those choosing not to read. With that, the component process became a formalization of what already worked in practice, and a quick way to onboard new members.</p><p>Thanks for reading. Our next post will cover how we created a more useful, usable, and accessible color system. Follow to stay updated as we publish each deep dive on how we built Jacobi.</p><p><a href="https://www.cloverhealth.com/en/about-us/current-openings">If you’d like to work on cool projects like this, join us! We are hiring across the United States and Hong Kong.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d6ccfd5c8c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clover-health/four-collaboration-lessons-from-the-jacobi-design-system-6d6ccfd5c8c8">Four collaboration lessons from the Jacobi Design System</a> was originally published in <a href="https://medium.com/clover-health">Clover Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Jacobi Design System and how we got here]]></title>
            <link>https://medium.com/clover-health/introducing-the-jacobi-design-system-and-how-we-got-here-47161e80b6c4?source=rss-4b1c7b10cc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/47161e80b6c4</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[healthcare-technology]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Mikail Gündoğdu]]></dc:creator>
            <pubDate>Fri, 22 Apr 2022 17:49:26 GMT</pubDate>
            <atom:updated>2022-04-29T16:56:09.370Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.cloverhealth.com/en/">Clover Health</a>’s mission is to improve every life. A big part of how we do that is through the Clover Assistant: a tool that breaks down barriers between today’s healthcare silos by delivering real-time, personalized insights to providers, with the aim of supporting better informed clinical decision-making.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDpn3Exh_aU09yQrOQ72pA.png" /></figure><p>But designing for the <a href="https://www.cloverassistant.com/">Clover Assistant</a> requires overcoming the complexity that is inherent to healthcare, and especially Medicare. Patient care teams need to manage holistic treatments while also keeping up with specialized documentation. Clover wants to focus on creating solutions for providers’ hardest problems, and those solutions should demand as little time as possible from our users.</p><p>That’s why we created the Jacobi Design System. In the coming weeks, we’ll be publishing a series of posts discussing how we created Jacobi. We’ll assume you know enough about design systems to understand<a href="https://bradfrost.com/blog/post/atomic-web-design/"> the concepts</a> and<a href="https://www.nngroup.com/articles/design-systems-101/"> why you need one</a>. For now, we’ll introduce you to the different facets of Jacobi and what you can look forward to.</p><h3>Jacobi: An Overview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/0*MmeIXDbgrq8n9u3y.jpg" /><figcaption><a href="https://en.wikipedia.org/wiki/Mary_Putnam_Jacobi">Mary Putnam Jacobi</a>, the namesake of our design system</figcaption></figure><p>Jacobi is the third version of Clover Health’s design system. While Clover’s past design systems were more akin to style guides and component libraries, we wanted Jacobi to enable our product and engineering teams to hit the ground running on each project. That meant upgrading to accessible foundations, a robust component library, and consistent patterns that would allow medical practices to focus on the patient instead of the computer.</p><h4>Team</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uE9w5xfv_cP034PT34e6Lg.png" /><figcaption>Peter prefers the color treatment of Mary Putnam Jacobi’s era</figcaption></figure><p>The Jacobi effort has been led by two of the biggest design system nerds on earth: myself, a UX designer, and Peter Agar, a UX software engineer.</p><p>The series will cover exactly why a relationship between a designer and engineer is so essential to a design systems effort and how we created the processes necessary for smooth cross-functional collaboration.</p><h4>Foundations</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mG8YSxGhnNvpYIarCQXg3Q.png" /><figcaption>Jacobi’s color system</figcaption></figure><p>Jacobi features a fully-fledged set of foundations, covering everything from colors and typography to a writing guide that facilitates careful copywriting.</p><p>Stay tuned for a post on how we created a color system that enabled AA WCAG compliance without the need for audits or color contrast tools.</p><h4>Components</h4><figure><img alt="Our calendar picker component" src="https://cdn-images-1.medium.com/max/596/1*dm9gt-Dn4s9AMXu2y5bmKQ.png" /><figcaption>Jacobi’s calendar picker</figcaption></figure><p>Jacobi’s library has grown to cover all components we’ve found more than a single use for. Each exists within our design tooling and our engineering tooling, enabling our team to move as fast and reliably as possible.</p><p>Does your team have a usable and accessible calendar picker? That was especially challenging for us, so look out for a post that covers what we did to create one.</p><h4>Patterns</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*3utUvdO4kRBokeAtclrI5A.png" /><figcaption>The information card pattern we use across the Clover Assistant</figcaption></figure><p>The Clover Assistant presents a unique problem. Healthcare staff, especially doctors, are tremendously pressed for time with patients, limiting our users’ ability to work with specialized digital tools.</p><p>We’ll present how we solved for that by creating patterns that leverage consistency and the mental models of our users, resulting in an interface that patient care teams can pick up and use in a snap.</p><h4>Documentation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HypQ_gerRC437yAcFeIMLw.png" /><figcaption>Tragically, our documentation does not use Calibre to document Calibre</figcaption></figure><p>Of course, a design system can’t achieve meaningful impact if nobody knows how to use it. We’ve documented all of Jacobi in our Zeroheight, with links to our Storybook and Figma component libraries.</p><p>We’ll cover how we approached documentation, but also the strategies we used to fit documentation into our busy workflows.</p><p>Thanks for reading. Follow to stay updated as we publish each deep dive on how we built Jacobi.</p><p><a href="https://www.cloverhealth.com/en/about-us/current-openings">If you’d like to work on cool projects like this, join us! We are hiring across the United States and Hong Kong.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47161e80b6c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clover-health/introducing-the-jacobi-design-system-and-how-we-got-here-47161e80b6c4">Introducing the Jacobi Design System and how we got here</a> was originally published in <a href="https://medium.com/clover-health">Clover Health</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eight Things You Need To Know About Design Systems]]></title>
            <link>https://medium.com/tradecraft-traction/eight-things-you-need-to-know-about-design-systems-bae8bd884b3b?source=rss-4b1c7b10cc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/bae8bd884b3b</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[airbnb]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Mikail Gündoğdu]]></dc:creator>
            <pubDate>Tue, 03 Jul 2018 15:46:01 GMT</pubDate>
            <atom:updated>2018-08-05T23:32:07.261Z</atom:updated>
            <content:encoded><![CDATA[<h4>I attended a whole lot of talks so you don’t have to.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIgoKoq1wHPUJI7mSW9tSA.png" /></figure><p>It’s on every job description. You see it all over the freshest design tool release. You might have even heard your family mention it at Thanksgiving. <strong>But what are the facts on these “design systems” that has the whole industry talking?</strong></p><p>Bridging design and engineering has been an intense interest of mine since transitioning to design from software engineering, so I was eager to learn all about design systems as soon as I heard they were powerful tools for design teams and their engineering stakeholders. Fortunately, <a href="https://www.rethinkhq.com/">RETHINK</a> and <a href="https://sfdesignweek.org/">SF Design Week</a> organized a whole lot of events on the subject over the last month and I tried going to every single one of ‘em.</p><p>That means <strong>I went to over fifteen different talks by designers throughout different organizations</strong>. Each designer brought <strong>unique, actionable insights on design systems.</strong> Here they are.</p><p><em>This is a longer read, so </em><strong><em>I’ve applied some liberal bolding if you want to scan the important bits</em></strong><em>.</em></p><h3>1. Why design systems are important.</h3><figure><img alt="Image result for figma design systems" src="https://cdn-images-1.medium.com/proxy/1*OMfPCTUNbHRkBp6GGkbhkQ.png" /><figcaption><a href="https://blog.figma.com/introducing-designsystems-com-8826fd2efd57">Source.</a> Figma‘s designsystems.com is their resource for design system learning.</figcaption></figure><p>Diana Mounter, Design Systems Manager @ GitHub, summed it up rather well:</p><ul><li><strong>Design systems bring order to chaos.</strong> Everyone is kept on the same page, so the entire product remains consistent and polished throughout.</li><li><strong>Design systems improve the user experience through the repeated use of familiar and proven patterns.</strong> Designing anything from scratch leaves room for error, so try to use what already works.</li><li><strong>Design systems improve workflow efficiency. </strong>Product teams know exactly how components of new features should look and how to implement them.</li></ul><p>Noah Levin, Head of Design @ Figma, really drove the last point home. He preached the philosophy of repeatability in his talk, explaining that <strong>the best thing you can do after spending your time doing something like building a new icon, is to automate that practice for the next person</strong>. In doing so, you will not only have brought value to your own work, but to the work of the entire organization. For Noah, Behavior = Motivation * Ability * Trigger. <strong>When somebody on your team is triggered to complete a design, we can do little to change their motivation, but we can do so much through design systems to improve their ability</strong>. <strong>The end result is behavior that produces a more consistent, proven design so much faster.</strong></p><h3>2. What a design system is.</h3><p>Karri Saarinen, Design Systems Lead @ Airbnb, gave this definition<strong>:</strong></p><blockquote>A set of shared, integrated patterns and principles that define the overall design of the product</blockquote><p><strong>If you have little experience with design systems, a definition so broad could be perceived as ambiguous or unhelpful. </strong>The lack of detail is key, though. Design systems don’t require a more specific definition. They need the room to be whatever an organization requires for design and its implementation to move fast without breaking things.</p><p><strong>But here’s a little more info, straight from the man:</strong></p><h3>Karri Saarinen on Twitter</h3><p>2/ notes: integrated = its built in to the product and organization/product development process, not merely a styleguide you reference</p><h3>Karri Saarinen on Twitter</h3><p>3/ shared = it&#39;s actually shared and adopted across the organization, in order to cover major part of the product</p><h3>Karri Saarinen on Twitter</h3><p>4/ patterns = can be patterns and/or components. principles = there is underlying principles behind those pattern that guide the work</p><p><strong>Flip through existing design systems to better understand what they are in practice</strong>. Here’s <a href="https://material.io/">Material Design</a>. This is <a href="https://protocol.mozilla.org/">Protocol by Mozilla</a>. And here’s the <a href="https://developer.apple.com/design/human-interface-guidelines/ios/overview/themes/">iOS Human Interface Guidelines</a>, which we don’t officially call a <em>design system</em> for some nuanced Apple-reason much like why we shouldn’t call the HomePod a <em>smart speaker</em>. <strong>All these systems are built differently, but understand how they all fit within the boundaries of Karri’s definition.</strong></p><p><strong>You might be wondering why the components you threw together in Sketch are merely considered “pattern libraries”, “style guides”, or “UI kits”.</strong> Mike Dick, Design Technologist @ SurveyMonkey, actually started with one of these UI kits when he went about componentizing their elements, but <strong>he went back to the drawing board as he started showing it to engineering. </strong>Rather than building a system of components for designers, <strong>Mike implemented a single source-of-truth for design to integrate with engineering</strong>. Designs built with this design system could easily be translated to CSS, the language used to define styling, and could therefore <strong>quickly cascade design changes to their front-end components. </strong>With enough resources, larger organizations like AirBnb can implement tooling that translates screens built with their design system directly to code (This is why <a href="https://framer.com/announcement?utm_source=designer_news&amp;utm_medium=launch_post&amp;utm_campaign=framer_x_teaser">Framer X</a> is such a big deal).</p><p>Looking back at Karri’s definition, we see a mention of principles. This is to say that <strong>design systems incorporate rules and guidelines</strong>, which inform users on how to implement the patterns and styles organized within the system. Rich Fulcher, Head of Material Design @ Google, explained why principles were a defining piece of the system: because<strong> a design system only truly exists if it can be used without the creator.</strong></p><h3>3. Any design system is better than no design system at all.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QMLoomi2PTs_BMwjMIl0GA.jpeg" /><figcaption>Diana Mounter, GitHub</figcaption></figure><p>GitHub’s design system, Primer, was being revamped internally and privately. Doing so, Diana said, was in part because <strong>her team faced Imposter Syndrome comparing Primer to the systems of matured and larger organizations</strong> like AirBnb’s <a href="https://karrisaarinen.com/dls/">DLS</a>, Shopify’s <a href="https://polaris.shopify.com/">Polaris</a>, and the <a href="https://designsystem.digital.gov/">US Web Design System</a>. <strong>Primer felt unpolished in comparison. Many components were deprecated.</strong></p><p><strong>But you know what’s worse than knowing a component is deprecated? Not knowing, and pushing that atrocity to production.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*f1UOQs9RfyPCZDludVtYbQ.png" /><figcaption>Primer and other systems use flags to quickly indicate whether or not components are deprecated.</figcaption></figure><p>That’s why Diana says you shouldn’t worry about comparing your design system to any other organization’s system, because thats not what proves its success. Instead, Diana says, <strong>push your design system out and analyze utilization to measure its success.</strong> Chaos will be a natural part of something so new to the practice as design systems, so focus on what matters and take advantage of the chaos. <strong>Are people using the design system in their workflow, and contributing back to it to make it better?</strong></p><p>There’s no doubt that systems like Polaris, iOS HIG, and Material Design are remarkably thorough and even cool to look at. <strong>But not only are these systems built by companies with massive resources, they’re especially targeted at third-party stakeholders who don’t work under them. </strong>It just comes with the territory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mHw4lY7EtIhhn5s5EW4SMQ.png" /><figcaption>Diana showed this funny blunder. Ideally, components would not hinder readability of the exemplified code.</figcaption></figure><p>Diana ended her talk with a tweet to share <a href="https://styleguide.github.com/primer/">Primer</a> with the world, flaws and all. In this way,<strong> GitHub’s system gives stakeholders: 1. Access to its resources, and 2. Opportunities to improve the system’s flaws.</strong></p><h3>4. How to get started on a design system.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QtSN6fzPto8Vvu6qhD4tLg.png" /><figcaption>The first thing you see at Shopify’s Polaris.</figcaption></figure><p>First off, you need a snazzy name. As soon as you read <em>Polaris</em>, you know you’ll be led to your well-designed salvation.</p><p>Just kidding.<strong> In fact, Material Design wasn’t officially titled until a month before being published.</strong> Rich Fulcher said it was known internally as ‘Quantum Paper’ most of the time.</p><p>And <strong>don’t start with a Sketch file</strong> either! <strong>Michael McCombie, Systems Designer @ Mozilla, made that mistake once. As soon as he brought on other stakeholders, he had to start again.</strong> A design system is a piece of design solving user problems. <strong>Understand the problem and the users first.</strong></p><p>When Jordan Girman, Sr. Director of User Experience @ Glassdoor, set out to make Glassdoor’s first design system, he had the team <strong>start with these questions:</strong></p><ol><li><strong>What’s the need for this system?</strong></li><li><strong>How is design being implemented now?</strong></li><li><strong>How should it be implemented?</strong></li></ol><p><strong>From there, they set goals and requirements for their design system that aligned with the rest of the organization. </strong>That alignment, as explained by Mike Dick, relies on a relationship. <strong>Without a relationship with your stakeholders, you’ll run into a few challenges</strong>:</p><ul><li><strong>Nobody will be speaking the same language.</strong> “Style guide” means two different things for engineers and designers. How will you know if your terminology and documentation will be understood by everyone?</li><li><strong>Getting everybody onboard with your design system will be a lot harder.</strong> Your people won’t understand the value of something they didn’t help create.</li><li><strong>Nobody will know what the source of truth is.</strong> Kiss your consistency goodbye.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gO1M0T6JNtl4LOjw6ngDQQ.png" /><figcaption>What an engineer thinks when you say, “style guide”</figcaption></figure><p><strong>Mike especially recommends finding a counterpart who complements your skills with a shared passion for bridging the design and engineering gap.</strong> If you’re not a great coder, make friends with someone who <em>is</em> a great coder with a deep understanding of the engineering stacks. <strong>That allowed Mike to understand that documenting CSS, rather than redlining system components, was key for engineering to make the best use of system.</strong></p><p>I recommend you search Medium for resources on what tools to use and how to use them to build your design system. You don’t want to hear it from me, <a href="https://blog.figma.com/how-to-build-your-design-system-in-figma-645a4d96509f">because I’m just going to say something about Figma.</a></p><h3>5. Design systems document everything.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tSK70LTKsf1EdouU3depSw.png" /><figcaption>Microsoft’s Fluent documentation on Radio Buttons.</figcaption></figure><p><strong>After you’ve established the goals and requirements of your system with stakeholders, nailing down your overarching, guiding design principles is a great place to start.</strong> Great design principles will allow you to build out your system with a consistency that aligns with your goals, and they can be a shortcut to your user’s fluency of the entire system. Again, I recommend you take a <strong>look at existing, robust design systems like Polaris to find </strong><a href="https://polaris.shopify.com/guides/principles#navigation"><strong>the best examples of principles in practice</strong></a>. When you start creating your own, Rich Fulcher and Selene Hinkley, Content Strategist @ Shopify, had <strong>a few things to keep in mind:</strong></p><ul><li><strong>Many don’t even want to read principles;</strong> if they do read, they might scan. If they scan, they may not understand. If they don’t understand, they certainly won’t apply. So, <strong>understand your audience when creating your copy and content!</strong></li><li><strong>Be guiding, not prescriptive.</strong> Leave room for creativity by giving a spectrum of what’s acceptable. Principles should be a guide for decision-making.</li><li><strong>Limit the number of principles.</strong> Shopify started with 13, but they now have it boiled-down to 4. They removed “top down” and “middle management” principles that didn’t do much for those designing and implementing the design first-hand in day-to-day work. Grassroot principles are gold.</li><li><strong>Reflect your principles in what you create. </strong>For the type of user that refers to the design system in-context and learns through example, this will do a lot to ingrain your principles and remain consistent.</li><li><strong>They can’t limit your brand or product principles.</strong> Design systems should be subsystems of your organization, so make sure they fit within the whole.</li><li><strong>Keep evolving your principles.</strong> Apply user-centered design to the creation of your principles so that they reflect your system and reality accurately. Otherwise, consistency will break down as other users apply your principles.</li></ul><p>From there, <strong>add the components of your design system while making sure to document their specific principles. </strong>Things will move so much faster, clueless teammates won’t bug you, and your name won’t be cursed when you’re not around. <strong>Here’s what Selene had to say about documenting your design system:</strong></p><ul><li><strong>Break paragraphs into bullets and lists.</strong></li><li><strong>Use visual examples wherever possible.</strong></li><li><strong>Keep sentences short and actionable.</strong></li><li><strong>Use dos/don’ts.</strong></li><li><strong>Make your don’ts less obvious. </strong>Model them after realistic mistakes that could result from misinterpretation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFqGQpn26SUezsOBYt_-kA.png" /><figcaption>Source: <a href="https://material.io/design/components/buttons.html#anatomy">material.io</a></figcaption></figure><h3>6. Design systems need to integrate accessibility.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xoEoK-2wEyKHK89XpZuqYw.png" /><figcaption>Check out this tool for checking accessible contrast ratios at <a href="https://webaim.org/resources/contrastchecker/">WebAIM</a>.</figcaption></figure><p>John Cassidy, Senior Designer @ Google, started his talk with a fat stat:</p><blockquote>1 in 7 people are disabled. That’s over a billion people.</blockquote><p>Still, John had more to say. A user is disabled as soon as their hands are full of groceries. If they find themselves traveling in a foreign country with no local language skills, they’re disabled. <strong>If you live long enough, you‘ll probably end up permanently disabled one day.</strong></p><p>If you’re convinced yet, John has this <strong>advice for bringing accessibility to your design system.</strong></p><ul><li><strong>Apply accessibility-minded design constraints. </strong>Ensure that your components account for scenarios in need of accessibility, like resized type for far-sightedness and alt-text for screen readers. Don’t forget about temporary disability; what if your product is used by drivers in bright daylight?</li><li><strong>Learn about the accessibility technology available to your users.</strong> OS technology like iOS Magnifier and Windows Narrator are most available, but add-on products like the Xbox Adaptive Controller exist, too. And some technology isn’t limited to use by disabled users, especially voice assistants.</li><li><strong>Test your components with those accessibility technologies turned on. </strong>Pretty simple. Turn on technologies like iOS VoiceOver and ensure they work with your system components in a useful manner.</li><li><strong>Test your product with users of varying disability. </strong>Of course, you need to bring your product in front of users who are on a spectrum of different mental, physical, and situational disabilities.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAXpddmWZm7bolSyLVTqhg.jpeg" /><figcaption>Microsoft’s Xbox Adaptive Controller is one of the latest accesibility technologies for users.</figcaption></figure><h3>7. Color and illustration can and should be systematic.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BmOoMK6WIm_gc0eFrebJBw.png" /><figcaption>Shopify’s Polaris color palette</figcaption></figure><p>Your organization may already have brand colors that would be handy for filling in your UI, but not so fast. <strong>Do not choose your UI colors by copy-pasting your brand colors.</strong> Brand colors do not take into account usability, though <strong>deriving your base colors from your branding is probably the best place to start</strong>. Linda Dong, Design Manager @ Lyft, recommends you <strong>create spectrums of brand colors with overlaid text to settle on UI colors that satisfy accessible color ratios.</strong> Of course, <strong>test all of this in the situations your product will be used in.</strong> Lyft needs to work for drivers in the dead of night and on the brightest of days.</p><p>When you settle on your colors, <strong>don’t refer to those colors in your design system with their hex code or their “official” name.</strong> Linda pointed this out with a funny color-naming quiz. Turns out that <em>dove</em> is a medium-grey. Call me unsophisticated, but I think <em>pidgeon </em>is what you’re looking for.</p><p>Instead, <strong>define your color scheme through color tokens</strong>. Michael McCombie and the Protocol system use basic color names like $color-red, while Linda and Lyft use a $ColorName-Value format because of their color spectrums. Of course, <strong>bring in all of your stakeholders as you build your color system — and advertise it when its ready — to ensure adoption.</strong></p><p>Jennifer Hom, Experience Design Manager of Illustration @ Airbnb, came onboard to revamp their illustration system. <strong>Before, Airbnb had illustrations shared across sizes or different illustrations between sizes. Jennifer changed illustrations to systematically increased vector weights and detail as export sizes went up (1x, 2x, 3x), allowing for a consistent but platform-appropriate design between devices.</strong></p><p>Jennifer also had these <strong>principles to consider for your illustration system:</strong></p><ul><li><strong>Ensure your illustrations are grounded.</strong> Illustrations should allow most, if not everyone, to relate to your product and without thinking about minutae.</li><li><strong>Don’t let your illustrations take the spotlight.</strong> They should increase delight without distracting the user from their goal.</li><li><strong>Use accessible colors.</strong> Check your color ratios!</li><li><strong>Be diverse, but realistic.</strong> Airbnb’s illustrations are based on real people, so they “feature” Donald Glover and Jennifer’s random Facebook friends. Airbnb also spoke with organizations and authorities on disabilities that gave them the idea to use a subtle cue like <a href="https://www.sciencedirect.com/science/article/pii/S1569186116300043">headphones</a>.</li><li><strong>Test your illustrations.</strong> Oh man, can you believe it? This piece of design needs to be tested as well. Showing the China-specific illustrations to the Beijing office allowed Jennifer to figure out that big-chested Chinese males wouldn’t be the most relatable.</li></ul><h3>8. How to scale a design system.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IMEfPXmciUiT665JuvH3Rg.png" /><figcaption>Karri Saarinen: How a design system will evolve with scale.</figcaption></figure><p>What’s that? Your company just announced a Series C! Within 3 months, you’re expected to have a full suite of apps across every platform and a team of Not-Yous managing every one.</p><p>Fear not. Others have made it to the other side. <strong>Here’s how Karri thinks you can scale your design system:</strong></p><ul><li><strong>Use defined primitives.</strong> Define the color schemas, text styles, grids, etc. that will be the building blocks for every addition to your design system. All of Airbnb’s core components and team-specific libraries are built with the same set of primitives.</li><li><strong>Build your components using those primitives, and build your patterns with those components.</strong> This will ensure consistency while allowing for a degree of flexibility and malleability.</li><li><strong>Remain flexible.</strong> You need flexibility to allow for spacing, text truncating, different text sizes for accessibility and internationalization, different color choices, custom components, and good ol’ creativity.</li><li><strong>Make your design specs platform-agnostic.</strong> DLS defines their components in JSON, a ubiquitous data standard that allows for automated translation to platform-specific styles like CSS.</li><li><strong>Add team-specific libraries, but keep them under control.</strong> Airbnb limits their team libraries to experimental and specific components. So, team libraries are monitored and components are sent up the chain if they are suitable core components. <strong>70 components make up 60% of Airbnb’s front-end across all platforms!</strong></li></ul><p><em>Big thanks to the incredible speakers: </em><a href="https://medium.com/u/b954a8b795dc"><em>Diana Mounter</em></a><em>, </em><a href="https://medium.com/u/8fd11f66a61f"><em>Noah Levin</em></a><em>, </em><a href="https://medium.com/u/b06e8b8cce79"><em>Karri Saarinen</em></a><em>, Rich Fulcher, </em><a href="https://medium.com/u/f97bedc3aa0b"><em>Michael McCombie</em></a><em>, </em><a href="https://medium.com/u/d551ece3563e"><em>Linda Dong</em></a><em>, </em><a href="https://medium.com/u/d90799c6e639"><em>John Cassidy</em></a><em>, Jennifer Hom, </em><a href="https://medium.com/u/1673bbd9e18c"><em>Selene Hinkley</em></a><em>, and </em><a href="https://medium.com/u/da31cf74d619"><em>Jordan Girman</em></a><em>. And thanks to </em><a href="https://medium.com/u/9088475dc405"><em>Julie Stanescu</em></a><em> (along with her team at Rethink) and </em><a href="https://medium.com/u/ac8e8ab936d9"><em>SF Design Week</em></a><em> for organizing their awesome talks!</em></p><p><em>Lastly, thanks to </em><a href="https://medium.com/u/482d19dd1f59"><em>Jasmine Rosen</em></a><em> and </em><a href="https://medium.com/u/386efc37be7d"><em>Jodee Cherney</em></a><em> for editing and the rest of </em><a href="https://medium.com/u/7be06999ed0a"><em>Tradecraft</em></a><em> for their continued support, and </em><a href="https://medium.com/u/3871a155440f"><em>Tyler Heucke</em></a><em> for being my “engineering counterpart”.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bae8bd884b3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tradecraft-traction/eight-things-you-need-to-know-about-design-systems-bae8bd884b3b">Eight Things You Need To Know About Design Systems</a> was originally published in <a href="https://medium.com/tradecraft-traction">Tradecraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bringing Your Engineering Face to Design]]></title>
            <link>https://medium.com/tradecraft-traction/bringing-your-engineering-face-to-design-680a8ba1a24?source=rss-4b1c7b10cc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/680a8ba1a24</guid>
            <category><![CDATA[framer]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[origami-studio]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Mikail Gündoğdu]]></dc:creator>
            <pubDate>Mon, 26 Feb 2018 18:25:54 GMT</pubDate>
            <atom:updated>2018-02-27T22:57:58.848Z</atom:updated>
            <content:encoded><![CDATA[<h4>How software engineering can influence your design process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Niuyu5SfjsuHNlOAuJsXMA.jpeg" /><figcaption>Asli Kimya at Tradecraft</figcaption></figure><p>Coming from a background in computer science, my transition into product design has been accompanied by a few questions: How do I best market my background without falling into a front-end developer hybrid role? What skills should I hold onto and expand? Do I have that “eye for design,” or have I been blinded by an undergrad of command line UI?</p><p>That’s why I had to listen to <a href="https://medium.com/u/36f2c0e52fdb">Asli Kimya</a>. She came by Tradecraft for a talk on how she applies her background in computer science to her process as a product designer at Twitter. Remembering my need for insight from other programmers-turned-designers inspired me to write this post. I wanted to share her points from the talk, and throw in a few others that I thought could improve anyone’s design process from an engineering perspective.</p><h4>A note for designers of all backgrounds:</h4><p>I tried to keep this post free of data structures and Big-O notation. Ultimately, the difference between you and a designer more familiar with the engineering side of things is exposure. I hope this read gives the right exposure to get you started with putting on your engineering face.</p><h3>Communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CsnwjR_8RiFBHVEpsAjNUw.png" /><figcaption>If you ever need an engineer to talk to, look for the hard hat.</figcaption></figure><p>Asli started her talk explaining that she brings engineers into her process as soon as it begins. Just hanging out with her engineering coworkers was a big help. In the earliest of stages, she explained, being friends with engineering allows her to casually run by design decisions and ideas to understand their feasibility before time and effort are really spent on them.</p><p>Ensuring that engineering is on board with building your product is essential. Asli exposes herself to their conversations to get the best understanding of her product’s underlying systems and constraints. She also picks up on a lot of jargon doing this, a useful tool for communicating with those building your product. Get engineers on board with your data viz by dropping a mention of a SQL join or two.</p><p>Designers are an empathetic bunch, a necessary trait for keeping the user’s needs in mind. So empathizing with engineering in the design process should come just as naturally. The result is a smooth handoff that leaves you and your coding stakeholders happy.</p><h3>Prototyping</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1XRVqM3Tx-lTc7m0RYuoUQ.gif" /><figcaption>Framer even integrates with… FIGMA!?! (<a href="https://blog.figma.com/introducing-figmas-integration-with-framer-c69a747aeee2">source</a>)</figcaption></figure><p>I thought I might put programming behind me as a designer, but it turns out that some easy front-end logic can bring designs so much closer to the finished app — no coding necessary! Asli and her coworkers at Twitter have become familiar working with Origami, Facebook’s free prototyping tool adept at very high fidelity prototypes. Origami uses visual programming rather than raw code, making it much easier to grasp than prototypes created using developer tools. Origami’s interactions and motion design can be fine-tuned to a near replica of the desired outcome. <a href="https://medium.com/soda-studio/a-review-of-the-new-origami-studio-461c5aa1e15">Origami is best limited to small interactions, though.</a></p><p>More recently, Twitter’s designers have been picking up Framer. Though Framer is pricey at $144 a year, it allows for even more possibilities and customization without breaking down as your prototypes get larger. You can even make API calls to use live information. This comes at the cost of utilizing CoffeeScript to define your interactions. CoffeeScript is what you get when you add <a href="https://en.wikipedia.org/wiki/Syntactic_sugar">syntactic sugar</a> to <a href="https://youtu.be/eWuRwu2DhwU?t=1m19s">JavaScript</a>, a language that needs it. You don’t need to write too much, though. Framer fills a lot of it in for you. Anything possible with JavaScript, like the web applications you know and love, <a href="https://medium.com/sketch-app-sources/five-app-prototyping-tools-compared-form-framer-origami-pixate-proto-io-c2acc9062c61">is possible with Framer</a>.</p><p>Both of these programs do have steeper learning curves than simpler tools like InVision and Principle, but they bring you so much closer to the real thing. This means much less costly tinkering to adjust your designs when they hit production, freeing up engineering’s time running your little social experiments. Programmers may feel a bit more comfortable picking up these tools, but anybody should be able to learn Origami without coding experience.</p><h3>Edge Cases</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*oUBIXuxlCuswqeQrHM9Y6g.gif" /><figcaption>Chrome’s error state minigame. (<a href="http://www.omgchrome.com/chrome-easter-egg-trex-game-offline/">source</a>)</figcaption></figure><p>Programs need to handle all edge cases, so what about your designs?</p><p>Asli pointed out that her presentation’s Origami prototypes were a little ideal. For example, button presses immediately played videos. Designers need to be careful not to design for a prototype utilizing static data, and consider that some users are stuck with AT&amp;T’s network. Error states at disconnection and loading states before every video are a part of the experience, but due consideration can make them a little more delightful.</p><p>Twitter’s international presence means that Asli also has to consider localisation and her audience. Some of this can be done by accounting for lengthy-word languages like Russian from the beginning. But that’s not all. In English, for example, Periscope displays a capitalized, “Let’s go LIVE”, to ensure that users don’t confuse the video-broadcasting app for a motivational life coach.</p><p>Put on your QA engineer hat, and challenge yourself to think up the crazy bits unrelated to the core experience. To remain confident that the final design is at its best, you can do what Twitter does: have office hours with power users that have unmatched familiarity of the products features and flaws. Discovering every corner of an app can take a lot of investment and stumbling around that can be difficult to reproduce at the office, but getting everything right shows so much more polish when engineering reaches those edge cases.</p><h3>Git</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*gb8fZJp2yJyNNa--qQJmSg.png" /><figcaption>(<a href="http://xkcd.com/1597/">source</a>)</figcaption></figure><p>Git is a system for teams to collaboratively build computer files. All of your changes can be tracked, compared, and undone.</p><p>If you don’t already know Git, this one’s a doozy. No two ways about it, Git on a production codebase is a challenge because you don’t just need to know Git, you need to pretend to be confident with Git. This takes some practice, and I know just the thing.</p><p>I recently ran an 8-person design project utilizing <a href="https://www.goabstract.com/">Abstract</a>, an app for Git-like collaboration on Sketch files. Despite my time with Git, I occasionally hesitated pressing Abstract’s big blue button, the primary call-to-action for syncing your work. Still, Abstract is a great first foray into version control and a fantastic tool for design teams. Try it for a project. Once you understand that a press of Big Blue can do no permanent wrong and why, there is a <em>possibility</em> you have a basic conceptual grasp of Git. At the very least, you will bring the same improvement to your design team’s collaboration that Git brings to the 99.9% of software developers who use it.</p><p>From there, any designer can try tutorials to learn Git and alleviate the need for JIRA tickets on pixel-perfect UI fixes. Going into code and adjusting it yourself will free up the time engineering spends cursing your perfectionism. Give your Git commits a descriptive message if you want even more mad engineering respect points. One day, you may even come to find yourself understanding Git.</p><h3>Repetition, Repetition, Repetition</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*QbQ9jk506osrCrkOXri2YA.jpeg" /><figcaption>(Andy Warhol)</figcaption></figure><p>There’s an idea in programming that my professors often talked about but my last-minute all-nighters rarely implemented: functional decomposition.</p><p>Programs are a set of steps, and programming often involves using the same steps over and over again. So, programmers put those steps into their own functions they can bring in throughout their code. They even borrow functions from other libraries.</p><p>This allows for easy repeatability of tried-and-true solutions. Remind you of anything?</p><p>UX/UI designs are a set of elements, and designing often involves using the same elements over and over again. So, designers put those elements into their own symbols they can bring in throughout their design. They even borrow symbols from other libraries.</p><p>Hey, thanks repetition! Repeatability saves monumental amounts of time. Create once, use everywhere. Fix once, fix everywhere. This philosophy works so well, <a href="https://jalopnik.com/volkswagen-plans-to-take-over-the-world-by-being-clever-646936695">other industries</a> are getting on board.</p><p>This is why sticker sheets and style guides bring easy uniformity and high efficiency to the design process. Design systems take that one step further, by bringing in a set of rules for components that engineering can use to translate those components into UI elements that formulaically respond to their environment. Seriously, if you want to truly bridge the gap between design and engineering, learning design systems is essential.</p><h3>All This… Why?</h3><p>I lied, I have to bring up Big-O notation. But all I’ll say is that there’s a notation for software engineers to communicate the efficiency of code to each other. Engineers are obsessed with efficiency, and for good reason. It frees up a system to make the most of limited resources, like AT&amp;T’s network.</p><p>And that’s just it. With efficiency, you can give so much more value to an organization with limited time and resources. Bringing your process closer to the development process makes the hand-off as hands-free as possible, letting engineers do their engineering thing with the efficiency necessary to competitively ship product. Former engineers might relate more to all that, but I think anybody can understand and apply the engineering mindset.</p><p><em>Big thanks to </em><a href="https://medium.com/u/36f2c0e52fdb"><em>Asli Kimya</em></a><em>, </em><a href="https://medium.com/u/a2cea8936326"><em>Tea Chang</em></a><em>, </em><a href="https://medium.com/u/f808c30b70de"><em>Britta Cheng</em></a><em>, and </em><a href="https://medium.com/u/7be06999ed0a"><em>Tradecraft</em></a><em> for making this article possible. And thank you for reading!</em></p><p><em>Don’t forget that you can give as many as 50 claps to a Medium post that changed your life.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=680a8ba1a24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tradecraft-traction/bringing-your-engineering-face-to-design-680a8ba1a24">Bringing Your Engineering Face to Design</a> was originally published in <a href="https://medium.com/tradecraft-traction">Tradecraft</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thoughts From a Happy Clapper]]></title>
            <link>https://medium.com/@mikailmikhail/thoughts-from-a-happy-clapper-ab314982e7cc?source=rss-4b1c7b10cc12------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab314982e7cc</guid>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[clapping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Mikail Gündoğdu]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 22:42:31 GMT</pubDate>
            <atom:updated>2019-11-07T20:14:59.571Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*fhVjrV9uv3w7a1EVDrA7-w.gif" /></figure><p>Another redesign, another controversy: Medium Claps.</p><p>Medium also changed their logo to mixed reactions. But I’d like to focus on my favorite change, replacing Recommends with Claps, despite the negative backlash. I love Clapping, and I think everybody can learn to love it, too.</p><h3>Social Media Commentary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aujPUHyzign660Z-YQi4mw.png" /></figure><p><a href="https://medium.com/search?q=medium%20claps">Yikes</a>.</p><p>Thoughtful criticism has mentioned that:</p><ul><li>Claps can be gamed.</li><li>Claps are lazy.</li><li>Claps cannot (easily) be undone.</li><li>Claps have wonky behavior between mobile and web when held down.</li><li>Claps are assigned to legacy posts as 1 Recommend (Heart) = 1 Clap, significantly degrading their reputation.</li></ul><p>I must admit, that last one is a doozy. Medium is now five years old. As a new user, some of my favorite content was published in its earlier days. These posts deserve continued attention. Regardless of how visible Medium or Google chooses to make them, fewer Claps will tarnish this content for users unaware of Medium’s evolution. If you will allow me to continue speaking as an armchair PM, perhaps Recommends should be assigned the average number of Claps posts receive from a single user. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*do_CMwCXtnT_C83wksOlQg.png" /><figcaption>Full Disclosure: I passed Statistics by the skin of my teeth.</figcaption></figure><p>The other criticisms can be applied to <a href="https://krebsonsecurity.com/2017/08/twitter-bots-use-likes-rts-for-intimidation/">any</a> <a href="https://www.theguardian.com/technology/2013/aug/02/click-farms-appearance-online-popularity">rating</a> <a href="https://www.usatoday.com/story/tech/news/2017/09/07/facebook-fake-likes-scammers-collusion-networks/642446001/">system</a>, or <a href="https://medium.com/tomyum/our-redesign-of-mediums-claps-and-why-they-may-not-have-chosen-to-do-it-this-way-edc9ff6b586e">they can be solved</a> in future updates. Reverting Claps to Recommends is unnecessary.</p><p>But there’s one big thing we need to talk about if this is going to work out:</p><h3>Stop Treating Claps As a Numbers Game</h3><blockquote>How do I decide how many claps a post deserves? Is 1 clap enough, or is that rude? How do I decipher the difference between 23 claps and 40 claps?</blockquote><blockquote>-<a href="https://medium.com/@Alex.Valaitis?source=post_header_lockup">Alex Valaitis</a></blockquote><blockquote>Claps go up by increments of 1, which is too granular. The chances a reader wants to give precisely 17 Claps is probably much lower than giving 15 or 20.</blockquote><blockquote>-<a href="https://medium.com/@ImJasonLi?source=post_header_lockup">Jason Li</a></blockquote><blockquote>So, the thing I’m wondering: I just gave someone 3 claps[…] — is that a great thing or kind of a put-down?</blockquote><blockquote>-<a href="https://medium.com/@dharmesh?source=post_header_lockup">Dharmesh Shah</a></blockquote><p>I get it, we’re human. We like to quantify shit. But when was the last time we counted our applause?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/328/1*8w_dBdrzfMZVYfXUgjgl6g.gif" /><figcaption>One.. Two… Three?</figcaption></figure><p>I try not to focus on the growing number that appears above the Clap button. I enjoy the animations, and the little in-app vibration is my crack, but I Clap to reciprocate the energy and time the author has given me in writing the post. Thoughtful writing is a favor to the reader, so an invaluable post encourages me to max out my Clap button in return. This interaction is more meaningful to me than a lazy 5-star rating. It’s why I love Claps so much.</p><p>I think that removing totals from our focus could help make Clapping fun for everyone. The decision to include it in Clap feedback could be why we’re finding ourselves philosophizing applause. If our behavior should emulate our post-performance meat slapping, counting out our claps detracts from that. What is the count really for? Of course, some feedback is necessary to understand if our Claps register and when we’ve maxed out our Claps.</p><h3>A Possible Alternative</h3><p>While I think it’s still a little early in my design career to dictate drastic changes to a multi-million user product, I’d like to bring my own input to the conversation.</p><p>Have you used Facebook Live before? If you spam the like button, thumbs fly across the screen. I feel inspired by that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*Pl19vc5C7SrmKrzkXmjZOA.gif" /><figcaption><a href="https://www.fastcompany.com/3058643/facebook-embellishing-live-video-with-snapchat-like-bells-and-whistles">Source</a></figcaption></figure><p>Displaying flying balloon Claps, with a “+1” label on each balloon, could encourage users to applaud more naturally. Claps would stream up the side of the screen as the user taps or holds down the Clap button, signifying the buildup of praise with more taps. Ideally, this would remove any focus on exact numbers and let the user enjoy showing the author their appreciation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*wZJbhyigTs2p_2L_vvmbaQ.gif" /><figcaption>Made with Sketch and Principle</figcaption></figure><p>At the 50 Clap limit, the flow would stop and the user would see a banner notifying them of the limit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*-LloTIqX7obvlVIADjze9Q.png" /><figcaption>Made with Sketch</figcaption></figure><p>Medium and the community are going through a rough patch. Feelings have been hurt. The best cure, like in any relationship, is communication. What we like, what we don’t, and how things could change. The goal of this piece is to keep the conversation going for the better. I would love to hear what adjustments you think Medium needs to make.</p><p>Hopefully, as Clapping becomes more familiar to everyone, users will more naturally applaud content whether or not we see adjustments. I am already happily Clapping.</p><p><em>Thank you to </em><a href="https://medium.com/u/b164ab53bfb1"><em>jessica poteet</em></a><em>, </em><a href="https://medium.com/u/33a873e95fb2"><em>Thomas Caruthers</em></a><em>, </em><a href="https://medium.com/u/42b058a719ed"><em>Zac Halbert</em></a><em>, </em><a href="https://medium.com/u/37c886855f49"><em>Russ Klusas</em></a><em>, and the rest of the team at </em><a href="https://medium.com/u/7be06999ed0a"><em>Tradecraft</em></a><em> for their support and editing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab314982e7cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>