<?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 Joshua Graves on Medium]]></title>
        <description><![CDATA[Stories by Joshua Graves on Medium]]></description>
        <link>https://medium.com/@itsjoshuagraves?source=rss-bc1a780bd22b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NsdodmSIAMScHsXFd7JGWQ.jpeg</url>
            <title>Stories by Joshua Graves on Medium</title>
            <link>https://medium.com/@itsjoshuagraves?source=rss-bc1a780bd22b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:54:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itsjoshuagraves/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[What we look for in a product designer’s portfolio]]></title>
            <link>https://medium.com/thisisartium/what-we-look-for-in-a-product-designers-portfolio-d7ae90056a3b?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7ae90056a3b</guid>
            <category><![CDATA[featured]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Thu, 13 Aug 2020 21:22:44 GMT</pubDate>
            <atom:updated>2020-08-13T21:22:44.671Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qqwz-4xMMYB_mD2jCz7jQ.png" /></figure><p>I had a lot of good responses to a question I put out on <a href="https://www.linkedin.com/feed/update/urn:li:activity:6687366713492803584/">LinkedIn</a> about advice for product design portfolios so I thought I’d expound on that here in hopes of helping you get called in for an interview.</p><p>While the principles here are applicable to almost all types of design roles, I’m going to narrow the focus of this to folks who are seeking a product design role.</p><p>Okay, let’s get into it.</p><h4>Include both process and finished work</h4><p>The best portfolios include not just the finished product, but work done along the way. I’m not talking about just adding a photo of an obligatory sticky note session or notebook sketches. I’m talking about showing things you tested and discarded or an idea that you tweaked along the way.</p><p>Product design is a deep, murky world and hiring managers are looking to see how well you can swim in the muddy waters. Process work is key here.</p><p>The reason process work is important is that it demonstrates your thinking. If you just show those Dribbble-perfect screenshots, hiring managers won’t have any idea how you got there. It’s a lot like showing your work on a math problem. Anyone can guess at the answer and get it right. Not everyone knows how to do it. Hiring managers want to see that you know how to do it.</p><p>Another tip, courtesy of Director of Design Strategy <a href="https://medium.com/u/bcdcaf48bb81">jonathanpberger</a> would be to include how your decisions relate to your process work.</p><p>How much of this do you include? You don’t have to show every single step, just enough to make your point.</p><p><strong>Practical examples</strong></p><ol><li>Show something you a/b tested or presented in a user interview, then talk about how it changed as a result of feedback</li><li>Talk about the legwork you did or data you reviewed and how it informed your decisions</li></ol><h4>Make sure your writing is concise and coherent</h4><p>While visuals are important, don’t neglect the words you wrap around them. You’re only going to get <a href="https://uxdesign.cc/ever-wonder-how-recruiters-look-at-your-design-portfolio-cc8dd1ecb698">3–10 minutes</a> of someone’s time, so pull out all the stops and don’t waste a word.</p><p>Writing a portfolio entry is a little like designing a billboard, we have to design them for someone who’s speeding by. Remember: this isn’t a Tolkien novel, it’s essentially a pitch to get someone to call you. So make every word count.</p><p><strong>Practical examples</strong><br>Be able to summarize these things in a few hundred words or less:</p><ol><li>What problem you addressed</li><li>Who was on your team and what your contributions were</li><li>Who you helped</li><li>What you learned along the way</li><li>What you achieved and the outcome</li></ol><h4>Demonstrate collaboration</h4><p>Product designers are the glue that holds a project together. They’re the bridge between the client, the people using the product, the engineers, and product managers. So it logically follows that these folks would need to be able to collaborate with others on their project.</p><p>If you had a heroic moment on a project, you should absolutely tell that story. But don’t forget to show how you worked with others. That helps make strong case about what you’d add to the company you’re trying to join.</p><p><a href="https://medium.com/u/bcdcaf48bb81">jonathanpberger</a> has this to say about collaboration in an interview with <a href="https://www.invisionapp.com/inside-design/inside-design-team-pivotal-labs/">Invision</a>:</p><blockquote>Also, ask for help. Don’t hide in a hole.</blockquote><blockquote>Don’t put your headphones on and block out everybody else. It can be gratifying to think that you’re some lone genius in your own little tower, but you’re probably not, and even if you are, it’s no fun up there alone. Engage in the conversation, and engage in the community.</blockquote><p>In short, don’t try to be be the lone hero. Talk about how you assembled your own Justice League and tackled your problem together.</p><p><strong>Practical examples</strong></p><ol><li>Talk about a time where you teamed up with a product manager or engineer to address a tricky problem. What’d you do or change as a result</li><li>Share a story about how you went out of your way to get that reclusive stakeholder involved</li></ol><h4>Show holistic thinking</h4><p>If you want to prove that you’re going to be a valuable long-term team member, show that you think bigger. Think about the entire customer journey you’re designing for, the design system that powers the thing you’re building.</p><p>Design doesn’t exist in a vacuum, it’s a complex and shifting set of variables and only those who consider the whole picture are going to effective long-term. It’s not just about designing that app, it’s about considering how that app design fits in with the other touchpoints someone will have with the product.</p><p><strong>Practical examples</strong></p><ol><li>Show a customer journey map or service blueprint</li><li>Dive into the style guide or pattern library</li><li>Talk about the big picture, not just one facet</li></ol><h4>Bonus: talk about you as a regular human</h4><p>I’ll speak for my company here: we’re hiring a whole person to join the team, not just a cog to fit in a machine. We hope you’ll feel welcome to bring your entire self to the team.</p><p><strong>Practical examples (if you’re comfortable with them)</strong></p><ol><li>Share a little about yourself, how you got started, or what fascinates you about Design</li><li>Share a personal or career goal</li></ol><h4>Final thoughts</h4><p>In this article, we discussed the most critical parts of a good portfolio by underscoring the need to show meaningful process work and how it relates to your decision. We discussed why we need to include examples of our collaboration so we don’t look like the lonely hero. Lastly, we discussed holistic thinking and how important it is.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7ae90056a3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thisisartium/what-we-look-for-in-a-product-designers-portfolio-d7ae90056a3b">What we look for in a product designer’s portfolio</a> was originally published in <a href="https://medium.com/thisisartium">Artium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Need a Code of Ethics]]></title>
            <link>https://medium.com/thisisartium/we-need-a-code-of-ethics-eaaba6f9394b?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaaba6f9394b</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[featured]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 22:33:58 GMT</pubDate>
            <atom:updated>2020-07-23T22:54:13.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L0VD7oa1ABT3ys34Psaitw.jpeg" /></figure><h4>We’ve been moving too fast for too long and it’s hurting everyone.</h4><p>I keep wondering what we can do to ensure we’re building a better world with the products we make and if we need a code of ethics. So often I see people fall through the cracks because they’re “edge cases” or “not the target audience.” But at the end of the day, we’re still talking about humans. <br> <br>Other professions that can deeply alter someone’s life have a code of ethics and conduct they must adhere to. Take physicians’ Hippocratic oath for example. It’s got some great guiding principles, which we’ll get into below. Violating this code can mean fines or the losing the ability to practice medicine.</p><p>We also build things that can deeply alter someone’s life, so why shouldn’t we have one in tech?</p><p>While this isn’t a new subject by any stretch, I made a mini one of my own. It’s been boiled down to just one thing and is flexible enough to guide all my other decisions. I even modified it from the <a href="https://owlspace-ccm.rice.edu/access/content/user/ecy1/Nazi%20Human%20Experimentation/Pages/Hippocratic%20Oath-modern.html">Hippocratic Oath</a>:</p><blockquote>We will prevent harm whenever possible, as prevention is preferable to mitigation. We will also take into account not just the potential for harm, but the harm’s impact.</blockquote><p>That’s meaningful to me because our for years, tech had a “<a href="https://facebook.com/">move fast, break things</a>” mentality, which screams immaturity. It’s caused carelessness, metrics-obsessed growth, and <a href="https://www.nytimes.com/2018/10/15/technology/myanmar-facebook-genocide.html">worse</a>— I don’t need to belabor that here.</p><p>We’ve moved fast for long enough, now let’s grow together to be more intentional about both what and how we build. Maybe the new mantra could be “move thoughtfully and prevent harm,” but maybe that isn’t quite as catchy.</p><h4>A practical example</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*EthOZquq1IFUCtw-9H69SA.png" /></figure><p>Recently, a <a href="https://twitter.com/tg_bomze/status/1274098682284163072">developer launched a de-pixelizer</a>. Essentially, it can take a pixelated image and approximate what the person’s face might look like. The results were…<a href="https://twitter.com/Kiloku/status/1274315587133587457/photo/1">not great</a>.</p><p>Setting aside that the AI seems to have been only trained on white faces, we have to consider how process this might go wrong and harm people.</p><p>Imagine that this algorithm makes it into the hands of law enforcement, who mistakenly identifies someone as a criminal. This mistake could potentially ruin someone’s life, so we have to tread very carefully here.</p><p>Even if the AI achieves 90% accuracy, there’s still a 10% chance it could be wrong.</p><p>And while the potential for false positives might be relatively low, the impact of those mistakes could have severe consequences. Remember, we aren’t talking about which version of Internet Explorer we should support, we’re talking about someone’s life — we have to be more granular because both the potential and impact of harm is high here.</p><h4>Accident Theory and Preventing Harm</h4><p><a href="https://medium.com/u/900a0a73e35d">Kaelin Burns</a> (Fractal’s Director of Product Management) has this to say about creating products ethically:</p><blockquote>“When you create something, you also create the ‘accident’ of it. For example, when cars were invented, everyone was excited about the positive impact of getting places faster, but it also created the negative impact of car crashes and injuries.</blockquote><blockquote>How do you evaluate the upside of a new invention along with the possible negative consequences, especially when they have never happened before? So when you’re creating new technology, I believe you have a responsibility, to the best of your ability, to think through the negative, unintended, and problematic uses of that technology, and to weigh it against the good it can do. It become particularly challenging when that technology also has the potential be extremely profitable, but is even more important in those cases.”</blockquote><p>If you’re looking for an exercise you can do, try my <a href="https://uxdesign.cc/black-mirror-brainstorms-f919ccf5938c">Black Mirror Brainstorm</a>.</p><p><a href="https://uxdesign.cc/black-mirror-brainstorms-f919ccf5938c">Black Mirror brainstorms — a product design exercise</a></p><h4>In closing</h4><p>In this post, we discussed why we need a code of ethics in our world. I shared one thing that I added to mine. We also talked about the impact of not having one. You also learned about Accident Theory and have a shiny new exercise to try.</p><p>I’m curious about one thing: What’s one thing you’d include if you made a Hippocratic Oath for tech?</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaaba6f9394b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thisisartium/we-need-a-code-of-ethics-eaaba6f9394b">We Need a Code of Ethics</a> was originally published in <a href="https://medium.com/thisisartium">Artium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Work: Quarantine Edition]]></title>
            <link>https://medium.com/thisisartium/deep-work-quarantine-edition-b963541ebd5f?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b963541ebd5f</guid>
            <category><![CDATA[deep-work]]></category>
            <category><![CDATA[featured]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Wed, 01 Jul 2020 16:16:00 GMT</pubDate>
            <atom:updated>2020-07-01T16:16:00.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AFsjQezyHdq7T26lc9J-Jg.jpeg" /></figure><p>Something I deeply believe is that if you’re able to have focused time to work, you’re going to be able to go further, faster, and deeper than those who don’t.</p><p>That’s been especially true for me in this time of quarantine. When this began, I was hyper-available to people, answering emails and chats much quicker than I would usually. That, paired with the uncertainty of this pandemic made for a huge drag on my focus and craft.</p><p>After a couple months, I’m happy to say that I’ve found my groove again and figured out how to re-adopt Deep Work for a post-COVID era.</p><p>I’d like to share what I’ve been doing in hopes of it helping you. I won’t say this is a prescription, I recognize that not all of this is applicable to everyone. I will say that it’s helped me and maybe you can find one tiny thing to help you.</p><p>I’d like to talk about the benefits of Deep Work, dispel the myth of multitasking, and give you practical ways of making it work for you.</p><h3>What is Deep Work and Why Do I Care?</h3><p>Deep Work is a term I stole from <a href="https://www.amazon.com/dp/B013UWFM52/ref=dp-kindle-redirect?_encoding=UTF8&amp;btkr=1">Cal Newport’s book of the same name</a>. I use it as a label for the intensive, focused work we value so highly in design. It’s so important that we made it a core value in our design team.</p><p>Let’s talk about how that applies to makers like us by reading an excerpt from Paul Graham essay called “<a href="http://www.paulgraham.com/makersschedule.html">Maker’s Schedule, Manager’s Schedule</a>.” It gets at the way we use our time in a really eloquent way. The entire essay is worth reading, then reading again.</p><p>In this essay, Paul sets up the ways makers and managers use their time and how each person’s use impacts the other. Here’s what he has to say about a meeting that dots our schedule.</p><blockquote>I find one meeting can sometimes affect a whole day. A meeting commonly blows at least half a day, by breaking up a morning or afternoon. But in addition there’s sometimes a cascading effect. If I know the afternoon is going to be broken up, I’m slightly less likely to start something ambitious in the morning. I know this may sound oversensitive, but if you’re a maker, think of your own case. Don’t your spirits rise at the thought of having an entire day free to work, with no appointments at all? Well, that means your spirits are correspondingly depressed when you don’t. And ambitious projects are by definition close to the limits of your capacity. A small decrease in morale is enough to kill them off.</blockquote><p>To me, this underscores one of my deeply-held beliefs: <strong>unbroken blocks of time are critical to being a contributing member of any team</strong>. Enter Deep Work.</p><h3>The Impact of Deep Work</h3><p>Think about metalsmiths, the ones who forge all the cool knives we use every day. Their work is incredibly careful and focused. It takes hours of dedicated focus to produce a blade. They have to hit the metal in just the right way in just the right spot. A lack of focus, even for a short time, means the possibility of a brittle blade that has to be reforged.</p><p>Designing and building software is no different.</p><p>If we lose focus, even for a minute to answer an email, we risk losing our focus and momentum. That design solution we’re working towards, we’ve got to go back to the beginning and retrace our steps. The algorithm we’re writing to process a bunch of data, we’re back at square one — all because of a short interruption. If you think this is an exaggeration, know that I’ve seen it happen firsthand to myself and others.</p><p>At work, we use Pivotal Tracker to measure our team’s progress towards a goal. One metric in there is velocity. Once we implemented deep work on the team, our velocity /tripled/.</p><p>How’d we do that? We blocked off time to do Deep Work. Let’s talk about things you can try next.</p><h3>What to Try</h3><p>Here’s a short list of things that help get you going:</p><h4><strong>Identify What You’ll Focus On</strong></h4><p>This might seem obvious, but it’s so important that it’s worth reiterating. If you know what you’re working on, you can really dive in. Otherwise, your lack of focus will make for a less rewarding and productive time because you’re spending too much time trying to figure out what to do. So, do this before you get started.</p><h4>Shut Off Notifications</h4><p>Those tiny red dots and push notifications are the best at stealing your attention. I recommend setting aside some time where you’re separated from things that notify you. Put your phone on Do Not Disturb and drop it in a drawer where you can’t see it. You may still need a way to let someone reach you. I’ll cover that in another post.</p><h4>Block Off Time, Ritualize It</h4><p>For Deep Work to happen and be effective, you need chunks of time to do it. I’ve experimented with short sprints and long stretches of time. But the most important thing is to drop time on your calendar, block it off, and make it consistent.</p><p>I’ve found you need at least 45 minutes of uninterrupted time to really get into flow. I find I can focus for an hour and a half, but then I need a break for half an hour or so before I go back.</p><h4>Chunk Your Meetings</h4><p>To call back to the problem outlined in Paul Graham’s essay from earlier, meetings — while important — can really sap your ability to focus. So put them in blocks. Find out when you work the best and protect that time.</p><p>I’ve seen people have a morning or afternoon of meetings so they work uninterrupted in the other stretch of time. I work best in the morning, so I protect that time.</p><p>If neither of those work for you, try putting your interruptions near your lunch break.</p><h4>Consider The Optimum Time for Meetings</h4><p>Our own Aldric had this addition. He says:</p><p>When working on the manager schedule, keep those tips in mind for your colleagues on maker schedules, particularly if you must set recurring meetings with them (e.g. 1:1): try to use the beginning or end of their day, or before or after their lunch.</p><h3>Wrapping Up</h3><p>To conclude, let’s revisit some of the topics we discussed. By now, you and I hopefully share the belief that Deep Work is valuable, rewarding, and worth your time. It can really boost the quality of what you were hired to do. You’ve got a few tools in your toolbox to help facilitate that time, such as identifying what you’ll focus on, shutting off distractions, blocking time on your calendar for it, and chunking your meetings.</p><p>What else have you done? I’d be eager to hear. Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b963541ebd5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thisisartium/deep-work-quarantine-edition-b963541ebd5f">Deep Work: Quarantine Edition</a> was originally published in <a href="https://medium.com/thisisartium">Artium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End of Day ceremonies: the key to sleeping better and staying focused during quarantine]]></title>
            <link>https://medium.com/thisisartium/end-of-day-ceremonies-the-key-to-sleeping-better-and-staying-focused-during-quarantine-7902b8e01339?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7902b8e01339</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Mon, 18 May 2020 16:37:52 GMT</pubDate>
            <atom:updated>2020-05-18T16:37:52.778Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An image if a guy with a sweet, sweet watch journaling." src="https://cdn-images-1.medium.com/max/1024/1*82azlWt6tkCFj877oF44oQ.png" /></figure><p>Remember the last time you couldn’t get something out of your head and you woke up thinking about it in the middle of the night? The last few weeks of quarantine have been one continuous stretch of undifferentiated time and it’s become hard to turn things off. So I’ll share what I did about it in hopes of it helping you too. After putting this self-care routine into practice, I’ve been much more effective and focused during the day. In these times, self care is key.</p><p>I had been waking up every night at 2:30am thinking about something going on at work, the industry, my family, or the world we’ll be living in after this passes. It’s not that what’s going on is bad necessarily; it’s that I can’t shut it off.</p><p>I hoped if I could take a few minutes at the end of each day to shut my brain down, I’d be able to sleep better. So I came up with an experiment: an End Of Day ceremony where I empty out my head so there’d be room to sleep. Experiment #1: journaling.</p><h3>Here’s what I write about</h3><ol><li>Anything notable from today</li><li>How’ve I’ve been feeling</li><li>What I’ve been wondering about</li><li>What I need to do next</li></ol><p>I write about the good, the not so good, the seemingly banal (because that’s the stuff that’s caught in my head in the middle of the night). If it’s in my head, it’s going to become text in this journal entry.</p><h3>Here’s how to set it up</h3><h4>Find a journaling tool.</h4><p>Invest no more than 20 minutes here. It’s important that your choice of software gets out of your way and makes writing pleasant. I use <a href="https://dayone.me/">Day One</a> (but something as simple as Google Docs or Notes could be enough to get you started.</p><h4>Set up a reminder each day at 5 PM to write.</h4><p>Day One, thankfully, handles that for me.</p><h4>Create a template that includes all the topics you want to cover.</h4><p>If you’re a director like me, this could be how your direct reports are doing, or initiatives you need to track. If you aren’t, some ideas could be tracking how you’re feeling, or noting tiny wins you’ve achieved. Just keep it simple.</p><p>Ten minutes later, I’ve emptied out my mind, leaving me free to enjoy a more relaxed sleep.</p><h3>Delightful Surprises</h3><p>This approach already yielded a few unexpected gems.</p><p>The first is that every morning I can start off knowing exactly what I need to focus on. I don’t spend any time looking for anything to do because Yesterday-Josh already figured that out and kindly set it in front of Today-Josh. It’s a huge boost to my focus.</p><p>Another bonus is the record of what I’ve been up to. It’s much easier to recall interesting insights from a project or decisions that I made so I don’t have to backtrack.</p><p>And finally, it helps me be more intentional about setting and accomplishing my goals.</p><h3>In closing</h3><p>After two weeks of this End of Day ceremony, my experiment in self-care did exactly what I wanted it to: I sleep much better than before. My brain is a little less frenetic and I’m able to focus more at work. Turns out, just taking time to purge my brain was the key to it all.</p><p>—</p><p><em>Photo by Alejandro Escamilla on </em><a href="https://unsplash.com/s/photos/journaling?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7902b8e01339" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thisisartium/end-of-day-ceremonies-the-key-to-sleeping-better-and-staying-focused-during-quarantine-7902b8e01339">End of Day ceremonies: the key to sleeping better and staying focused during quarantine</a> was originally published in <a href="https://medium.com/thisisartium">Artium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get the best feedback on your design]]></title>
            <link>https://medium.com/thisisartium/how-to-get-the-best-feedback-on-your-design-54d109df2fa9?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/54d109df2fa9</guid>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Fri, 28 Feb 2020 23:39:19 GMT</pubDate>
            <atom:updated>2020-12-10T19:40:12.060Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLvncwN6v9epl0mzpyK5cA.png" /></figure><p>It won’t be a surprise when I say that feedback is a critical part of delivering a project. What might be surprising, however, is that we can find better ways to solicit it. In this article, we’ll talk about a few tweaks you can make to how you present your work and how you receive feedback.</p><h3>Presenting the work</h3><p>How you present your work forms the basis for the kind of feedback you get. What do you think will be more effective:</p><ol><li>Show the work, ask if your stakeholder can approve it.</li><li>Show the work, talk about the problems it solved, what you did, and ask for specific feedback on how it meets the objectives?</li></ol><p>If you said #1, please keep reading. If you said #2, this is a great start…but you should still keep reading, too.</p><p>The more objective we can be about our design accomplishing a goal, the less subjective feedback we get. It’ll still happen — we’ll address that in a future post — but presenting the work in this manner will be a surefire way to guard against someone saying something about their preferences. One favorite I heard long ago with a client of mine was, “My wife doesn’t like this shade of blue, so I want to change it.” In case you’re wondering, I chose route #1 when presenting my work that time.</p><p>One thing we’re doing at Artium is presenting the work in terms of problems being solved, but we also break our design review down into three sections: the first one’s for presenting, the second’s for a sticky note exercise where the client writes down their feedback, and the third is for focused discussion.</p><p>We do it this way because this is usually the first time some stakeholders have seen the design and that makes for a good deal of knee-jerk, off-the-cuff feedback. This kind of feedback is lower value since those thoughts often haven’t been fully baked. This sticky note exercise gives clients a little more time to think deeper about what their gut told them. Remember: clients didn’t go to school to be your client, they went to school to learn their profession. It’s your job to bridge that gap and lead them.</p><p>We also go into the design review wanting to learn specific things, so we ask specific questions of our clients. Some things we usually ask:</p><ol><li>What might we not be seeing about implementing this?</li><li>Do you see any hurdles for getting this adopted (e.g. with their team, other management)?</li></ol><h3>Receiving feedback</h3><p>The single biggest problem I see with younger designers is that they take feedback personally. I know I certainly did. It makes sense why. So much heart goes into making this product that it’s only natural that we’d see our work as an extension of ourselves.</p><p>But that’s ultimately not helpful. By doing this, we’re unnecessarily inserting our personal goals into a project where we should be objective and focused on the outcome.</p><p>I think at the core, designers get so caught up in the tactics that they forget the goal. If you focus on the goal, the tactics are easy to change and make adapting less painful. For example, don’t think about the request to change the blue button, think about getting a user across the finish line.</p><p>In short: divorce yourself from the work.</p><h3>Conclusion</h3><p>So, to conclude: we talked about how to structure your design review so it’s geared toward objectivity. We also discussed how and why to give your clients time to think about their feedback so it’s the most fully-formed critique possible.</p><p>We also took a look at how to structure your presentation and established the importance of giving time for reflection. If you hear something subjective, you now know how to probe and get to the bottom of it. Lastly, we talked about how essential it is to not take things personally.</p><p>If you have questions, I’d love to chat. Leave a comment or <a href="http://linkedin.com/in/joshuamauldin">reach out on LinkedIn</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54d109df2fa9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/thisisartium/how-to-get-the-best-feedback-on-your-design-54d109df2fa9">How to get the best feedback on your design</a> was originally published in <a href="https://medium.com/thisisartium">Artium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How using Cranky Conclusions makes tough conversations easier]]></title>
            <link>https://medium.com/conflict-resolution-for-people-who-hate-conflict/how-using-cranky-conclusions-makes-tough-conversations-easier-4af9789dfa1e?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4af9789dfa1e</guid>
            <category><![CDATA[accusations]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[conflict-resolution]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 17:10:08 GMT</pubDate>
            <atom:updated>2019-07-16T17:10:08.092Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ever needed to tell a teammate something tough but fear they’ll get too defensive? Here’s one way that’s proven to work.</h4><figure><img alt="Very sad doggo wrapped in a blankey to ward off the bad vibes of your conversation" src="https://cdn-images-1.medium.com/max/1024/0*kOKfC0fS6aLcRDxb" /><figcaption>Photo by <a href="https://unsplash.com/@matthewhenry?utm_source=medium&amp;utm_medium=referral">Matthew Henry</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>You’re going to say the technique I’m about to share is just a glorified way of manipulating someone. Hear me out though.</p><p>Not all conflict is easy to address. We’re by no means perfect. <strong>We put so much of ourselves into our work that it’s hard to not take some feedback personally.</strong> Telling someone they’re under-performing or having a negative impact on a team can put them on the defensive quicker than you blink an eye.</p><p>How are we supposed to talk to someone about the sticky things? Sure, we could just dive right into it and risk them getting defensive. Or we could be a little more pragmatic.</p><h3>Introducing Cranky Conclusions</h3><p>Let me introduce you to my favorite preparation tool for hard conversations. It starts with a simple question:</p><blockquote><strong>What’s the worst thing they can say about me?</strong></blockquote><p>This is helpful for two reasons: it <strong>primes your brain for empathy</strong> and <strong>prevents you from being caught off guard </strong>when you go talk to the other person.</p><p>How’s it prime your brain? By visualizing the worst places they can go, you’re putting yourself in their shoes. You’re also exploring what they might think when they hear this news.</p><p>Cranky Conclusions help you be better prepared for a conversation that could get weird. It works because you’ve you<strong> anticipate the negative places they might go even before you breathe a word of it them</strong>. They give you the chance to tailor your conversation and route around those bad thoughts<strong>. </strong>If you use them in a conversation, <strong>you’re going to short-circuit them thinking the worst case scenario.</strong></p><h3>Putting it into practice: the smelly teammate</h3><p>For example, let’s say you’re working with someone who smells like the inside of a moldy, smoke-filled motel that’s recently been unsealed after years of being shut off from any kind of fresh air. You appreciate them as a person and respect their work but the smell is oppressive and makes concentrating or staying next to them for more than a few moments difficult. If this example sounds really specific, it’s because it actually happened to me. I still remember the smell to this day.</p><p>If I do go and talk to them, I use Cranky Conclusions find the worst thing they can say. Here are a couple things that come to mind:</p><ul><li>I’m an asshole, they smell just fine</li><li>I shouldn’t try to tell them what to do</li></ul><p>Armed with those thoughts, I can now go talk to them. Hopefully, I can prevent them from thinking the worst so they can actually hear what I have to say. I usually say something like this:</p><blockquote>You’re going to think [the really bad thing]. Hear me out though.</blockquote><p>Note that this statement doesn’t include “but.” <strong>Cranky Conclusions are just like apologies: if you include a “but,” you negate everything that comes before it.</strong></p><p>Back to the smelly teammate: once I made my Cranky Conclusions, I went up to them one-on-one to talk. I said “hey, I’m gonna sound like an asshole who’s trying to control you when I say this. Please hear me out: I’m very sensitive to the smell of smoke. When someone smells of it, it makes concentrating really tough. Is there any way that before we work together that you can do something about it?”</p><p>Luckily, they were cool about it and offered to use some mouthwash before working together. Problem solved, but that was hard to broach for me because I know how touchy people can get when it comes to hygiene.</p><p><strong>Once you’ve used a Cranky Conclusion in your conversation, you’ve likely short-circuited their brain from thinking its worst thoughts.</strong> Now you can have a more productive conversation.</p><p>I’ve used this technique with my direct reports, my teammates, stakeholders, (and even family members). It’s been very successful in helping me talk about hard topics.</p><h3>Going even deeper</h3><p>You can go even deeper with Cranky Conclusions by asking how you might’ve contributed to the situation.</p><p>It gets a little harder from here. Looking at your role requires a mountain of honesty and willingness to be wrong. It’s like that because this exercise often highlights how selective your perceptions of a situation are. While we want to believe we’re being fair, we often aren’t; it’s because we forget to look at how we might’ve contributed.</p><p>Claire Lew (CEO of KnowYourTeam) has a great perspective here:</p><h3>Claire Lew on Twitter</h3><p>When an employee is underperforming, the first question you should ask yourself is: &quot;Do they know, or do they not know?&quot; If they know, the problem is misalignment on consequences of &quot;poor work.&quot; If they don&#39;t know, the problem is misalignment on definition of &quot;good work.</p><h3>Claire Lew on Twitter</h3><p>Second question to ask yourself when an employee is underperforming: &quot;How am I contributing to their underperformance, unintentionally?&quot; Particularly... What is common sense to me that is not to them? What feels urgent to me, but not to them? Am in the way or out of the way?</p><p>It’s perfect that she asks you to think about what might be common sense to you but not to them. I have been lucky to have a few managers who operated that way. They were the most effective ones I ever had, by a long shot. While this applies well to the manager/direct report relationship, it’s also incredibly effective for teammates.</p><h4>What if I I don’t have any responsibility here?</h4><p>You won’t always find that you have any responsibility for the situation being what it is.</p><p>This is especially true if you’re on the receiving end of harassment or abuse. I’d like to think that’s obvious but there are always one or two dudebros reading along that still don’t get it (hi, dudebros!), so I’m going to say it again: victims bear no responsibility for someone else’s actions. If you disagree, [Joshua points behind you] there’s the door.</p><h3>Overall</h3><p>Cranky Conclusions are really helpful because at its core it’s a tool to build empathy. After all, you’re putting yourself in their shoes and asking yourself what they might say in response to some hard news. Cranky Conclusions also make it harder to get surprised in a conversation. You can even use it to start a conversation with one (for an example, go back and read the first line of this article).</p><p>If you want to go deeper, you can ask yourself how you might’ve contributed. It’s a great way to help you be fair in your perceptions because we’re often selective about our facts and the roles we play.</p><h3>Try this before your next conversation</h3><ul><li>Ask yourself “what’s the worst thing they can say about me?”</li><li>If you think it’s going to be a hard conversation, use something from your Cranky Conclusions to start the conversation</li><li>Take a moment and look at how you might’ve played a role in things being like they are</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fh8xe9h%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fh8xe9h&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fh8xe9h%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href">https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4af9789dfa1e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict/how-using-cranky-conclusions-makes-tough-conversations-easier-4af9789dfa1e">How using Cranky Conclusions makes tough conversations easier</a> was originally published in <a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict">Conflict Resolution for People Who Hate Conflict</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Prime Directive and the limits of assuming positive intent]]></title>
            <link>https://medium.com/conflict-resolution-for-people-who-hate-conflict/the-prime-directive-and-the-limits-of-assuming-positive-intent-59b7b2d735f1?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/59b7b2d735f1</guid>
            <category><![CDATA[conflict-resolution]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Tue, 02 Jul 2019 17:04:48 GMT</pubDate>
            <atom:updated>2019-07-12T20:23:18.490Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to build psychological safety and give someone the benefit of the doubt without downplaying the impact of their actions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rHuI3B5e26ewQBdm" /><figcaption>Photo by <a href="https://unsplash.com/@muukii?utm_source=medium&amp;utm_medium=referral">Muukii</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Here’s the most helpful thing I’ve ever learned by far about conflict: <strong>before you have a conversation with someone, make sure you assume positive intent.</strong> Read on to discover a technique you can use to apply that idea — if you’re like me, you’ll find it will resolve most conflict before it starts. And, in a fun plot twist, we’ll also cover how this idea shouldn’t be applied at all times because it can harm underrepresented folks if we aren’t careful.</p><h3>The Prime Directive</h3><p>I facilitate a lot of retrospectives at work. If you’re unfamiliar with retrospectives, these are meetings that exist to help a team process how the last few days went. They generally cover what went well, what could be improved, and what was frustrating.</p><p>One thing I do before a retrospective with a new team (or team member), we go over <strong>The Prime Directive</strong> (no, not <a href="https://en.wikipedia.org/wiki/Prime_Directive">the Star Trek one</a>). It’s this one from what Norm Kerth:</p><blockquote>Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.</blockquote><p>Retrospectives need to be a safe space to discuss how the last two weeks were for everyone. After all, you’re talking about things that need improvement and it’s easy for things to get heated. The Prime Directive helps enshrine psychological safety because it helps us frame every event as an opportunity for improvement.</p><p>Once you <strong>assume positive intent</strong>, it’s much easier to defuse tension when it arises. It’s easier because you’re <strong>building psychological safety.</strong></p><h3>The limits of assuming positive intent</h3><p>I want to make a distinction that might be not be obvious: you can’t (and shouldn’t) assume positive intent in every scenario. It isn’t a magic wand you wave and resolve all conflict —actions have impact and that impact should be acknowledged. For example, If I step on your foot once, you probably won’t think I did it intentionally. It doesn’t mean you didn’t get hurt.</p><p>Similarly, it’s important to not negate the impact of someone’s actions just because they meant well. What I’ve found is that <strong>assuming positive intent can disproportionately affect underrepresented folks.</strong></p><p>I’ll let <a href="https://thebias.com/2017/09/26/how-good-intent-undermines-diversity-and-inclusion/">Annalee from The Bias</a> explain:</p><blockquote>On its face, [assuming positive intent] might not sound like a bad idea. After all, isn’t assuming the best in others generally a good way to go through life? What’s the harm in encouraging that within your community?</blockquote><blockquote>The harm is that telling people to “assume good intent” is a sign that if they come to you with a concern, you will minimize their feelings, police their reactions, and question their perceptions. It tells marginalized people that you don’t see codes of conduct as tools to address systemic discrimination, but as tools to manage personal conflicts without taking power differences into account. Telling people to “assume good intent” sends a message about whose feelings you plan to center when an issue arises in your community.</blockquote><h4>Let’s look at a more concrete example</h4><p>Take Roz, whose boss regularly praises her appearance. Her boss — we’ll call him Luc — is a successful manager who’s a few generations older. He’s been a little touchy with some of the other women in the office but not her.</p><p>Luc regularly praises Roz’s appearance by saying how beautiful she looks or how nice her hair is. One day, she’s in the middle of updating a document and she’s wearing a new top that’s a little revealing. Luc comes in and says how nice that new top is. “What the hell did he mean by that?” Roz asks.</p><p>Roz is uncomfortable that her boss says these things to her. She’s not there to be seen, she’s there to work. While she can assume positive intent all day and know that Luc only meant to make her feel better, she still feels objectified.</p><p>If she does tell someone, say HR, they could point to their code of conduct and say “see here, it says we assume positive intent. Luc didn’t mean anything by this. Don’t make this into something it isn’t” and send her on her way. That sucks.</p><p>She might opt to quash her feelings, suck it up, and keep going, which also sucks. Or she could talk to Luc about it, risk the relationship, <em>and </em>have to do the emotional labor of educating him. This, too, sucks.</p><p><strong>What’s the ideal way forward here?</strong></p><p>Ideally Luc will come to this realization on his own and not force Roz or the other women in the office to fix it. That shouldn’t be their job. There’s another ideal option: have an ally step in to educate Luc, which takes the effort off of Roz.</p><h3>Overall</h3><p>Assuming positive intent is a game-changer and tools like The Prime Directive help enshrine psychological safety in your workplace. While it does a lot of good, we have to make sure to not blindly apply it and ignore the impact of someone’s actions because it can disproportionately affect underrepresented people.</p><h3>Try this before your next conversation</h3><ul><li>Before starting a conversation, remind everyone (including yourself) about The Prime Directive. Do you believe it applies in this situation?</li><li>Remember the limits of assuming positive intent and don’t ignore the impact</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fh8xe9h%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fh8xe9h&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fh8xe9h%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href">https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b7b2d735f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict/the-prime-directive-and-the-limits-of-assuming-positive-intent-59b7b2d735f1">The Prime Directive and the limits of assuming positive intent</a> was originally published in <a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict">Conflict Resolution for People Who Hate Conflict</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How video games taught me to be better at conflict]]></title>
            <link>https://medium.com/conflict-resolution-for-people-who-hate-conflict/how-video-games-taught-me-to-be-better-at-conflict-69cdb52e670f?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/69cdb52e670f</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[conflict-resolution]]></category>
            <category><![CDATA[patterns]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Wed, 26 Jun 2019 18:44:44 GMT</pubDate>
            <atom:updated>2019-07-12T20:31:35.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9cj6jhvJr4O2wb_jWmAAtA.jpeg" /><figcaption>The Legend of Zelda</figcaption></figure><p>I played a lot of video games growing up. It all started with The Legend of Zelda. I had such bad allergies that most of my adventuring had to be more pixel-based than anything. I didn’t expect to learn all that time spent playing video games would amount to anything, especially when it came to conflict resolution. Turns out there’s a lot more in common with old school video games and modern day human behavior than you’d think.</p><p>Games of that era had such limited computing power that everything had to happen in a pattern. Enemies would move in a certain way — once you learned how they acted, you had a much easier time understanding how to defeat them. I’m fascinated by how that can apply to human behavior.</p><p>Let’s explore how spotting patterns in behavior makes for better outcomes when it comes to conflict.</p><h3>The big question you ask yourself</h3><p>It all starts by asking myself “<strong>has anything like this happened before?</strong>”</p><p>If so, I’ll try to <strong>find three examples to share</strong>. Let’s say you’re going to talk to person who shows up late to client meetings consistently. Think up two other examples before you talk to them. I like to stay as objective as possible and avoid saying things like “you’re always late,” and focus on saying something like “the last three client meetings we’ve had, you were more than 15 minutes late.”</p><p>One event is almost too easy to explain away and isn’t usually enough to draw a useful conclusion from. Finding two examples helps you two piece things together — there could still be a lot you’re missing though. <strong>It’s only when you reach three that you come up with almost undeniable evidence for your conclusions about your issue.</strong></p><h3>A quick note about assumptions</h3><p>I’m not a big fan of assumptions generally. However, I am a fan of <strong>assuming positive intent</strong>. Sure, it’s possible that someone’s trying to cover their ass or being malicious — we’ll get into that another time — but isn’t it more likely that there’s just something they aren’t seeing? This is where patterns are really helpful: they help both of you connect the dots.</p><p>I’m also assuming <em>you</em> have positive intent. If you’re cherry-picking things to just shut someone down, if you’re out for revenge, or you just want to be right, you should back off, full stop.</p><h3>Overall</h3><p>It’s worth revisiting what patterns do well:</p><ul><li>Make it easier to help people see what’s really happening</li><li>Help you make the strongest case when having a conversation</li><li>Assist the other person in seeing their behavior’s impact</li></ul><h3>Try this before your next conversation</h3><ul><li>Ask yourself if they’ve done anything else that’s similar</li><li>If so, can you find two other examples?</li><li>Check your motives: be fair and don’t cherry-pick to make someone feel bad</li></ul><p>So the next time you think about conflict, think about all the patterns present in those old video games — it could give you the clarity you need before talking to someone.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fh8xe9h%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fh8xe9h&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fh8xe9h%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href">https://medium.com/media/cbf568bfaea18aa0dfae925236dcd4f2/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69cdb52e670f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict/how-video-games-taught-me-to-be-better-at-conflict-69cdb52e670f">How video games taught me to be better at conflict</a> was originally published in <a href="https://medium.com/conflict-resolution-for-people-who-hate-conflict">Conflict Resolution for People Who Hate Conflict</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Black Mirror brainstorms — a product design exercise]]></title>
            <link>https://uxdesign.cc/black-mirror-brainstorms-f919ccf5938c?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f919ccf5938c</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Mon, 26 Nov 2018 17:53:01 GMT</pubDate>
            <atom:updated>2018-11-30T02:40:57.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JMSxb1MjvJFDYrjWN4-Krg.jpeg" /><figcaption><a href="http://twitter.com/blackmirror">Black Mirror on Twitter</a></figcaption></figure><p>I want to have more ethical products. I feel like we all do. Sometimes, though, we don’t consider how this amazing thing we’re working on might have some unintended and negative consequences.</p><p>In my job, I help clients build products. Part of the process is framing the project and defining our goals. We also talk about anti-goals, which are things we absolutely don’t want to happen and run counter to our intentions.</p><p>If you’ve ever seen Black Mirror, the show excels at diving into how our products can have (severe) negative impacts on our society. I thought it might be an interesting idea to make a product design exercise out of it. Enter Black Mirror Brainstorms.</p><p>This exercise helps us guard against the negative effects of our goals by giving us a clear understanding of how our product could be misused. The outcome of this exercise is to more clearly define our anti-goals. Here’s how it works.</p><h3>About the Exercise</h3><ul><li>Groups of 3–4 people</li><li>Play time: 30–45 minutes (depending on the number of groups)</li><li>2 minutes to explain/give example</li><li>15 minutes to sketch</li><li>2–5 minutes to present</li><li>5 minutes to define anti-goals</li><li>Before the activity, create a template to distribute to each team</li><li>Provide markers, paper, stickies</li><li>Each team should get one template to work on together</li></ul><h3>How to Play</h3><p>The exercise breaks down into four sections: the <strong>brainstorm</strong>, <strong>quotes,</strong> <strong>plot points</strong>, and the <strong>poster</strong>. Here’s a template.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S1-LWrkeI_2MmpRT2-qQZw.png" /></figure><p>Next we’ll start with an example to get us thinking.</p><blockquote>Let’s say we’re a large technology company who’s looking to have the most personalized content so people will spend more time in our product. To do that, we’re building a targeting engine that sifts through millions of data points to spot trends. Our goal is to figure out how this can go wrong for people who we’re collecting data on.</blockquote><p>Now let’s get to each of the sections.</p><h4>Brainstorm</h4><p>Here, we’ll write down some of your ideas for what might go wrong. Here are a few areas to help frame your activity:</p><ul><li><strong>Economic Issues:</strong> could we enable bad faith actors to prey on vulnerable groups?</li><li><strong>Politics:</strong> could a corrupt government could use this info to identify and target dissidents?</li><li><strong>Social Issues:</strong> could our product reinforce already-present societal divides?</li></ul><blockquote>Important note: some folks won’t do well thinking on the fly in a group setting. To help them, instruct everyone to take 2–5 minutes to think up ideas before talking with the group. The stickies you provide are perfect for this.</blockquote><h4>Quotes</h4><p>This section is for quotes people in the episode might say. It can also be things people say about the episode after watching it.</p><p>Don’t be afraid to get dramatic or go over the top.</p><h4>Plot Points</h4><p>Plot points are helpful in describing how this bad situation comes to pass. They’re the substance of the story. Consider these four as a starting point:</p><ul><li>The characters: who’s going to be affected</li><li>The setup: the well-intended idea</li><li>The problem: how the well-intended idea goes wrong</li><li>The effect: how the idea going wrong affects people</li></ul><h4>The Poster</h4><p>Here, we’ll communicate the big idea. I suggest using a big quote that sums up the episode. If a team’s so inclined, they could also do an illustration.</p><h3>After the Exercise</h3><p>When everyone’s finished presenting, take a moment to look for common elements from everyone’s posters and write them on stickies. We’ll take the stickies, put them up, and group similar ones together. These are excellent candidates for anti-goals.</p><h3>Wrapping up</h3><p>We don’t have to look far to see how this might be helpful. Consider that <a href="https://www.forbes.com/sites/kashmirhill/2012/02/16/how-target-figured-out-a-teen-girl-was-pregnant-before-her-father-did/#7f6150856668">Target figured out a teen was pregnant</a> and started sending her pregnancy-related coupons, much to the shock and anger of her parents. Another time, Facebook year in review showed <a href="http://meyerweb.com/eric/thoughts/2014/12/24/inadvertent-algorithmic-cruelty/">Eric Meyer a photo of his recently-deceased daughter</a> surrounded by confetti and dancing people. None of these things products intended to be cruel. But because the designers didn’t consider the negative implications of their decisions, unintended things happened (and some of them were pretty rough).</p><p>Black Mirror Brainstorms are intended to help us consider the negative impacts of our work. By doing this, we help ensure that our products are great and don’t end up causing harm. The unceasing march toward growth will often pull us in unexpected ways and it’s easy let any negative impact of our decisions fall by the wayside.</p><h3>Credit and thanks</h3><p>Adapted from <a href="https://twitter.com/aaronzlewis/status/1063544871472914432">Aaron Lewis</a> and Gamestorming’s <a href="https://gamestorming.com/cover-story/">Cover Story</a> activity. Thanks to Andrew Zusman, Christine Luc and Weiman Kow at Pivotal for the feedback.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f919ccf5938c" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/black-mirror-brainstorms-f919ccf5938c">Black Mirror brainstorms — a product design exercise</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[What I learned making my first VR app]]></title>
            <link>https://blog.prototypr.io/what-i-learned-making-my-first-vr-app-e6c19a160342?source=rss-bc1a780bd22b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6c19a160342</guid>
            <category><![CDATA[vr-design]]></category>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Joshua Graves]]></dc:creator>
            <pubDate>Tue, 08 May 2018 16:16:01 GMT</pubDate>
            <atom:updated>2018-05-13T15:52:40.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXpmVqUYLVDUVEYTKcAjBg.png" /><figcaption>Virtual Reality Experience by Mooms from the Noun Project</figcaption></figure><p>I recently made my first VR app for a client who commissioned an app to celebrate their 100th anniversary. In it, you walk through a 3D art gallery complete with with audio and imagery to understand their history.</p><p>Having primarily designed for mobile over the last few years, this was a fun new medium to explore. The new constraints and considerations were interesting, too.</p><p>For instance, I found typography worked a little differently here. Things like motion and interaction took on an entirely new form, too. Not only that, but the process for making VR apps were also a little different than most other projects. I’ll walk you through those here.</p><h3>Interactions</h3><p>We have two main ways of using VR apps: with <strong>our gaze</strong> or a <strong>controller</strong>. each method has something different to consider, but I’ve found that they both affect how you design in similar ways. Let’s start with how they affect interactive objects like buttons.</p><p>Apple recommends buttons have a 44pt minimum touch target size for apps. You’re going to want to go larger for VR. If you use Google’s VR framework, Daydream, it recommends a default size of 64pt. While that’s considerably bigger, I found that increasing the size allowed for much better usability.</p><p>If you’ve ever heard of Fitt’s Law, you’ll recall that one of its key points is to make important elements larger and positioned closer to someone. That concept goes double for VR.</p><p>VR environments, because of their immersiveness, make it easy to miss a button. If you’re using a controller, remember that it’s tougher to direct a pointer than it is to tap a button on your phone.</p><p>It’s fine if you want to focus on only using someone’s gaze to navigate. If that’s what you’re doing, show a timer or some other sort of progress bar when someone gazes on an interactive object. This makes it clear what will happen if someone keeps staring and it. Doing this also prevents accidental interactions. I’ve found that anywhere from half a second to one second for a timer is a good idea.</p><h3>Motion</h3><p>What makes VR so much fun is its immersiveness and movement. We have into two main areas to consider here: <strong>how your body moves</strong> and <strong>how you move around within the app</strong>.</p><h4>How your eyes and body move</h4><p>First, I’m really thankful for the work of <a href="https://www.youtube.com/watch?v=id86HeV-Vb8&amp;t=0s&amp;list=PLzag1H05l3TI7yiOpxg0OmB5bjv_hEC_J&amp;index=1">Mike Algers</a> and Alex Chu here because they articulated these principles so well. Here, we’ll talk about eye movement as well as body movement.</p><p>If you want someone to see something without them turning their heads, you’ve got about <strong>30º in any direction</strong>. Anything outside of that is out of focus and causes eye strain.</p><p>We can comfortably turn our heads about <strong>60º in any direction</strong> before our muscles begin to fatigue. Moving more than 60º in any direction can trigger motion sickness, which we’re keen on avoiding.</p><p>Its important to consider how far you’re making someone stretch themselves to use your app. Unless you’re making a VR app for yoga, remember that less stretching is better.</p><h4>How you move within the app</h4><p>The other type of movement is the motion someone experiences while using your app. While we can have more fun with snappy animations on desktop and mobile, we must be more considerate and delicate here.</p><p>Don’t vary your motion speeds here, this is a huge trigger for motion sickness. No one should feel like they’re on a rollercoaster (unless that’s what you’re going for). In general, opt for slower or instant transitions.</p><p>Most of my transitions take anywhere from 1–2 seconds in VR. That’s a much longer timeline than the 500 milliseconds most of my app animations take. It feels slower, but at least I’m not getting motion sickness here.</p><h3>Typography</h3><p>Reading…kinda sucks in VR. I have a really big interest in typography (so much that <a href="https://www.fontspring.com/fonts/joshua-mauldin/uptown-sans">I made my own typeface</a>), so I spent a lot of time understanding this.</p><p>There are two reasons why reading isn’t so great: <strong>our devices</strong> and <strong>methods of experience </strong>greatly vary.</p><h4>Our devices</h4><p>We have so many different devices capable of VR, all at varying resolutions and sizes. Some run at ultra-high resolutions, like the Galaxy S9, while others are at lower resolutions, like the iPhone. There are a few in between, like Playstation VR.</p><p>Because the resolution can vary so much, text can look blurry or crunchy. That’s especially true on lower-resolution devices.</p><h4>Methods of experience</h4><p>The other factor is the methods we use to experience VR. We can use anything from a head-mounted visor that straps to your head to a Google Cardboard that you hold up to your face. They both come with their own set of benefits and tradeoffs.</p><p>While holding something like Google Cardboard is the easiest and cheapest way to get into VR, what you gain in convenience you lose in comfort. Holding the VR device in your hands causes fatigue after a little while — we’re not used to sustaining that position. It also causes the experience to be a little shakier, which can cause eye strain and motion sickness.</p><p>The head-mounted visors are my favorites because they allow you to stay in the experience longer. You also get to use your hands if you want. These are generally a little more expensive than a Google Cardboard, which will be a barrier for some.</p><h4>So what can we do to have better typography?</h4><p>Downplay any kind of longer-form reading. Think about PowerPoint summary slides, that’s about the right amount of text to use.</p><p>Focus on infographics and imagery when you can, even if they’re simple. This helps communicate your message with much more clarity and makes for quicker scanning.</p><p>You will inevitably have to set some text in paragraphs (and that’s okay!). Here are some considerations:</p><ul><li>Use only medium-to-bold fonts. Even on high resolution devices, thin fonts look crunchy and hurt both legibility and readability</li><li>Make your default text size larger than usual. My starting point is about 24pts</li><li>Shorten your line length from 50–75 characters to 30–40 characters</li><li>Use as much contrast as you can with text, so consider setting your paragraph inside of a semi-transparent, dark background</li></ul><h3>Process considerations</h3><p>I haven’t encountered a designer-friendly environment for VR yet. The best thing you can do to get started is learn the basics of how to navigate within Unity and become good buddies with your engineer.</p><p>For a simpler experience, you could try Sketch-to-VR. You’ll need to realize that this is only to help you get a basic idea of what you’re building; the sizes and positioning won’t match your design 100%.</p><p>You’ll need to do a little work to test it out — it’s not so bad, I promise! <a href="https://blog.prototypr.io/sketch-plugin-sketch-to-vr-4e23ced47e6">Here’s how to do it.</a></p><h3>Wrapping up</h3><p>Clearly there’s a lot to VR, and a lot to be excited about. Best practices and patterns are still being worked out, but we know that we have to make different considerations for typography, motion, and interaction.</p><p>It’s my hope that one day a good prototyping environment will come around for VR, but the best thing seems to be to get close to your engineer pals here. Have fun!</p><h3>Resources</h3><ul><li><a href="https://designguidelines.withgoogle.com/cardboard/designing-for-google-cardboard/a-new-dimension.html">Google Cardboard design principles</a></li><li><a href="https://facebook.design/vr-template">Facebook’s VR Prototyping Template</a></li><li><a href="https://developers.google.com/vr/design/sticker-sheet">Google Daydream Sketch template</a></li><li><a href="https://www.youtube.com/watch?v=id86HeV-Vb8&amp;list=PLzag1H05l3TI7yiOpxg0OmB5bjv_hEC_J">YouTube VR Playlist</a> (I curated this, it’s got some great videos!)</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6c19a160342" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/what-i-learned-making-my-first-vr-app-e6c19a160342">What I learned making my first VR app</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>