<?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 Kurtis Beavers on Medium]]></title>
        <description><![CDATA[Stories by Kurtis Beavers on Medium]]></description>
        <link>https://medium.com/@kjbeavers?source=rss-d2e4f2a00968------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*fSnUJwH-bU0nLGiv.jpeg</url>
            <title>Stories by Kurtis Beavers on Medium</title>
            <link>https://medium.com/@kjbeavers?source=rss-d2e4f2a00968------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:44:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kjbeavers/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[How Stack Overflow Redesigned our Top Navigation]]></title>
            <link>https://medium.com/stack-overflow-design/how-stack-overflow-redesigned-our-top-navigation-f77b7f968bff?source=rss-d2e4f2a00968------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77b7f968bff</guid>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Kurtis Beavers]]></dc:creator>
            <pubDate>Fri, 17 Feb 2017 13:30:49 GMT</pubDate>
            <atom:updated>2017-02-19T13:22:40.377Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YMXOXKuJVeNSpRSibXPLkA.png" /></figure><p>You may have noticed Stack Overflow sporting a new look lately.</p><p>We launched this update as part of a series of changes supporting our core mission: Make developers’ lives better. In the past year, we fully integrated our by-developers, for-developers <a href="http://stackoverflow.com/jobs">Jobs</a> product. We added a whole new content type — <a href="https://stackoverflow.blog/2016/07/introducing-stack-overflow-documentation-beta/">Documentation</a> — to help you find even more solutions to your programming questions. And we added <a href="https://stackoverflow.blog/2016/10/bye-bye-bullets-the-stack-overflow-developer-story-is-the-new-technical-resume/">Developer Story</a> to help developers ditch the outdated resume format.</p><p>During this time, we also evolved our product development process to include more user research, allowing us to validate ideas earlier and surface more users’ voices. There’s a ton you can learn by watching people try to use a feature — things that don’t get uncovered when directly soliciting feedback. As both product and process expanded, it quickly became apparent that Stack Overflow had outgrown some of our previous design decisions.</p><h3>A Common Theme</h3><p>A pattern surfaced when talking to users: even with the addition of Jobs and Documentation to the navigation, many developers weren’t aware of the change. Digging deeper, we discovered that many weren’t really seeing the top bar at all — a “mental block” so effective that most users also couldn’t identify what the icons meant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yr0UBOO8rh5WeBZtEorLgA.png" /></figure><p>Here’s what a few of you said:</p><blockquote><em>“When I come here I’m on a mission; I don’t care about the rest.”</em></blockquote><blockquote><em>“You’re only there for 1 reason: to find the answer to your question.”</em></blockquote><blockquote><em>“From my point of view, nothing above the question title exists.”</em></blockquote><blockquote><em>“I scroll down and read the question.”</em></blockquote><p>The data validated our hypothesis — of the average 9.3 million daily visits to Stack Overflow, we get fewer than 88,000 clicks to the navigation or top bar (this includes inbox, rep, profile, and search.) If you divided each individual click per visit, that’s fewer than 1% of visits navigating anywhere (and far fewer if you counted multiple clicks per visit). Our navigation is not being used by 99% of our users.</p><p>The common use case for millions of daily visitors is “come from Google, scroll to middle of the page to a find an answer (without seeing the nav and sometimes evening ignore the question itself), and leave. This workflow makes sense — and we love helping the world’s developers gain programming knowledge quickly — but this also means many visitors don’t benefit from everything that Stack Overflow has to offer. If they’re not aware, then we’re less effective in helping more developers share their knowledge by finding questions to answer, advance their career search, utilize Documentation, or become contributing members of our community.</p><p>We hypothesized that a lack of engagement with the nav was due to a combination of browsing habits, visual hierarchy, and the right-hand position of the layout. Based on research about <a href="https://www.nngroup.com/articles/f-shaped-pattern-reading-web-content/">F-shaped reading patterns</a> and how readers’ eyes commonly move down the page, it made sense that our navigation was sub-optimal for most people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pw66NGDWvZTL3rYbZph-Xw.png" /></figure><p>We also hypothesized that the focal point of the page (the logo) caused many users to skip over the small top bar. Plus the nav and top bar quickly scroll out of view when moving down the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0SwWai0e9edYjXUHdW0Uw.png" /></figure><p>The product design team then did a <a href="https://robots.thoughtbot.com/the-product-design-sprint">design sprint</a>. Each designer created their own design of the top nav and then converged to critique and identify the strongest ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nsBtYLq-O39wMehLxiFNIQ.png" /></figure><p>The team then combined the best parts of their ideas into one design. The main thinking generated from the sprint:</p><ul><li>Remove clutter and group similar information in a way that’s more quickly parsable</li><li>Stick the navigation to the top of the page so that users who are scrolling quickly to answers or arriving from answer or comment links still have access to search or navigate the site</li><li>Use navigation design patterns more commonly found in contemporary web apps</li><li>Design the navigation as shorthand for the Stack Overflow brand</li></ul><blockquote>“I’m not even sure if the black bar is new.”</blockquote><blockquote>“I logically filter out the stuff that I know I’m not looking for.”</blockquote><blockquote>“Nav looks like tags — they might filter, but they don’t look like navigation. Makes you question what it is so I don’t click it and instead go back to Google that I’m familiar with.”</blockquote><blockquote>“I’m signed in and I still don’t know what those (inbox, achievements) mean.”</blockquote><blockquote>“Jumbled stuff at the top that you have to read and decipher.”</blockquote><blockquote>“Black bar is kinda… doesn’t look like it belongs, all else is white, grey, orange.”</blockquote><p>And the <strong>new version</strong>:</p><blockquote><em>“On the current nav I didn’t know what the inbox / rep icons were, on the new one I know what every button will do.”</em></blockquote><blockquote><em>“I know I can search, I know I can go to Jobs.”</em></blockquote><blockquote><em>“Much more modern, this one.”</em></blockquote><blockquote><em>“I like the old black bar, but I like that I know what I’m getting myself into on the new one.”</em></blockquote><blockquote><em>“A lot less noise, more signal.”</em></blockquote><blockquote><em>“Cleaner, more organized. Instead of jumbled stuff at top you have to read and decipher you can go to this.”</em></blockquote><blockquote><em>“More standardized position that you’re used to on other sites.”</em></blockquote><h3>Project Definition</h3><p>At this point there was enough info to make the top navigation redesign an actual project. The nav is an area of the site that touches so many different use cases, user types, and metrics; it was important to tightly scope the project and clearly define the goals in advance in order to ship quickly. To mitigate scope creep, feature parity to the current navigation was the defined scope (with a few exceptions).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E06QK1TsUdfTe45dE9oL3Q.png" /><figcaption>(Remember Windows’ Hot Dog theme?)</figcaption></figure><p><strong>Primary goals</strong></p><ul><li>Present all the tools we provide for developers in a way that’s consistent with them actually discovering them</li><li>Increase traffic to Jobs and Documentation</li><li>More intuitive, updated visual design</li><li>Increase the number of users who sign up and gain access to more site features</li></ul><p><strong>Secondary goals</strong></p><ul><li>Increase in notifications acknowledged</li><li>Increase or no decline in searches</li><li>No decline in questions asked</li><li>And a handful of other important and boring metrics that we simply didn’t want to screw up</li></ul><p>The progressive rollout plan to measure success had the following objectives:</p><ul><li><strong>Usability tests</strong> on clickable prototype with 6 additional users to catch any major UX and functionality issues and gather qualitative insights about the new design</li><li><strong>A/B test with 5% of anonymous users</strong> to measure usage data</li><li><strong>A/B test with 10% of registered users</strong> with less than 500 reputation to measure usage data</li><li><strong>Opt-in for all Stack Overflow employees</strong></li><li><strong>Opt-in for all users</strong> for Meta feedback and for debugging</li></ul><p>Our findings from each…</p><h3>Usability Tests</h3><p>These tests were conducted in 1–1 recorded hangouts with 6 users who ranged from having low to high reputation.</p><p>While a few participants struggled with identifying two of the icons (which were updated mid-testing), all participants successfully completed all tasks, and all participants preferred the new design over the current.</p><blockquote>“Looks really, really good. By far I like the new one — in the current one, you don’t notice the navigation at all, only the top bar. The (sub) tabs catch my eye before the current navigation.”</blockquote><blockquote>“In the old, it is weird to me that the two bars exist separately. This one feels more natural.”</blockquote><blockquote>“The new one is cleaner. Less wasted space. Things are more compact on the new one and account info is better grouped. Tabs across the top is preferable because a lot of sites have a similar flow. …much prefer the new one.”</blockquote><h3>A/B Test with 5% of Anonymous Visitors</h3><p>This test ran from 2016–12–01 to 2017–01–19 for about 2 million users in each A/B group. Anonymous visitors account for about 97% of all page views but only 61% of the current navigation clicks.</p><ul><li>Signups increased by 7%</li><li>Clicks to Questions increased by 163%</li><li>Clicks to Jobs increased by 160%</li><li>Clicks to Documentation increased by 229%</li><li>Clicks to Tags increased by 113%</li><li>Clicks to Users increased by 178%</li><li>Clicks to Ask Question increased by 33%</li><li>Searches decreased by 13%*</li></ul><p>*Adjustments to the design between the anonymous test and the registered user test were made that resolved this issue and actually improved the number of searches in the next test.</p><p>While some dropoff often happens after launch due to novelty effect, these increases were large enough to make us think that a good portion of the increases would be sustained after launch. Regardless, we’ll continue to measure and monitor the performance of the new top nav.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YICAnl8xS5_0iRrVvVNpg.png" /><figcaption>Our handmade tracker for A/B testing funnels.</figcaption></figure><h3>A/B Test with 10% of Registered Users with Less than 500 Rep</h3><p>This test ran from 2017–01–18 to 2017–01–30 for about 100k users in each A/B group . Registered user account for about 3% of all page views but about 44% of the current top navigation clicks.</p><ul><li>Inboxes shown increased by 45%</li><li>Achievements shown increased by 11%</li><li>Clicks to Questions increased by 51%</li><li>Clicks to Jobs increased by 99%</li><li>Clicks to Documentation increased by 113%</li><li>Clicks to Tags increased by 32%</li><li>Clicks to Users increased by 82%</li><li>Clicks to Ask Question remained the same</li><li>Searches increased by 8%</li></ul><h3>Opt-in for Stack Overflow Employees</h3><p>This phase began Tuesday, February 1. About 100 Stack Overflow employees opted in to test the new top nav.</p><h3>Opt-in for All Users</h3><p>This phase began 2017–02–07 to 2017–02–14. Around 1600 users opted in.</p><p>Feedback from the Meta community has been extremely helpful. Thank you to everyone who participated! A number of bugs were fixed during this period, some feature requests were implemented and others considered or planned.</p><h3>Next Steps</h3><p>There’s a running list of ideas we’d like to try in the near future. We plan on iterating upon the design and functionality of our new top nav in a series of A/B tests. There are also early-phase explorations into how this might roll out to international and other Stack Exchange community sites.</p><p>The design team is working on <a href="https://medium.com/stack-overflow-design/building-a-design-system-21647dc1ae74#.qnxxi7mcl">a cohesive design language</a> in order to create consistent experiences across all our product areas. Some of these changes have already rolled out, and more are coming in the near future. Special thanks to <a href="http://twitter.com/ludwiczakpawel">Paweł Ludwiczak</a>’s and <a href="https://twitter.com/OdedCoster">Oded Coster</a>’s hard work designing and implementing the new top navigation.</p><p>As always, we appreciate your feedback. If you have a bug or feature request — post it on <a href="http://meta.stackoverflow.com/">Meta</a>.</p><p>This post was originally published on the <a href="http://stackoverflow.blog/2017/02/Why-Stack-Overflow-Redesigned-the-Top-Navigation/?cb=1">Stack Overflow blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77b7f968bff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stack-overflow-design/how-stack-overflow-redesigned-our-top-navigation-f77b7f968bff">How Stack Overflow Redesigned our Top Navigation</a> was originally published in <a href="https://medium.com/stack-overflow-design">Stack Overflow Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Benefits of Side Projects]]></title>
            <link>https://medium.com/stack-overflow-design/surmounting-a-fixed-mentality-as-a-designer-5e790aa4b78b?source=rss-d2e4f2a00968------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e790aa4b78b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Kurtis Beavers]]></dc:creator>
            <pubDate>Fri, 01 Jul 2016 19:51:36 GMT</pubDate>
            <atom:updated>2017-02-02T20:11:56.924Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>TLDR: Side projects and design exercises are an antidote to a <a href="https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/">fixed mentality</a>. They take your brain on a road trip, stop to see the world’s largest ball of earwax, and are really in a hurry to get nowhere, but eventually do.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1hQG10tLn-bEmdd0FRZCQ.png" /></figure><p>Even meaningful design work you love occasionally becomes… just work. Product design in an app that’s alive and loved can feel like remodeling a home while wearing a straightjacket. Instead of a green field full of possibility, creativity entangles with user needs, resourcing, business goals, fear, and too much caffeine. There’s a danger of preemptively squelching ideas before having a chance to fully explore or externalize them. This isn’t a state of mind you want to remain in for great lengths else you lose tenacity and develop a censored imagination. As a designer, it’s important to continually find ways stimulate creative thinking.</p><p>Recently, <a href="https://medium.com/@stephane_m_">Stéphane Martin</a> organized an exercise for the product design team that went something like this: “Imagine that there were no boundaries, no stakeholders, no problem definitions, and no code limitations; what would you design for <em>X</em>?” (But in a French accent of course.) We called it our 5% Fun exercise.</p><p>Each designer stole a few hours throughout the week to work on the project. We met back up in our secret personhood at the end of the week to discuss our ‘concept cars’. Many of us had solved the same problems even though they were never clearly defined, and the approaches were unique.</p><p>Work became play, and there were a lot of good ideas generated in a relatively short amount of time. We now had an even deeper understanding of what the problems were. The discussion focused on what was innovative or interesting and was quite invigorating.</p><p>In fact, the team was so excited that the conversation quickly began shifting toward “What if we actually made a version of this happen?” As we crossed the threshold from our world of fluffy clouds and rainbows back into reality, something interesting happened — stress and disagreements began to form around the team.</p><p>Partially because this didn’t match our product development structure and there were too many owners and none of them were from any of the other essential disciplines, but a bigger part of it was because our regular limitations and self-imposed boundaries resurfaced. There are few, rare times when an iterative development process merits a green grass approach, and really these types of designs are loaded — what is seen can never be unseen. Even a good idea can be a disruption if resourcing, roadmaps, and strategy don’t align. Sometimes “We ain’t got no time for that right now.” is an appropriate reaction.</p><p>So are these potentially fruitless pursuits worth it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTB3NwRwN9vPH4mUUrp7HA.png" /></figure><p>Heck yeah, they are.</p><p>Children use play to explore ideas about why and how things happen in the world around them. It’s a safe place without the weight of consequence where ideas are pliable. This is what the team was doing with the 5% Fun exercise.</p><h3>stefan klocek on Twitter</h3><p>Getting over the belief that you&#39;ve got to be right, frees you up to experiment, explore and riff; all methods to real insight</p><p>I can’t think of a side project where I didn’t learn a new skill or a new approach to solving a problem that wasn’t eventually applicable to another situation. As a matter of fact, I’ve got a hard drive full of unfinished projects that have contributed something new and good to a later project that actually shipped even though the play never saw the light of day. These are mental seeds full of potential.</p><p>A key strength of a good designer is her/his ability to take ideas from multiple inputs and realize them as something new and relevant. Creative problem solving builds intuition, rejuvenates a growth mindset, and generates a strength to continually consider the improbable possibilities.</p><p>Beagles need to run, dancers gotta dance, and designers have to live in a state of perpetual discovery. Plus imagine the alternative — getting into your car, driving directly to your destination, and never noticing the world around you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e790aa4b78b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stack-overflow-design/surmounting-a-fixed-mentality-as-a-designer-5e790aa4b78b">The Benefits of Side Projects</a> was originally published in <a href="https://medium.com/stack-overflow-design">Stack Overflow Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Etiquette of Dance]]></title>
            <link>https://medium.com/stack-overflow-design/the-etiquette-of-dace-ec353d9f8417?source=rss-d2e4f2a00968------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec353d9f8417</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kurtis Beavers]]></dc:creator>
            <pubDate>Wed, 15 Apr 2015 04:42:49 GMT</pubDate>
            <atom:updated>2015-04-15T15:47:50.527Z</atom:updated>
            <content:encoded><![CDATA[<h4>Fostering a culture of creative collaboration</h4><p>Back at a time when boys and the girls still polarized on the playground, there was a day when the teachers pulled us into the gymnasium and pushed us together for an experience that was so repellant and exciting that memories of the incident still resonate.</p><p>While we were all secretly praying to be paired with the cute one, the teachers proceeded to lecture us about <a href="http://www.cheek2cheek.net/2012/etiquette2.html">the etiquette of dance</a>. It was the first time I heard that word <em>etiquette</em>, and I viscerally hated it. At the time the word translated simply: “do the exact opposite of what you feel like doing right now.” There were a million other things a 10-year-old would rather be doing than holding the sweaty hands of our random partners as we fumbled across the dance court. But still we had no choice. We suffered through it, and we were all awful.</p><p>Over the years these rules have grown on me as I’ve worked with good and bad ‘dance’ partners in the creative field (and I have been a good and sometimes bad partner). They grow on me because a culture of collaboration is one of the most valuable assets of any creative team. And intangible things like positive team momentum have a tangible impact on the final product.</p><p>So here’s how the rules began and an adaptation to creative collaboration:</p><blockquote>Never blame your partner for anything that may happen on the dance floor. Not if you want him/her to dance with you again.</blockquote><p>Don’t throw your coworkers under the bus. Just don’t — even if they dance worse than <a href="http://giphy.com/gifs/YqaEhVPNe0W4w">left shark</a>. Andrew Glasnow once wrote, “A good leader takes more than their fair share of the blame and gives more than their share of the credit.” That quote equally applies to a good teammate.</p><blockquote>A request for a dance must be accepted under almost all circumstances. If you decline a dance, you yourself cannot dance until the end of that song.</blockquote><p>Don’t intentionally exclude others from conversations or projects. Sideways conversations are the kryptonite to a healthy, transparent culture. If you are excluding a teammate just because it’s easier without them, then you might be working around a problem that will exist again and again until it is directly addressed. In the end, flexibility, understanding, and appreciating others’ differences wins out over being right, smart, or just loud.</p><blockquote>No unsolicited teaching on the dance floor! There is a good chance this will make your partner feel small and humiliated. Not exactly a great way of encouraging him/her, or others, to dance with you.</blockquote><p>Sharing what you are learning or have learned is different from correcting a teammate. Correction infers an air of superiority. There’s a time and place for teaching — The whiteboard room is not one of them. In front of other teammates is not either. If you hear the words “in my experience” coming out of your mouth, you might be doing it wrong.</p><blockquote>Do not monopolize a partner on the dance floor. Dancers are polite and rarely say no to a dance, but this is no carte blanche to impose on their kindness. Dance with everyone, and let everyone dance.</blockquote><p>Don’t bogart the conversation. If you are waiting for the other person to finish talking so that you can say the next brilliant thing but not actually hearing their ideas, maybe sit out a round or two. Good follow-up questions and listening skills are some of the greatest tools in collaboration.</p><blockquote>On the floor, be considerate of the other couples. Exercise good floorcraft; do not cut other couples off; no aerials or choreographed steps on the dance floor.</blockquote><p>Be considerate of other teammates’ thoughts, ideas, and objectives. Giving feedback is hard. Receiving feedback is hard. It can feel like getting the gift of a self-help book on your birthday. If you are receiving feedback or differing ideas, remember you don’t have to implement it all, but you should at the very least give it an honest consideration. Otherwise it sends a message to the other person that you don’t value their ideas or opinions. If you are giving feedback, be sure it’s logical, actionable, and helpful. Comments like “I just don’t like it.” are the worst because they’re impossible to translate into specific action.</p><p>Oh, and celebrate your teammates’ victories — even if you’re not on the project.</p><p>To be a great dancer don’t aspire to be a great <em>dancer</em>, but aspire to be a great <em>dance partner</em>.</p><p>And it always helps to remember that we all have days that we’re still sweaty-palmed children stumbling across the gym floor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec353d9f8417" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stack-overflow-design/the-etiquette-of-dace-ec353d9f8417">The Etiquette of Dance</a> was originally published in <a href="https://medium.com/stack-overflow-design">Stack Overflow Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The thing about being a designer…]]></title>
            <link>https://medium.com/@kjbeavers/the-thing-about-being-a-designer-68aa7a492a52?source=rss-d2e4f2a00968------2</link>
            <guid isPermaLink="false">https://medium.com/p/68aa7a492a52</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[designer]]></category>
            <dc:creator><![CDATA[Kurtis Beavers]]></dc:creator>
            <pubDate>Fri, 03 Apr 2015 16:56:43 GMT</pubDate>
            <atom:updated>2015-04-03T18:45:05.356Z</atom:updated>
            <content:encoded><![CDATA[<p>Designers are often stereotyped as being oversensitive. As with any stereotype, that may by a gross oversimplification.</p><p>The thing about the visual language is that everyone and their odd nephew knows it. It’s the first dialect we all learn. Before we speak, we see. And over time, we all gain an opinion regarding aesthetics. That gives the entire world a free pass to express their opinion when looking at something. Design is different from other fields. For instance, we may not all feel qualified to critique a complex mathematical formula (unless that’s your thing) because mathematics is not a language that is innately learned by most. But when designers put something out there, we sometimes feel assaulted by a barrage of opinions from those outside the profession. Some opinions are valid — some aren’t. Either way, they flow freely. And depending on the day, they can make us feel like we need to validate our very existence.</p><p>Paul Rand said, “The public is more familiar with bad design than good design. It is, in effect, conditioned to prefer bad design, because that is what it lives with. The new becomes threatening, the old reassuring.” This can put us on the defense.</p><p>We designers probably need to grow thicker skin. We’ll try. But non-designers maybe could learn to extend a little trust and turn their honesty settings to 90%? Because 100% isn’t always the most diplomatic solution and doesn’t always help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68aa7a492a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>