<?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[It Depends - Medium]]></title>
        <description><![CDATA[An advice column about design and tech - Medium]]></description>
        <link>https://medium.com/it-depends?source=rss----9ac3bd4e117b---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>It Depends - Medium</title>
            <link>https://medium.com/it-depends?source=rss----9ac3bd4e117b---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:35:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/it-depends" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Should I Be A Manager or An IC?]]></title>
            <link>https://medium.com/it-depends/should-i-be-a-manager-or-an-ic-c78063878c7d?source=rss----9ac3bd4e117b---4</link>
            <guid isPermaLink="false">https://medium.com/p/c78063878c7d</guid>
            <category><![CDATA[advice-column]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[advice]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jon Bell]]></dc:creator>
            <pubDate>Wed, 04 Mar 2020 04:37:51 GMT</pubDate>
            <atom:updated>2020-03-04T04:55:49.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>From It Depends, an advice column about design and tech</h4><p>So I have this friend named <a href="http://allidryer.com/">Alli Dryer</a> who is a super impressive designer and thinker. She’s also kind, fun, and I-can’t-believe-she-just-said-that hilarious. Here is a representative example:</p><h3>Alli Dryer on Twitter</h3><p>smells like someone is smearing tuna fish on my personal face in here</p><p>We were internet friends for a few years before joining the same design team, and I was happy to note just how much everyone liked working with her. Not just peers, but people who she was leading through complex and political feature releases. (Those who were there, you know what I’m talking about.)</p><p>So you can imagine how I felt when she posed a question for this publication. She was curious to know the thinking around deciding to be a manager versus an IC, or “individual contributor.” This is a little like Serena Williams asking if you have any thought about tennis forehand technique, but here we go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LzyBX5q7STVudH1Aqn2gQg.png" /></figure><h4>Being a good designer is not a transferrable skill</h4><p>Just because you’re good at golf doesn’t mean you’re good at yodeling. Being good at identifying birds doesn’t mean you can write poetry. And just because you’ve mastered white space, composition, Sketch, Figma, and colour theory doesn’t mean you have any clue how to be a manager. They’re different things.</p><h4>In fact, it might make you a worse manager</h4><p>Most designers and developers get into their fields to <em>make things. </em>So you can imagine the upset they experience when “make things” gets replaced by “support other people who are making things” in their priorities list.</p><p>But oftentimes a new manager clings on to their old life. That leads to micro-managing people too much, because they wish they were back in the pixels. If they never find the satisfaction in management that they did in design, they’ll never put the time in, and they’ll never be great at it.</p><h4>Would you do it if it didn’t pay more?</h4><p>Twitter’s design team had a principle that people moving into management were not being promoted. The VP of design at the time wanted people to understand that it was a parallel path, not a better one. Not a more lucrative one. Just … another one. One that happens to focus on people.</p><p>And I think that’s a good way to put it in your own head. Would you love learning how to manage people if it paid exactly the same as an IC job that you already know you’re pretty great at?</p><h4>A book I enjoyed</h4><p>One of my favourite thinkers is a guy that goes by Rands in Repose. He has a book for ICs looking to be managers called <a href="https://randsinrepose.com/archives/managing-humans/">Managing Humans</a>. It’s for a developer audience, but I love his clear way of writing and I learned a lot from his book. I also love reading the essays on his site. (<a href="https://randsinrepose.com/dont-skip-this/">More here)</a></p><h4>A story</h4><p>I was leading a team that was designing the “incoming call” screen for Windows Phone. I had designed it out myself just to think about the UX, but it was formally assigned to another designer. He presented his work to me, and he found a different path than I would have chosen. I challenged a few of the tradeoffs and he had good answers. And that was good enough for me.</p><p>I told him <em>“It’s my job to advocate for you even when I don’t agree.”</em> What? Well, I think designers get in this trap of thinking “the way I would do it” equals “the right way to do it,” which leads to design managers that are really hard to work with because they don’t give enough autonomy. They’re the helicopter parents of tech, and their metaphorical kids suffer for it. Those unlucky designers learn less, experiment less, and often just feel like “hands” for the creative director.</p><p>But <em>everything depends</em> in design, and everything has tradeoffs. If you can watch a design go out the door that’s not necessarily the tradeoff you would have chosen, because you trust the designer and their thinking, that’s a good sign. It means you understand something that was an epiphany for me: when you become a manager, say goodbye to pixels. Your new canvas is your team.</p><h4>Summarise it for me, please</h4><p>You got it.</p><p>Understand that being a level 100 pixel master doesn’t change the fact that you’re going to start as a level 1 people listener. Let it sink in that some of the best designers you have worked might have been the worst managers. Think about management as a thing that pays zero dollars more, removes your ability to get your hands dirty, and keeps you in meetings all day. And if that’s still something that sounds good to you, great! Please skill up to be a manager, because we need more people like you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c78063878c7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/it-depends/should-i-be-a-manager-or-an-ic-c78063878c7d">Should I Be A Manager or An IC?</a> was originally published in <a href="https://medium.com/it-depends">It Depends</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Do You Win Support for Your Designs?]]></title>
            <link>https://medium.com/it-depends/how-do-you-win-support-for-your-designs-7085a8bb6992?source=rss----9ac3bd4e117b---4</link>
            <guid isPermaLink="false">https://medium.com/p/7085a8bb6992</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Jon Bell]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 06:20:38 GMT</pubDate>
            <atom:updated>2018-12-03T06:20:37.911Z</atom:updated>
            <content:encoded><![CDATA[<h4>From It Depends, an advice column about design and tech</h4><p>A few months ago a designer write a tweetstorm that started like this:</p><blockquote>“Now that Google+ has been shuttered, I should air my dirty laundry on how awful the project and exec team was. I’m still pissed about the bait and switch they pulled by telling me I’d be working on Chrome, then putting me on this god forsaken piece of shit on day one.”</blockquote><p>Nirawit thought it might be a good topic for It Depends. He clarified further:</p><blockquote>“I think one question would be: how do you win support for your design in an org where maybe people aren’t so supportive or enthusiastic?”</blockquote><p>It’s a great question. Many books have been written about this topic, and many designers have burned out because they couldn’t find a way forward on this. So. Let’s dive in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMvC-LDt5MkpPOWP0Cc4gQ.png" /></figure><h4>Stop Saying “I Hate Politics”</h4><p>Everyone in tech says they hate the politics that comes with the job. Well, not everyone. Just the people that fail, and people fresh out of school.</p><p>People often use the word “politics” as a shorthand for “collaborating across multiple teams, each of whom has different goals that you need to consider.” Most people take the phrase as high-minded and noble, with a dash of common sense. “We’re here to make something great,” they proclaim, as if making something great is somehow divorced from talking to humans.</p><p>Some people really believe this. Those poor, poor dears.</p><p>Step one to winning support for your designs: stop thinking that politics is a bad word. Stop thinking that talking to others is slowing you down. Stop believing that everything would be fine if everyone would just leave you alone long enough for you to make the world’s greatest design. That’s not how anything works. It’s not going to work at a corporation.</p><h4>Figure Out People’s Motivations</h4><p>The engineer wants to make something great but also has concerns about the quality of the code they’re being asked to deliver on a quick timeline. The product owner wants to make something great that can move metrics like new sales, or engagement stats, or whatever. The executive has the board breathing down their neck about executing a multi-year turnaround plan. Everyone has motivations. Figure them out and care about them.</p><h4>Directly Ask How Coworkers Like to Work</h4><p>When you join a team with a new person, take them out for coffee and ask them what they like to see out of a designer. Product owners all pretty much say the same thing. They want a designer with a point of view … that can also take other information on board, and even change their mind if warranted. Designers are famous for not caring about any aspect of the business other than the design, and their designs suffer for it. If you can be a designer that holds a high bar for design but also knows how to compromise, you’ll be in a good place.</p><h4>People Should Ask For You By Name</h4><p>At Twitter they give promotions based on five key areas. One is whether or not your coworkers ask for you by name. Some designers are a pain, so people ask not to work with them. The middle 80% are fine, so people are fine with them. But the top 10% are easy to find because people really love to work with them. How can you be one of them? Well, it depends. But it’s probably going to do less with your grid and typography choices and more to do with how you are to work with.</p><h4>Lay the Groundwork Early</h4><p>Once someone asked me how to save a work relationship after a year of fighting, and a week before a product was set to go live. This is like a couple going to couples therapy 3 days before divorcing. It might be too late.</p><p>Every new person you get to work with is a chance to build the best working relationship you’ve ever had. And the best working relationship your coworker has had as well. If you put in a lot of work up front, you don’t end up with giant fights later on. Build rapport. Listen. Care. Adjust accordingly.</p><h4>You Win More When People Enjoy Your Company</h4><p>Let go of the idea that your design is the right approach. Let go of the idea that only you can fight for the user. Let go of the idea that you have great taste, and the belief that if only they’d let you make more decisions, the design would improve. It’s simply not true.</p><p>Software design isn’t actually as mystical and complicated as we make it seem. Learning the tools and foundational skills isn’t rocket science. Anyone can learn it if they put in the time. But there is one surprising detail that it took me too long to learn. The single most important aspect of a designer, more than literally any other skill – even those twin red herrings of “passion” and “taste” – is if people actually want to be in the same room as them.</p><p>Get that right and everything else falls into place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7085a8bb6992" width="1" height="1" alt=""><hr><p><a href="https://medium.com/it-depends/how-do-you-win-support-for-your-designs-7085a8bb6992">How Do You Win Support for Your Designs?</a> was originally published in <a href="https://medium.com/it-depends">It Depends</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does criticism always need to be constructive?]]></title>
            <link>https://medium.com/it-depends/does-criticism-always-need-to-be-constructive-e17b59bf48b5?source=rss----9ac3bd4e117b---4</link>
            <guid isPermaLink="false">https://medium.com/p/e17b59bf48b5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Jon Bell]]></dc:creator>
            <pubDate>Sat, 13 Oct 2018 20:35:03 GMT</pubDate>
            <atom:updated>2018-10-13T20:47:17.236Z</atom:updated>
            <content:encoded><![CDATA[<h4>From “It Depends,” an advice column about design and tech</h4><p>Tom writes:</p><blockquote>Ken Kocienda (the writer of Creative Selection) and Linda Dong (previously a designer at Apple, now at Lyft) had a public discussion on Twitter last week about criticism. He said it doesn’t always need to be constructive:</blockquote><blockquote>“Steve Jobs one told me straight to my face that my work was “dog shit.” He wasn’t attacking me. He was saying my work wasn’t good enough yet. And it wasn’t. Criticism doesn’t need to be constructive to be useful in the long run.”</blockquote><blockquote>Linda did not agree:</blockquote><blockquote>“I’m sorry NO. One of the worst parts of my time at Apple was the toxic culture this line of thinking bred. Swearing at and insulting people’s work is not okay and is never helpful. Criticism for criticism’s sake is a power move.”</blockquote><blockquote>… and this sparked a bit of a rant and discussion.</blockquote><blockquote>I was wondering, what can you say about constructive/deconstructive feedback?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nxBLqdBQBmS2Go8XL3nXbA.png" /></figure><p>Great question. Let’s start with an extreme and work our way back from there. Does a marathon runner need to run forwards? Technically, no. If you chose to, you could run all 26.2 miles of a marathon backwards. You probably wouldn’t run as quickly. You probably wouldn’t win any records. But I guess there’s nothing preventing you from doing it, technically speaking.</p><p>In Steve Jobs, we happen to have a guy who successfully ran marathons backwards. But just as surely as you can run better if you’re pointing forwards, you will ship better products if you learn how to give better feedback. And now we have creative directors around the planet running their own marathons backwards, since Steve did. I wish they’d stop.</p><h4>The myth of brutal honesty</h4><p>The argument for cruel feedback goes like this: “Give it to me straight. I’d rather you say something directly than make me have to guess.” But no one’s talking about shying away from feedback or being vague. The question before us is if brutal feedback helps the design process. It does not.</p><h4>Case study</h4><p>I was leading the Windows Phone Apps team in 2012, and we got a request from China. They requested that incoming calls have a “respond with text” feature. By now the feature is widespread (China sent the same multi-hundred feature requests to all phone makers) but at the time we were thinking about how to design it from scratch. Here’s where we landed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h9JV0W2E7iCn_n9Ye_KwfQ.png" /></figure><p>I don’t remember all the twists and turns of the design. I forget what the designer came up with first, I forget what my exact feedback was, I forget if I agreed with the tradeoffs that led to this screen or not. But imagine you were TD, the fantastic designer that was assigned to this screen. Which would you rather hear me say if I had some concerns with your design?</p><ol><li>Steve Jobs approach: “This is dog shit.”</li><li>Constructive approach: “Awesome, thanks. I have some questions about how you arrived here. a) “Text reply” is the biggest and most easy-to-reach button, can you tell me more about that decision? b) I see we’re not bottom-aligning the buttons, meaning there’s a big gap there. Is there something we can do about that, or is it a technical limitation? c) Can you show me some explorations around showing the common text replies on this screen? Curious to know if there’s any way to make that work, or if it definitely needs to launch a second screen or modal dialog.</li></ol><p>I know that second option looks like I’m showing off and trying to prove a point. Sadly, this is literally the difference in quality that I see working in tech. Some people genuinely believe that #1 is an appropriate start to a critique. And #2 is a faithful reconstruction of how I try to give feedback. It should be specific, understanding, and leave space for the designer to explain.</p><p>“This is dog shit” fails on all fronts. Even if it’s followed up with very specific feedback, it’s already changed the entire dynamic of the discussion from “how can we best juggle these tradeoffs” to one of fear and failure.</p><h4>Moving beyond “don’t be a dick”</h4><p>I asked my questions to TD and he had answers for each. Let’s say they were:</p><p>a) “I needed a single design that would work even if ‘text reply’ wasn’t an option. Meaning always putting ‘answer’ on the left and ‘ignore’ on the right, which left the next row for ‘text reply.’ If I didn’t do it this way, I’d need two completely different designs whether or not the feature was supported, meaning it would affect muscle memory.”</p><p>b) “Yeah, that’s a technical limitation. I’ve been working with them to bottom-align it, but it’s like a webpage. We can position things really easily to the top edge, but predicting exactly where the bottom edge is, with hundreds of different screen sizes and an outdated tech underpinning makes this really hard. It will be bottom aligned on the Nokia phones, though.”</p><p>c) “We did explore having the replies on the screen itself but it was really cluttered. What we’re doing instead is a half-sheet control to emulate sort of how Apple does their popovers. And we’re only going to show 3 options there, but it’ll be customisable to more in Settings.”</p><p>We talked it through for a few minutes, me poking at different assumptions and considerations, him readily providing answers. He had done his homework. But here’s the thing. I still didn’t like the screen, aesthetically-speaking. But TD had a much better understanding of the issue and had worked through each of the ideas doggedly. So here’s what I heard myself saying, to much giggling in the office.</p><blockquote>“It’s my job to advocate for your designs even if I disagree with them.”</blockquote><p>I have an earnest and blunt way of talking, and it often leads to awkward moments like this. My team was giggling because my comment sounds a lot like “This is crap, but fine.” (They posted it on Twitter as an “overheard in the office” tweet) It wasn’t my intention to say it that way, so I could have picked my words much better. I apologised to TD but he just chuckled.</p><p>But clumsy and unhelpful delivery aside, I did mean what I said. As a lead to a skilled designer, it’s not my job to micromanage design tradeoffs and use people as a vessel for my creative output. It is my job to be a sounding board, make sure the design has been given appropriate care and consideration, and then get out of the damn way. It is my job to advocate and support my designers. Not make them ship the exact thing I would have shipped.</p><p>You can’t stop at “don’t be mean.” You have to fully lean into the idea that you’re not being asked to design features anymore. As a lead, you’re designing the culture and processes that let other people design the features. You’re there to use your experience as guardrails. You’re not driving the car. Sorry.</p><h4>The sad irony of that Twitter firestorm</h4><p>So the original post talked about Steve Jobs calling work “dog shit.” And Linda wrote back saying that she disagreed. It turns out there’s a lot more going on in the thread, and it’s a good example of how feedback can be shared well.</p><p>The thread continues like so:</p><p><strong>Kim Scott:</strong> “Here’s my perspective FWIW. If Ken didn’t mind being told that &amp; Steve knew that, then it was Radical Candor. Radical Candor gets measured at the listener’s ear not the speaker’s mouth. If Steve spoke to me like that it would be obnoxious aggression. I’d hate it, too. <a href="https://twitter.com/kocienda">@kocienda</a>”</p><p><strong>Ken Ocienda:</strong> “My reaction to Steve’s words was that I needed to make my work better. I didn’t consider it an insult. In my article, I wrote about the mutual feeling of trust I felt in that demo room. Take that trust away, and friendlier-sounding words could be much more hurtful.”</p><p><strong>Linda Dong: </strong>“Here’s a data point. I was also in a room with Steve when he told everyone a product I had worked on was one of our biggest fuck ups. I felt attacked, disheartened, insulted. You can never assume mutual trust.”</p><p><strong>Ken Ocienda:</strong> “I’m genuinely sorry. I remember being in meetings with you and your group, and I always considered it a privilege to see what you and your colleagues thought future products could be like.”</p><p><strong>Linda Dong:</strong> “Thanks Ken, I appreciate it.”</p><p><strong>Ken Ocienda:</strong> “Thank you Linda. When someone like you challenges me about something I’ve done or said, I worry that I might be completely wrong. Twitter can be a difficult place to figure that out.”</p><p>Wait, what happened? We can learn from this. Ken asserted something. Linda disagreed. Ken provided context. Linda provided context as well. Ken hears Linda’s perspective and does not minimise it. Linda appreciates being heard. Ken says he appreciates the challenge and says maybe he can learn something. This is all really good stuff! This is why these folks have done great things in their careers. They’re running the marathon forwards.</p><p>Meanwhile, the other 90%+ of the feedback I saw was — irony alert — just as poor quality as calling someone’s work dog shit. So there were people so mad at Steve Jobs’ harshness that they were super harsh with Ken. This is not a small detail or an odd little coincidence. This is the problem. People are really good at being awful with one another when they think it’s justified.</p><h4>Parting thoughts: context matters</h4><p>One thing that gets lost in the mix is how important context is. You speak differently to your drinking buddy than to your boss. Different to your mom than a sibling. And something that’s lost in this story is how Steve Jobs and Ken Kocienda had a close and trusting working relationship. Here’s a quote from his op-ed article:</p><blockquote>“But let’s be honest: Most of us swear. The key to making harsh words count is to have a trusting environment where everyone knows that comments are about your work and not about you.”</blockquote><p>I still disagree with cruel feedback. I still think Jobs’ “dog shit” comment was unhelpful. But what’s more cruel? Steve Jobs being blunt with someone he knows very well as a shortcut to making their work better, or hundreds of anonymous people on the internet attacking Ken’s character based on an article they didn’t bother to read and a comment they disagreed with?</p><p>Steve Jobs could reasonably argue that he was harsh with the goal of improving his team’s work. You can think that’s bullshit, or an excuse, or justifying sociopathic behaviour. But people on the internet angrily tearing down other people’s designs, opinions, and products have no such excuse. They’re not running a marathon. They’re not improving a product. They’re just yelling at each other. Many of us are. There’s no justification for this behaviour, and nothing good comes of it.</p><p>I wish we’d stop.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e17b59bf48b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/it-depends/does-criticism-always-need-to-be-constructive-e17b59bf48b5">Does criticism always need to be constructive?</a> was originally published in <a href="https://medium.com/it-depends">It Depends</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What should designers should do in their first few days at a new job?]]></title>
            <link>https://medium.com/it-depends/what-should-designers-should-do-in-their-first-few-days-at-a-new-job-9658ac5824a0?source=rss----9ac3bd4e117b---4</link>
            <guid isPermaLink="false">https://medium.com/p/9658ac5824a0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[advice]]></category>
            <dc:creator><![CDATA[Jon Bell]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 07:30:49 GMT</pubDate>
            <atom:updated>2018-10-01T20:20:36.127Z</atom:updated>
            <content:encoded><![CDATA[<h4>From “It Depends,” an advice column about design and tech</h4><p>Today’s question comes from Nirawit:</p><blockquote>I’ve heard you speak in the past about how you started a new job by introducing yourself to all your co-workers using a voiceover video. That is really cool.</blockquote><blockquote>My question is this: what are some things designers should do on their first few days at work to start off on the right foot?</blockquote><p>This is a great question, because starting a new job is a lot like kicking off a new project. Like, for example, an advice column. Such as the one you’re currently reading! And the advice is surprisingly similiar whether a new job or a new project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qhV_AqyRky-M8Wb8uOMbjA.png" /></figure><h4><strong>Understand your strengths</strong></h4><p>What works for one person might not work for another. Everything depends on context, and whatever you do should play to your strengths. For example, a voiceover video could work in some situations and backfire in others. Same with making a point to meet everyone on the team in your first week, or wearing a suit on your first day, or any other piece of advice. So step one is understanding how things seem to work best for you and your envrionment and leaning towards that sort of approach. Spend time thinking about this.</p><h4><strong>Note the gaps</strong></h4><p>Every person, or team, or company has things it’s better or worse at. Maybe you’re at a company that’s really good at selling boots but don’t have a very mature set of processes around design. Maybe your company has had a long track record making apps and now it’s struggling to move into wearables. See where the company needs some help to grow. Delight in everything that’s being done poorly, because those are places where you can make impact!</p><h4><strong>Bite your tongue</strong></h4><p>Designers are famous for parachuting onto a team and being overly negative about the current product, process, or team. I used to work with someone in Seattle who was infamous for doing this, and no one wanted to work with him. Surprise, surprise. Assume the people around you are aware of the problems you’re seeing, but also try to remember two things: they are your allies and they have knowledge that can help you if you let them. There will be plenty of time to judge and fix things later. When you’re new, it’s important to over-index on listening. Bite your tongue.</p><h4><strong>Frame things as solutions, not problems</strong></h4><p>Imagine some time has passed and you’re ready to start proposing ways to make things better. Be very careful not to point out a problem without a proposed solution. No one wants to hear “it’s crazy that we don’t have a wiki,” they want to hear “we’re going to be trialing a new wiki later this month, please let me know if anyone would like to help beta test it!” But getting there requires buy-in from your superiors. How do you get there? By listening well.</p><h4><strong>Listen well to build buy-in</strong></h4><p>Most things you want to achieve at a company are going to require someone agreeing with you. The way to get them to agree with you is to ask lots of questions and genuinely care about the answers. Sit down with your manager and ask “Hey, have we ever tried running an internal wiki for the team?” Maybe they have. Great. Ask “How did that go? What did we learn?” Take notes. Let their answers guide your response.</p><p>When you ask questions and stay curious, solutions have a way of presenting themselves. But when you lead with solutions (“We need a wiki”) and negativity (“I can’t believe we don’t have a wiki”) roadblocks spring up pretty fast. People want to be heard and collaborated with, not lectured to.</p><h4><strong>Be couragous</strong></h4><p>In some video games, you are invincible for the first few seconds of a new life. I try to keep that metaphor in mind when I start a new job. Sometimes it’s easier to push things forward when you’re brand new … as long as you’re curious, a good listener, and kind. It can be hard to find the courage, but the company hired you for a reason. Someone who is showing (good-natured) initiative stands out in a good way. But someone too afraid to offer ideas can get pigeonholed, which makes it harder and harder to raise your voice as time goes on.</p><h4>Don’t fall into the designer clique</h4><p>Designers have earned a reputation for being aloof and preferring the company of other designers. But in most modern design jobs, you’ll be spending far more time with your product managers and developers than your fellow designers. Act accordingly. Go to lunch with your engineering team. Learn the names of your PM’s kids. Build bridges outside the design team. And not just on a personal level: you should also try to learn about the business model of your company (lunch with a biz dev person!) and the tech stack you’re working with (coffee with a tech lead!)</p><h4>Get a “studio voice”</h4><p>It’s easy to disappear as a designer. Getting a “studio voice” means people know what you’re up to. You’re sending interesting links, sharing tips and tricks with the team, and so forth. It’s the digital equivilent of having a good personality. Everyone likes a good personality.</p><p>I’ve found that one or two messages sent in your first couple days can send a clear message that you have a studio voice and a digital personality. They don’t have to be anything special, but you do have to remember to speak up. You’re a designer, and it’s your job to communicate. Raise your studio voice.</p><h3>A second opinion</h3><p>This question has a lot of results on the web, including <a href="http://hrnasty.com/first-30-days/">http://hrnasty.com/first-30-days/</a>. Here’s what that essay says:</p><ol><li>Learn about the culture</li><li>Take voracious notes</li><li>Meet with your manager in the first week</li><li>Don’t piss anyone off</li><li>Make friends and influence people</li><li>If you make a mistake, admit it quickly and don’t make excuses</li><li>Watch and observe</li><li>Use spellcheck and one minute mail delay</li></ol><p>I agree with everything, especially meeting the manager. There’s a great book called <a href="http://beinggeek.com/">Being Geek</a> that I’d highly recommend to learn more about how to best work with your manager. And when people ask what my favourite design book is, I usually surprise them when I tell them. It’s <a href="https://en.wikipedia.org/wiki/How_to_Win_Friends_and_Influence_People">How to Win Friends and Influence People</a>. I recommend it to everyone I work with, and it is the most impactful book, by far, I have ever read about being a designer on a big team.</p><p>Hope that helps!</p><p>Jon</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9658ac5824a0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/it-depends/what-should-designers-should-do-in-their-first-few-days-at-a-new-job-9658ac5824a0">What should designers should do in their first few days at a new job?</a> was originally published in <a href="https://medium.com/it-depends">It Depends</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>