<?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 Y. A. on Medium]]></title>
        <description><![CDATA[Stories by Y. A. on Medium]]></description>
        <link>https://medium.com/@yamilah?source=rss-1713555e580d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0SoAF-MpGnY1Xh8nJesZDQ.jpeg</url>
            <title>Stories by Y. A. on Medium</title>
            <link>https://medium.com/@yamilah?source=rss-1713555e580d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:15:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yamilah/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[Dichotomous Designers and Where to Find Them]]></title>
            <link>https://medium.com/@yamilah/dichotomous-designers-and-where-to-find-them-6fbdb430314e?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fbdb430314e</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 02:11:00 GMT</pubDate>
            <atom:updated>2025-06-17T02:45:46.311Z</atom:updated>
            <content:encoded><![CDATA[<p>Something I’ve frequently noticed is that most content online for designers is aimed at beginners — it’s easier to give, and it feels good to help the people arguably most in need of it, and this is all true enough. Despite this, though, whether you’re just starting your design career or a few years in, there’s one mental model that can be a major unlock worth considering over the course of your design career: deciding whether or not you’re more of (what I call) a <strong>Business Designer </strong><em>or</em> an <strong>Artisanal Designer</strong>.</p><p>Rest assured, I will be sure to explain how this all works to the best of my ability but, first, you might be wondering what these two profiles even are!</p><h3>The Business Designer</h3><p>The experienced will not need much initiation on this profile, but for the less experienced: it’s the profile of designer your bootcamp (and most advice on Medium, Reddit, and LinkedIn) is modeled after and optimizes your career for.</p><h4>What do they work on?</h4><p>All kinds of stuff. One example that’s big with this profile is e-commerce, but that’s not all they can do: they’re everywhere, on everything! They might work on tools, checkout flows, notification standards, trust and safety, internal tools, settings, onboarding, and more. Truly, anything you can think of!</p><h4>Where do they work?</h4><p>All over the place. These can be found at “digital transformation” companies (e.g., Target, Walmart, insurance companies, banks, etc.), to unknown quantities (e.g., 50 person software companies), to large companies like Cisco, IBM, Intuit, Adobe, and Accenture, all the way up to teams at tech companies like Amazon, Facebook, Google and even on some of the Services teams at Apple.</p><p>Another note of importance: while most career advice is geared towards people in the States, this type of design profile is most in demand outside of it!</p><h4>What do they work with?</h4><p>They tend to use frameworks (UCD, UECD, Design Sprints, etc.), and use tools like Customer Journey Maps, User Personas, etc. They may use Figma, but also may use Adobe XD (though this is being phased out by Adobe), or Axure. They tend to work on webapps, and they usually deliver screens.</p><h4>What core values do they tend to share?</h4><p>These are the designers that cluster the most on topics and concerns like organizational empowerment of designers, as they often lack presence at their companies. They get a lot out of proving the ROI of design, and so they focus a lot on analytics and conversion rates, user research, following accessibility standards, and design systems.</p><p>They tend to work with Product Managers, Product Owners, Scrum Masters, and more. There tends to be a difference between UX designers and UI designers. They tend to get a lot of value from drawing boundaries between titles in their industries (UX/UI Designer versus Software Architect versus Product Designer, etc.), and have a lot to say about the importance of detailed case studies in interviews.</p><h3>The Artisanal Designer</h3><p>These are people who do not fit the above category; there are (almost) no entry level roles for these.</p><h4>What do they work on?</h4><p>True interaction and VFX in software. For these designers, brand and interaction are inseparable — complex visual effects define how the software works in a way that’s core to how the software is used. They may tend to work on social products and operating systems, but not exclusively: what’s important to note is that these are products that require technical and creative execution at the highest levels, and their brands are nearly indistinguishable in importance to the products that they build and sell.</p><p>These designers can be seen writing bespoke shaders, quadratic equations for very specific animations, and making unique materials in interfaces they work on. All of these things unlock new ways to use software, and new patterns for interactions never before considered. Their work is time-based, and screens are the smallest share of their work. Their engineers tend to be the ones building the APIs and platforms other companies depend on for success.</p><h4>Where do they work?</h4><p>Around 3 teams at IG, around 3 teams at Apple, a few spots at Figma, and some smaller companies like LoveFrom (purely as examples! — not an exhaustive list). Many of these designers also often <em>eventually</em> run solo, choosing to run their own studios, or consult with special project teams at larger companies.</p><p>These are teams nearly exclusively located in Manhattan, SF, and Cupertino and, to a <em>much</em> lesser extent, Venice (in LA), and some clusters in Europe. For the designers that run solo, they often are alumni from these teams, often having gone remote. There’s usually not much known about these teams outside of their immediate circles — this is <em>usually</em> on purpose (“iykyk” type beat; this actually helps with recruiting, ironically).</p><h4>What do they work with?</h4><p>These are designers that are highly technical — they tend to have significant engineering experience for this reason, and are often incredible visual designers. They may have custom scripts they’ve written in AE, tend to dream big in tools like Photoshop, and use Origami/Mica when making interfaces, often with bespoke JS scripts. On a daily basis, they may multiply matrices, write shaders, and make use of the Pythagorean theorem. They may tend to work with 3D as part of their interaction work. They tend to also touch a lot of hardware — not just software.</p><h4>What core values do they tend to share?</h4><p>They use words like “vision” and “point of view” a lot. On teams that employ these designers, they tend to run the show — this is not questioned internally, and is seen as the norm. Designers are expected to also be highly technical: write your own shaders, make your own materials, write your own animations, etc.</p><p>These people tend to be more like artisanal woodworkers: they know everything there is to know about wood, they sweat the small stuff, make their own tools, and quality matters more than anything. Titles don’t matter, people just do whatever it takes to execute their vision. Everyone is just a “designer,” and the work reveals what your unique superpower would be (are you a shader person? 3D person? Graphic designer in product? Etc.). No further title differentiation needed.</p><p>Everything is a demo, only output matters, there are no metrics or post-mortems, frameworks, and scarcely any formalized design systems (these are highly interpreted through each individual).</p><h3>Why any of this matters</h3><p>The sooner you decide where you want to end up, the faster you can figure out where to start. After all, getting started is always the hardest part! It doesn’t matter if you’ve got 8 days of experience, or 8 years: if you’re not sure where next to go, it’s a great exercise to consider where you may want to be in <em>some</em> future, clarifying the next steps you’ll need to take to get there. For example:</p><ul><li>If you are passionate about building interfaces for software that is involved in protecting minors from predators online, then a trust and safety team at a big tech company may be the perfect option for you! You may be a business designer</li><li>If you enjoy advocating for design, discussing the ins and outs of proving its ROI for companies, then a digital transformation company may be a great option for you! You may be a business designer</li><li>If you mostly care about vision, defining new interactions, and executing exhaustively, then you may be an artisanal designer</li></ul><p>There are lots of reasons to consider this model of the industry, but here are some (not an exhaustive list):</p><ul><li>Insight into your longterm economic potential, as these teams tend to compensate very differently</li><li>A natural guide on where to apply — for example, it wouldn’t make a lot of sense for a business designer to try to work on iPhone, or for an artisanal to work on webapps at Cisco or a bank</li><li>Clarity on the kind of work you’ll be doing every day (do you wanna write distance formulas, access light or gyroscope data while building novel interactions? Or run accessibility and design system workshops to uncover user pain points?)</li><li>More information about the kind of people you’ll be surrounded by every single day, what they tend to value, and what kind of work they tend to be impressed by — and expect — of their peers and reports</li><li>A sense for how big of an opportunity there is on the market. For example, if you’re a business designer, there are lots of job openings. If you’re an artisanal designer, there are limited positions, as there are simply fewer pieces of software that require artistry</li><li>Greater clarity on work-life balance. Artisanal designers (and artists, more generally) tend to have poor work-life balance and require significantly higher off-work investment, for example, so if that’s not for you, then the artist route may not be a fit</li><li>More detail on how these teams hire, and what they want to see — setting you up for higher hit rates!</li><li>Expanded ability to contextualize advice in the wild, helping you best understand what is most appropriate for your career (artsy types, I know this requires no explanation, but for the stragglers: neither LinkedIn, Medium, nor r/UXDesign are the optimal places for you to grow 🫶)</li></ul><p>A couple things to keep in mind when thinking about all this, though:</p><ul><li>Many people ask about this one! There is no “Instagram” or “Apple,” but rather specific teams at these companies. These distinct teams also almost feel like entirely different companies: for example, despite the marketing, <em>most</em> teams at Apple are best suited for business designers</li><li>These teams all have their unique cultures. For example, IG has great options for artisanal designers, but those teams have work styles and expectations that similar teams at Apple don’t. Even two artsy teams at IG have different norms!</li><li>Artsy teams represent the smallest market — once you’ve found one you want to work on, just be aware that it may take you a lot of time to be ready for it</li><li>The least visible teams tend to be artisanal teams — artisanal designers usually have worked with (or were, themselves) business designers, but the reverse is usually not true. As a result, business designers have a disadvantage on awareness</li><li>Always bears repeating: a job’s a job! You will have both very good and deeply bad days — even when you end up on the team you’re most excited about. Excitement is <em>so</em> key, but be sure not to idealize and obsess over anything too much! A chicken really ain’t nothing but a bird, after all</li></ul><p>The reason I think this approach is great is because of how helpful it is to start at the end and work backwards: the sooner you understand what truly makes your heart beat, the sooner you can take steps to getting there — and less time feeling stuck and spinning out.</p><h3>Some observations from the wild</h3><p>More “artisanal designers” are asserting themselves, though, I think. I’ve read many people talk about a “hard shift towards craft” in the industry, with posts like these stirring up controversy:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1lcJB25-ou5ejRsotOMycA.jpeg" /><figcaption>Did you notice the use of “point of view” here! No coincidence :)</figcaption></figure><p>What this kind of post does is demonstrates a signal to potential candidates, and to the designers internally: it draws a line in the sand, showing that leadership is committed to artistry, and that people who don’t share that value are probably not the right fit.</p><p>Lately, both Airbnb and Duolingo have also demonstrated a shift towards things like true prototyping and interaction work — the latter coming from the impact of people like Mig Reyes (ex Instagram). As you can see, human capital does matter, and culture does impact expectations!</p><p>The team over at Linear has had similar posts in the past draw up controversy, for the same reasons:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6NATfRusidaX6PGBRDY_Ag.png" /><figcaption>Notice the explicit call out to brand, and the usage of words like “taste” and “craft” and “building”!</figcaption></figure><p>These kinds of posts tend to awe and cause a stir among artisanal and business designers, respectively, highlighting their differing sets of values and interests. A few other things to note:</p><ul><li>The tenor of conversation that these kinds of posts stir on Twitter (notice that they’re always posted there!) differs very clearly from that which you see on LinkedIn — this demonstrates network effects across the internet when it comes to where artisanal and business designers hang out, respectively. So keep that in mind!</li><li>These posts, themselves, don’t cause massive shifts — they just formalize philosophies that already exist; they polarize the different types of designers. There are hiring and culture benefits to this</li></ul><p>If you’re feeling stuck in your career, your heart may naturally guide you towards “your people” — but, if it doesn’t, try to look at what people post! What someone says (or, sometimes more importantly, doesn’t say) is a great way to find your people.</p><h3>A more personal note…</h3><p>My heart’s always been in the artistry of it all, but I felt compelled to force myself into being more like a business designer — particularly at the start of my career. (I touch on that in <a href="https://medium.com/@yamilah/what-if-there-is-no-design-process-da0fe3ed060e">this</a> older article I wrote, if you’re curious!) Given how many roles there were available for this profile, I thought that was just “how it was,” and in workplaces, Medium posts, and conventions, the explicit takeaway was to curb artistic inclinations (peer pressure, in so many words). For many people, this works!</p><p>But it didn’t make me happy. It took me a while to notice other ways of working were even available — and then even longer to build the courage to just go for it! If I’d realized this sooner, I would have saved so many years painfully trying to override my natural predispositions, only to follow my heart, anyway!</p><p>The important thing to consider here, though, is that there really is no right or wrong decision: it’s your life, and you’re the main character of it. Also, these are just guidelines and general patterns I’ve picked up on — none of this is settled science, and your own conclusions are encouraged!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbdb430314e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designers, are you applying, but not getting bites? Do this.]]></title>
            <link>https://medium.com/@yamilah/designers-are-you-applying-but-not-getting-bites-do-this-2be6cf0ee63a?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2be6cf0ee63a</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-hiring]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Mon, 25 Mar 2024 06:29:03 GMT</pubDate>
            <atom:updated>2024-03-25T16:29:04.350Z</atom:updated>
            <content:encoded><![CDATA[<p>I stopped mentoring in an official capacity, but designers do still reach out and it’s hard for me to say no — while I’ve talked about portfolio suggestions to increase your chances of getting hired before, I’ve got a renewed desire to clarify this all in one place. If you’re applying to places as a designer but not getting responses, consider this list of things that could be amiss in your work.</p><p>Please note that this is a guide for designers that want to work at tech companies (e.g., Instagram, Apple, Clubhouse, Uber, Airbnb, Figma, Linear, etc.) — if you want to work at other companies (e.g., Cisco, Workday, Amazon, U-Haul, Target, Fidelity, Walmart, Bank of America, CVS, Adobe, Autodesk, LinkedIn), this list will still work, but being <em>too</em> good at craft <em>might</em> hurt your chances with these companies.</p><h3>Suggestion #1: push your visuals</h3><p>Tech companies care a lot about the craft and quality of the software they put out, and the quality of their software and their brand is reflected in their stock price. A drop in quality will reflect in market closings — even for private and small companies like Linear and Figma, a big part of their appeal is their regard for quality — a value shared both by employees, and their discerning customers. They hire people who will be likely to share this value, and steward their established baseline for quality, and they sell to people who care about this.</p><p>I put this at the top of the list because, when a recruiter/CEO/designer/design manager pulls your portfolio up and they see a lack of craft, they’re closing the tab immediately. As mentioned, they need people who have a regard for quality, and it’s not optional. If your portfolio site looks bad, the probability that your work looks better is vanishingly low.</p><p>Companies that are willing to negotiate on this are not likely to be your target employer (e.g., tech companies — especially on smaller teams, where every hire absolutely matters). Technical skills are very hard to teach, take a very long time to build, and are strongly tied to your personal drive. For some practical examples of what quality you should not be aiming for, consider these corporate websites:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*sHLXD3587G-msj54J4Hylg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vMDqSDjotqlkGYSDA8C4eQ.gif" /><figcaption><a href="http://pwc.com/">PWC</a> and <a href="http://intralinks.com/">Intralinks</a>. See also: <a href="http://cvs.com/">CVS</a>, <a href="http://cisco.com/">Cisco</a>, <a href="https://www.workday.com/">Workday</a>, <a href="http://amazon.com/">Amazon</a>, etc. This is the level of quality I regularly see in mentoring. This isn’t going to work.</figcaption></figure><p>Here are some random examples of what your north star should be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*VEekXK-SkQbvNg4H9XMaWA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*KYKZPFxaxVUnhIm0H6GocQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*wG8PH3LbWjBooqodtL9cLQ.gif" /><figcaption>This is what you should be shooting for. LTR: <a href="https://jeongsteph.design/">jeongsteph.design</a>, <a href="https://www.kwokyinmak.com/">kwokyinmak.com</a>, <a href="http://yamilah.com/">yamilah.com</a>. Notice that these all have traits like: unconventional layouts, color, type choices, interaction models, and so on.</figcaption></figure><p>If you find it difficult to produce this quality of visual work, you need to put your graphic designer hat on. Here’s how:</p><h4>How to improve your visuals</h4><p>Product designers at tech companies generally have to have strong visuals, and the visual, at its most pure, is the domain of the graphic designer. Dipping your toes into their line of work is, therefore, the fastest way to get good at this. Interface work is intended to be simple and with minimal effects, so practicing product visuals over and over again will net you fewer gains over time. Push yourself the hardest to make the fastest gains.</p><p>Check out <a href="https://pin.it/ML2vc17Zq">these</a> <a href="https://pin.it/54YzApbl8">posters</a> <a href="https://pin.it/WDQhWzrPV">and</a> <a href="https://pin.it/1m560DtMs">reproduce</a> <a href="https://pin.it/HMqbRgCg2">them</a> <a href="https://pin.it/19JO7rrZP">perfectly</a> <a href="https://pin.it/RSVzlhTk3">every</a> <a href="https://pin.it/5EDamHYsz">day</a>. Over time, work your own takes into these. Visual design is a technical skill and, as you can imagine, technical skills take time — there’s no way around having to do these reps every day. With enough time, you’ll develop a taste for excellence, and you’ll start becoming more and more independent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*Rp5WyX3U41PJGQiWgsKHEQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*Ffx_WOpyy2VUrIXkiLJAxw.jpeg" /><figcaption><a href="https://pin.it/54YzApbl8">Left</a> and <a href="https://pin.it/ML2vc17Zq">right</a>.</figcaption></figure><h3>Suggestion #2: push on your concepts</h3><p>When you finally get your visuals in order, you’ll need to have interesting ideas to use your dazzling technical skills on. Starting from the most important consideration, though: in your portfolio, you don’t need to show everything you’ve ever worked on.</p><h4>What not to include</h4><p>Here are some things you shouldn’t include in your portfolio:</p><ul><li><strong>Bootcamp prompts.</strong> Your bootcamp/university may have given you prompts for your portfolio, like: “Design a food delivery app for a bakery.” “Design a delivery tracking app for a sushi restaurant.” “Design a flower catalogue app for a florist.” “Design an order tracking app for a trendy florist.” “Design a menu and payment app for a beachside snack shop.” These are completely unrealistic ideas that no consumer would ever want — they will bore your panelists, so they should not be in your portfolio.</li><li><strong>Wesbite design.</strong> Your bootcamp/university may have encouraged you to work with a local business (coffeeshop, etc.) to make a website for them. You’re looking to work at tech companies as a product designer, not a website/graphic designer, so any website work should not be in your portfolio.</li><li><strong>App redesigns.</strong> Your bootcamp/university may have encouraged you to redesign an app. These apps have dozens — and sometimes hundreds — of designers, dozens of strongly opinionated leaders, and a CEO that’s highly invested, etc. The probability that you can redesign Instagram better than Instagram is low. You’re probably not as visually skilled, can’t create a great justification for why the app should be redesigned, etc. And if you do have a great idea that would justify IG being redesigned, why not just purify that idea into your own, new app concept and build it yourself? If your redesign looks worse, works worse, isn’t interesting, your panelists will know and this will count against you.</li><li><strong>Simple/generic flows.</strong> You may have done some work for a company on things like onboarding flows, or checkout flows, improvements to alerts and messaging, changes to settings in the app, etc. These are very simple flows and are not going to demonstrate your skill, so these should not be in your portfolio.</li></ul><h4>What to include</h4><ul><li><strong>Mobile app work.</strong> Since you want to work at a tech company, and most tech companies work on mobile apps (with some notable exceptions, e.g., Linear and Notion), you need to mainly show mobile work. (Remove any websites or simple web apps (e.g., e-commerce, settings, etc.).)</li><li><strong>Sensible, original, and interesting app/feature concepts.</strong> Original ideas that actually make sense, like: design a karaoke experience into Disney+, allowing parents to play and sing along with their kids. Design the ability to pair their phones with their smart TVs so they can use it as a mic and get a nice sing-along UI. When you have an interesting idea that actually makes sense, it’ll make conversation super easy and fun. People reviewing your portfolio will actually be authentically curious, your panelists will “get” it, and that makes talking about your work way easier. Better, yet, if the idea is actually interesting and different!</li><li><strong>Feature ideas, rather than app redesigns.</strong> As mentioned, I’d recommend building features you believe should exist into something that currently exists. This is usually a lot less difficult than making a whole new, novel app, and it’s what you’ll be doing in most of your career as a designer, anyway. E.g., that karaoke idea, a new feature built into D+, rather than a whole new, karaoke app. I’m sure those already exist, anyway. Create these concepts every day. See something you think would be fun/useful in Discord, Spotify, Medium, iOS, macOS, IG, Snap, etc.? Go and design it.</li><li><strong>Lots of iterations.</strong> Try lots of different executions on your ideas. It shouldn’t be that you make a few screens, and they should also be coherent, full flows that go from end to end. At the highest performing teams at IG and Apple, you’re going to be doing iterations until you’re blue in the face, so get the jump on that early!</li></ul><p>You should be concepting frequently and often. Think of a cool idea? Jot it down and save it for later. Keep a running list of ideas that you think of every day, pick your best three, and then go and make them!</p><p>(There are times when a company might find itself falling out of PMF and needing to completely reinvent itself and its app; if you’re a very skilled designer, you might be hired to help concept new app directions by companies in these situations, or you might work on a studio team at a big company where this happens in some capacity. But these are atypical situations and probably not something you’ll be doing early in your career, in the first place.)</p><h3>Suggestion #3: don’t stop at Figma</h3><p>This is a major unlock, but is difficult. While it has the highest return, it also has the highest cost to invest in — which is why I put it at the bottom of the list: you need to be prototyping. Once you start building complicated enough software, you’re not going to be able to get by with just simple, clickable prototypes you can make in Figma (or whatever you might be using, e.g., Sketch, Axure, etc.).</p><p>For example: the following are two concepts that are exactly the same, except with two different interaction models — left: TikTok style swipe. Right: Tinder style swipe. This interaction model, alone, changes entirely how the view is structure and how it works. Difficult to explain this with just screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*S63WZB1sL5eklaAErLAw-Q.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ykucniHiojW-CZrauLNf-A.gif" /></figure><p>Or, how about TikTok style swipes in stories? How would that change fundamentally how the feature is used? This is difficult to distill in just screens, alone. Changing just this interaction model completely changes stories in key ways: this opens up things like double tap to like, a whole new world that brings consistency to the IG stories universe! And so much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*SEiibWhaVVD8AfmjPu7W9w.gif" /></figure><p>I’ve talked about this at length in a <a href="https://medium.com/@yamtaro/what-is-prototyping-common-misconceptions-and-some-clarity-07cf468273ed">previous article</a>, but prototyping is an expectation at the highest performing teams in tech (e.g., IG, Apple, etc.). Very few designers in the world can prototype but, if you want to work on the best teams at IG, Apple, and etc., it’s not optional. If you want to get attention from the coolest teams out there, you’ll need to speak their language!</p><h3>TLDR</h3><p>If people aren’t hitting you back up, think of it like a sales funnel to hack: people are not converting into your pipeline, and they seem to be bouncing on the first step. People are bouncing at the first glance at your application. This strongly implies that this is due mainly to the quality of your work you show up with. Push the quality! And you can do it by:</p><ul><li>Improving your visuals</li><li>Concepting better ideas</li><li>Prototyping (bringing those ideas to life in a very clear and visual way)</li></ul><p>If you have, at times, gotten to further down the funnel (i.e., portfolio review stage) and it’s fallen off, this also strongly implies a quality problem that would be resolved by doing the above — what you share with your panelists during your portfolio review should be: (1) a deck, not a website, (2) visually high quality, (3) full of great concepts, (4) have some prototypes that clearly explain what your ideas are. If you’re sharing a website during a portfolio review, that’s not good. The website is a brochure you use while applying, and the deck is what you use to fully explain yourself while in the interview loop.</p><p>I realize that what I’m suggesting here likely means that, if acted on, you’d be restarting your portfolio. This has been the case with every individual I’ve mentored, and that’s most certainly over eighty people — I’ve sincerely lost track. You’re not alone in needing to reassess and reposition your work, though.</p><p>I know it’s a lot of work, but it’s what I’ve always done for myself — the advice I give is the advice I take, and the advice I’d give my dearest loved one. A lot of programs, bootcamps, and universities don’t prepare students to actually compete hard on the market but, being totally real, this is what it’s going to take.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2be6cf0ee63a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is prototyping? Common misconceptions and some clarity.]]></title>
            <link>https://medium.com/@yamilah/what-is-prototyping-common-misconceptions-and-some-clarity-07cf468273ed?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/07cf468273ed</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-engineer]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 21:15:34 GMT</pubDate>
            <atom:updated>2024-03-17T02:51:40.191Z</atom:updated>
            <content:encoded><![CDATA[<p>At the highest performing teams at tech companies, prototyping is not a nice-to-have, but an expectation. Most of them have bespoke internal tools just for prototyping, but only some of them make them public (e.g., Origami, by way of Meta). Prototyping is hard and so, naturally, few designers can do it. What’s more, most products are low-interactivity and do not require much interaction work. Because of this, I think there’s some lack of clarity in what prototyping actually is, and the term is often used in ways that have different meanings to different people.</p><h4>What does “prototyping” mean?</h4><p>“Prototyping” usually just means anything that demonstrates some complete user flow in a way that simulates the actual usage of the software in some capacity. So, instead of having screens lined up, some linear progression that shows a user going from point A to point B in some flow. This is usually to explain to XFN partners how some software should work, to pitch an new idea, etc.</p><p>This can range from simple clickable prototypes you can make in Figma, or less popular solutions, like Adobe XD/Axure (not sure if both of these are still around), all the way to highly detailed prototypes in Origami, to just straight up building the interface in SwiftUI or JS yourself.</p><h4>What does prototyping mean to most people?</h4><p>For most people, prototyping means a “clickable” prototype, like what you can make in Figma (or, extremely rarely, XD/Axure). These are simple prototypes that rely on simple conditionals and triggers, and they mainly do things like load another view, or hotswap some portion of a view with something else based on some simple trigger (a user taps on some specific element, etc.).</p><p>Figma has an additional feature called “Smart Animate” that allows simple <a href="https://en.wikipedia.org/wiki/Linear_interpolation">lerps</a>, allowing users to transition properties of an object on the canvas (e.g., a button transitions linearly from gray to blue when a field is filled). This is very simple and, for most people and products, is just fine, as most products are low-interaction and very simple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*lMmfN_gNwHGOKhG0r_mnhA.gif" /><figcaption>This is a pretty simple, clickable prototype made in Figma. This is the kind of thing you can also make in Sketch/XD/Axure, or whatever simple prototyping tool of your choice.</figcaption></figure><h4>What does prototyping mean to <em>other</em> people?</h4><p>For others, prototyping means building a truer-to-life interface simulation, either in something like Origami or, in the truest-to-life, something like SwiftUI or JS. This is not <em>just</em> for funsies (but it is funsies) — this is because the product necessitates this.</p><p>Something like Medium, Slack, or Airbnb are very simple products, on the whole. They are text editors, simple messaging interfaces, and hotel book software that don’t require a ton of interaction work — mainly simple taps, maybe some drags (e.g., duration pickers for dates), and other simple interaction models like this.</p><p>But consider your phone: it has far more complex interactions. It doesn’t have a physical home button, so the way you get to home is by swiping from the bottom. It doesn’t have a “task manager” app, so the way you manage executing processes on your device is by swiping from the bottom while holding. You’ll notice it responds to the exact acceleration of the user’s finger — so if you pull from the bottom very slowly, the task manager animates in very slowly until you feel some haptic feedback that tells you you’re in task manager mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*YYwbeh9fjHltbnwigeg8-A.gif" /><figcaption>Instead of a standalone “task manager” app, managing processes on your device is now behind a gesture, which impacts how the phone is navigated at a core level. The haptic and gestural feedback when going into this experience and closing processes, alike, “feel” right.</figcaption></figure><p>Another example: NameDrop on iOS. You can hold your phones together and swap contact info. As you hold your phones together, a continuous wave appears that goes from phone to phone, and shows you when the process is complete. It’s beautiful, but it also functions as a loading state that clarifies what is happening across your devices and gives user feedback for when the process is under way, and when it completes. This is not just for fun — it’s not just skin deep. You can imagine a loader appearing abruptly — this can feel broken and stilted. A wave moving across your devices communicates clear progression and process status. When you’re standing around awkwardly trying to get someone’s number, this makes it <em>way</em> less awkward. (It is also not a minor detail that it’s beautiful — as it should be!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*oZaxHJOrZ9PnQa-f09WAbw.gif" /><figcaption>NameDrop at work!</figcaption></figure><p>There are other interactions on your phone, but consider that the above examples I provided are (1) core to how some functionality on your phone works (read: not decorative), (2) more complex than simple tap triggers (compare <em>swipe up + longpress + specific y position = trigger is set to true </em>to <em>tapped on a button = trigger is set to true</em>), and (3) are very gestural, and they have substantial consequence for the core structure/“information architecture” (as some call it) of the device, from digital to physical (e.g., removing the physical home button in favor of a swipe gesture means the hardware is totally redesigned, and also fundamental aspects of navigation on your phone has to be completely redesigned).</p><p>Engineers at Apple are not the ones building and simulating these features and their interaction models — designers are.</p><h4>Is prototyping making animations (e.g., microinteractions)?</h4><p>For people who do not prototype, this is a common view. But, as shown above, this is not the case. Making beautiful and refined work is an important part of design’s responsibilities at the highest performing teams in the world but, again, animations are just one part of prototyping. Animations have to feel high quality in order to create clear user feedback (e.g., pulling from the bottom of your phone to return home isn’t abrupt and jarring, it accelerates based on the user’s <em>y</em> position, or the slow shader effect that loads from phone to phone when NameDropping — which feels more clear and intuitive in both cases).</p><p>All of these decisions add up to an experience that feels reasonable and clear, and also impact significantly how you use your phone. You’ll notice that fun checkbox animations (classic example of a microinteraction) are atypical in iOS or Android — decoration for the sake of it is not common because it can sometimes distract from quick work and create too much visual noise.</p><p>Prototyping is more than microinteraction work and, in fact, tends to not be common among the most skilled prototypers. Prototyping, in its truest sense, is mainly used when you work on a highly gestural piece of software that is too difficult to explain in simple images. These gestures are not fun, optional things — they are core to how the software works (again, consider Tinder’s left/right swipe gesture — it’s fun, sure, but it has fundamental consequence for how the app is used and how dating on these apps works today).</p><p>This kind of complex prototyping (complex triggers and all) is known in engineering as <a href="https://en.wikipedia.org/wiki/Signal_processing">signal processing</a>. This involves taking signals that fire from various triggers you’re watching, and then synthesizing them into logic gates you use to trigger other things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hv-VQr8B6nFGQup0lEYDjQ.png" /><figcaption>You can see an example of some fairly complicated signal processing here. I’m watching for an element (“Card 1”) to emit a pulse when “Downed,” and also emit a pulse when it isn’t — synthesized together into a logic gate that emits yet another pulse, and then synthesized with a “Drag” watcher, which I use to pull the dimensions from a 2D translation.</figcaption></figure><p>Or, consider TikTok: gone are the days of simple taps to bring up a video to watch — now, watching on TikTok is all behind a flick gesture. This decision to make watching more gestural had a substantial and core impact on its adoption and usage, leading it to be one of the rare breakout apps in a time when this is becoming almost vanishingly rare. It’s a mistake to believe that things that are fun, refined, elegant, or beautiful are “frivolous” and that this is all a “function of visual design” or “production design.” A simple gesture completely transformed the watching experience for TikTok. Simplicity that hides complexity is deceptive — it can be lost on those with little prototyping experience, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*HyWQWpIPk-zPJIR6mTDn5w.gif" /><figcaption>It’s a fun experience that reduces all the friction behind what to watch. It’s as simple as changing the channel back in days of yore!</figcaption></figure><h4>TLDR</h4><p>For most, “prototyping” means simple conditionals set up in Figma/XD/Sketch/Axure. In Figma, <em>if</em> statements happen on the artboard level — in Axure, that can be done, but also some <em>if</em> statements can reload just parts of an artboard. Either way, the mechanics and limitations are exactly the same, and neither provide complex conditionals allowing for things like Tinder card drags, or asynchronously running animations alongside other triggered elements (e.g. something continuously rotates while a user drags on something). This is just fine for most software — even Medium. It’s a simple web/native app that mainly works with simple tap targets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*2tMMOSVPP6HgLbYcCq3wAQ.gif" /><figcaption>Even something like a drag gesture for repositioning in a user’s story while a talking head bounces (demonstrating that a user is talking!) can’t be done in something like Figma/XD/Axure. The dragging is happening dynamically while a random seed feeds into the scale of the avatar, while the user can tap and completely swap the orientation.</figcaption></figure><p>But, as you go deeper into your career and work on highly gestural software (e.g., Instagram stories, reels, iOS, macOS, etc.), you can’t get away with simple, clickable prototypes anymore.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*_kPP0dGkTxpx03YAszibtw.gif" /><figcaption>Notice that the position, rotation, and scale attributes change based on the user’s drag position. Also notice that hint text is toggling while the mic button pop animates in. None of this is possible in Figma/Axure/etc.</figcaption></figure><p>In my own work, I’ve found that it’s impossible not to prototype, given that I work on very heavily gestural products, and I tend to select for products that require this kind of work. The “information architecture” and other core aspects of this kind of software are inextricable from interaction work — there are no “Motion Designers” I can rely on to do this work for me, it’s all me, as it’s core to the feature’s functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ykucniHiojW-CZrauLNf-A.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*S63WZB1sL5eklaAErLAw-Q.gif" /><figcaption>This is the same feature, but the “information architecture” of this view is completely impacted by the difference of a <em>single</em> interaction model (Tinder swipe versus TikTok swipe).</figcaption></figure><p>At some point, you need to start crossing into engineering territory — whether you like it or not! As a designer friend over at Apple Maps said: “the job of the designer doesn’t end in [Figma].”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3Eb9cFM9KIxUoHJkYNurYg.gif" /><figcaption>Making audio consumption experiences better involves things like on-the-fly subtitles. Hard to communicate how important that is to the listening experience without showing it. Also in this prototype is a bouncing head that makes clear to the user who’s talking — this is in sync with audio spikes, and is running while the subtitles reveal themselves. Not shown here is the ability to scroll this while this all happens. Impossible to do in Figma/etc.</figcaption></figure><h3>FAQs</h3><h4>Is Figma/Axure/XD/Sketch prototyping an example of prototyping?</h4><p>Mentioned earlier! Yes, but the simplest possible kind of prototyping. As mentioned, this will do for most software products, as most software is not gestural/interaction-heavy, and this is totally fine. This is especially true if you mainly work in e-commerce, or web apps, etc. The more you get into mobile territory, and the more you get into entertainment/social, the most you lose the ability to use simple prototypes.</p><h4>Is Figma/Axure/XD/Sketch prototyping an example of programming?</h4><p>No! Though they offer conditionals (e.g., <em>if</em> statements and some stored values) and this is something all programming languages allow for, but this is not what establishes something as programming.</p><h4>Where can I learn to prototype?</h4><p>Most prototyping tools at the highest performing teams are internal and, therefore, not externally available. But Meta externalized theirs (<a href="http://origami.design/">Origami</a>). You can also just go straight to rolling your own using SwiftUI or JS, if you like. This is probably better, longterm.</p><h4>Should my company be encouraging prototyping?</h4><p>For most, the answer is most likely no. But some exceptions can be made under these conditions:</p><ul><li>You want to cultivate a “high-design” design brand</li><li>Your software is very gestural and difficult to get right without simulating complex gestures</li><li>You generally care about the small stuff</li></ul><p>If you work on a webapp, or e-commerce, etc., you won’t really need this, and it’s probably overkill unless something in the above list is true.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07cf468273ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How design (generally) works at tech companies: Reloaded]]></title>
            <link>https://medium.com/@yamilah/how-design-generally-works-at-tech-companies-reloaded-e8ee97f00025?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8ee97f00025</guid>
            <category><![CDATA[tech-companies-culture]]></category>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 06:35:24 GMT</pubDate>
            <atom:updated>2024-03-16T19:45:02.797Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey, everyone! Rearing my head again to post.</p><p>In a <a href="https://medium.com/design-bootcamp/how-design-generally-works-at-tech-companies-36c591ac4744">previous post</a>, I talked about how tech companies are generally run. In that opinion, and in some a <a href="https://medium.com/@yamtaro/whats-a-tech-company-anyway-c79f6daa055">follow-up</a> <a href="https://medium.com/@yamtaro/ux-design-is-over-online-opinions-in-an-offline-reality-de8710ba9860">posts</a>, I discussed the importance of appreciating the differences between what I call “software companies” more generally, and “tech companies,” or a specific subset of software companies. While I’ve talked about the ways that they differ in previous posts, I want to get into more detail about what this looks like by way of common misconceptions seen at software companies that do not map to tech companies.</p><h4>Myth 1: There are UI designers, and there are UX designers</h4><p>If you’re at a software company, you might see that, at your company, there is a fleet of UX designers, and a fleet of UI designers. You won’t see this at tech companies.</p><p>When you’re hired on to a tech company, you are expected to reason about optimal user journeys, while also crafting them in a way that is high excellence and matches the company’s visual “voice.” Tech companies tend to be very particular about the brands and marketing they cultivate (Apple is a classic example of this), and so the expectations are high that you are able to create usable things that match the visual execution expected at that company.</p><p>When the word “designer” is used at a tech company, it refers to someone who designs optimal user experiences in a visually excellent manner. There are no “two kinds” of designers. This is usually shorthand for “Product Designer” (Meta, Snap, Linear, Figma), but you might see other terms used at other companies (some bespoke terms, like “Experience Designer” at Airbnb, or “HI Designer” at Apple — these are all used interchangeably, however).</p><p>If you’re hired at a tech company as a designer, it’s because you meet a certain threshold of excellence in optimally designed experiences, visually crafted in a professional manner.</p><h4>Myth 2: There are UX designers, and there are strategic designers</h4><p>If you’re at a software company, you might notice that there are people with titles that have words like “strategist” in it, and those designers “design strategies,” and “UX Designers” typically do not. Like UI and UX designers, these are considered separate responsibilities.</p><p>This is not the case at tech companies. When you’re hired on to a tech company, especially if you’re higher in level than a new grad, you’re expected to make meaningful contributions to the roadmap — at some companies (e.g., Instagram, some teams at Apple, etc.), you entirely control it almost exclusively, as a designer. PMs either take second fiddle to design in these contexts, or are, at most, at parity with designers. Design can veto anything, especially when combined with the outsized power of design leadership, which is typically the hulking, six-hundred pound gorilla at the company.</p><p>In fact, being able to reason and strategize about what consumers want and come up with novel offerings on your own is something expected of all employees at tech companies. This is considered a baseline skill among all tech company professionals on core product teams.</p><p>At a typical tech co, designers are often paired up with an PM (at the least), and sometimes even with an EM (engineering manager); you guys work together to come up with the most interesting and impactful ideas that fit into your designated product area. On the highest performing teams, designers are constantly working on creating novel ideas, and executing them to the highest level of fidelity via complex product demos.</p><p>But this can vary, too, somewhat — at most teams at Apple, for instance, there aren’t PMs (this is just part of their culture). At IG, PMs tend to play second fiddle to designers, but not always. At Clubhouse, the CEO has the most sway on product direction, and bounces ideas off the head of design and head of product.</p><p>If you’re hired on to a tech company as a designer, it’s because you are able to reason about what consumers want, then execute on this optimally, and in a high-craft manner. Regardless of how you feel about this debate, if you want to work at a tech company, you will be evaluated on three axes, the minimum: product thinking (strategy), functional execution (the actual functionality, how the thing works, etc.), and visual execution. At IG and some teams at Apple, there’s an additional expectation: prototyping (typically involves programming).</p><p>Designers are not a “service” internally at these companies — they have outsized deciding power, especially true at the largest ones.</p><h4>Myth 3: Research is very uncommon, or very common</h4><p>This depends on the size of the company, and also its culture. If you work on iOS, you’ll not work with a researcher. In fact, you might hear designers there say things like: “there is no place for researchers on product development.” If you work at IG, you’ll almost always be paired with a researcher (also other roles, like content people, data scientists, and maybe even more, depending on your situation). You might even go on lavish research trips interviewing real users in foreign countries for weeks with translators and all.</p><p>At Apple and IG, I never saw “usability testing,” I only saw concept testing. That said, pitching and roadmapping is usually intuition-based, and usually comes from design, even at IG.</p><p>At small tech companies like Clubhouse or Abstract, there’s usually almost no research done, and pivots are frequently intuition-based, and the CEO is the final decider. The presence of research typically varies considerably at tech companies.</p><h4>Myth 4: Data is rife, or not at all</h4><p>Similar to #3, this is highly variable. At Twitter, analytics dashboards were pretty uncommon. Most decisions were highly intuition-based. At IG, while most decisions are still intuition-based at the concepting and roadmapping stage, before anything is permanently shipped, they are rigorously A/B tested across multiple countries, over and over, until we are confident the metrics we care about are at least neutral before truly shipping.</p><p>At Abstract, we had no customers on the new offering, so no analytics were available, and the focuses were entirely intuition-based. At Apple, you will probably never see analytics.</p><h4>Myth 5: Design is “overlooked” and kept out of high level discussions</h4><p>This connects back to #2. At tech companies, designers often even have outsized presence in deciding strategy and execution, which is usually the expectation, especially if you aren’t a new grad (in which case, usually, the standards on this are somewhat relaxed and other XFN partners, or your manager, might help out more on this).</p><h4>Myth 6: You just change colors of buttons</h4><p>When you work on a high performing team at a tech company (e.g., IG Stories, Reels, iOS, macOS, etc.), you are going to do the hardest work of your life. The features you make are going to be the biggest ones you’ve ever worked on, with the most iterations you’ve ever made, and every large strategy detail will be scrutinized, and every detail and pixel will be criticized.</p><p>Your Figma files will become unmanageably large. If you are on one of those listed teams, you are going to likely be prototyping, meaning that you’ll also be making product demos for pitching, and this is done via node-based visual programming tools (e.g., Origami), or via actual programming frameworks (e.g., SwiftUI).</p><h3>Frequently asked questions</h3><p>I saw an article once that asked a lot of great questions that feel relevant to the above section, so I’ll just bring these together. I’ll answer them using my experiences at many tech companies I’ve worked at:</p><h4>Is UX allowed, if not encouraged, to do strategic work?</h4><p>This connects back to a few points above, but yes, and this is even <em>the</em> expectation of designers at most tech companies (provided you are not a new grad — but, if they have the aptitude, even they can throw their hats in!).</p><h4>Who plans UX’s time and priorities?</h4><p>You do, but you have to work in lockstep with general time expectations. You usually have seasonality in your work — at Airbnb and Instagram, you work on a biyearly basis (roadmapping done every six months, with the expectation that most things are finished within those six months); at the highest performing teams at Apple, it’s yearly, and you’re racing to get everything in to meet that time.</p><p>So, with this in mind: you typically have to work backwards from the important dates the rest of the org operates on and function in that seasonality, so there’s that constraint. Then, depending on the size of what you’re working on, there are general expectations around turnaround — for larger features, that might be about two months. It just depends on what you’re working on, and what the seasonality at your company is, as mentioned earlier.</p><p>If you work at a small company, there probably isn’t any seasonality, so you probably pick up work as it comes up organically. Some features might be super straightforward and might take a few hours to make, others, weeks. At the largest, highest performing teams, you usually take on very large bodies of work (with smaller things sprinkled in) that take enormous amount of iteration and revision work.</p><p>If you work on something much larger at a smaller tech company, like general direction of the product (e.g., Clubhouse and its renewed search for PMF), this might take longer and be more exploratory. Again, depends on what you work on. Your manager probably has some expectations, just make sure you’re aligned.</p><h4>Did we give UX access to the users or customers they need to research?</h4><p>Meta (and companies like it) probably has, per capita, the largest research budget of any software company, so the answer there is yes. At many teams at Apple, research doesn’t exist, and intuition rules, so the answer would be no, but that that’s never been how the company works, anyway.</p><h4>Do we wait for UX’s work?</h4><p>Yes, but usually engineers can build out some scaffolding ahead of time. Sometimes, they might buy you some time with what’s called “bridge work” at IG to keep engineers busy, working on bugs or other things from the last half. Nothing goes out if design doesn’t approve it, however.</p><h4>Are we “democratizing” other roles, or only UX?</h4><p>It would be impossible for an XFN partner to do what designers do at IG or Apple! These are extremely technical roles. You don’t even have to imagine the confusion of a PM (or even your design manager) opening Origami and trying to figure out how to draw one (1) rectangle! (Respectfully. Hard tool to use, I get it.)</p><h4>Can a UX professional make a UX decision?</h4><p>Yes, at tech companies, design ICs and leadership are the only ones that do this.</p><h4>If we’re using a trio, is UX part of it and truly empowered?</h4><p>Yes, see above.</p><h4>Is UX treated as the many specialties that it is?</h4><p>Designers are expected to be competent in product thinking and execution, these are not seen as separate roles or specialties. You need to think of great ideas and execute well — all on your own.</p><h4>Are there CX roles at tech companies?</h4><p>I’ve never seen one.</p><h4>UX is diluted, minimized, and disempowered. What do we do?</h4><p>I’ve never seen this at a tech company. If this is happening at your software company, there could be a few ways to see about solving this that might be specific to your situation — generally, though, this entails either accepting what you can’t change (that design plays second fiddle to everyone else), or changing your situation (e.g., going to a tech company).</p><h4>How do I sell the value of design at my company?</h4><p>Mentioned above, but this is already a given at tech companies. There might be strategies that are worth trying depending on your very specific situation. <em>But</em> you might not be able to win this battle, so a tech company might be best fit for you.</p><h4>Do you use a work methodology (e.g., agile, waterfall, sprints, etc.)?</h4><p>I’ve never seen this at a tech company.</p><h4>Do you use Jira, or some other ticketing systems?</h4><p>I’ve never seen this at a tech company.</p><h4>What do I do if my engineers don’t implement the quality that’s been agreed upon by design?</h4><p>This could be a mistake on their part, so it’s worth talking to them about it. They can learn to be more careful next time! However, this can also be fundamental to the culture: at some software companies, quality is not of importance. If you find that this is your situation, your solution is most likely that you should leave. You’re in a situation where your idea of what excellent software is does not align with the companies: so either you change, or the organization changes.</p><p>Realistically, what do you think is the most likely outcome here? Sometimes, you have to agree to disagree — not always a good culture fit so, depending on your situation, I’d recommend you try working at a place that aligns with your values (e.g., pretty much all tech companies).</p><h4>What do I do if PMs come up with all the ideas, and there’s never any space for my ideas, as a designer?</h4><p>If the ideas are higher quality than yours, then it’s worth learning to improve your product thinking, and this is probably for the best. However, if their ideas are low quality, growth-hacky, generally just bad, and you are rightfully frustrated by this, then the above advice from previous sections applies: either you accept that this team values product as the final deciders on where ideas come from, regardless of quality, or you somehow change the company. You have to decide what battle you think is worth fighting.</p><p>Something you can try is making decks showing a list of incredible ideas you’ve concepted and prototyped on your own time (using Origami or some other equivalent tool), and pitch to whoever you can (your manager, or your CEO, or whoever you have access to with deciding power) in order to build credibility and build hype with. If this doesn’t work, then either your concepts and the execution weren’t compelling enough, or they were great, and your colleagues are territorial or something like this, and you should probably work at a tech company.</p><h4>If tech companies index heavily into intuition, how do they make good decisions?</h4><p>You just do. This is a combination of hiring only the most experienced people and retaining them for very long periods of time, and having consistent leadership with deep knowledge in the area. High quality opinions are easier to come to fruition in this setup.</p><h4>Do high performing teams hire juniors?</h4><p>No, almost never. Junior designers are exceedingly uncommon at IG, Airbnb, and others, and do not exist on the highest performing teams at Apple. There are, at times, limited spots at IG for new/soon-to-be grads, but these are mainly engineering roles. Those with junior-level skills are extremely rare (or nonexistent), particularly as you scale up the highest performing teams in the tech industry.</p><p>Junior designers are generally not defined by YOE (though this can impact pay expectations) — at tech companies, this is defined by level of skill, stack racked against the skill quality on the existing team. For example, a junior level designer at the highest performing teams at IG is likely to be ranked as a staff level designer at legacy companies. It’s all relative to talent on each team, but the basis is on hard skills.</p><h3>TLDR</h3><h4>You might be a good match for a tech company if you:</h4><ul><li>Want control over your roadmap</li><li>Enjoy excellence in all things (craft, strategy, and functionality)</li><li>Want to see for yourself how the sausage is made</li></ul><h4>You might be a good match for a high performing team at a tech company if you:</h4><p>…Have all the above, and:</p><ul><li>Are intrigued by programming skills needed to make advanced product demos</li><li>Are obsessed with getting everything right</li><li>Don’t mind constant iterations for months on end</li><li>Want to be on the hook for everything— from strategy questions down to the pixels</li><li>Want to pitch constantly to leads</li><li>Are really good at making product and strategy decks</li><li>Don’t mind picking up the work that PMs typically do</li><li>Want to do the work of your life</li><li>Want to take on very large features on the highest profile surfaces on earth</li><li>Wouldn’t crack under that pressure</li><li>Don’t mind very poor work-life balance</li><li>Aren’t religious about any specific process (you won’t find it at that tech company)</li><li>Can work very fast</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8ee97f00025" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“UX Design is over”: online opinions in an offline reality]]></title>
            <link>https://medium.com/@yamilah/ux-design-is-over-online-opinions-in-an-offline-reality-de8710ba9860?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de8710ba9860</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[tech-industry]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Sat, 25 Nov 2023 03:35:13 GMT</pubDate>
            <atom:updated>2023-11-25T03:35:13.647Z</atom:updated>
            <content:encoded><![CDATA[<p>Over my career, I’ve noticed something that’s always interested (and confused) me: online, there are lots of strong opinions argued about how design should be done, but they never (or, charitably, almost never) apply to my day-to-day work. And, if not for the internet, I’d also never (or, charitably, almost never) hear these strong opinions represented in my day-to-day, either — not from colleagues, managers, nor anywhere else in my daily life. And this is precisely what I want to explore in this article: <em>why</em>?</p><p>But I want to be clear: my motivation in writing this opinion piece is <em>not</em> that I do (or don’t) want those opinions to be shared — it’s that, despite the forcefulness of the opinions concerning correctness in how one “does” design, it all seems entirely unrecognizable to my daily life (and, cumulatively, the entire arc of my career), and I find this very confusing. This is never more obvious than when I spent some months mentoring heavily: every mentee told me they’d never heard of my advice before, and I’m not the only mentor who’s talked about this. What’s more, with every passing year, these aforementioned opinions only grow less relevant to my daily life.</p><p>But then I open LinkedIn once in a while, or see suggested articles on Medium, or video recommendations on YouTube, or stumble across design subreddits, or mentor pre-career designers from bootcamps (or self-taught via the aforementioned online sources), and these views reappear once again, and it’s professional whiplash all over again. So, again, I wonder: what explains this?</p><h3>What are some examples of this?</h3><p>Before I go into my analysis of this discrepancy, I do want to spend some time elaborating on what opinions I’m referring to in the aforementioned section. I try my best <em>not</em> to cite specific sources that represent some of the strongly held opinions I refer to in this article, as I prefer to focus on ideas, rather than on organizations or individuals. Instead, I’ll do my best to provide a list of commonly argued themes that I only hear outside of my daily work, rather than within it:</p><ol><li>Arguments about “UX” being “ruined” by “UI,” <em>or</em> that they are separate functions, or any derivation of this.</li><li>Arguments about product development and interface design being a “science,” or any derivation of this.</li><li>Arguments about “information architecture” being a separate role, function, or step apart from regular, daily design work, or any derivation of this.</li><li>Arguments about design “needing to get a seat at the table” (needing to prove itself as a valuable function), and that the way to do this is to connect it to “business outcomes” in order for design to justify itself as useful in an organization, or any derivation of this.</li><li>Arguments about “design maturity,” and how (at low design maturity companies), UX Designers are often treated as little else than visual designers with no agency or impact on whether something should ship, or how something works, mindlessly improving the look of mocks created by PMs (or any other function), or any derivation of this.</li><li>Arguments about designers “needing a process” of their own (usually involving frameworks, methodologies, or things like user journeys, empathy maps, wireframing, agile/scrum being good or bad, double diamonds), or any derivation of this.</li><li>Arguments about how “UX Design is over” because we have “left behind traditional User Centered practices” (or any other design framework that is not commonly used), or any derivation of this.</li><li>Arguments about titles, where “UX Design” is a different role (with different expectations) to “Product Design,” or any derivation of this.</li><li>Arguments about how there are specialties within interface design, or any derivation of this.</li><li>Resources with particular focuses on design for websites, or very simple web apps (e.g., e-commerce sites, etc.).</li></ol><p>And so on. <a href="https://bootcamp.uxdesign.cc/how-design-generally-works-at-tech-companies-36c591ac4744">I’ve</a> <a href="https://medium.com/@yamilah/visual-design-the-designers-great-satan-590c32cf1f97">touched</a> <a href="https://bootcamp.uxdesign.cc/let-the-buyer-beware-a-warning-for-pre-career-designers-ad2aa9000ed6">on</a> <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055">many</a> <a href="https://bootcamp.uxdesign.cc/you-dont-need-mentors-to-tweak-your-portfolio-you-need-to-start-over-4acc46ed5f88">of</a> <a href="https://internetgrill.substack.com/p/frequent-questions-i-get-around-tech">these</a> <a href="https://medium.com/@yamilah/you-know-what-the-design-industry-needs-another-methodology-37a30ccd268a">topics</a> <a href="https://bootcamp.uxdesign.cc/are-we-overthinking-product-designer-versus-ux-ui-designer-b94fcb60e476">in</a> <a href="https://medium.com/@yamilah/what-if-there-is-no-design-process-da0fe3ed060e">the</a> <a href="https://medium.com/@yamilah/whats-in-a-case-study-an-alternative-perspective-a2605eac55da">past</a> <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055">but</a>, <a href="https://bootcamp.uxdesign.cc/what-if-there-arent-actually-any-specializations-in-design-ad3f455e5c37">looking</a> <a href="https://medium.com/@yamilah/how-to-find-a-good-mentor-6130eed6ee3e">at</a> <a href="https://bootcamp.uxdesign.cc/okay-networking-but-does-it-work-though-612d0e48cbad">this</a> <a href="https://medium.com/@yamilah/whats-the-story-with-storytelling-88a84b0af78d">list</a>, <a href="https://medium.com/@yamilah/things-i-secretly-wish-designers-would-please-stop-saying-cb600f8e3436">none</a> <a href="https://bootcamp.uxdesign.cc/things-you-might-want-to-avoid-as-an-early-career-designer-35eb9770621a">of</a> <a href="https://bootcamp.uxdesign.cc/is-dribbbalization-really-that-bad-though-a89503db9aeb">these</a> <a href="https://medium.com/@yamilah/i-believe-anyone-can-have-a-design-career-that-said-it-might-not-be-right-for-you-329af9e6e840">focuses</a> or themes come up in my daily life at work. I’ve worked at big tech companies (the fruit company, previously the camera app company, the bird factory app, the yoga project management app), all the way to unknown, smaller tech companies of eight to one hundred people, and I never (or, charitably, almost never) saw hide nor hare of these arguments or focuses. I also never see any of these processes, frameworks, ideologies, etc., feature in my (or my colleagues’) work.</p><p>Certainly, it’s the internet, so people will opine on anything and everything, which is a great thing! But this is not why I write this, again: what I’ve been trying to understand is why this discrepancy between <em>online opinions</em> and <em>offline reality</em> has cropped up in the first place. I haven’t been able to put my finger on this — that is, until more recently.</p><h3>From where does this tension source from?</h3><p>I’ve turned this tension over in my mind for some time, but have had a hard time getting all my thoughts connected until more recently. What changed for me was hearing some of the personal experiences of designers that typically discuss the topics mentioned above — their motivations and personal stories, and really trying to connect them all together. I’ve come to two major conclusions:</p><ol><li><strong>They are right…</strong> When these designers talk about <em>any</em> of those topics listed above, they are completely right in their assessments, and they are telling the truth. I’ve personally experienced all of this in my time working at Disney+, and a company called <a href="http://intralinks.com/">Intralinks</a>, to offer personal examples, and can personally confirm the veracity of the above mentioned claims.</li><li><strong>…But only within the context of their industry.</strong> Despite the aforementioned conclusion, the topics discussed above by these designers do not apply to the industry I’m in. This is because, <em>despite sharing the same title</em> (as myself and other designers I’ve worked with), <em>we work in different industries</em>, and their experiences are best considered within the context of theirs, rather than the one I work in, for example.</li></ol><p>I realize this is kind of confusing, so let me elaborate best I can: <em>I believe these designers</em> when they say that, at their companies, the aforementioned topics are real concerns and phenomena that they experience and observe. I believe them when they say that, at their companies…:</p><ul><li>…UX and UI are (often) two different functions, performed by two different people.</li><li>…Design is the last consulted when new products or features are considered, and they have a hard time convincing company leadership to change that.</li><li>…Design is relegated to a role where they have no meaningful control over the shape of business decisions — they only exist to “beautify” some mocks a PM (or someone else) made, even if the feature, itself, makes no sense or has no hope for market fit (i.e., no consumer demand).</li><li>…Processes and frameworks matter to their managers, and are important to help create an air of authority and respectability in the eyes of leaders whom frequently dismiss them. They want to show leadership that there is a science to this, and they want leadership to respect their authority, as seekers of customer truth, and representatives of what customers want.</li><li>…They work (often) on web experiences, and the web is still a highly relevant platform on the market at large and to their users, especially.</li><li>…The nature of their work tends to focus heavily on fundamental structural issues, like the information architecture (or structure) of a web page, and interaction work is mainly about animations and flourishes.</li><li>…Design maturity is a reality they have to assess at their companies, for all the reasons listed above.</li><li>…They often have to tail engineers, and operate using agile/scrum, when it doesn’t feel appropriate for them.</li><li>…The situation described above (for many) is not improving, and they might even feel stuck, demoralized, and even hopeless in the face of a lack of progress in the industry, and even in their own careers.</li></ul><p>It’s been a really long time, but after hearing some of their personal stories, it brought me back to the fact that I’ve felt this way before, most notably at the start of my career (at <a href="http://intralinks.com/">Intralinks</a>, with a brief interlude at Disney+ as a reminder (which I quickly forgot about until more recently — it’s all a blur!). I’ve observed all of this at these two companies and, though I’m happy to go into detail about what these experiences looked like compared to my experiences in the tech industry, it’ll probably make this article longer than it already is, so I’ll just have to leave this to another time!</p><h3>Not all software companies are tech companies</h3><p>Again, like I said in point two above, these experiences I’ve touched on above — ones that designers at these companies talk a lot about — <em>are real</em>, but here’s an oft-neglected (but extremely important) caveat: they really only apply to their industry. What I mean by this is that, in the tech industry, these experiences are uncommon, at best.</p><p>I’ve talked about what defines a tech company at length in previous articles, but to summarize: the “tech company” is a subset of software companies, in general. To keep this concise, I’ll use examples: where companies like U-Haul, General Motors, General Electric, Fidelity, Target, Walmart, Visa, PricewaterhouseCoopers, Bank of America, Best Buy, etc., are all massive companies that make software (they can be called software companies for this reason), they are not tech companies. Tech companies also make software, with notable examples like Figma, Apple, Uber, Instagram, Notion, Substack, Slack, etc., but they aren’t like the companies listed earlier, where the aforementioned experiences are rife. Your day to day just looks different, despite sharing the same (or similar) titles.</p><p>I’ve talked about <a href="https://medium.com/design-bootcamp/how-design-generally-works-at-tech-companies-36c591ac4744">how design (generally) works at tech companies</a> (probably my most popular opinion piece for reasons that, if not already self-evident, will hopefully become more obvious by the end of this opinion), but just to summarize some top-line differences between their experiences and those of designers at tech companies: you don’t have to “fight for a seat at the table” when you work at Airbnb or Apple or Instagram, for example — the design org can veto anything and everything, and they can even be said to have outsized power when compared to other functions. Idea generation for what to build also often comes from designers, themselves, rather than PMs, so you’re not really getting told what to do at these companies, as a designer.</p><p>At most tech companies, web experiences are less commonly a priority when compared to native apps — as a result, there’s a high expectation around interaction work (for example, iOS is highly gestural and heavily interactive — there are scarcely “pages” in iOS, outside of things like the settings view). The web isn’t a highly performant platform and also can’t take advantage of gestures, so interaction work should be reasonably limited, which means designers at non-tech companies won’t be doing much of that in their day to day.</p><p>What’s more, tech companies don’t hire UX designers and UI designers, respectively. There is usually one designer per workstream, and you’re expected to do it all. The bar is very high — you need to come up with pertinent ideas (have good product sense), you need to be able to model it taking advantage of native gestures (have good interaction skills), and it also needs to look very professional and fit into the quality of the rest of the app (have good visuals). There is no wireframing your way into a complex swipe or pinch gesture of multiple elements on a canvas (as is the case in Instagram stories), you model it by building a prototype using something like Origami (or AE, or whatever you prefer, but something like this). The barrier to entry is high when designing for these apps.</p><p>With some exceptions, we don’t frequently have to worry overly much about redesigning the whole structure of an app (i.e., information architecture at the app-level, because we usually don’t have fatal structural issues that need to be resolved — we worry about the structure of the features we add in, because the foundations we build into are usually pretty solid in the first place (though decluttering apps is normally required over time, e.g., Spotify, Google Maps, Instagram, Uber, iOS, etc., have all undergone substantial structural UI changes with time in my living memory).</p><p>I could go on forever, but the point I want to emphasize here is that, while these designers are facing real issues, these are issues experienced mainly in their industry — not in the tech industry. When these designers write things like “UX Design is over,” or “designers are relegated only to visuals now,” or “you need to prove to company leadership that design matters by connecting it to business outcomes,” or “web design is key,” or “you need frameworks in design,” or anything mentioned above, these are realities in <em>their</em> industry, not in tech.</p><p>I’ve had the privilege of working in their industry and seeing these realities they struggle with first-hand, but I’ve also been fortunate enough to have a look behind the curtain with first-hand experiences at tech companies, and they are genuinely just different beasts. These differences aren’t small, and they are hard to appreciate when you’ve not had that first-hand experience, yourself, so it can be very easy to write these articles talking about design at large without realizing that the experiences of non-tech designers are not relevant to the experiences of designers at tech companies.</p><h3>Ending this opinion now, lol</h3><p>I think these designers should continue to share their perspectives, and I hope things improve for them in their industry. I know the pain — so much so that this is actually why I decided to hustle and leave the industry and get into tech, because I knew immediately that I didn’t like the way software companies like those described made me feel about myself and my life. But I also think:</p><ul><li>Designers at tech companies don’t frequent LinkedIn, Medium, or Reddit, so their voices are underrepresented on these surfaces (favoring Twitter and Substack).</li><li>Designers at non-tech companies do frequent LinkedIn, Medium, and Reddit, so their voices are overrepresented on these surfaces.</li></ul><p>However, bootcamps and universities, mainly optimizing students for careers at non-tech companies, encourage students to spend most of their time on LinkedIn and Medium, which I’ve realized is what explains the complete shock that I (and other designers I’ve talked to who do a lot of mentoring) see from mentees when I explain how tech companies <em>actually</em> work. There’s even a thread from a designer who got hired from a design program directly into IG, and he <a href="https://twitter.com/joekndy/status/1091355418842955777">talked about exactly this discrepancy</a> (for any designer that wants to work in tech, I strongly encourage this read!).</p><p>As long as educational programs continue to encourage students on to these platforms, consuming content from non-tech designers, while not first assessing their students’ longterm goals (i.e., whether they want to have a career mainly in tech, or non-tech), then students will continue to be surprised by what designers at tech companies have to say.</p><p>And, as long as designers at non-tech companies conflate their experiences with designers at tech companies, newcomers will continue to be caught in career bootloops, and non-tech designers may never realize the changes they’ll need to make to turn those rejections into offers from tech companies they (sometimes) don’t admit to wanting to work at — the conversation will just continue to start and stop at <a href="https://en.wikipedia.org/wiki/The_Fox_and_the_Grapes#:~:text=The%20story%20concerns%20a%20fox%20that%20tries%20to%20eat%20grapes%20from%20a%20vine%20but%20cannot%20reach%20them.%20Rather%20than%20admit%20defeat%2C%20he%20states%20they%20are%20undesirable.%20The%20expression%20%22sour%20grapes%22%20originated%20from%20this%20fable.%5B3%5D">sour grapes</a>, with no abatement.</p><p>And, as long as designers at tech companies remain largely silent before the eager and curious, the fewer opportunities aspiring designers will have to grow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de8710ba9860" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Okay, but what if A/B testing is not that useful, though? Haha, just kidding… Unless ]]></title>
            <link>https://medium.com/@yamilah/okay-but-what-if-a-b-testing-is-not-that-useful-though-haha-just-kidding-unless-9a043d2f3e46?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a043d2f3e46</guid>
            <category><![CDATA[a-b-testing]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[split-testing]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Wed, 22 Nov 2023 11:28:12 GMT</pubDate>
            <atom:updated>2023-11-22T12:14:51.032Z</atom:updated>
            <content:encoded><![CDATA[<p>(Just jokes, please don’t hurt me.)</p><p>Okay, so, recently, I was shooting the breeze with a friend and we were musing about the importance of A/B testing (don’t ask) — said friend agreed that it’s science, but brought to product development. We went back and forth a bit about why this matters. While I’d love to have a transcript about the conversation, our conversation involved private matters, so I figured I’d just write something about it, instead, and keep it general. The subject is the message. But first:</p><h3>What’s A/B testing?</h3><p>If you’re reading this opinion, you probably already know what this is, so feel free to skip over. But I do have readers who are new to this stuff, so I’d prefer to explain. In scientific research (e.g., pharmaceutical testing, academia, etc.), it’s understood that the Gold Standard (so to speak) in test design and research is double blind testing. Here’s what <a href="https://en.wikipedia.org/wiki/Blinded_experiment">double blind testing</a> is:</p><blockquote>In a blind or blinded experiment, information which may influence the participants of the experiment is withheld until after the experiment is complete.</blockquote><p>Here’s why it matters:</p><blockquote>Good blinding can reduce or eliminate experimental biases that arise from a participants’ expectations, observer’s effect on the participants, observer bias, confirmation bias, and other sources.</blockquote><p>Here’s an example:</p><ul><li>I have uncovered a cool, new substance that I believe, when taken orally, can grant you <a href="https://www.tiktok.com/t/ZT8yrqetf/">level 5 gyatt rizz</a></li><li>I want to prove this beyond reasonable doubt</li><li>I find 100 healthy people with varying, naturally occurring levels of rizz</li><li>Give 50 the rizzpill</li><li>Give the other 50 a sugarpill that looks exactly like the rizzpill</li><li>None of the patients know this (this is illegal btw, hit you with that rizztraining order)</li><li>No staff involved knows who’s rizzpilled and who’s not</li><li>We measure their rizz levels at the same intervals over time</li></ul><p>If, after a year, the rizzpilled people all are level 5 gyatt rizzlers (at the minimum) when compared against the sugarpilled control, then the rizzpill can be said to work beyond a reasonable doubt.</p><p>This is called science, or the scientific method. You might remember this from primary school. The purpose of science is to isolate variables, and then test as best you can to see what variables, when moved, result in change, so as to (in)validate hypotheses. This is the best way to actually test if something works or not. You have a control group (sugarpilled), and any number of variants (rizzpilled), and then you compare the variant(s) against the control. All things being equal (no one knows who’s sugarpilled or rizzpilled), we create the perfectly controlled environment in which to isolate a single variable and see exactly what impact it has.</p><h3>What’s this got to do with product development, though?</h3><p>The process I described above, in pharmaceutical/academic settings is often referred to as double blind testing. In product development, we usually call this A/B testing (or split testing). In software, we wouldn’t test on people’s bodies, so what we would do is the following:</p><ul><li>You have some cool, new feature</li><li>Go get some A/B testing software (at big tech companies, this is often an internally made service, rather than an off-the-shelf solution, like Google Analytics, etc.)</li><li>Set up your parameters (duration, percentage of population, location, session persistence, and anything else you want)</li><li>Make sure there are no other A/B tests running that could conflict or bias yours (this can happen especially when you run thousands a day)</li><li>Drop whatever tracking that spits out into some part of the codebase</li></ul><p>A lot of big tech companies A/B test in New Zealand, among a few other places. It’s an English-speaking market that simulates the American one, but it’s smaller and lower profile, and doesn’t burn through the American trees, so to speak, so that’s why. At massive companies, you can select some insanely small population percentage, too, and you get stat sig in weeks, but you can run it as long as you want. Then you wait.</p><p>You can watch the logging events roll in. Eventually, you get to see if your change affected any core metrics you want. Did it lower some metric you care about (e.g., likes, views, replies, DMs, session length, number of items purchased, etc.)? What about any other metric? At that point, you decide what metrics matter.</p><h3>Why does this matter in product development?</h3><p>As mentioned, this allows you to see if, beyond reasonable doubt, your change has had any impact on any user behavior — without anyone from the company’s side affecting their behavior, or even users knowing they’ve been rizzpilled. All things being equal, we create the perfectly controlled environment in which to isolate a single change and see exactly what impact it has.</p><h3>So what’s there to discuss? This is unequivocally great.</h3><p>Fair. Consider the following, though:</p><h4>Consideration 1: You use your intuition to determine what to test</h4><p>How do you even know <em>what to A/B test in the first place</em>, though? The passage above describes <em>how</em> you set up an A/B test — but it doesn’t tell you <em>what</em> to A/B test <em>with</em>; the machine can’t tell you whether you should test the rizzpill at 0.5mg or 1mg, or whether the pill casing should be hard or soft. <em>You</em> decide that. You have to make some executive decisions on this (read: a hypothesis; also goes by: “intuition”) concerning what to show up to the test with.</p><p>This means that, when A/B testing, you’ve already used your intuition to determine what variants to test with. You’re not showing up with 1 million rizzpills of 1 million color variations, casing variations, etc. You’re showing up with probably one or two. You’re using your intuition here to make these calls about what to test.</p><h4>Consideration 2: A/B tests happen at the end of a product development loop</h4><p>This <em>also</em> means that A/B tests are most appropriate towards the <em>end of the product development lifecycle</em>. This is something you’d do to determine whether the feature you’ve made is worth getting the go-ahead to ship. Going back to the pharmaceutical example: this means that you’ve already manufactured a limited round of those rizzpills (at hopefully not too much cost — lacking some refinement, I’m sure).</p><p>To put it back into software terms: <em>you’ve made the feature already</em> (or some sufficiently satisfying version of it, see: <a href="https://en.wikipedia.org/wiki/Minimum_viable_product">MVP</a>/MLP/etc.). The cost to make the limited round of rizzpills or initial test wasn’t zero. It took some time and effort. There’s not really a way around this, and it means that, again, you’re using your intuition to decide what those first variations to test will be.</p><p>At a real company, especially a bootstrapped one, you usually don’t have a ton of money, or limitless morale, even. You have to work within this reality and make some calls and accept that testing, itself, incurs some cost. It is impossible to bring this cost to zero, and I’m not sure that that should be the goal anyway.</p><h4>Consideration 3: A/B tests only tell you about what you have, not about what you don’t</h4><p>When you A/B test, you’re comparing some variation(s) against a control. This means that you are benchmarking — comparing — between some change and a status quo. This is great but, as mentioned in #1, there’s no clear proof that the variations you’re testing are any good. An A/B test will reveal which of these states are — when compared against each other — the best. It doesn’t tell you that there isn’t some other, better way to do this thing that consumers would like even more. Anything outside these variations is totally out of bounds.</p><p>Consider this scenario: imagine you could somehow set up an insane lab and watch humans organically step into dog dookie, and the reason you want to do this is because you want to A/B test to determine what kind of poop (wet or dry) elicits the strongest disgust response in human subjects. Personally, my hypothesis is that, <em>all else being equal</em>, the disgust responses would be significantly higher among participants stepping in wet dog dookie. The conclusion (that literally no one alive would dispute) would, therefore, be: all else being equal, if the average person would have to pick, they’d prefer to step in dry dog dookie, rather than wet.</p><p>Amazing, we did science! And what did we learn from this?: people hate one kind of dog dookie more than another. Consider, though: both options are still dog shit.</p><h4>Consideration 4: you probably won’t run this test forever, so you’ll see novelty effects</h4><p>Chatting with data scientists at the camera app company, something you’ll hear many say is that we never really have enough time to track second and third order effects of a feature. We test for a few weeks, get stat sig, and then make a call. (It <em>is</em> a phase, mom!) But introducing something new into an ecosystem — especially something large — can affect user behavior in ways that cause shockwaves across the ecosystem in ways that are hard to watch for. What’s more, novelty effects can take a while to buff out. But most tech companies (even the large ones) aren’t running A/B tests for years. They’re doing it in the town of weeks, maybe a couple months, being real. Novelty effects are a real thing, and you can only control for this bias with elapsed time. Which we typically don’t want to spare.</p><h4>Consideration 5: you can play funny money with metrics (if you want)</h4><p>A lot of people shut their brains off when the word “data” or “science” drops but, again, <em>how</em> you set up a test is the sole, determining factor in whether a test can be said to be scientific or not. Quality of test design matters in the world of research. But, for example, you might increase the number of ads on your social media platform. This means your unit economics (cost per user) metrics will look green. But other indicators might look red, or neutral, or maybe slightly red.</p><p>It all depends on what you want. You get more money, but you take a hit to user experience that’s difficult to truly capture in metrics, and might show up in second or third order ways that you aren’t measuring. For example, you have market dominance <em>now</em>, but then, perhaps, a competitor comes out, and while you dominated, you could shove ads in users’ faces because there was no better way for them to be entertained and they’d begrudgingly accept it. But, lo and behold, a competitor has fewer ads or other cool and amazing features, and now you’re seeing evidence that you’re losing market share.</p><p>Your engagement metrics might look neutral. You’d have to look at retention metrics to see the full picture, though, and you might not be noticing that, or it might just be the start. And, in these cases, once you burn through those trees, they probably won’t return.</p><p>What’s more, you can be misled by empty calories, too. Let’s say you have this super annoying feature where, when you react to someone’s story, it sends the reaction as a DM — someone does a laugh emoji, and it literally spams this big ol’ face into your friend’s inbox. A <em>whole push notification</em> is sent with a cringey laugh emoji. This is so cringe and weird and no one likes this. Can we just unship this weirdo feature?</p><p>No! Because, guess what?: for the two whole people who use this feature without any sense of shame or remorse, that’s a +1 updoot to the company’s “this feature starts a conversation” engagement metric! Huge win, right? Nope, empty calories. You’d have to look at response rates to those weird emoji-reactions-turned-DMs, and these DMs have, on average, lower response return rates.</p><p>It’s difficult to capture in metrics peoples’ hesitation around sending emojis when, on literally every other service, sending emoji reactions is standard and not weird. The reason is because they feel awkward sending a giant face as a DM into someone’s inbox, where emoji reactions are usually just appended to the post and super subtle. A whole push notification for a reaction feels like overkill. People just won’t use the feature and this increases overall anxiety when using the software in ways that are difficult to capture. You could start by running a separate A/B test where emoji reacts send in the story viewer list versus via DMs, and then you might start seeing a fuller picture (again, second and third order effects at work here!).</p><p>There’s a pertinent phrase here: “not everything that counts can be counted, and not everything that can be counted counts.”</p><h3>You’re probably wondering if we A/B test things at the camera app company</h3><p>The subject is the message, and the answer is: yes. I can’t prove this, but there are probably thousands of A/B tests running concurrently across the entire literature face company every day (or at least hundreds? IDK), across all services — all of the time. Anything that ships gets A/B tested against the status quo to see impact on things like DM rates, conversation starter rates, comment rates, reply rates, response-back rates, session length rate, like rate — whatever metric you want, data scientists will pull it for you! But consider the following (real life examples from the trenches, guys):</p><ul><li>I’ve seen stuff go green across our key metrics (performed overall better than the control), and a lead thought the idea wasn’t compelling enough, so it didn’t ship</li><li>I’ve seen stuff go red across our key metrics (performed overall worse than the control), but the experience was clearly superior and objectively better to literally anyone on the planet with even a crumb of brain activity, but red square go brrr, so it didn’t ship</li></ul><p>If you’re wondering about other famous tech companies: at a certain fruit company, no A/B testing happens (at least, not to anyone’s knowledge). In the words of a director on the fruit company’s cloud service team: “we don’t hire designers that <em>need</em> data to make decisions,” acknowledging that: “I know that’s weird, considering all the other Silicon Valley companies, but we just don’t.” Continuing: “we expect a strong product intuition from our designers.” When asked how one determines whether something ships, this director responded, shrugging: “we have an intense internal culture of debate.”</p><p>Two tech companies, two different ends of a product’s life cycle — one runs A/B tests with aplomb. The other? A/B test <em>who</em>? Both wildly successful, and I’m sure anyone would jump at the chance to work at these places. So make of this what you will.</p><h3>Ending this opinion now</h3><p>Do I recommend A/B testing? I mean, why not? It’s cheap to drop in creepy trackers, so whatever. But will you benefit a ton from it? Probably not, unless maybe these conditions are met:</p><ul><li>You feel comfortable sparing the time to let tests run (this rules out most startups)</li><li>You have enough sessions to get to stat sig (this rules out most companies, and not even just startups)</li></ul><p>If these things aren’t true, probably A/B testing’s not for you. Also, if you’re at a startup and are wondering if you should be concerned that your company doesn’t do testing, I’d recommend you adjust your expectations and just let that one go, personally. If your company doesn’t get hundreds of thousands of unique sessions a day, one A/B test would take forever to get stat sig on, realistically.</p><p>I do recommend this for companies like camera app company, or bird factory company, etc. It’s good to do your due diligence, and it’s not that expensive (even at scale). What’s there to lose? But I wouldn’t use it place of good faith intuition. As mentioned, a certain company doesn’t A/B test at all, and they also happen to be the richest company on earth — as my mom used to say: “<a href="https://www.google.com/search?q=en+el+mundo+de+dios%2C+hay+de+todo+translate&amp;oq=en+el+mundo+de+dios%2C+hay+de+todo+translate">en el mundo de dios, hay de todo</a>.” 🤷‍♀️</p><p>Elephant in the room time: <a href="https://youtu.be/59RIVbWC4oE?si=UXPHDS4UUYiDiThB&amp;t=4">been away for a while</a>, sorry. 😅</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a043d2f3e46" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What if there aren’t actually any specializations in design?]]></title>
            <link>https://medium.com/design-bootcamp/what-if-there-arent-actually-any-specializations-in-design-ad3f455e5c37?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad3f455e5c37</guid>
            <category><![CDATA[specialization]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Tue, 27 Dec 2022 12:14:15 GMT</pubDate>
            <atom:updated>2022-12-30T06:00:55.405Z</atom:updated>
            <content:encoded><![CDATA[<p>In a <a href="https://medium.com/design-bootcamp/how-design-generally-works-at-tech-companies-36c591ac4744">previous article</a>, I described the internal workings of a number of tech companies I’ve worked at over my seven years in the industry — these ranging in size from eight to eighty thousand employees, with products that have zero DAUs (daily active users) to 500 million.</p><p>My intent was to provide a portrait (as sincerely and clearly as I could) of how products are made at tech companies: how teams are organized, what designers get up to, how product strategies are made, and so on. Some designers may never have worked at FAANG companies before, while others may never have worked at tech companies with employees in the single digits, and so the opinion may provide an interesting look behind the curtain.</p><p>But I also wanted to document how <em>I’ve</em> worked and, by extension, how the designers I’ve worked with at these companies have <em>also</em> worked. This was for the purpose of building up shared context, with which I could then approach a question I don’t frequently hear asked: are there such things as specializations in product design <em>at all</em>?</p><h3>I can explain!</h3><p>I understand that the reader may be quite familiar with (and potentially invested in!) the debate over whether product designers should “specialize,” or whether they should “generalize.” Before detailing my perspective on this debate, specifically, I’ll detour to provide some context about the common positions in it (mainly for those who may not be familiar with this debate at all).</p><h4>Why should one “specialize”?</h4><p>With respect to a product designer’s career trajectory, it is generally said that there’s one major concern a designer ought to decide on at some point in their career: whether they should “specialize” or “generalize,” with people usually arguing for one over the other for various reasons.</p><p>Among those who believe designers should specialize, there are often numerous supporting arguments. From <a href="https://www.uxmatters.com/mt/archives/2015/09/ux-generalists-or-specialists.php">UXmatters</a>, laying out benefits of specialization:</p><blockquote>- You gain a lot of in-depth experience in your specialty. By focusing all of your time on either user research or design, you gain in-depth experience in one area. You’re able to focus on what interests you most.</blockquote><blockquote>- You get to work on the best projects for your specialty. Companies that choose to hire specialists are usually those that value both user research and design, and they tend to spend time and money on both of those activities. Companies with dedicated user researchers tend to allocate more time for research and trust researchers to innovate new activities. Consulting companies with specialist researchers tend to place a high value on user research. This attracts clients who also value and want to include user research on their projects.</blockquote><blockquote>- You have more time to focus on your specialty. Instead of being overburdened and stretching yourself too thin by trying to perform all of the activities of both user research and design, you’ll have more time to focus on your specialty.</blockquote><blockquote>- You become a rare and highly valued UX professional. As you gain more experience, you’ll become an increasingly rare and more highly valued UX professional. Although there are fewer specialist positions available, you’ll have much less competition for them. Plus, you can command a higher salary.</blockquote><h4>Why should one “generalize”?</h4><p>This is the other side of the coin. It is said that, instead of specializing, one can generalize,— or choose to cast a wide net — allowing one to accumulate a lot of knowledge about a great many things. As is frequently believed, however, this comes at the cost of deep knowledge in any one thing in particular. Once again, from <a href="https://www.uxmatters.com/mt/archives/2015/09/ux-generalists-or-specialists.php">UXmatters</a>:</p><blockquote>- You gain more experience. As generalists, new UX professionals, who are just starting out in their UX careers, have the opportunity to gain a lot of experience in both user research and design.</blockquote><blockquote>- You have more career opportunities. Because many companies combine user research and design into a generalist position, there are far more job opportunities open to generalists than to specialists. So generalists have more career options and mobility.</blockquote><blockquote>- You experience more variety. Generalists experience a wider variety of activities. When user research begins to get boring and repetitive, they can move on to design. As multiple wireframe iterations begin to get tedious, they can move on to usability testing.</blockquote><blockquote>- You experience the user research firsthand. While specialist designers may or may not observe all the user research and usability testing sessions, generalists conduct the user research and usability testing themselves. Through their firsthand involvement in the research, they can internalize the findings more deeply and then are better able to apply that knowledge to their designs.</blockquote><blockquote>- It’s easy to become a specialist later. It’s far easier for a generalist to become a specialist than it is for a specialist to become a generalist. Generalists can choose to specialize in one of their areas of expertise, but specialists usually lack experience in one or more of the tasks that generalists must perform.</blockquote><p>As is the case above, I’m sure that there is more that can be said about the arguments for this position and, as always, the reader is encouraged to check out these (and other) sources to learn more about the commonly cited, different angles in this debate.</p><p>Separately, I’ll also add that, in my seven years, I cannot recall a situation wherein an individual has argued specifically <em>for</em> generalization <em>over</em> specialization — personally, I have only ever seen arguments in favor of the latter. My impression is that this is a common perspective.</p><h3>Back to what you came here for</h3><p>With a shared understanding between reader and author concerning the arguments broadly made for specialization or generalization, respectively, in product design, the reader may be wondering why I do not appear to be arguing in favor of one approach or another, as is typically done. I do this for a few reasons. To start, however, I think it’s instructive to talk about what the specializations are said to be <em>at all</em>.</p><h4>What are the available specializations in product design?</h4><p>Searching “ux design specialize,” multiple results return. Just going down the list of those results, starting with <a href="https://careerfoundry.com/en/blog/ux-design/what-are-ux-ui-and-interaction-design-and-which-should-you-learn/">Career Foundry</a>, some specializations are listed (quoting from the source):</p><ul><li>UI design,</li><li>Interaction design,</li><li>Information architecture,</li><li>Visual design,</li><li>UX research.</li></ul><p>From <a href="https://www.uxmatters.com/mt/archives/2015/09/ux-generalists-or-specialists.php">UXmatters</a>, the quoted specializations include:</p><ul><li>User research,</li><li>Interaction design,</li><li>Information architecture,</li><li>Usability testing,</li><li>Visual design,</li><li>Front-end development.</li></ul><p>From <a href="https://www.invisionapp.com/inside-design/5-ux-specialties/">Invision</a>:</p><ul><li>UX researcher,</li><li>Information architect,</li><li>UI/UX developer,</li><li>Usability analyst,</li><li>UX writer.</li></ul><p>Right, so I think the reader can see some interesting patterns developing here: despite how authoritatively each source speaks, it seems none of them can agree on exactly what those specializations <em>are</em>. This seems important — I think many might agree that, if one is to successfully argue for specialization <em>or</em> generalization, one should be able to agree on what those specializations are in the first place.</p><p>There are other problems with these lists, though: not only do the listed specializations not agree with each other, but some of these roles don’t even exist — or are not specializations of product design <em>at all</em>. Just going down the titles provided above:</p><ul><li><strong>UI design.</strong> As stated in my <a href="https://bootcamp.uxdesign.cc/how-design-generally-works-at-tech-companies-36c591ac4744">previous article</a> (mentioned above), I detailed how tech companies <em>do not hire UI designers</em>. We hire product designers that are expected to execute on the product to a high level of craft. Having visual excellence is considered a baseline expectation on the market. Some companies have higher standards than others when it comes to visual excellence, but <em>some</em> level of excellence is still considered a minimum requirement of the designer role across all tech companies. A minimum requirement is <em>not a specialization</em>, and you cannot specialize into a role that doesn’t exist, given that tech companies do not hire for them, exclusively.</li><li><strong>Visual design.</strong> Visual design and UI design are interchangeable phrases in tech, so see above. More rarely, a company (e.g., Google) hires for a title like “visual designer,” but <em>this is not a product design role</em>. You cannot specialize into a role that doesn’t exist. Visual designers at Google, for example, are people are who are hired to perform tasks like (but not limited to): making icons (illustrators), making product imagery (illustrators), doing branding work (graphic designers), and other visual work on <em>creative</em> (read: non-product) teams at tech companies. This is <em>not a product design role</em>, so it is definitionally <em>not a specialization</em> of product design.</li><li><strong>Interaction design.</strong> This is just what product design fundamentally requires one do. When one is hired to design products at tech companies, one is expected to open up Figma and plan out how the proposed software behaves based on various user inputs. This is the minimum, floor-level requirement to perform this role. If one can’t design interactions (e.g., “user taps this, this other thing happens”), then one cannot work as a product designer. A minimum requirement is <em>not a specialization</em>.</li><li><strong>Information architecture.</strong> Tech companies do not hire “information architects.” Like with visual design, designers at tech companies are expected to be able to design screens that simulate viewports in native and web apps, and place elements within them in a way that would make sense for most users when quickly scanning and parsing. A minimum requirement is <em>not a specialization</em>. You cannot specialize into a role that doesn’t exist.</li><li><strong>UX research.</strong> This is not a specialization within design, but a <em>completely different role</em>. The hiring pipeline for researchers at tech companies is completely different to the ones for designers — they have totally different promotion expectations, pay bands, managers, cost centers, reporting structures, and so on. Small companies may hire designers that can help pick up these tasks, but <em>this is still just a designer</em> who is flexing to help with coverage. A completely separate role is <em>not a specialization</em>.</li><li><strong>User research.</strong> See above.</li><li><strong>Usability testing.</strong> Usability testing is something a researcher (or anyone else) <em>does</em> while doing research work. This is not a specific role, but an action one can take while working as a user researcher. A specific, narrow task only sometimes performed within a role is <em>not a specialization</em>.</li><li><strong>Usability analyst.</strong> This is not a role tech companies hire for. You cannot specialize into a role that doesn’t exist. Depending on what this analysis entails, this is not a specific role, but an action one can take while working as a user researcher. A specific, narrow task only sometimes performed within a role is <em>not a specialization</em>.</li><li><strong>Front-end development.</strong> This is not a specialization within design, but a completely different role. This is an <em>engineering</em> role. The hiring pipeline for engineers at tech companies is completely different to the ones for designers — they have totally different promotion expectations, pay bands, managers, cost centers, reporting structures, and so on. Rarely, designers may become interested in engineering and pick this up on their own time (this is true in my case, as well). I would highly recommend this, but this is not a specialization of design. A completely separate role is <em>not a specialization</em>.</li><li><strong>UI/UX developer.</strong> This is a title variation on the role above, so see above. Some companies have a few, rare roles called “UX Engineers.” Again, these are specific kinds of front-end engineers — not designers. A completely separate role is <em>not a specialization</em>.</li><li><strong>UX writer.</strong> This is not a specialization within design, but a completely different role. The hiring pipeline for product writers at tech companies is completely different to the ones for designers — they have totally different promotion expectations, pay bands, managers, cost centers, reporting structures, and so on. Small companies may hire designers that can help pick up these tasks, but <em>this is still just a designer</em> who is flexing to help with coverage. A completely separate role is <em>not a specialization</em>.</li></ul><p>The sources above don’t seem to agree with each other, and most list specializations for design that either don’t exist, or are fundamentally not specializations <em>at all</em> (the most egregious including listing <em>engineering</em> as a design specialization!). These sources, therefore, have fatal problems in their assertions and understandings of product companies, — and technology — more generally.</p><p>For what are probably obvious reasons, by contrast, specializations in engineering are usually more broadly agreed upon. For instance, in engineering at tech companies, there are these common specializations:</p><ul><li>People who work on the client (e.g., iOS, Android, and web — unless using something else, like React Native or Flutter),</li><li>People who don’t work explicitly on the client (e.g., backend engineers, so people who focus on building APIs and other infrastructure, etc.).</li></ul><p>At smaller companies, engineers might be expected to work across client and infrastructure, both (the reader may have heard of the term “fullstack,” for example), but you won’t find engineers expected to make PRs in Java codebases (Android), and then also expected to pull up the company’s Swift codebase (iOS) and push out the equivalent feature there, and then another one in a web codebase.</p><p>If you work at a small company, these tend to either focus on one platform at a time (iOS is a common choice in Western markets), deprioritizing other platforms (e.g., Android, etc.). <em>Or</em> they might use something like React Native or Flutter — these require web or C++ engineers, respectively.</p><p>However, some people argue that specializations in design don’t occur on the <em>title</em> level (e.g., “researcher,” or “UI designer,” etc.), but on the <em>industry</em> level. For instance, some argue that there are designers who are most optimized for different kinds of product industries: fintech, healthtech, femtech, etc., and that these product areas are specializations, themselves.</p><p>Interestingly, no other roles are segmented this way. For example, copywriters at Twitter (a blogging app) have the same responsibilities as copywriters working on Chrome (a web browser).</p><p>Engineers are also not segmented this way, despite that an engineer working with patient data (as in a healthtech company) would have to deal with the complexity that <a href="https://www.hhs.gov/hipaa/for-individuals/guidance-materials-for-consumers/index.html">HIPAA</a> (federal heathcare legislation in the States) tends to introduce. There are no “healthtech engineers” — there are just engineers who, due to various circumstances, currently work at companies that make technology for the medical industry. Then, one day, these same engineers will pack their bags and move over to another company, frequently to one in a completely unrelated product area.</p><p>There’s a reason why the engineering hiring pipeline at Coinbase (a crypto trading service), for example, is virtually indistinguishable from the engineering hiring pipeline at Meta (a social media and ads service) and Slack (an enterprise IM service) and Medium (a web-based blogging service). The reason for this being that these companies agree that <em>engineering is engineering</em> — no matter what company it’s done at, and no matter what product is being made. Likewise, hiring pipelines for <em>designers</em> at Coinbase, Meta, Slack, and Medium are also virtually indistinguishable for the same reasons: these companies all take this exact position with respect to design, as well.</p><h3>Back to basics</h3><p>Certainly, there appears to be disagreement among those who accept that specialization or generalization in product design is possible — mainly around what the specialization even <em>is</em>. Before jumping into my perspective on one side or another, I want to talk about what both sides of the argument (“specialization versus generalization”) assume to be true:</p><ul><li>Product design, like being a surgeon or a developer, has a high enough ceiling of complexity such that specialization is needed,</li><li>Specializing is seen in other industries (e.g., surgery, etc.) — so, too, is it required in product design,</li><li>In other industries, specialization results in higher compensation — this is true in product design, too,</li><li>Tech companies specifically seek to hire product designers who are specialists and generalists, respectively.</li></ul><p>I do not agree with any of these assertions.</p><h4>Product design isn’t surgery</h4><p>As mentioned, the argument for why specialization or generalization is needed in product design is typically done via comparisons, mainly to other industries (like engineering, medicine, surgery, etc.). However, I think this comparison is not appropriate — what is generally true for one profession or role is not necessarily true for another. Product design is far too different to the other industries and roles it’s frequently compared to (surgery being the classic example).</p><p>Going on the example of surgery: there are many organs in our bodies that are wildly and unrecognizably different from each other, such that a surgeon working on a heart would be <em>completely incapable</em> of impromptu working on a brain. Designers do not have this problem. Like engineers, they are expected to be able to be effective at the search engine company they work at <em>this</em> year, and then the social media company they work at the next.</p><p>What’s more, the margin of error when working on human bodies (compared to working on software) is extremely low — in some surgeries, there is virtually <em>no</em> margin of error. Designers do not have this problem, which means that the tolerance for risk by companies that employ us is just higher. Software and businesses can always be amended when a mistake <em>does</em> occur, — forever and ever — as long as there’s still enough money to keep the lights on. Humans don’t have this advantage. Once tissue is disturbed, it’s disturbed forever — no takebacks.</p><p>Given that organs are wildly different from each other, and the margin of error involved in working on them so low, specializations cannot be said to be nice-to-haves among surgeons — depending on the specific operation and the patient’s risk factors, a specialist may be <em>required</em>. In some cases, a generalist would be completely unable to render any services in <em>any</em> way — some legislation may also exist to <em>legally bar them</em> from rendering certain services, for example, which is also not a constraint that exists in the making of software. These restrictions occur because the law understands that body parts vary drastically — expertise in one organ system doesn’t at all suggest one has the capacity to work on another. This is not the case in product design (or even engineering).</p><p>Interestingly, however, even in surgery, — a context in which margin of error is <em>extremely</em> tight — becoming a specialist is neither common, nor <em>always</em> required, either. Generalist surgeons are the most common of all surgeons, and they are perfectly suited (and, in fact, frequently recommended) for most surgical concerns. They are a <em>must-have</em>, not a nice-to-have, in any nation’s medical system. Sending patients to specialists — when they’d be just as well with a generalist surgeon — taxes medical systems (incidentally, this exact issue is why <a href="https://www.humana.com/medicare/medicare-resources/what-is-ppo">PPO</a> and <a href="https://www.humana.com/medicare/medicare-resources/what-is-hmo">HMO</a> plans exist in the States).</p><p>More interesting is that, even among <em>very</em> narrow specialty surgeons, they have to be ready for a wide variety of reasons to be seen by patients — even among specialists, generalization within their area is still expected.</p><p>For example, <a href="https://stanfordhealthcare.org/medical-treatments/o/oculoplastic-surgery.html">oculoplastic surgeons</a> (eye doctors who only operate on the structures around the eyes) may be seen for a variety of reasons. For example, some patients may need emergency surgery due to a severe and sudden onset of dangerous and life threatening bacterial infection in the eyes; some may be patients with glaucoma, thyroid eye disease, macular degeneration, and other long-term disabilities that tend to cause wildly different — and equally complicated — deformations of the eyes; some patients may have no diagnosis, but may be soliciting their services for purely aesthetic reasons.</p><p>And yet, oculoplastic surgeons are the best people to consult for <em>all</em> of these concerns. Specialist surgeons, doctors, and etc., still take on a <em>huge</em> variety of cases within that specialty — they absolutely must to be prepared to do so, or else they just couldn’t be considered to be very experienced. As mentioned earlier, a surgery as specialized as an orbital decompression can be indicated for many <em>different</em> reasons (from aesthetic, to medically necessary as part of rare eye disease) — and they have to be prepared for patients to consult them under any (or all) of these circumstances. To put this another way, when a patient comes in for an orbital decompression due to Graves’ related eye disease, concerns are <em>both</em> for functionality (restore functionality to the eyelids), and for aesthetics (return the eyes to their natural position in the sockets). Oculoplastic surgeons have to optimize for both concerns, as their customers care about both.</p><p>If even <em>specialist</em> surgeons have to be ready to take on a wide array of extremely varied cases and concerns when the risk to one of the most important sense (i.e., vision) to human beings is on the table, one can only hope that we can all have the strength of character and humility to accept that product designers can certainly manage to do the same — especially when our risk of failure is as low as it is (luckily for us!).</p><h4>Product design is also not engineering</h4><p>Within the context of these arguments, another common role product design is compared to is software engineering. I do not think this comparison makes sense within this context, either.</p><p>The only reason why tech companies hire Android, iOS, and web developers <em>separately</em> is because no human could reasonably be expected to have the fortitude to push out PRs for <em>one</em> feature across <em>three codebases</em> at the <em>same time</em> — each codebase with its own quirks, build pipelines, expectations around QAing, and etc.</p><p>It would be unreasonable to expect someone to even be able to type fast enough to do this within a reasonable amount of time — and also extremely painful and inefficient. It’s in the company’s interest to parallelize the work with a fleet of iOS, Android, and web developers picking up one feature and implementing it alongside each other at the same time in their respective codebases.</p><p>What’s more, the level of complexity in engineering is extremely high. It’s not just that engineers have to learn different technologies and work with a wide variety of tools they didn’t make (imagine working with five different Figmas, and each Figma has to integrate well with the next Figma in your toolchain, and pull information from the other Figmas in your toolchain, and send information from one Figma into another). It’s also that some kind of engineering is very different to other kinds.</p><p>For example, there are engineers that work in sandboxes provided by various platforms (iOS, Android, the web), and they build internet services on top of those platforms. These are comparatively easier to go between (especially between the native platforms), as they are in similar areas of concerns, and have very similar concepts. However, the engineering work that goes into the creation of these platforms is different than that which goes into making the software built on top of them — it’s a lower level kind of engineering, closer to the hardware, and so the scope of the concerns in this kind of engineering is significantly increased.</p><p>For instance, it is very common that engineers can feel comfortable working across web, Android, and iOS when working on personal projects. However, they often have their professional preferences, which is how they sort themselves professionally (for example, an engineer may feel comfortable making iOS and Android apps, but has most of his/her professional experience working on Android, so the engineer tends to mostly choose to interview for Android roles).</p><p>It is, however, not common that an iOS, Android, or web engineer pick up work on <a href="https://www.vulkan.org/">Vulkan</a> or <a href="https://developer.apple.com/metal/">Metal</a> (or vice versa), even in their personal time (or other lower level engineering of this sort). As engineers frequently quip when venturing into the world of graphics engineering (especially Vulkan): “it took me two weeks to figure out how to even render a triangle to the screen.”</p><p>What’s more, it is commonly discussed in software engineering circles that there’s a shortage of engineers who will take up the mantle of the more (what some might call) dated, lower level programming on which most technology today relies on (e.g., graphics, networking, etc.).</p><p>This situation I’ve described (it being too expensive to reasonably expect engineers to go between codebases in professional settings; it being too difficult to switch engineering areas; etc.) is a result of the fact that the ceiling of complexity of engineering is naturally very, very high. It is exactly this which attracts engineers to this role.</p><p>By contrast, you can be asked to onboard on to a company as a designer to work on social apps, or enterprise apps, or fintech apps, or use Figma (or, more rarely, Sketch or Adobe XD), and these are all easily interchangeable and routinely expected by companies (for good reason). In fact, it’s frequently argued within design circles that tools are “just tools,” and that a good designer should be able to use any tool and still output good design. For good reason.</p><p>Engineering is hard (which is what explains the compensation), but this is not explicitly why specializations occur. They occur because there’s just no alternative: no one can type fast enough to reasonably push out the same feature across three codebases within a reasonable timeframe. For example, despite their similarities, an Android engineer switching to working professionally on iOS is going to need a substantial time investment before they are able to be effective in the role at all; switching between different kinds of engineering (e.g., from app development to graphics programming, etc.) is also <em>extremely</em> difficult. It’s almost like restarting your entire career.</p><p>There’s nothing like this in design — the ceiling of complexity is comparatively significantly lower. Meanwhile, some argue that expecting one product designer to both be able to create well-reasoned, easy-to-use products <em>while</em> expecting that same designer make it look professional is unreasonable. As this argument goes, building up your reasoning capacity to reason through interactions in products takes away from developing your aesthetic skills — as such, these two things need to be separate roles. Despite this, tech companies have this expectation, anyway. Quoting myself from that <a href="https://medium.com/p/36c591ac4744">previous article</a>:</p><blockquote>Tech companies do not hire “UI designers” — designers are expected to make good products, and make them look professional.</blockquote><p>Quoting myself from <a href="https://medium.com/design-bootcamp/things-you-might-want-to-avoid-as-an-early-career-designer-35eb9770621a">another</a>:</p><blockquote>In reality, you do not get to choose whether you are a “UX” or “UI” designer in today’s market. This is an academic discussion about a market that no longer exists — a luxury belief. The reality is that you are going to experience increased difficulty finding — and retaining — customers as a designer if you do not make professional looking work. When FAANG companies hire designers under titles like “UX designer,” or “product designer,” or “interaction designer,” these are all the same jobs: you are planning out how some software will work. But there is an additional expectation — not always explicitly stated — that you will put in the effort to make the product or feature look professional. There will not be an attendant visual designer at your beck-and-call to jazz up your schematics. It’s just you.</blockquote><p>Despite it taking time to get to a point where one can design software that works <em>and</em> looks professional, this <em>is</em> the expectation tech companies have — for good reason, as it is entirely possible to hit this bar, and thousands of people do it every year. If one wants to work at tech companies, one has to be ready to meet (or exceed) their expectations. By contrast, pushing out PRs across three different codebases for the same feature just is physically not a reasonable expectation. <em>This</em> is why these specializations in engineering exist.</p><h4>In design, specialists are paid less</h4><p>It is commonly said that specialists are paid more. In most industries and roles, this is probably true. This isn’t the case in product design, however. It’s commonly understood that designers who work on the brand side (visual designers, so not product designers) are paid significantly less than designers who work on the product. Even designers who specialize in design systems (i.e., design system designers) are frequently paid significantly less than designers who work on product.</p><p>While it depends on the company, in general, designers that do feature work — the ones who design products from end-to-end — make more than designers on non-product work (e.g., visual designers, design system designers, etc.).</p><p>Specialist surgeons command higher rates than generalists because this work is <em>extremely</em> risky and hard, and takes <em>significantly</em> greater time investments to excel at — as a result, fewer doctors want to invest in these skillsets. This creates scarcity, translating directly into higher rates for these providers. It’s simple supply and demand — product designers assume more risk than brand or design system designers, given that the products worked on are customer-facing and directly related to the business’ bottom line (i.e., the product users are “paying” for), and so this is part of why compensation is higher.</p><h3>Closing thoughts</h3><p>Product design is already a very narrow and specialized role. Tech companies have specific expectations in these roles, usually and mainly these two:</p><ul><li>Designers are paid to plan and model how some software should work, and</li><li>Designers should make the software they model look professional.</li></ul><p>Certainly, some companies produce software that is known to be easier to use — and more professional looking — than others than others but, regardless, these are the two main expectations that all tech companies have of designers. In its truest sense, “design system designer” is the best shot product design has at specialization — and these roles, as mentioned, tend to command lower compensation than designers who work directly on the customer-facing product, rather than internal tooling.</p><p>In addition to these minimum requirements, however, expectations can vary per team and company, too, of course. For example, where most companies are fine with just representative, still screens in Figma to model how some software should work, with engineers doing interpretive work to fill in the blanks as needed, a certain Gradient Camera app asks designers to model higher levels of detail. For instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*OncdIAT64mmRPZxOERGF_g.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*BSM9nht1RiMFdPj3eJcBoQ.gif" /><figcaption>Two prototypes showing advanced animations and interactions in a user interface.</figcaption></figure><p>These are complex interactions that tools like Figma, Axure, etc., cannot reproduce. However, the Gradient Camera app has enough interaction complexity that there’s no way around this level of detail in our models. Notice a few things:</p><ul><li>Animations are asynchronous (e.g., the video player animating in while the toast animates out),</li><li>The prototyping is not screen-based, but object-based (e.g., the cards in the stack individually animate out into their positions, even when not visible in the stack; a particle emitter is taking in sound data and rendering an animation based on that data; etc.),</li><li>These prototypes can take user inputs in complex ways (e.g., users can tap and drag on the album art and reposition it freely on the canvas).</li></ul><p>This is what goes into making a prototype pictured above.</p><figure><img alt="A screenshot showing some nodes in an Origami prototype." src="https://cdn-images-1.medium.com/max/1024/1*HpgKxJ1EssvWaZBnLgTPww.png" /><figcaption>Origami uses a node editor to represent things like functions and parameters they take.</figcaption></figure><p>Due to the nature of this product, this particular company needs designers who can step up and model these advanced interactions — this is because the Gradient Camera app is a product that uses <a href="https://developer.apple.com/documentation/swiftui/canvas">canvases</a> and canvas-like surfaces to allow users to interact with the product in complex ways (e.g., users can draw, add in GIFs and resize them, objects animate in and out in complex ways, etc.). These interactions are some of the most complex a designer might work on in their career.</p><p>When the ceiling of complexity around interactions increases (as is the case in Gradient Camera app), designers are commonly expected to fill that gap. This is reasonable. As interactions get more complicated, designs become less possible to split across designers. It is easier to have “pure UX” designers (who then pass gray boxes off to “pure UI” designers) the simpler the products are (e.g., websites, e-commerce sites, etc.). As they get more complicated, this becomes nearly impossible. In products with complex interactions, the gray boxes are hidden behind complex gestures, are usually ephemeral, and can often be highly dynamic, themselves. I don’t see a way to sustainably break this up between multiple people, which is why Gradient Camera app doesn’t bother.</p><p>For my part, I’m not sure where the “UX” ends and the “UI” starts in the models above. The timing of interactions in gesture-based products really matters — and it’s one of those things you need to “feel” out, and only while building a very detailed model. This cannot be easily separated into “UX” and “UI,” as more simple products that only rely on simple tap targets can.</p><p>But there are other products that can be this complicated, too, for example: the TikTok editor, FigJam, Facebook Live, etc. In products like these, there are <em>also</em> a lot of gesture-based interactions that can asynchronously occur, and that are difficult to communicate in still screens. This is why products like the Gradient Camera app ask this of their designers. This is contrast to even when I worked at a certain Bird App — in that product, like most I’d worked on in my entire career, there were mostly just simple tap and click targets that either bring up modals, or cause page refreshes.</p><p>Certainly, most products don’t <em>need</em> complex dragging and pulling and pinching that is commonly seen in mobile video or image editors (e.g., TikTok, IG Stories, etc.), and so the amount of motion and animation work needed in these products is very low. This is a good thing — most products are simple enough that simple taps and clicks are exactly all that’s needed. Again, it’s not every day that you work on interaction-rich products.</p><p>For our part, designers at a certain Gradient Camera app are expected to (1) be the sole designers on their teams, and (2) develop product strategies (our cadence is every two quarters — it was quarterly at Bird App), and (3) execute on those strategies as sole designers, and (4) build complex prototypes of every interaction (see above). At every workplace over my last seven years, though, I’ve had to do 1–3 — and, sometimes, other tasks. The last one being new to me.</p><p>For example, I’ve designed A/B tests and dropped the trackers in the codebase — this is frequently done by data scientists and developers at companies like Bird App and Face Literature company, but it made sense for me to do it in the situation I was in. Other times, I’ve written scripts for users to follow in usability tests of interaction prototypes concerning features I wanted a gut check on — researchers are the ones that are usually employed to do this, even on a part time basis.</p><p>At most companies, I’ve been relied on to inform our quarterly roadmaps — and sometimes relied on very heavily. I’ve also worked as both a designer and developer at tech companies (very few companies ask designers to know anything about engineering because they understand this is a very tall order — it makes hiring nearly impossible).</p><p>Making software isn’t a science — it’s just software. As a result, there will be lots of role collision, and designers should seek to, above all, be grateful, be helpful, and be open to doing stuff that isn’t explicitly in their job descriptions. Learning is not subtractive, either — it’s always additive. A designer learning how to make incredibly detailed prototypes or learning to be a fully functioning engineer can only be said to be a stronger professional for it, for example.</p><p>There is no specific reason why, in product design, putting points in your aesthetic or technical abilities should somehow take points out of your capacity to reason through user flows in a feature you’re building. We are fortunate to work in an industry where it is <em>possible</em> to be good at a great many things without significant investment or risk of failure seen in other industries (see: surgery).</p><p>No matter where you go as a designer, you’re going to be expected to produce software that is made in way that’s reasonable for most users (“easy to use”), and that looks professional (read: <em>some</em> regard for visual design, or whatever your client/employer allows you to get away with). From there, responsibilities might increase, where you may be expected to take on a lot of strategy work (usually more commonly done by product managers), or to model very detailed interactions (see: prototypes above), etc. My advice would be to roll with the punches.</p><p>Whatever is needed to get the software out — and, ideally, a great product made — is our one job. That creates a lot of incredible opportunity for lots of depth in lots of directions. It’s not every day that all of this lines up as well as it does in software.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad3f455e5c37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-if-there-arent-actually-any-specializations-in-design-ad3f455e5c37">What if there aren’t actually any specializations in design?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How design (generally) works at tech companies]]></title>
            <link>https://medium.com/design-bootcamp/how-design-generally-works-at-tech-companies-36c591ac4744?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c591ac4744</guid>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Sun, 18 Dec 2022 23:15:01 GMT</pubDate>
            <atom:updated>2022-12-20T04:50:13.390Z</atom:updated>
            <content:encoded><![CDATA[<p>In my seven years as a designer, I’ve worked across a lot of companies — this wasn’t my intent, and so it’s not necessarily something I’m particularly proud of. That said, life’s full of all sorts of unexpected twists!</p><p>It is certainly true that there are things that aren’t <em>great</em> about constantly switching jobs (which I can reflect on in some other opinion, if there’s interest). Nonetheless, while I wouldn’t necessarily recommend job switching for <em>every</em> early career designer (particularly for ones who are lucky enough to land at top tech companies early on), I might broadly recommend it for the majority of them (i.e., the ones who don’t).</p><p>Putting the downsides of job hopping to one side, there <em>is</em> an upshot to having worked at a ton of companies over the years: I’ve gotten a lot of experience figuring out the patterns across a great deal of companies, and I can, therefore, more readily impart reflections on this topic on readers and mentees.</p><p>In this opinion, I’ll reflect on this very topic: how digital products are made across <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055">tech companies</a> — big and small, with a brief mention about what it’s like to build digital products at non-tech companies.</p><h3>Real quick: definitions</h3><h4>What’s a “big company”?</h4><p>Understandably, a discerning reader may want a clear barometer from the author around what a “big” tech company is, compared against a “small” one. For instance, a certain Face social app has 70,000 employees, a certain googly search engine company has 150,000, and a certain Bird application had 7,000 (at the time I worked there, anyway). Which is the “big” company in this situation? Which is not?</p><p>Is it based on employee size, or DAUs (daily active users)? For example, a certain Gradient Picture app (by the Face app company) has 500 million DAUs and around 3,000 employees. A certain Bird application has 300 million DAUs and 7,000 employees. Which company is the bigger company in this situation?</p><p>I’ll leave it up to the reader to decide on this question. I think, for most people, all of these companies would be considered in the “big company” bucket, with some big companies being <em>bigger</em> big companies than other big companies. This definition feels satisfactory enough for me, personally.</p><h4>What’s a “tech company”?</h4><p>That said, readers may also be wondering about what I mean by “tech” company versus “non-tech” companies. In my view, I believe there is a distinction to be made between software companies. For expediency, I’ll quote myself from a previous opinion, <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055"><em>What’s a tech company, anyway?</em></a>:</p><blockquote>Consider this question: which company feels more like a classic example of a “tech company” to you? Tata Consultancy Services, or Stripe? … Despite that both of those companies listed above make software, I think we all know the answer to that question. It seems that there are traits about companies that would make some software companies “tech companies,” while other software companies are not. I think most people have a sense for this, but simply haven’t formalized these thoughts. Consider the following:</blockquote><blockquote>- All “tech companies” are software companies, but</blockquote><blockquote>- Not all software companies are “tech companies.”</blockquote><blockquote>This is best illustrated by the comparison above (between Tata Consultancy Services and Stripe) — both of these companies make software, but few people would say that Tata Consultancy Services is a “tech company” (more correctly, most would probably say something like it’s an “IT company”).</blockquote><p>Giving an example to more concretely describe what I mean, seven years ago, in what was my very first design job, I worked at what I would today call a company that makes software, but that is <em>not</em> a tech company. It was quite a dated company, even by my own standards at the time.</p><p>Non-tech companies and organizations can be big or small in size, can be agencies or product companies, can be government or private, and so on, but the common denominator between all of them is that they operate nothing like tech companies do.</p><p>It’s difficult to provide the reader a surefire, absolute way to define which software companies are and aren’t tech companies. As I write in that same opinion:</p><blockquote>I don’t mean to suggest that this is some kind of scientific system — there’s something inherently fuzzy about all this, as it requires one to consider a company’s internal culture and make judgments about it.</blockquote><p>But I think that the most meaningful, distinguishing factor between tech companies and non-tech software companies is the work culture, as well as the product worked on. To give some concrete examples:</p><blockquote>In an example that holds some real emotional value for designers this week, I propose that Adobe is a software company, while Figma is a tech company. I would also say that Disney+ is a software company (more accurately, a team that makes software inside of a media company), while Netflix is a tech company. Best Buy is a software company (they do actually make software!), but Amazon is a tech company. U-Haul is a software company (they also make software!), but Uber is a tech company.</blockquote><p>What’s more, tech companies build digital products, and those products <em>are</em> their business — which is why they are called SaaS (software as a service) companies. Non-tech companies maintain and offer software services (e.g., Bank of America), but that isn’t usually their core business.</p><p>I wouldn’t try to come up with an overly complicated system of taxonomy — just go with your gut. A lot of tech companies feel “hip” and “cool” and “tech forward” (e.g., Stripe), which is often enough to signal to you that it’s a “tech company.” When the companies are somewhat more dated and stodgy, or don’t have software as the main focus of their business model, then it’s probably not.</p><p>With definitions to one side, on to what the reader came here for!</p><h3>Great, back to regular programming…</h3><p>In my experience, design at big tech companies doesn’t feel much different to design at small tech companies.</p><p>What’s usually different between big and small tech companies is the team composition — the availability of extra hands. At almost every single tech company, there is usually one PM per designer, and multiple engineers supported by these two. This is usually the minimum composition of most product teams, but I’ve also worked at companies where I was the only designer, and we had no PMs. Below are a smattering of examples from my work history, to give the reader an idea of team compositions at variously sized tech companies.</p><h4>An extremely small company</h4><p>At an 8 person tech company, I was the sole designer, but also a front-end developer. Our CTO, also a developer, was the one who most often behaved like the PM, but this was never explicitly stated. We had broad ideas for what to work on, we might talk about it as a team and decide what we wanted to work on each week, and I would often design right in the browser and push commits to the codebase and get the features built myself. We only had one designer (myself), and the rest were developers, with the exception of the CEO. I would say this product had <a href="https://mailchimp.com/resources/product-market-fit/">product-market fit</a>, but the market was not financially viable (especially in the way we were monetizing it). Regardless, the features we chose to build were mostly based on a culture of debate and back-and-forth — in other words, just, like, vibes.</p><p>This startup was fortunate to have 150,000 unique sessions a day in some parts of its product. We could A/B test to a very high confidence interval (“statistical significance”) in just a few weeks due to this. For most startups at this size, they’d be lucky to have a few thousand DAUs. We would A/B test whole new flows in features, and whichever one performed the best would be the one that shipped.</p><h4>A pretty small company</h4><p>At a tech company of 80 employees, I was one of three designers, and each designer owned one of the three main problem areas in the product (we had a plugin thingamajig, a text editor, and this native app, and so there were teams formed around each of these products). Likewise, there were three PMs, and each designer was supported by their respective PM and, together, they presided over their problem area. We had a bunch of engineers, and they tended to pick up similar areas of work, and so the same engineers were always in our calls. These were what many refer to as “feature teams” (other words for these might include “product teams” or “pods”), but it was the same designer, PM, and set of engineers working on the same product areas all the time. We had one copywriter who supported all three product areas, and you could walk her through the feature you were working on to solicit her perspective.</p><p>The roadmap and strategy was mainly decided on by the three PMs and their manager (who carried a title some of you may have heard of before: “VP of Product”), and the work distributed among the three feature teams accordingly, based mostly on focus. It often felt like you could just pitch an idea to your PM and get it on the roadmap without fuss (provided it was a decent idea that made sense with the product’s strategy), so the roadmap was frequently flexible and you could sort of do whatever you wanted if your reasoning was good enough — that said, sometimes the idea would be pushed to another quarter, or prioritized relative to other, higher priority efforts in the business. PMs often liked writing <a href="https://medium.com/@yamilah/common-words-phrases-and-acronyms-you-might-hear-while-working-in-tech-a46a088e910f">PRDs</a> (other words for this: product spec, brief) and have those ready for designers to reference when building. Sometimes they were made after the designer had already started. It just depended on the situation.</p><p>We had a part-time researcher who would help out when you felt you wanted to test a feature you were building with users and get a sanity check in terms of its usability, or desirability. Before it was acquired by Adobe, this product never found product-market fit. This product had no users at all, and our product strategies were also determined through a culture of debate (read: vibes).</p><p>I was the one who built our design system, as I thought it would be helpful to have a bunch of shared components as we onboarded new designers on to the team. It was super helpful. There was no specific design system team, I just made it on a weekend myself.</p><p>We also had a brand team (sometimes called a “creative team”), which was made up of two brand designers. They didn’t do product work — they worked on marketing materials (like the product’s website) and general branding. They often consulted with the copywriter for some brand writing, as far as I saw. They were often in our critiques and always had fun things to say.</p><h4>Still a pretty small company</h4><p>I worked at a dev &amp; design shop of 150 people that sold feature teams to tech companies of various sizes. For example, Houseparty might approach this dev &amp; design shop and buy a feature team to come in and build an MVP of a new product or feature they might be looking to build.</p><p>We would often come on board for 6 months and be directly embedded in their company to figure out what they had in mind, help with strategy, and then build the full MVP of a new product or feature they were looking to build. They often had a PM on their side — if it was a very small company (they often were), it was often just the CEO or CTO. If the founders were very inexperienced, the designer on our side would behave like a PM, but it was never an explicitly stated role. They just needed us to build an MVP of their idea to go to market, so we’d help them with whatever they needed to help get some validation as early evidence of potential for product-market fit for the product we were building.</p><p>These small companies were often bootstrapped (raised their own capital) — they’d reach out to us to buy a ready-made feature team to build the feature (a designer and multiple engineers). Designers at this company were expected to perform both as designers, but also front-end developers, so everything we designed, we also built ourselves.</p><p>The designer and the engineers usually decided what to work on together, week over week. Sometimes, the clients had special concerns, and we’d consider those concerns. Other times, they were very hands-off and we just prioritized as we saw fit (read: vibes). We never made design systems, and there weren’t brand teams (unless we were helping build a product at an established company).</p><h4>A large company</h4><p>At a certain Bird app company of 7,000 employees, I worked on three, separate teams (I team transferred once, and then that team got re-orged, and dissolved into another team, making it three teams I’d worked across). On one of the teams I’d worked on, there were three PMs, and I supported all three of them across three different product areas they owned. We were looking to hire one designer per PM (and their attendant problem areas on the product), but it was just taking some time.</p><p>On another team I’d been on while there, there was only one PM, and he supported all three of us designers. None of the teams I was on had dedicated data scientists, but we did have a researcher on one of the three, and copywriters in two of the three.</p><p>On teams where we lacked one or more cross-functional partners, we often made requests to the respective orgs (where needed) to see if we could get those resources reviewing our work on one-off bases — as if on a consulting basis. Each of the three teams, however, had their respective set of engineers (web, iOS, and Android, as the products across all three teams required implementations across all three codebases), at least one designer, and at least one PM, at any given time.</p><p>Each team was formed by directive of product people higher in the chain — someone in the organization decides that an opportunity is worth pursuing, giving the team its broad charter (“build a consumer-facing subscription app in the Bird company app,” or “build group-like functionality into the Bird company app,” etc.). From there, all cross-functional members of the team could decide together what our <em>specific</em> strategy would be, though PMs were most often the deciders on how to prioritize the order of the work to be done.</p><p>The entire Bird company was broken up into three, main teams, with smaller and smaller teams flowing from these segments:</p><ul><li>Internal tools (e.g., lots of engineering teams, internal performance tools, etc.),</li><li>Premium products (so directly revenue-generating products, e.g., the ads platform, etc.),</li><li>Freemium products (e.g., the home timeline, the search surface area, growth teams, etc.).</li></ul><p>Within the “freemium” products, there were further segmentations (often called “pillars”):</p><ul><li>Core products (e.g., the home timeline, search, DMs, etc.), which were the products with obvious product-market fit, sort of “bread-and-butter” products, and</li><li>Horizon products (e.g., “group-like” functionality, audio calls, “Patreon-like” functionality, subscription services, etc.), which were bigger bets the company was making that were “on the horizon,” or ones that didn’t quite yet have obvious product-market fit.</li></ul><p>So, if I was working on the Bird App Consumer Subscription Product TM, that was on the Horizon pillar (it was frequently confusing to people on this product why it wasn’t directly orged under the Premium org), and there were a bunch of sister teams on this pillar, like a certain Bird App Audio Calls TM team, and a Bird App Groups Team TM, etc.</p><p>These were all teams that focused on finding product-market fit to prove to leadership to keep investing in them. They were autonomous teams that operated in whatever way made sense for them, so some people could conceivably have wildly different experiences at the same company — even on teams on the <em>same</em> pillars.</p><p>The objective of all these teams is to increase DAUs (daily active users) for the entire product as much as possible, and/or acquire new users (bring on new users) to the product. If a team can demonstrate that its product is driving key metrics (these depend on each company, but for most companies, DAUs and user growth are both a common key metrics to go by), then there’s stronger signal that customers want that product — which indicates product-market fit. At that point, the team tends to receive more investment (in the form of greater resources, like staffing), and is often moved to a “core” product area, and out of the more speculative areas of the organization.</p><p>Product strategies are mostly vibes, and we did them roughly quarterly, but we could add and remove work from the roadmap as we saw fit. At this company, there was a culture of debate on most of the teams I was on (between all of us — PMs, designers, and engineers, though the PMs would often be the deciders), and then we’d agree on the work we’d want to do, and in what order. We’d release features and sometimes have basic analytics we’d pull, so as to check for any regressions in any key metric. If there weren’t too many serious regressions, we’d just keep the feature. We often just shipped without any holdouts (e.g., A/B testing), though, and just went with vibes, especially on smaller product areas with no (or few) established users yet.</p><p>There was a design system team, but they weren’t embedded in any specific product team — it was more like a standards committee, and they mostly enforced usage of the design system, often through product reviews (particularly if you were working on a totally new product area). I wasn’t able to meet one designer that enjoyed using the provided component libraries, so they mostly copypasted from themselves in their own, outdated files. Developers still got the gist, and it was fine.</p><p>Also, this Big Bird app had a very robust brand team (internally referred to as the “creative team”) — there were art directors, illustrators, and more. Illustrators, as I understand, were separated into people who made product imagery (so spot illustrations in marketing pages, or fun error imagery, etc.), and people who made iconography, etc. There were people who made time-based work, too, I’m sure. Also, there were general “visual designers,” and these people tended to be the ones who worked on marketing pages (the website-y elements of the product), and then they’d work with illustrators and others to get assets for the pages they’d work on.</p><p>None of the listed people above were involved with product work. They helped with creative services, and product teams could consult with them to get new icons (and stuff) if we needed any for our new product areas, if any.</p><h4>A ginormous company</h4><p>At a certain Gradient Camera app of 3,000 employees in a larger Face social app of 70,000 employees, I’ve so far worked on two teams. One, just for a few weeks, as the entire pillar my team was on got re-orged (I was subsequently moved on to another team). As mentioned earlier, re-orgs are fairly common in tech companies, and tend to increase in likelihood as market situations change. These are opportunities for leadership to define their visions for the pillars that they respectively own and, in turn, respond to directives from some of the highest leadership in the company.</p><p>For example, if leadership feels that the market has shifted, and that the org needs to focus on bringing up DAUs, and they notice that most DAUs are using specific products, they tend to remove investment in the underperforming products in the portfolio, and more strongly invest in more promising parts of the product, or kick up entirely new product areas to focus on, instead, if they believe an untapped area in the product exists. Leadership will resource these teams as they see fit, and those teams have to build the strategy that concurs with the team’s provided (and often somewhat broad) charter, and prove to leadership that their strategy for the half is sound.</p><p>At a company of this size, both teams I’ve been on thus far only ever have had one designer and PM, an EM that behaves more like a technical PM, a bunch of engineers, and we always have a copywriter, researcher, and data scientist — but these roles are usually shared across multiple teams. For example, my researcher might also support a sister team on my pillar, too — same with the copywriter and data scientist. If leadership sees fit, they might also staff very specific and special roles on your team, too, like a “growth data scientist,” which is a special kind of data scientist that very specifically focuses on and can help with growth metrics and strategies (as an example).</p><p>Designers, PMs, and engineers are only ever (with few exceptions in my career) staffed on to one team at a time where, by contrast, researchers, data scientists, copywriters, and other roles tend to support multiple teams simultaneously, usually in the same pillar.</p><p>At this company, designers are expected to drive product strategy, but with input from their partners on the team. It’s recommended that you work with researchers to pull information from user interviews (mainly) to evidence problem areas to focus on, and then use that as evidence in meetings with leadership to get sign-off on your proposed roadmap. You can ask data scientists to pull analytics about target cohorts and associated behaviors, churn rates, and other metrics, to further evidence your product strategy. This is done in “halves” (or two quarters, meaning a “half year”), but most of the companies I have worked at have done strategy and roadmap planning quarterly.</p><p>Ultimately, the goal is to get approval from leadership to execute on a vision for the half, mainly led by the designer, but in collaboration with partners. After this, the entire team goes into execution mode for the entire half — as things come up, the team can adjust, but generally you want to work on what you say you will.</p><p>While researchers and data scientists can help designers and PMs evidence their suggested strategies and roadmaps for each half, there’s no expectation that these strategies are going to work out <em>exactly</em> as planned — it’s understood that building these plans every half is purely evidentiary (read: vibes), rather than a reflection of perfect reality. Research is used to bolster intuition-based arguments about the direction to take the team in (read: vibes), and designers are expected to use whatever evidence they have at their disposal to persuasively argue for the visions every half (also read: vibes). The team also has to define what their key metrics of success are on their team, and what metrics they want to move, specifically. Features in their roadmap should ladder up to that metric goal.</p><p>There is a culture of debate here (read: vibes), and not every idea makes the cut after extensive discussion with leadership. When things do ship, they always ship as A/B tests against very small portions of the population, usually in target locations in the world. If the variant performs well and causes no significant regressions to key metrics, the feature can ship to bigger populations in more locations, and the test is often repeated again. If there are ever significant regressions, the recommendation is automatically a “no-ship.” If there are slight regressions, but some positive changes, then a ship <em>may</em> be recommended.</p><p>From what I’ve seen, no matter how persuasively you’ve argued with research for a feature earlier in the half, if a feature is tested and performs poorly, it will not ship. Actual user behavior measured via extensive analytics are the deciding factors here. Research and other information is purely evidentiary, helping to guide strategy and vision.</p><p>What’s more, <em>this</em> product, specifically, is a very complicated one. We use a prototyping tool called <a href="https://origami.design/">Origami</a> very extensively to model very complicated, canvas-based interactions. Where most products (e.g., Medium, LinkedIn, Twitter, etc.) work by using simple tap targets on things like buttons, causing simple modals and page refreshes to occur, this particular product has an enormous amount of asynchronous and complicated gestural interactions and animations. Given that it’s a canvas, complicated properties (X and Y positions on a canvas) are set by user input, for example, via drawing tools users can use, or tools to add fun stickers to one’s images that be repositioned and resized with two-finger gestures, or filters set via drag and pull gestures, and other complicated interactions.</p><p>Something like Figma goes underused here. I’ve never seen this before, and I probably will never see something like this again, as there aren’t many products that require this amount of complicated gesture-based interaction work. Some notable examples of this very thing could be TikTok, FigJam, and other more canvas-based products. The prototyping tool we use (as mentioned: <a href="https://origami.design/">Origami</a>) is a node editor, and one can declaratively toggle props on elements in the canvas using these nodes. But it also allows one to use JavaScript to build one’s own nodes, if one should like. This is a tool that, as a result, has a very high ceiling of complexity, and it’s a common topic of discussion among designers here as being incredibly painful to use. But we make it work.</p><p>There appears to be a lot of collision between teams across different pillars that sometimes appear to work on very similar problem areas, which can be very disorienting, if I’m honest. Competition between teams for “impact” appears to be encouraged.</p><p>What’s more, there’s a strong incentive among designers to come up with lots of ideas to then bequeath to other teams, where those ideas have better roadmap fit. You’re constantly learning about teams you’ve never heard before that work on something slightly similar to the thing you just thought of, and that it went well or didn’t, or that maybe you now have to have calls with them to get the inside scoop.</p><p>Performance cycles appear to be rigorous: designers have to prove “impact” by using evidence to argue for their success over that year — designers might use things like product launches that increased DAUs or user acquisitions, or other key metrics. They might also use other things they’ve done that lack obvious measurements to argue this as well (e.g., cleaning up component libraries, organizing stuff for the team that makes working on stuff less annoying, helping with hiring, helping with teaching Origami, etc.).</p><h4>Commonalities</h4><p>These are just a smattering of companies I’ve worked at spanning my seven years in the industry, but what’s clear to me are a few traits shared in common:</p><ul><li>Most product decisions are intuition-based, even at the highest level of leadership,</li><li>On product teams, the core teammates are almost always a singular designer, singular PM, and a bunch on engineers (as needed),</li><li>The “feature team” approach (PM, designer, and engineers — and, sometimes, other roles — working as an autonomous unit, and closely together, to build in a specific product area) is a very common setup at tech companies,</li><li>PMs and designers tend to have role collision at various times (e.g., they might work together to build a strategy and roadmap), but it just depends on the company’s style and culture,</li><li>Tech companies do not hire “UI designers” — designers are expected to make good products, and make them look professional,</li><li>Most companies, even ones with several thousand employees, don’t have robust data analytics pipelines set up,</li><li>Roles like researchers, data scientists, copywriters, and etc., are somewhat uncommon, but increase in commonality the larger the tech company gets — even so, these individuals are usually multi-purpose, and support many teams at once,</li><li>Even at a big company, you might never work with a researcher, data scientist, or copywriter,</li><li>Designers are expected to always be significantly ahead of engineers — designers have to move much faster, and generate a large dearth of ideas to help the team shape what it wants to work on,</li><li>Leadership decides which teams and pillars are created, but teams have to work within that initial charter to create their own strategy and roadmap (though some companies may have leadership that provides this, and creates a very top-down approach to product strategy — it just depends on the company),</li><li>Tech companies don’t engage in any formal processes — designers don’t make personas, make site maps, and etc. We just make software, and there’s an expectation that we move quickly and ship fast. When available, the deciding factor in whether a feature launches is analytics and what they say about impact on key metrics — nothing else goes into deciding whether to launch.</li></ul><h3>A final note</h3><p>My very first job in the industry was at what I’d call a software company, but not a tech company. We had a “UX design” team, a “UI design” team, a research team, a copywriting team (and probably some others), and they all reported to the product org. There weren’t any feature teams — designers picked up prioritized tasks in a queue, and that’s how work started.</p><p>UX designers made gray-box schematics, mainly in Axure, exported them as PDFs, and then passed those off to the UI designers, who sat in Sketch making the gray boxes look good. UI designers also made a lot of “redlines,” which were measurements of spacing in the product (e.g., padding), which would get handed off to front-end developers. Researchers made a lot of personas, presented them to us during our “lunch and learns,” and hung them up in hallways to “build empathy,” and other such things. I distinctly recall a woman in a persona called “Busy-Bee Bethany,” and there were paragraphs about her lifestyle, and bar graphs to measure all sorts of characteristics about her. I recall finding this to be very curious and fantastical.</p><p>This was seven years ago now. My suspicion is that this approach might be more common among agencies and other non-tech companies. Looking back, this was a company that made a product that could be called something like “Dropbox for mergers and acquisitions” (legal stuff, don’t ask), and so the product was pretty conceptually simple. But, in true non-tech company fashion, I recall the product being very crowded, with tons of products and features users very obviously didn’t want and were very confused about. We had lots of sales people to argue for why these add-ons should be purchased by our customers. I recall feeling skeptical about whether or not those add-ons were truly helpful.</p><p>After I left that job, though, I’ve never seen anything like this setup again. I don’t have a strong reason to believe that I ever will.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c591ac4744" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-design-generally-works-at-tech-companies-36c591ac4744">How design (generally) works at tech companies</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</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 find a good mentor]]></title>
            <link>https://medium.com/@yamilah/how-to-find-a-good-mentor-6130eed6ee3e?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6130eed6ee3e</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Sun, 18 Dec 2022 15:14:40 GMT</pubDate>
            <atom:updated>2022-12-18T16:49:05.742Z</atom:updated>
            <content:encoded><![CDATA[<p>As many of you know, I’ve done a lot of mentoring — probably with north of eighty people at this point. Though I am no longer mentoring, something I’ve noticed is that almost all of the things I tell my mentees are a serious surprise to them.</p><p>By this, I mean that, without fail, they all remark that they’ve never heard my advice before. Real quotes abound, like: “no one has ever told me the truth about my work, not even the other mentors I’ve talked to,” “I’ve never heard this about the industry before,” “I now have a better understanding of how design works at companies, my mentors didn’t talk about this,” “I didn’t know that interviewing worked like that, my bootcamp mentors haven’t mentioned this,” “all the other mentors said my work was fine,” and so on.</p><p>Because my advice comes as such a surprise, the majority of those I’ve mentored choose to dispute what I say right on the call — they try to argue with me, prove me wrong, and get me to change my mind. I wouldn’t recommend this approach with your mentor — <a href="https://medium.com/@yamilah/how-to-incentivize-your-mentor-to-keep-mentoring-you-4014c9ad2e02">if you want them to keep doing you this favor</a> (a previous article I wrote explaining how to be respectful of your mentor), I would recommend practicing gratitude and emotional restraint when you feel like being combative. Personally, when this kind of behavior reveals itself, I no longer maintain these relationships. I’m certain many mentors can relate.</p><p>Putting respect for the person doing you a solid to one side, I’m not alone in hearing complete surprise from mentees. Chatting with other experienced designers who do — or have done — mentoring, I notice a few things: the nature of our feedback is nearly identical, mentees are always blindsided by said feedback, and most of them become argumentative (see above).</p><p>What is of particular interest to me, however, is that mentees are surprised at all — frankly, <em>I’m</em> surprised that <em>they’re</em> surprised. This tells me that there are a dearth of mentors not saying things that need to be said — even when they professionally advise as part of design programs (e.g., bootcamps, universities, etc.). This is likely part of what explains another common thing I hear from pre-/early career designers: “there’s so much conflicting information out there.” Many mentees feel confused and frustrated by the amount of confusing information out there — by the amount of “your work is great”s they receive from mentors, compared against the little interest they receive from prospective customers.</p><p>There could be many reasons why this occurs, however. For instance, it could be that mentors know most mentees easily become irate, argumentative, and ungrateful, and so mentors simply don’t feel comfortable telling the truth, as a result. Alternatively, it could be that many people attracted to becoming mentors just aren’t very experienced, themselves, and so they don’t have much actionable feedback or useful information to give. Perhaps there are other explanations — it’s hard to speculate.</p><p>Nonetheless, it is very concerning to me that there are so many mentees walking out of sessions with misconceptions and distortions about their work — and their chances on the market. In this opinion, I wanted to help discerning mentees figure out how to evaluate their mentors before committing to sessions (or subsequent ones).</p><p>This opinion also assumes that the reader is a designer that already knows what they want: to work at <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055"><em>tech companies</em></a> (e.g., Medium, Substack, Notion, Twitter, TikTok, Instagram, Webflow, etc.). If this is you, consider the traits below that will work for you.</p><h3>1. Your mentor works in tech</h3><p>If you want to work in tech, ensuring that your mentor does, too, is your first order of business, and is absolutely mission critical. You need someone who competes on the same market you are targeting — if they don’t, they will not be able to advise you. This is why your bootcamp mentors and university professors can’t help you, and you’re surprised when people who work in tech disabuse you of the misconceptions these individuals proliferate — the majority of them are not competing for the jobs you’re competing for.</p><p>The advisors in your design program, generally speaking, compete for jobs in <em>education</em> — you are competing for jobs in <em>tech</em>. These individuals don’t know how to compete on the market you’re targeting, and it’s because they don’t have to know. As a result, it is very easy for them to <em>believe</em> they know what it takes to compete on this market — but those beliefs will never be checked against reality, because they’ll never experience it, themselves.</p><p>Equally, there are many mentors who <em>believe</em> they work in tech, but actually just work at companies that sell technology services in some other capacity. There are many ways to <a href="https://medium.com/@yamilah/whats-a-tech-company-anyway-c79f6daa055">work on software, but still not work in tech</a> (a previous article wherein I explain the difference between working on software, and working in tech, specifically). Here are some examples of companies (and organizations more generally) that could have you working on software services, but that are, nonetheless, not tech companies:</p><ul><li>Agencies (e.g., you might work on websites advertising services for companies, or simple checkout experiences for e-commerce companies, etc.),</li><li>Government (e.g., a local government where you might be working on informational websites about resident benefits, often with simple account management, etc.),</li><li>IT companies (e.g., simple ticketing software for enterprise customers, making simple package managers with skins for a company’s employees, etc.),</li><li>Brick-and-mortar turned digital (e.g., banks, insurance companies, airline companies, rental companies, moving companies, old payment processing companies, hardware companies like IBM and Intel, etc.),</li><li>E-commerce companies (e.g., retail of physical products that are sold online on a simple e-commerce platform they maintain for their brand, etc.),</li><li>Educational institutions (e.g., bootcamps or universities, etc.).</li></ul><p>Again, there’s nothing wrong with these companies or organizations, but the listed examples above will not have designers working on products. As I’ve mentioned in <a href="https://medium.com/@yamilah/how-to-speedrun-building-a-product-design-career-in-90-days-for-free-d55765dac9e8">previous articles</a>, for example, <em>websites</em> are not <em>products</em>. They are online brochures. You don’t want to compete for jobs where you make online brochures — you most likely want to work at companies like Twitter, Notion, Medium, Instagram, Instacart, Slack, Google, Apple, Uber, Lyft, Snap, Spotify, Discord, etc. These designers do not touch their company’s marketing material, and they don’t make simple checkout experiences. They make chat products, text editors, music streaming services, ridesharing products, image sharing apps, etc. These are complicated experiences that take in a ton of user inputs.</p><p>By contrast, websites don’t do any of this. Websites exist to allow people to consume information and either take a simple action (purchase, download, subscribe, etc., to something), or nothing at all. They mostly display what developers call <em>static</em> content, where products leverage user data to render <em>dynamic</em> content. In other words, websites are brochures that generate leads for businesses and/or provide information — this is all to incentivize some top of funnel action on the part of the user, to get them into the product, itself (usually). This is not product work.</p><p>What’s more, if you want to successfully get jobs at tech companies, you need to know <a href="https://medium.com/@yamilah/what-its-like-to-interview-as-a-product-designer-fcb7c88e75ca">how they interview</a> candidates, what their expectations are, and what your competition is. People who work at the companies and organizations above will not usually know how to interview at tech companies, nor how to attract tech companies as customers, as those more traditional organizations listed above tend to have their own beliefs about what designers are (and what they do) — and those beliefs are not consistent with the ones that tech companies have.</p><p>For example, many people who work with more dated and/or simple software companies are accustomed to more dated work styles, such as having “pure UX” designers that pass gray box schematics off to “pure UI” designers. This is not going to be easy to do when working on a complex product, because the interactions on software like FigJam, Instagram Stories, Instagram Reels editor, TikTok, etc., are just too hard to enable this kind of ping pong between “UX designers” and “UI designers.” Product design is interesting in that, the more complicated it gets, the more it becomes inefficient to break roles up.</p><p>Tech companies don’t hire “UI designers.” They hire people who build good products, and know how to execute on them to a professional level in terms of craft, and then they hire people who work on the brand team (they usually refer to these as “visual designers,” etc.). Mentors accustomed to work styles where there are “UX designers” and “UI designers,” therefore, will unintentionally misinform prospective designers about the (lack of) importance of visual excellence in their work, for example. This will result in mentees applying to tech companies and getting no results, without realizing they are putting out work that is being crushed by the superior competition.</p><p>Another example is the nature of one’s case studies. People who work in more traditional workplaces listed above are not usually working on complex software, so they couldn’t advise on the kind of work mentees need in their portfolios (i.e., <em>real software</em> within products). They are likely to advise website redesigns (common in bootcamps and universities for this reason), or redesigning of successful apps, and other things that tech companies don’t care to see.</p><p>They will tend to advise you have stereotypical things like: personas, double diamond graphics, Google Forms research, site maps, walls of stickies and “maps,” and other “process” work, etc. These are things that recruiters at tech companies specifically <a href="https://medium.com/@yamilah/whats-in-a-case-study-an-alternative-perspective-a2605eac55da">ask candidates not to show</a> (a previous article written about what your case study content, specifically, should include, and quotes from recruiters at companies like Meta and Apple requesting specifically to <em>not</em> to see “process”), as this is not interesting to interview panelists, does not help us evaluate you, and we don’t have this “process” internally.</p><p>Adding to this is that tech companies are results-based and, as such, are highly merit driven. It is extremely difficult (read: impossible) to “talk” one’s way into these jobs, and so mentors from traditional organizations may often mislead mentees into believing they need to <a href="https://bootcamp.uxdesign.cc/okay-networking-but-does-it-work-though-612d0e48cbad">over index into “networking” and begging for referrals</a> (a previous article wherein I explain my thoughts on the efficacy of networking) when, in reality, they should be advising mentees to redo their portfolios, and focus on building software and visual excellence — with this being unequivocally the most optimal use of their time.</p><p>Lastly, tech companies also tend to have certain values, expectations, and styles of working that create culture shock in people who have never worked at them before. Tech companies do not work like how any of the bootcamps or universities claim — these programs do not prepare one to work at tech companies, but rather at more dated organizations. Mentees may onboard on to tech companies and be surprised at how little marketing bingo there is at tech companies, and that “process” work cannot be relied on as a crutch to appear to be getting results — people at tech companies make software, and it’s hard to fudge that. It’s hard work, and you will not be prepared in any way if you follow advice from those in traditional organizations. Expectations are frequently very, very high at tech companies — and for good reason (see: <a href="https://www.levels.fyi/">tech compensation</a>).</p><p>However, if you are not looking to work at tech companies, and you want to be a web designer (i.e., mainly work on websites, etc.), product designers are not good matches for you. Ultimately, you have to decide what you want to do, — work on websites or products — and make your decisions from there.</p><h3>2. Your mentor builds products, not websites</h3><p>As mentioned above, the reader is probably looking to work at tech companies, — working on digital products — rather than at companies that build websites for other businesses. As a result, it’s best to consider mentors that work on digital products, particularly at tech companies.</p><p>When people mostly work on simple software like websites, they don’t know what it takes to work on complex software, like webapps or native apps. They are very unlikely to know how to prepare case studies that persuasively argue based on past work that tech companies (companies that build digital products) should hire them. Building websites (and other simple software) tends to result in work styles that are also very different to building products, so they wouldn’t know what it’s actually like working at a digital product company, or how to become more appealing to them.</p><p>These work styles tend to be dated and very different to the kinds seen within tech companies, which makes it hard for one to understand the expectations that tech companies have, and so it’s not a great idea to take the advice of individuals who have only worked at places that have had them working on websites (see list above).</p><h3>3. Your mentor interviews — a lot</h3><p>Whether you’re a pre-career designer looking to get into the industry, or one that’s early in your career and looking to get subsequent jobs, you need someone who interviews a lot. Ideally, someone who interviews multiple times a year at tech companies.</p><p>Tech companies interview in <a href="https://medium.com/@yamilah/what-its-like-to-interview-as-a-product-designer-fcb7c88e75ca">particular, but fairly consistent ways</a>. If your mentor doesn’t interview often, or doesn’t work at tech companies, then they won’t be able to advise you well.</p><p>Your mentor should be very comfortable with whiteboarding and app critiques. They should frequently do well on these. They should be able to provide actionable tips on how to do these well, how to manage time, and the conversation. They should be able to help you practice an app critique or whiteboarding session with you on a call. They should be able to cite specific whiteboarding challenges from the tech companies they have interviewed with, and how they solved those.</p><p>Your mentor should be able to talk to you about how to make a case study slide deck, and how to present your work. They should be able to offer you feedback on how to make a portfolio site that is attractive, and the importance of craft as a differential advantage in the early parts of hiring pipelines.</p><p>They should have extensive experience being on the other side of hiring, too, — on interview panels at tech companies — and should be able to describe how those work. They should be able to explain how referrals, hiring pipelines, and hiring panels work and be able to advise you on all three of these topics.</p><h3>4. Your mentor has good visual design</h3><p>Many people believe that craft doesn’t matter in product design — this is probably true for people who work at more traditional companies (e.g., banks, old payment processors, ad agencies, etc.). But this is not true in tech. If you want to work in tech, you’re going to need to compete — hard.</p><p>At tech companies, compensation is higher for a reason: you are expected to produce quality work in all ways — product strategy, and execution to a high level of craft. There’s usually only one designer per feature and problem area, so your output is expected to be high. There are no visual designers waiting on your beck-and-call to polish your work — that’s all you. You are expected to go through reviews of your work with your peers, and so the software you work on should be well reasoned, and should look professional. Your mentor should be able to understand the importance of good visual design and that, at tech companies, “UI designers” are not hired. They should be able to explain that visual excellence in the product is your responsibility — not someone else’s.</p><p>Your mentor’s work should reflect this. They should be good at making software, and good at making it look professional. It’s going to be difficult for you to evaluate visual excellence, as someone who doesn’t have it, but you should look for designers who have unusual visual voices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IiA1LdsL5Cmadxfw59Fnwg.png" /></figure><figure><img alt="A screenshot of a website with interesting layouting." src="https://cdn-images-1.medium.com/max/564/1*ujlw91y6dj6QPXiEh_v9tg.jpeg" /><figcaption>These are unusual visual voices. People like this are very hardworking. Credit for <a href="https://www.thenewcompany.com/">left</a> and <a href="https://dribbble.com/shots/9807983-M-Editorial-Website-Hover-Animation">right</a>.</figcaption></figure><p>By contrast, you might want to avoid designers with portfolios that look generic. It indicates that they are unlikely to have much visual skill, and so they won’t be able to spot the weaknesses in <em>your</em> visual work. They are likely to tell you that your work “looks good” or is “fine.” They likely sincerely believe that.</p><figure><img alt="Screenshot of a generic website." src="https://cdn-images-1.medium.com/max/564/1*mzrQ1ikofvwfpeQS-i25dQ.jpeg" /><figcaption><a href="https://www.designerpeople.com/blog/website-design/99-website-design-templates/">Credit</a>.</figcaption></figure><p>They should be able to see the problems in your visual work, and explain how to get better in the most efficient way possible.</p><h3>5. Your mentor builds a lot of software</h3><p>Your mentor should make software for a living — as stated, this should not include websites, but digital services, and specifically at tech companies. They should have a lot of experience making software and working on software teams. They should have worked on software teams for some time now, and have been around the block with the production of software.</p><p>They should be able to tell you how product teams work at tech companies. They should be able to explain what a <a href="https://medium.com/@yamilah/common-words-phrases-and-acronyms-you-might-hear-while-working-in-tech-a46a088e910f">PRD</a> (or spec, or brief, etc.) is, how research is used in most tech companies, how quarterly/half planning works, how roadmaps work, what product strategies are, and how to get impact on products. They should be able to explain how work gets picked up at tech companies, and what it’s like to lead a product from end to end. They should be able to explain where ideas for products and features come from. They should be able to explain the role of research at their company (if any), and companies more generally.</p><p>They should have experience working with design systems at companies, and should be able to tell you how important it is that you know much about Figma and design systems. They should be able to explain the importance of discovering edge cases while designing a feature, and what it’s like to build features in a team on a larger product. They should be able to explain how promotions work (especially at bigger companies), and how to deal with social situations that might come up at work.</p><p>They should be able to tell you what is going to make your portfolio attractive to recruiters and hiring managers. They should be able to explain what needs to be in your portfolio. They should be able to advise on what should be in your slide deck and how to explain the software you’ve worked on.</p><p>They should also be able to help you reason about software you want to make — when you’re building your own, they should be able to look at your software’s premise and its execution to tell you where there are problems. They should be able to break down your software into attendant parts and come up with optimal solutions. They should be able to tell you if the software you’re proposing makes any sense in the first place. They should be experienced in making product strategies, and should be directly involved in (or even leading) quarterly or half planning at their company.</p><p>In other words, they should be very experienced with working on software teams and building software — whether on small teams, or large ones. They should be able to advise on what the differences are between tech companies and other kinds of companies, and help you disambiguate what steps you could take in your career based on your goals in order to most quickly and optimally achieve your goals.</p><h3>6. Your mentor is very technical</h3><p>Your mentor should be experienced with working on software teams, and so should be experienced with software, itself. Ideally, they have built software on their own, as well, and should be able to tell you technical information about how software works and what it can do.</p><p>They should be able to explain what native apps are, what web apps are, what’s the difference between these two things, and some of the quirks of designing for either case. They should be able to help dispel technical myths common among non-technical designers (e.g., the importance of “grids,” the overstating of design systems, how developers consume your designs, etc.), and help you remain focused on what really matters when building software.</p><p>They should be able to help push you in your designs, reminding you of untapped areas in software that you could consider in whatever product you’re building. They should be able to help you push your designs technically, and impart technical knowledge about how you can consider new areas in your product work.</p><p>They should be able to advise about how to use shortcuts in your work (e.g., ripping SVGs from the web using the inspect panel, using autolayout to make things more convenient when designing) — they should have answers to the most complicated Figma questions you can have, or might not even know you have. They should be able to help you build assets and animations that engineers can actually deploy in the codebase.</p><p>They should be able to explain how analytics work, what A/B testing is, and how these work in software. They should be able to explain how to prototype complex, canvas-based, and asynchronous interactions in software.</p><p>I’ll stop here, as I think this has gotten long enough. What I want to stress here is that, for people who want to be designers, — who want to design software at tech companies, — they’ll need someone who is also a designer who designs software at tech companies. If this is the situation you want to be in, you’ll need someone who is very experienced being you — who <em>was and is </em>you.</p><p>Your mentor should be able to have serious reflections on what, exactly, they’d do if they had to redo their career all over again — telling you what the highest value steps are to take to reduce the time it takes to get into the industry reliably, and how to use your time most optimally. The best way to do this is to find someone who’s made a lot of software, and who can tell you the truth about how this is done — not the academic, theoretical recounts of how software is made. You need actionable, clear steps to take to make your candidacy attractive to potential customers.</p><p>Here are examples of things that tell you that you need to consider other mentorship relationships:</p><ul><li>They give general advice,</li><li>They don’t work at a tech company,</li><li>They haven’t interviewed at any (or even a few) tech companies,</li><li>They make websites, rather than digital products,</li><li>They don’t have a good analysis about how the industry works,</li><li>They advise you use checklist “design processes” in your case studies,</li><li>They can’t tell you how to improve your visual design,</li><li>They can’t reason about software you’re building,</li><li>They’re never made a product strategy and don’t get involved in quarterly or half planning.</li></ul><p>Most importantly, the best way to determine all of this is to look at the software they’ve built. This is a (generally) good proxy for how rigorous they are in their own work — you want someone who will be able to encourage you to have rigor, too. If they work at agencies, local governments, brick-and-mortar-gone-online companies, etc., and they mainly build websites or simple products, you should look for other mentors. They are not likely to be able to advise you in the way you need in order to be successful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6130eed6ee3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual design — the designer’s Great Satan]]></title>
            <link>https://medium.com/@yamilah/visual-design-the-designers-great-satan-590c32cf1f97?source=rss-1713555e580d------2</link>
            <guid isPermaLink="false">https://medium.com/p/590c32cf1f97</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Y. A.]]></dc:creator>
            <pubDate>Fri, 09 Dec 2022 12:43:05 GMT</pubDate>
            <atom:updated>2022-12-09T18:02:58.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>Visual design — the designer’s Great Satan</h3><p>For my entire career in design, I have observed what appears to be an industry-wide low opinion of visual design (and its attendant visual designers) among product designers — or, as they were once called, UX designers. Such as it was, the UX design industry was in a golden age — there was a focus on making good interactions, doing good research, and all rejoiced. All was well.</p><p>But that all changed when the UI designers attacked. UX design became the dreaded UX/<em>UI</em>. This was verbal proof that visual designers had bastardized UX — they transformed UX into a shell of its former self, averting the eyes of all away from the important things (e.g., interaction, research) and, instead, towards such frivolous matters as a product’s aesthetics. The market (i.e., employers and clients) became equally as vapid, expecting time put into a product’s appearance, where they didn’t used to have such unreasonable expectations. After all, customers cared about the real things — the <em>important</em> things.</p><p>UI design’s terrible twisting of the industry is the cause of many problems within the industry, itself — it has been said to be the source of things like: worse software made across the industry via the phenomenon of “Dribbblization,” the reported decline of research in organizations, a saturation of hopeful talent at the top of the funnel (i.e., pre-career designers) rather than at the bottom (i.e., experienced designers), and so on.</p><p>But there’s another problem: I must confess that I don’t believe any of this has actually occurred.</p><h3>Some historical context</h3><p>I started as a designer around 2015. My first role was a “UX/UI design” role, though I didn’t know what that was at the time. I learned about what “UX/UI design” was months into that very job, when I heard colleagues presenting their thoughts on this career (until that point, I’d simply thought it was another job I’d had! — one can imagine my surprise to discover it was, in fact, a <em>career</em>), which they’d share during our “lunch and learns,” usually after returning from design conferences that discussed this topic. Through this, I learned that what I was being paid to do had a formal name.</p><p>This is all to say that, in 2015, this interpolation of “UX” and “UI” already occurred, and it seems like it was fairly established (e.g., being discussed in such large contexts as conferences and workplaces, etc.). This was nearly ten years ago now. If there was a time when this concept <em>didn’t</em> exist, it doesn’t appear to be the case as early as 2015, at the very least. To my surprise, chatting with older designers, I’ve heard some remark that, as early as 2008, they’d heard that very term, as well.</p><p>2008 was an interesting time. Many observe that this was the time when SaaS (software as a service) companies truly became viable and widespread — when they’d truly begin to pop up in ever-greater numbers.</p><p>The reader may be inclined to notice that 2008 was also the time of something else of importance: the creation of iOS’s App Store. At this point, it became easier than ever to get software in the hands of consumers. Previously, to get customers using one’s software, they either needed to visit an address on the web on their bulky computers, or get them to install your executable (which, as you all recall, often came with numerous installation issues for users). On consumer-grade OSes (e.g., Windows and macOS), there was no centralized package manager, and so executables had to be found in the wild, with users visiting those disparate addresses to solicit those apps. Malware abound!</p><p>Then came the App Store, or the “there’s an app for that” age. Software companies could get their code running on peoples’ mobile devices easily, and they’d stay updated, with a trusted, centralized source where software without malware could be found. From this came a boom of software and their attendant companies cropping up — absolutely <em>everyone</em> was making an app for <em>everything</em>.</p><p>The large change that Apple introduced into the market in 2007 (the Apple phone, and its attendant OS), itself, ushered in a new kind of culture around software and, with it, a change in consumer expectations.</p><figure><img alt="An image of a Motoral Sidekick. This phone was super cool for its time." src="https://cdn-images-1.medium.com/max/792/1*-7u9hPSbF-yK5PgRDWYo7A.jpeg" /></figure><figure><img alt="A screenshot of the original iOS interface." src="https://cdn-images-1.medium.com/max/259/1*ILPes6QxVWa843Rof4AIjg.jpeg" /><figcaption><a href="https://www.csmonitor.com/Technology/Horizons/2010/0702/Sidekick-finally-yanked-out-of-commission-by-T-Mobile">Left</a>: the Motorola Sidekick, a certified middle school classic (2008). <a href="https://en.wikipedia.org/wiki/IPhone_OS_1">Right</a>: a screenshot of the very first iPhone’s OS (2007).</figcaption></figure><p>Technology was changed forever. Consumers would accept phones on the left, but not for much longer. Apple came in, cut <em>all</em> of the features above (e.g., physical keyboard, mechanical folding of phones for convenience, overly complicated OS, etc.), turning up to the market with a box and a screen. People absolutely lost their minds. And for good reason, as these changes were substantial: for a long time, Apple had already been generating a lifestyle — bespoke hardware, but also software. But, after it unveiled its phone, it created something unto a <a href="https://en.wikipedia.org/wiki/The_Cult_of_Mac">cult</a>, as many quipped.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVQKMoT-6XSg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVQKMoT-6XSg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVQKMoT-6XSg%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/206226f3a798e9a551550e2ed0c09781/href">https://medium.com/media/206226f3a798e9a551550e2ed0c09781/href</a></iframe><p>When looking at the Motorola Sidekick above with perfect hindsight, the reader couldn’t be blamed for seeing it as almost a marker of a bygone era — a metaphor for what consumers <em>used</em> to accept, and how business was done. Messy software, buttons everywhere, a feature for everything you could never want nor ask for, and so on. When Apple cut all the fat and delivered only what the user wanted, — and nothing more — what followed could almost be described as a market correction on feature inflation.</p><p>Certainly, with the proliferation of software that the iOS’s package manager enabled, and, with the differential advantage of well designed hardware and software that Apple created for themselves on the market, there was, too, an increased conscientiousness around how software should look and behave, aligning with evolving consumer expectations. It is around this point where companies like Apple began to formally hire people to just think about software (and hardware) appearance and behavior, where it was historically the domain of people putting the hardware and software together (e.g., engineers).</p><p>Before this point in 2008, it seems having roles for this focus was not common. Most practicing designers at the time, themselves, were likely web designers, if at all — perhaps they made templates on <a href="https://business.adobe.com/products/magento/magento-commerce.html">e-commerce platforms</a>, or made marketing sites for businesses, or worked in agencies that made ads and micro-sites on the web, etc. But that’s the closest the industry had to people thinking about software’s external design as deeply as we do today.</p><h3>A paradise lost</h3><p>When I consider the narrative above, — that conniving and vapid visual designers came in and took our golden age from us — it doesn’t feel like it represents anything to my recollection.</p><p>I recall using computers (and the internet) as early as five years old. My parents didn’t understand the appeal, and they were perplexed by its absolutely abysmal interface, and my addiction nonetheless. They didn’t see what I saw — certainly, I saw the same confusing interface that they did but, putting that to one side, I could look past that and see so far beyond the annoyance of its slow, poorly performing, and generally frustrating exterior. I saw fun games I could play for hours on end, or fun things to read, niche forums where people discussed things no one talked about around me, and so on. I could spend <em>literally</em> all day on the computer.</p><p>In retrospect, allowing children unadulterated access to the internet was most certainly a bad idea — the knock-on effects of this we are feeling to this very day. Nonetheless, I was part of a demographic (geeky, tech-curious children in their single digits) that can be said to have been relatively early adopters of the internet, and personal computing more generally.</p><p>Putting cool math games to one side, my parents were completely right: computers really were absolutely horrible. They had a feature for everything you didn’t want, and nothing that you did. Nothing “just worked.” Errors happened and they weren’t human-readable. Everything was a hack on a hack. They were slow. They took thirty minutes (and, I recall, at times, hours) to boot up. Malware was rife — popups everywhere. A 200KB image would literally decimate your entire setup. Websites were spammy and full of e-garbage. Everything about it was objectively awful — the digital world was totally underdeveloped. Its visuals reflected that.</p><figure><img alt="A screenshot of how awful the internet was. It’s got text everywhere and looks spammy." src="https://cdn-images-1.medium.com/max/724/1*1LK-_723W_GtFXMFt47XLQ.jpeg" /><figcaption>Someone extend the digital world an IMF loan. Credit: “<a href="https://www.itsnicethat.com/articles/geocities-before-the-internet-was-cool">RIP GeoCities: what the internet looked liked before the internet was cool</a>.”</figcaption></figure><p>I’m not the only one who remembers this weird time in software land. As Emily Gosling writes in <a href="https://www.itsnicethat.com/articles/geocities-before-the-internet-was-cool"><em>RIP GeoCities: what the internet looked liked before the internet was cool</em></a>:</p><blockquote>Remember when the internet was just for geeks and gamers and the sort of people who fell in love with pneumatic virtual reality babes? Before it was all “millennials” and super-styled pictures of dinner, it was a bright, flashy cornucopia of fucked-up alien heads and planets and stuff like rooms. … [A] WTF level of weirdness…</blockquote><p>Websites looked like the above. For webapps, behold Neopets (circa 2000), a popular webapp among children at the time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*OP_EprAUf3-6nBRSv88rcQ.jpeg" /><figcaption>2000s software: not even once. <a href="https://www.reddit.com/r/nostalgia/comments/5l8rx4/neopets_circa_2000/">Credit</a>.</figcaption></figure><p>Clearly, the internet was a complete mess. But it wasn’t just the internet that was horrible: native software (that ran on your machine, e.g., Windows, macOS) were train-wrecks, of course, too. Check out a basic text editor — a popular one for its time, Microsoft Word 2000:</p><figure><img alt="A screenshot of how overly complicated Microsoft Word was." src="https://cdn-images-1.medium.com/max/624/1*o20ppzmYD1SJjBV1xoaw_Q.png" /><figcaption>Average Ohio software. <a href="https://edu.gcfglobal.org/en/word2000/word-window-new-open-and-change-view/1/">Credit</a>.</figcaption></figure><p>Today, web-based text editors are a dime a dozen — they’re fast, have very few UI elements (given that almost none of the UI pictured above was necessary in the first place), and so on. Microsoft Word 2000, by today’s standards, is hilarious.</p><p>And, anyway, good luck trying to find basic settings on your Windows machine. There wasn’t a way to search your machine for settings (as you can today), nor a centralized place to control various settings on your device until much, much later. In fact, this came later for macOS, too. Early OSes were all about the desktop — from where you’d launch other software, and where most of your computing would happen. But, today, people just use desktops as dumping grounds for <em>Screenshot 2022–12–09 at 12.37.34 AM</em> and <em>maxresdefault.jpg.</em> For everything else, there’s Spotlight search.</p><p>But the absolute insanity didn’t end at software. Check out standard hardware for the time:</p><figure><img alt="An image of a Gateway laptop from 1997. It sucks." src="https://cdn-images-1.medium.com/max/1024/1*EeZEDnAMEnkpH8ywc9P84Q.jpeg" /><figcaption>This machine comes with an extended warranty and an apology. <a href="https://www.youtube.com/watch?v=ThItRZqFKX4">Credit</a>.</figcaption></figure><p>Today, having lightweight machines with big trackpads and high quality displays are features that are not negotiable. But times were different.</p><p>All of this to say: was there <em>ever</em> a golden age of software but today? If there <em>was</em> a time, presumably before 2008, — or even 2015 — where it was “just UX,” and things were better, why was software so bad? Why was internet adoption so low during that alleged golden age? I booted up a computer one day in 2000 and never logged off, and I tolerated way more then than I have the appetite for today. On every single metric you could possibly quantify, the digital experience of the time was objectively inferior to that of today’s — ironic for a time when UI designers have reportedly ruined the industry.</p><p>But I <em>don’t</em> see a ruined industry today. I see one that makes leaps and bounds in improvements with <em>every</em> passing year. I remember lugging around a very heavy Gateway laptop in 2009, and having a meltdown at my recalcitrant printer the night before an essay was due (you guys remember printers? I no longer wish to). By comparison, the digital world I exist in almost all day today (terminally online) is vastly superior to the one I remember growing up in.</p><figure><img alt="A screenshot of Facebook 2005. Hilariously bad." src="https://cdn-images-1.medium.com/max/1024/1*HBwQk3dFqlsYB37ZEgEfhQ.jpeg" /></figure><figure><img alt="A screenshot of today’s Facebook profile. It’s just better." src="https://cdn-images-1.medium.com/max/1024/1*DufZOW4hApfJU6nSd3SMzA.jpeg" /><figcaption><a href="https://time.com/11740/facebook-10-year-anniversary-interfaces/">Left</a>: Facebook profile, 2005. <a href="https://pathofex.com/how-to-see-who-viewed-your-facebook-profile/">Right</a>: Facebook profile, 2022.</figcaption></figure><p>For example, above, you can see two renditions of the same product: the Facebook profile. Apologies for the Windows context menu in one’s face but, putting that to one side, the right is very obviously better in every capacity — it’s easier to read, feels less spammy, is more focused for what users would generally want in this view in that it has fewer extraneous features (why would someone ever want to “subscribe via SMS” to anyone, ever? Even in 2005?), and just looks more professional.</p><figure><img alt="A screenshot of Amazon when it was somehow worse than it is today." src="https://cdn-images-1.medium.com/max/1024/1*MKsnodyJB_jRKmimiIuWEQ.jpeg" /><figcaption>If you can believe it, Amazon was worse. <a href="https://www.hardwarezone.com.sg/tech-news-check-out-newsweek-article-23-years-ago-predicting-internet-would-be-passing-fad">Credit</a>.</figcaption></figure><p>Can it really be argued that software of the past was better than that of today’s? Would anyone <em>sincerely</em> like to RETVRN to Geocities days? Or even 2008, the year of the Motorola Sidekick?</p><h3>More technical expertise, more fun</h3><p>Though I hear frequently from designers (usually making it a point to explicitly refer to themselves as “UX designers,” rather than more common terms today, like “product designer”) that UI designers are the cause of seemingly everything that’s terrible about the tech industry, I just don’t know how that’s possible.</p><figure><img alt="Cheese with three circles highlighting the phrase “UI designers cause cancer.”" src="https://cdn-images-1.medium.com/max/1024/1*QPr_kMCAAN3bZtZadsrwIg.png" /><figcaption>Behold: the cheese of truth.</figcaption></figure><p>The claims, as mentioned above, are frequently as follows:</p><ul><li>There was a moment when “UI design came in” and “changed” the industry to be “UX/<em>UI</em>,”</li><li>There was a time before UI designers “came in,” and it was glorious,</li><li>There was a time when research mattered more, and better products were made.</li></ul><p>But I don’t see evidence for these claims at all. In fact, I only see evidence to the contrary:</p><ul><li>I <em>don’t</em> recall a <em>specific</em> moment when there was some kind of mass influx of visual designers into the industry — in fact, I remember a time when today’s product designers upset at those who have visual skills staked their <em>own</em> beginnings as “web designers,” themselves who were mostly just worse graphic designers making templates and marketing sites online,</li><li>I <em>don’t</em> recall a time when there was a golden age in digital products before this point — the internet (and software, in general) was objectively horrible, mostly did stuff no one actually wanted (solved problems no one had), and made things often worse for people — the adoption of it was summarily low,</li><li>I <em>don’t</em> recall a time when research bored out fruits of its labor more than it does today: the age of infomercials and useless software is truly over — the competition is simply too stark, and consumers are increasingly informed and discerning. Flop products don’t sell, most businesses fail. Consumer tolerance is so low it’s basically catching drinks in a tavern in hell.</li></ul><p>In fact, the internet was so bad that writers at Newsweek — an incredibly popular publication in the States — <a href="https://www.newsweek.com/clifford-stoll-why-web-wont-be-nirvana-185306">predicted it would flop</a> back in ‘95:</p><blockquote>What the Internet hucksters won’t tell you is tht the Internet is one big ocean of unedited data, without any pretense of completeness. Lacking editors, reviewers or critics, the Internet has become a wasteland of unfiltered data. You don’t know what to ignore and what’s worth reading. Logged onto the World Wide Web, I hunt for the date of the Battle of Trafalgar. Hundreds of files show up, and it takes 15 minutes to unravel them — one’s a biography written by an eighth grader, the second is a computer game that doesn’t work and the third is an image of a London monument. None answers my question, and my search is periodically interrupted by messages like, “Too many connections, try again later.”</blockquote><p>He had a point. The internet was really that bad.</p><p>Nonetheless, statements like “no online database will […] change the way government works” are objectively hilarious in an age of cold wars waged by authoritarians with creepy databases of dissidents and religious minorities, squabbling over free hearts and minds on the internet. This serves as a reminder that, no matter how confidently someone’s opinion sounds, it can still be wrong.</p><p>Anyway, it seems obvious to me that, if Apple released the iPhone 384986589268, adding a regression to make its OS look like its very first, the public would laugh Apple all the way to a flatlined stock price. Consumers have higher standards today — when considering making digital products as a business today, the high barrier to entry that’s caused by these higher standards is <em>real</em>, and it <em>would</em> show up in even surface-level market research.</p><figure><img alt="Screenshot of the first iPhone’s homescreen." src="https://cdn-images-1.medium.com/max/259/1*ILPes6QxVWa843Rof4AIjg.jpeg" /><figcaption>Be honest: you hate this. <a href="https://en.wikipedia.org/wiki/IPhone_OS_1">Credit</a>.</figcaption></figure><p>This is all to say that most customers <em>do</em> care about aesthetics, at least in some capacity. This preference can be stronger across different products and markets, and aesthetics, at times, can become differential market advantages.</p><p>For example, the aesthetics in personal fashion: most consumers are very, very sensitive to this. There are brands that exist to sell non-aesthetic clothes, but these are not widespread. Most consumers are very particular, and enjoy trendy aesthetics.</p><p>Or consider the aesthetics of furniture and homes, where consumers always prefer beautiful and professional looking furniture, rather than cheap, ugly furniture. Consumers also go out of their way to spend a ton of money with contractors to install prettier kitchen cabinets, and steel appliances — all because they look better.</p><p>Human beings do have aesthetic preferences — we are a species intelligent enough to develop these kinds of advanced preferences and tastes. When trying to sell stuff on a market, people who conduct research about the probability that their proposed product will succeed <em>do</em> have to determine how sensitive their target market will be to unprofessional looking work, and what they can get away with. In some markets, however, that margin of error is razor-thin (see: Apple’s market).</p><h3>“Dribbblization of design,” and other things</h3><p>Another thing I notice is that the view that visual design is the stuff of inferior, simpleminded, drooling Dribbblers is <em>rife</em> in design programs (e.g., bootcamps and universities). It goes without saying that these programs, themselves, are recent phenomena (I will make no commentary on the irony of this).</p><p>As some of you know, I’ve mentored maybe what’s probably around eighty people, all of them from these programs (with the exception of just one), and I have seen not a single example of a student from one with a portfolio that has acceptable product thinking — to say nothing of their visual design. With no exception, I’ve heard from them that what they are taught about product design is that they “do research” and “UX.” That “UI” is a “separate job.”</p><p>Right, except that this is a severe distortion, and this is not how the market operates today. For expedience, I’ll quote myself in <a href="https://medium.com/design-bootcamp/things-you-might-want-to-avoid-as-an-early-career-designer-35eb9770621a"><em>Things you might want to avoid as an early career designer</em></a>:</p><blockquote>In reality, you do not get to choose whether you are a “UX” or “UI” designer in today’s market. This is an academic discussion about a market that no longer exists — a luxury belief. The reality is that you are going to experience increased difficulty finding — and retaining — customers as a designer if you do not make professional looking work. When FAANG companies hire designers under titles like “UX designer,” or “product designer,” or “interaction designer,” these are all the same jobs: you are planning out how some software will work. But there is an additional expectation — not always explicitly stated — that you will put in the effort to make the product or feature look professional. There will not be an attendant visual designer at your beck-and-call to jazz up your schematics. It’s just you.</blockquote><p>I have the uncomfortable job of telling these hopefuls that, not only does their portfolio site (and its content) look unprofessional, — causing opportunity loss for them on the market — but that their work also demonstrates no understanding of how businesses, products, services, and software fundamentally work. Unfortunately, I see portfolios from these programs filled to the brim with infantile, implausible software. To quote myself in <a href="https://medium.com/design-bootcamp/you-dont-need-mentors-to-tweak-your-portfolio-you-need-to-start-over-4acc46ed5f88"><em>You don’t need mentors to tweak your portfolio — you need to start over</em></a>:</p><blockquote>By “serious case studies,” I mean you need plausible case studies. Those prompts you got in your program about making a snack delivery service for your favorite brand of snacks, or a food delivery app for your favorite restaurant: these are not plausible. We already have a food delivery app: it’s called Uber Eats. You don’t need to revisit that. So, for example, these are prompts from one of those programs:</blockquote><blockquote>- Design a game preview app for an arcade.<br>You and I both know that no one will ever need or want this.</blockquote><blockquote>- Design a food delivery app for a bakery.<br>Uber Eats.</blockquote><blockquote>- Design a delivery tracking app for a sushi restaurant.<br>Uber Eats.</blockquote><blockquote>- Design a flower catalogue app for a florist.<br>Squarespace.</blockquote><blockquote>- Design an order tracking app for a trendy florist.<br>Shopify.</blockquote><blockquote>- Design a menu and payment app for a beachside snack shop.<br>Physical menu &amp; Square.</blockquote><blockquote>Do not use these. These are easily solved with already available, off the shelf solutions. Try something realistic. You can add a feature into an existing product … Or you can improve the navigation of a certain, famous social media app. … Or you can also go big: could LinkedIn have a mentor and mentee matching service in their product? …</blockquote><blockquote>Regardless of your choice …, make sure it’s realistic. By this, I mean that it passes the “reasonable person test…”</blockquote><p>Further, to quote myself from <a href="https://medium.com/design-bootcamp/is-dribbbalization-really-that-bad-though-a89503db9aeb"><em>Is “Dribbblization” really that bad, though?</em></a>, I write:</p><blockquote>For all the talk about how unimportant visual design is, particularly from product design programs, I would instead expect to see graduates coming out as incredible entrepreneurs, building unforgettable products and features that people want to bang their doors down to buy off them, even if they look unprofessional. But I don’t see that. I see people spending thousands to come out with not only poor visual design, but also implausible case studies — ones that show not even a cursory understanding of markets and products, and then talking down on people who have the interest, humility, and grit to put in the work to at least make something excellent from a visual perspective.</blockquote><p>I would expect that, for all the time not invested in to craft and visual excellence, designers would be highly technically inclined, or making incredible products. But I don’t see that. I find this to be a huge disservice to hopefuls, who frequently cannot see what I see in their uncompetitive work.</p><h3>All right, so what’s really going on?</h3><p>Some have asked me why I believe this amount of vitriol for visual designers exists. I think every designer’s answer will be different but, at times, I wonder if this isn’t a result of a few possibilities:</p><ul><li>A lack of technical knowledge about and appreciation for graphics standards (and related technologies),</li><li>General human tribalist tendencies — “I’m smart, you’re not, I work on hard, valuable stuff, you work on the easy, frivolous stuff,”</li><li>Conformity, especially if one’s coming from a bootcamp — anyone who’s anyone feels pressure to agree with these mainstream views, and,</li><li>If I’m honest: resentment caused by jealousy — probably sourcing from insecurity that others have put in the effort to create visual excellence and reap benefits for it on the market, while they haven’t and don’t,</li><li>Potentially, some feelings of anger towards engineers, due to being higher value in production of software.</li></ul><p>Or, perhaps, it’s some combination of these things. My experience has been that designers routinely write off the difficulty that is required to create great visuals — and not even just in terms of design, but rather in engineering. For example, from the same article above, I write:</p><blockquote>Building beautiful products takes an enormous amount of skilled, technical execution from engineers. Consider that entire game engines are written and rewritten just to improve things like collision to create reasonable behaviors when objects collide; physics are replicated with painstaking dedication in game engines; algorithms are thought and rethought — and rethought again — just to create plausible visual randomness in assets; asset generation and management is enormously costly, and some people are hired just to make technical pipelines for artists to create convincing grass textures on the floors of games; writing shaders that are performant across all kinds of devices to access internet products (e.g., browsers) requires lots of dedicated, low level graphics programming, too; and so on. This is extremely admirable and takes such an incredible amount of technical experience — and raw grit and patience. […]</blockquote><blockquote>As organizations that maintain important developer tooling and services notice the way that aesthetics are pushed and consumer expectations evolve, they work hard to create standards that accommodate all these changes. This improves usability and performance across internet services more generally. This means that, as technologies that are used on the internet improve, the products and services that use those technologies <em>also</em> improve — the resultant effect is that more is possible with less (e.g., less strain on our devices and networks). As demand for more complex assets on the internet grows, technology standards we all rely on respond — and become more resilient. We all win in this equation.</blockquote><p>My experience is that the dismissal of visual excellence in software likely (at least partially) occurs because designers do not know enough about how graphics work in order to see its value, and how important it is to technology that our technological standards that underpin the internet (and native platforms) improve over time, and how visual excellence pushes on these boundaries — and the benefits this confers to every day individuals.</p><p>I also think that many designers do not appreciate how hard it is to make something look beautiful. I see this the most in the people I mentor — when we start our relationship, they frequently speak disdainfully about visual design, which is consistent with what they were taught. I would expect that someone who speaks disdainfully of a topic would have excellence and experience in that area — but they never do. As mentioned, I’ve yet to see one single individual from a design program that has acceptable visuals. I find this to be puzzling. As our relationship develops, they become less haughty and disdainful of visual excellence, and start putting in the actual effort to build up that skillset. Unequivocally, they all seem to indicate that it is the absolute hardest one for them to acquire control over.</p><p>This is because visual design is hard. It is not a clear and direct process of reasoning, as interaction design is. Founders routinely explain to venture capitalists in under an hour what their product is, and they have little time to sell them on it. It is not difficult to explain why some software would work, why there’s market demand for it, and why someone should invest in it. It is, however, very difficult to explain why something is beautiful to humans.</p><p>There <em>is</em> a way to create a very strong case for why a product will solve a market demand, and become a viable business. One can source evidence in analytics (if an MVP is out), or discuss market trends, talk about market size and opporunity, and other information. There is no “evidence” to pull about why something is beautiful. There’s no reasoning about why this strange orange looks beautiful on this eggshell white. It just <em>does</em>. This is what makes visual design hard. It’s all about getting reps in — not following sound reasoning. It’s about developing an adult taste for strange food. It just takes time. This is why mentees demonstrate incredible progress, week over week, when it comes to making software and reasoning about it — but that the progress is painfully slow on developing their taste.</p><p>Interestingly, I notice a real absence in retaliation among those who are skilled in visual excellence. Whenever I inquire about this topic, skilled visual designers do notice this phenomenon I’ve described in this opinion, but also seem to shrug, indicating that they feel these sentiments are just hot air and hysteria. I also commonly notice in my discussions with them sentiments like “visual design for interfaces is easy,” which might catch less skilled designers off-guard.</p><p>But it’s hard to disagree — making visuals for interfaces <em>is</em> among the easiest kind of visual design to do. It makes the amount of noise about how dangerous visual excellence is, how awful its effects are on the industry (and so on ad nauseam), seem almost out of step with the dead-simple reality of making rectangles look good.</p><p>Certainly, interfaces are intended to cut all extraneous content and features from views and be as focused as possible so, necessarily, visual design for these surfaces tends to be very easy — simple rows and headings, sometimes columns if the product calls for it. No complex layout work (e.g., nothing overlaps, no fractional layouts, etc.); colors and type is usually conventional; lots of white space that uses the same spacing values over and over; no treating of imagery (e.g., via shaders); content is always dynamic, so content has to go untreated; etc. Nonetheless, unskilled designers still mishandle this, which is all too easy to do.</p><p>It is no wonder, then, that most skilled visual designers confess to finding those surfaces to be the least interesting to work on, from the perspective of visual work.</p><h3>I’m not sure how to end this opinion, sorry</h3><p>From what I can tell, every year is software’s best year. By every measure, digital (and even physical) interfaces significantly improve, year over year. I would need a lot of evidence to convince me of the opposite: that my youth filled with garbage software was <em>better, actually — </em>but I’m all ears.</p><p>For my part, my quality of life has improved substantially due to improvements in software. As is the case for other consumers, I have low tolerance for nonsense from software. I want things to “just work,” to borrow Apple’s branding. I know you all do, too. Where I’m told that “the UX” of software has worsened as “the UI” has improved, I see the opposite: as digital products have matured, they have worked better, faster, and given me what I want more efficiently — all while leaving its Geocities-looking past further and further in the distance. I think there is a real and prescient case to be made that there is, in fact, an extremely strong correlation between improvements to visuals and to functionality, both.</p><p>I’ve noticed this among the designers I most respect: they seem to be good at everything — they are skilled developers, visual designers, and make awesome products, and seem to be able to solve every brain-busting interaction you throw at them. They can think of everything. They can solve anything. They just know everything. From what I’ve seen, it <em>is</em> possible to “do it all” — provided one has the discipline for it. Chatting with those designers, they say the same. It’s probably just the can-do attitude that does it. Rather than self-limit and believe that “no one can do it all,” that “companies expect too much,” and that they are “looking to decrease our wages by hiring one person for everything,” they seem to say “challenge accepted.” I’m happy with that.</p><p>For my part, if my very online childhood was the golden age of software, created by a glorious time when only “UX” design and “research” dominated — if the outcome of this is the kind of software I grew up with, rather than the software I have today, then I’m okay with that paradise being lost. Regardless, it makes me wonder if perhaps neither “UX design” nor “research” return the results they’re said to, after all.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=590c32cf1f97" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>