<?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 Joe Pemberton on Medium]]></title>
        <description><![CDATA[Stories by Joe Pemberton on Medium]]></description>
        <link>https://medium.com/@joepemberton?source=rss-2b9738356858------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qPRMHIVTxc48S6R2QMJZ5g.jpeg</url>
            <title>Stories by Joe Pemberton on Medium</title>
            <link>https://medium.com/@joepemberton?source=rss-2b9738356858------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:03:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joepemberton/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[Found type]]></title>
            <link>https://medium.com/series/found-type-f1d9506516a?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1d9506516a</guid>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Sat, 12 Jan 2019 05:19:51 GMT</pubDate>
            <atom:updated>2019-01-12T14:01:11.148Z</atom:updated>
            <content:encoded><![CDATA[<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1d9506516a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design + Tech at CES 2019]]></title>
            <link>https://medium.com/series/apple-never-goes-to-ces-but-trolls-them-anyway-4000abad9dcf?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/4000abad9dcf</guid>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Fri, 11 Jan 2019 05:16:30 GMT</pubDate>
            <atom:updated>2019-01-12T04:43:45.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-lWJPWfYG2PkUc2esCjuA.jpeg" /><figcaption>Google had the biggest footprint at the show.</figcaption></figure><p>Overheard at <a href="https://twitter.com/hashtag/CES2019?src=hash">#CES2019</a> on Trump’s trade war with China</p><h3>“We build it in China, and ship it to a company in Taiwan and then we import it with a sister company in California. Just to get around the trade war.”</h3><p>My observation is innovation is like water, it finds the fastest path.</p><p>Overheard at <a href="https://twitter.com/hashtag/ces2019?src=hash">#CES2019</a> on the Internet of Things</p><h3>“Internet of THING is very easy. Internet of THINGS is exponentially harder.”</h3><p>— <a href="https://twitter.com/FredYentz">@FredYentz</a>, Telit, IoT platform provider</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2XxfXR8fxII6m0qI_mAEaw.jpeg" /><figcaption>After sharing a table and making a new acquaintance, this guy from Seoul says, can I take a picture with you? It’s for memories.</figcaption></figure><p>Overheard at <a href="https://twitter.com/hashtag/CES2019?src=hash">#CES2019</a> on the Internet of Things</p><h3>“Where do you put the compute?”</h3><p>Explaining that IoT companies have to decide whether computations should happen on the IoT Devices (which use precious resources), on a smartphone (which has plenty of computational power, but not 100% present when you want it), or in the cloud (which opens added security risks).</p><p>— <a href="https://twitter.com/SMC_on_IoT">Sarah Cooper</a>, Amazon Web Services for IoT platforms</p><p><a href="https://twitter.com/hashtag/IoT?src=hash">#IoT</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXfDtz__9Yc4hoKl96ldAA.jpeg" /><figcaption>Smart herb garden, “Ava Byte.” Each plant is chipped and scanned when you insert it. It then gets light cycles, and watered according to moisture sensors in the soil to match it’s unique needs at it grows.</figcaption></figure><h3>The future has servant robots that look like children? No thanks.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4000abad9dcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The user experience serenity prayer]]></title>
            <link>https://uxdesign.cc/the-ux-serenity-prayer-fce3e6d49461?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/fce3e6d49461</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[lettering]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Sat, 10 Nov 2018 04:22:45 GMT</pubDate>
            <atom:updated>2020-10-16T16:40:12.374Z</atom:updated>
            <content:encoded><![CDATA[<h4>Staying focused on what matters takes constant vigilance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j7EgKh0o8Z93dJBqlqX3PQ.png" /><figcaption>Illustration ©<a href="https://medium.com/u/2b9738356858">Joe Pemberton</a></figcaption></figure><h4>God grant me the focus to ignore distracting buzzwords</h4><p>Sprinkling your work with buzzwords can make it sound like you have a strategy, but you just might be jumping on the next crypto-, AI-, wearable- bandwagon without a real plan. Strategy is just a fancy word for plan. Making it <em>wearable</em> or <em>dark mode</em>, or <em>mobile</em> are fine attributes, but don’t mistake that for a plan.</p><h4>Courage to focus on the real issues</h4><p>Strategy requires a well defined problem — a problem you’re going to work on until you get it right.</p><h4>And the wisdom to know the difference</h4><p>Because strategy requires the discipline to decide what you’re <em>not</em> going to do.</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=fce3e6d49461" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-ux-serenity-prayer-fce3e6d49461">The user experience serenity prayer</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[Empathy in UX: Why I put an iPod on my team’s desk]]></title>
            <link>https://uxdesign.cc/empathy-in-ux-why-i-put-an-ipod-on-my-designers-desks-feb0bcf55a51?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/feb0bcf55a51</guid>
            <category><![CDATA[mobile-web]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 23:41:27 GMT</pubDate>
            <atom:updated>2018-11-13T04:17:15.487Z</atom:updated>
            <content:encoded><![CDATA[<h4>When designing with empathy we need constant reminders</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qd7l-x0mz6ygq0GcAMybcQ.png" /><figcaption>Photo illustration by <a href="https://medium.com/u/2b9738356858">Joe Pemberton</a></figcaption></figure><p>Why iPod Touch? Because, most people who use our site have older phones. The small screen and slower processor of the iPod is an inexpensive way for the team to experience our product the way our users do.</p><p>I’m not prescribing this device for your team. You need to get your own viewport and OS analytics. The device(s) you should you use on your team should be a proxy for your audience.</p><h3>We already know we’re not the target user</h3><p>We’ve got a fat internet connection, a 20 inch monitor, an iPhone X (or Galaxy S7) and sometimes iPads. Meanwhile our users have phones that are 2 or 3 years old.</p><h4>Visualize your UX designer bubble:</h4><blockquote>You are taking a tour of DisneyWorld in a self-driving, air conditioned Audi A6 with a chilled Dole Whip in your hand.</blockquote><blockquote>While your users are standing on 106 degree Orlando blacktop, eating an $8 churro, while they wait for a crying kid to get off the Dumbo ride.</blockquote><p>Make design decisions from the vantage point of the actual experience, not a protected bubble.</p><h3>It’s a physical reminder</h3><p>On the site we’re working on, most users have an older Android (Samsung Galaxy S3, S4) or if they’re on iPhone it’s most likely 3 generations old (iPhone 4, 5, or SE). Small.</p><p>Instead of looking at our designs on all those devices we use the iPod as a proxy. It’s got a 320 x 568 screen (the retina pixel density is double that, but physically it’s just bigger than a credit card). We use the actual devices on Android for QA, but here I’m talking about referencing screens during design, long before it’s built and deployed in a QA environment. Don’t wait until QA to fix issues with screen size, that’s way too late.</p><h3>It’s a mental reminder</h3><p>With that small phone in our hand — a device we wouldn’t choose for ourself — we remember who we’re designing for. What are their motivations? Why are they on your site/service/product? Is this comfortable to read/watch/use? Is it good?</p><blockquote>It’s like walking in our users’ shoes a little bit. Using a device you wouldn’t normally use to review our work is mental, and it can be a daily reminder who we work for.</blockquote><h4>Tips for responsive design</h4><h3>1. Look at your viewport data twice a year: January and July</h3><p>You probably have a report showing the most common device sizes (screen sizes, or viewports) your users have when visiting your site. If you don’t then get it done in January and again in June.</p><blockquote>But why January and July? I’ve seen a bump in new devices coming into our analytics after retailers push new devices on Christmas and again in July after their “Dads and Grads” sales.</blockquote><p>You don’t need to look at this metric monthly, twice a year is enough because people refresh their mobile devices every 1.5 years in the US. If you’re watching g your metrics you can see the viewports after the holidays.</p><h3>2. It’s not enough to shrink down your desktop browser window</h3><p>You’ve got to view it in Safari or Chrome, on the actual OS. Try it: compare your desktop browser, shrunk to it’s smallest size, with an actual mobile device, at your target size, and you’ll realize how far off it is.</p><h4>Hold down that clap button, would you? Now go design for good.</h4><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=feb0bcf55a51" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/empathy-in-ux-why-i-put-an-ipod-on-my-designers-desks-feb0bcf55a51">Empathy in UX: Why I put an iPod on my team’s desk</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[Creative directors are wolves: A tip for your in-house team]]></title>
            <link>https://medium.com/@joepemberton/creative-directors-are-wolves-97f9baea4dd9?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/97f9baea4dd9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[creative-director]]></category>
            <category><![CDATA[agency]]></category>
            <category><![CDATA[creative-process]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Sun, 10 Sep 2017 01:32:06 GMT</pubDate>
            <atom:updated>2019-01-19T02:17:36.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*WdJLajvuu4xkLo7DdIxlyw@2x.jpeg" /><figcaption>Wolf, by Francesco Cesqo Stefanini, Noun Project</figcaption></figure><h4>Observations on the necessity of adding Creative Directors to your organization</h4><p>If you’re at an agency, you might understand this because it’s the norm. But if you work at a place where Creative Directors are unknown creatures, this article is for you.</p><p>Below is a mini documentary (less than 5 minutes long). It’s about <em>trophic cascades — y</em>eah, that’s a new vocab word for me too — about a massive cascading effect on the ecosystem in Yellowstone National Park when wolves were reintroduced after decades of absence.</p><p>At worst creative directors are feared. At best they’re valued and empowered. Most often they’re <a href="https://medium.com/@joepemberton/5-things-your-creative-director-shouldnt-do-294835278106?source=linkShare-2b9738356858-1505042381">just misunderstood by the teams they serve</a> or they are nerfed by management who don’t understand the balancing effect creative directors can have in an organization. <a href="https://medium.com/@joepemberton/5-things-your-creative-director-shouldnt-do-294835278106?source=linkShare-2b9738356858-1505042381">They get marginalized</a>.</p><h4>Things I’ve heard over the years…</h4><blockquote>“We need a creative director badly, but our management hasn’t allocated enough budget to hire one.” — Marketing director</blockquote><blockquote>“I don’t want a creative director. I’m the keeper of the creative vision. This is my art and a Creative Director just gets in the way.” — Film producer</blockquote><blockquote>“My client likes my work, why should I have a creative director review it? He will just make me change it and that makes us deliver late.” — Designer</blockquote><blockquote>“I’m fine with having a creative director on this, but I can’t pay for it out of my project budget. Does he have to be billable?” — Product manager</blockquote><blockquote>“We don’t need a creative director on this, the client knows exactly what they want.” — Project manager</blockquote><p>Watch the 5 minute video, keep an open mind, and keep reading.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fysa5OBhXz-Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dysa5OBhXz-Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fysa5OBhXz-Q%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1cf3e737fc338627f967ed87af869bde/href">https://medium.com/media/1cf3e737fc338627f967ed87af869bde/href</a></iframe><h3><strong>So what?</strong></h3><h4>1</h4><p>Creative directors, at their best, motivate and inspire <strong>creative, production, a</strong>nd <strong>UX teams.</strong> These teams are talented, but without the presence of a leader empowered to push them they might just hang out in the valleys by the watering hole. The work gets better when you add hustle, revisions, and rethinking.</p><h4>2</h4><p>Creative directors, at their best, balance out <strong>product managers</strong>. Product managers know a CD is going to hold to a higher objective: meeting user’s needs, not just shipping products that meet business objectives. This isn’t about ego. This is about striking the balance between user needs and business needs so value is generated when they meet in the middle.</p><h4>3</h4><p>Creative directors require <strong>analysts</strong> to turn raw data into actionable insights. A CD will not be satisfied with vanity metrics, but will be pushing analyst teams to understand the <em>why</em> behind the data.</p><p><em>Add claps 👏 for every person that should read this post. Read my post, </em><a href="https://medium.com/@joepemberton/5-things-your-creative-director-shouldnt-do-294835278106?source=linkShare-2b9738356858-1505042381"><em>5 Things your Creative Director shouldn’t be doing</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97f9baea4dd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“You’re holding it wrong” Vertical video is not a passing fad]]></title>
            <link>https://medium.com/@joepemberton/youre-holding-it-wrong-vertical-video-is-not-a-passing-fad-fda9225828a7?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda9225828a7</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[videos]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Thu, 27 Apr 2017 18:10:29 GMT</pubDate>
            <atom:updated>2019-01-19T02:18:32.000Z</atom:updated>
            <content:encoded><![CDATA[<p>It doesn’t matter that I hate when I see people watching video while holding their phone vertically. To me, it’s worse than finding the toilet paper roll facing the wrong way. But people vote with their behavior, and I’m losing that one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAXa0DNFg65f9ovUxIp3HQ.png" /><figcaption>Cinemas, TVs. The orientation matches our field of vision because human eyes are side by side, not stacked vertically. (Image: <a href="https://unsplash.com/@cant89">Davide Cantelli, Unsplash</a>.)</figcaption></figure><p>Recently, while trying to evaluate our social media marketing channels, our team (thanks <a href="https://twitter.com/seanmj">Sean Johnson</a>) pulled together some research. We wanted to know whether our videos would perform better in vertical (portrait), square, or horizontal (landscape). What we found confirmed our fear. The industry has data that videos in social media get higher engagement rates with square and vertical video on mobile where mobile comprises the majority of the audience.</p><h3>What’s the data say?</h3><blockquote>AdWeek: “Cropped clips increase completion rates by 67%”</blockquote><p>Source: AdWeek: <a href="http://www.adweek.com/digital/instagrams-box-shaped-videos-are-influencing-facebook-marketers-172490/">Instagram’s Box-shaped Videos Are Influencing Facebook Marketers</a></p><blockquote>Adweek: “3X better CPMs”</blockquote><p>Source: AdWeek, “<a href="http://www.adweek.com/digital/facebook-vertical-video-ads-just-went-live-and-are-producing-great-results-173276/">Facebook Vertical Video Ads Just Went Live and Are Producing Great Results</a>”</p><p>Besides that, with Snapchat and Instagram stories, vertical video is simply required … there’s no other option. And though you can now post “traditional” aspect ratio videos on Instagram, square is still the coin of the realm.</p><p>Even old school platforms like <a href="http://newsroom.fb.com/news/2017/02/new-ways-to-watch-facebook-video/">Facebook are jumping on the vertical video</a> bandwagon, introducing formal support just weeks ago.</p><h3>But why does it work? Two reasons.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h9fBuD9k6mPFbPlPMjqGQQ.png" /><figcaption>When a person holds their phone upright, the horizon stays in the same orientation (duh), but now the restricted field of view pulls the subject closer, and creates a more intimate viewing experience. (Image: <a href="https://unsplash.com/@anniespratt">Annie Spratt, Unsplash</a>)</figcaption></figure><p>First, when a person holds their phone upright, the horizon stays in the same orientation (duh), but now the restricted field of view pulls the subject closer, and creates a more intimate viewing experience. The social networks have embraced this sense of intimacy. Whether intentionally or not, SnapChat, Periscope, Meerkat, Instagram Stories, Twitter Events, Facebook Live’s vertical orientation have embraced this more intimate view.</p><p>Second, when people use technology we, as designers, or creators, should know better than to prescribe how to use or consume our stuff. If most people engage your interface a certain way, you can try to teach them, or you can embrace their behavior, and optimize your experience to match.</p><p>I don’t expect to ever enter a movie theater with a vertical screen, or to pivot my television vertically on my wall, but in social media, the format works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda9225828a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX pro tip: How to reboot a stalled project]]></title>
            <link>https://uxdesign.cc/when-a-priority-is-not-a-priority-18da1dbe1017?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/18da1dbe1017</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Thu, 01 Sep 2016 14:47:28 GMT</pubDate>
            <atom:updated>2018-11-14T22:15:20.772Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s a familiar scenario. A client has a hot project with no budget. A UX strategy skill set can help.</h4><h4><strong>A long time ago—when words mattered—priority meant, “before everything else.”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Eq35QYI7OVMc-ZeXBQCpEg.png" /></figure><h4><strong>Nowadays words are cheap, and we have priorities, plural. That’s an oxymoron if you’re going by the actual meaning of prior.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IkTDR3ZP4Z3tpF1fL6mGw.png" /><figcaption>Illustrations by ©<a href="https://medium.com/u/2b9738356858">Joe Pemberton</a></figcaption></figure><h3>The scenario is pretty common</h3><p><strong><em>Client</em></strong><em>:</em> “Here’s what we’ve got to do. It’s a big deal. The executives are on board and this really needs to get done.”</p><p><strong><em>UX Team</em></strong><em>:</em> “Great. We really think we can help and this won’t be difficult. What budget have you planned for this?”</p><p><strong><em>Client</em></strong><em>:</em> “That cost is a problem because there’s no budget. We just need to be creative to solve this.”</p><p>Sound familiar? It happens: the idea is solid, the need is apparent, the manager got buy-off from an executive. But when there’s no budget allocated it tells you that this manager’s priority isn’t really the organization’s priority.</p><h3><strong>Here’s how to turn it into an opportunity</strong></h3><h4>1. If it’s a great idea you’ve got to find ways to test and validate it</h4><p>Devise ways to use general testing budget to split test (A/B test) some of the ideas using existing products/sites to give you stronger data to support the concept.</p><h4>2. Help your stakeholder sell it</h4><p>Turn the tests into a proposal. Help that manager communicate the opportunity by showing what the solution <em>might</em> look like using rough prototypes, or prototypes. This can go a long way to building trust with stakeholders.</p><h3>Pick your battles. You can’t burn time on every pet project, but when you do you will elevate the way your organization sees the UX team</h3><p>In the process of helping your client this way, you will be seen as a partner to help visualize and solve problems, rather than a production team who is there to execute. Win, win.</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=18da1dbe1017" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/when-a-priority-is-not-a-priority-18da1dbe1017">UX pro tip: How to reboot a stalled project</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[Why Instagram shouldn’t make their brand mark into an interface icon]]></title>
            <link>https://medium.com/@joepemberton/instagram-did-the-right-thing-by-not-making-their-brand-mark-into-a-ui-icon-2e87c57604d5?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e87c57604d5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Sat, 21 May 2016 21:22:36 GMT</pubDate>
            <atom:updated>2019-01-19T02:19:18.805Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BL2PE29d6VlxT5uvzVTI_Q.png" /></figure><p>UI designer Bryan Mamaril has a <a href="https://medium.com/@bmamaril/an-ocd-critique-of-the-new-instagram-logo-ui-2c8f9917c651#.ge92s4w3w">thoughtful critique of Instagram’s new UI icons</a>, but I wanted to respond to his assertion that Instagram should have used their brand mark as a UI icon. Instagram didn’t, and for good reason.</p><h4>1- Icons and Meaning</h4><p>Icons are valuable because they imbue meaning, often more quickly than words can (that’s way obvious, but stick with me), and in both branding and UI, meaning is everything. The camera icon in Instagram has the job of conveying <em>access the camera</em> and that should be different from the job of the Instagram brand, which has a much bigger meaning. Something like <em>find great images and share my own.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/208/1*pucJF1yX7XD2CJTPTVxHFQ.png" /><figcaption>Fiagure 1. The brand mark should have a singular meaning: roughly, find great images and share my own</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/208/1*rzVGzCGvn27vjBsRquonGg.png" /><figcaption>Figure 2. The camera icon should have a singular meaning: <em>access the camera</em></figcaption></figure><h4>2- Brand protection</h4><p>Instagram may be protecting the brand mark (a camera) from becoming pedestrian the way the Kleenex® brand became pedestrian and now can’t protect the mis-use of the word kleenex. It seems valuable for Instagram to protect that glyph from becoming other camera apps’ go-to app icon, or another apps’ interface icon for <em>snap a picture</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e87c57604d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Friends at Sketch,]]></title>
            <link>https://medium.com/@joepemberton/friends-at-sketchapp-31d2b475de77?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/31d2b475de77</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Wed, 02 Dec 2015 17:58:39 GMT</pubDate>
            <atom:updated>2015-12-03T00:24:39.356Z</atom:updated>
            <content:encoded><![CDATA[<h4>First off, congratulations on your massive success. You’ve made Adobe wake up to the reality that their tools are 10 years behind. (Okay 5 years because I’m being nice and I like Adobe.)</h4><p>But the poor support for typography holds me back from a full-throated endorsement of Sketch <em>as an Adobe Illustrator replacement</em>. It’s fantastic for native app UI frameworks, but it’s not good for holistic layout of finished app views/layouts, or web views/layouts. (Carefully avoiding the word pages, because <em>eww</em>).</p><p><strong><em>Web = Content + UI</em></strong></p><p><strong><em>Apps = Content + UI</em></strong></p><p>I’ll explain. Sketch is good for styling UI elements, such as menus, headers, buttons, and controls. But Sketch struggles at defining the styling of in-page content.</p><p>If Sketch were to just enable good typographic control — meaning setting multiple type styles within text blocks — instead of just styling an entire text block I could fully endorse it. It’s as if the makers of Sketch ignore how content is displayed in an app, instead, just focusing on the shell/framework of the app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31d2b475de77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Not Created Here Syndrome]]></title>
            <link>https://medium.com/@joepemberton/not-created-here-syndrome-7eb98a28576f?source=rss-2b9738356858------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb98a28576f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creative]]></category>
            <dc:creator><![CDATA[Joe Pemberton]]></dc:creator>
            <pubDate>Tue, 11 Aug 2015 16:00:13 GMT</pubDate>
            <atom:updated>2016-08-23T17:29:55.954Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>The inability to recognize or appreciate the value of another team’s work.</blockquote><p>Developers and engineers may have heard of “not invented here” (NIH) syndrome, which is well documented. From <a href="https://www.princeton.edu/~achaney/tmve/wiki100k/docs/Not_Invented_Here.html">Princeton.edu</a>:</p><blockquote><strong><em>Not Invented Here (</em>NIH) </strong>is a term used to describe persistent <a href="http://www.wikipedia.org/wiki/Social">social</a>, <a href="http://www.wikipedia.org/wiki/Corporate_culture">corporate</a> or institutional culture that avoids using or buying already existing products, <a href="http://www.wikipedia.org/wiki/Research">research</a> or knowledge because of their external origins. It is normally used in a <a href="http://www.wikipedia.org/wiki/Pejorative">pejorative</a> sense…</blockquote><p>When I say other teams I’m not just talking about outside design agencies, I would include other teams or departments in your own organization. I get annoyed when designers or writers or photographers can never seem to see the good in other teams’ work.</p><p>The best way to triage <em>Not Created Here</em> is humility and listening, try to understand their strategy. If you’re looking at some other teams’ work without understanding their strategy or their constraints you’re only critiquing <em>style</em>, not the <em>substance</em> of their work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb98a28576f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>