<?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 Yichen He on Medium]]></title>
        <description><![CDATA[Stories by Yichen He on Medium]]></description>
        <link>https://medium.com/@yichen.h3?source=rss-facd03d2fd36------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*9fIs9OJcredC9oLsq_Wjxg.jpeg</url>
            <title>Stories by Yichen He on Medium</title>
            <link>https://medium.com/@yichen.h3?source=rss-facd03d2fd36------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:38:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yichen.h3/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[Reflections on the early 2024 job hunt as a Product Designer]]></title>
            <link>https://medium.com/@yichen.h3/reflections-on-the-early-2024-job-hunt-as-a-product-designer-b31de26321c5?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/b31de26321c5</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[personal]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 16:32:11 GMT</pubDate>
            <atom:updated>2024-02-20T17:18:05.756Z</atom:updated>
            <content:encoded><![CDATA[<p>On the last day of November 2023, I found out that my entire product team at VMware will be <strong>laid off</strong> effective at the end of January 2024.</p><p>It didn’t come as a surprise. Things had been pretty rocky for a while, ever since Broadcom announced the second-largest tech acquisition in history. As getting laid off experiences come and go, I would say it was as good as it gets.</p><p>Then started the grind. The end of 2023 was already slim pickings, but it slowed to a crawl in December. In January, things started picking up again a few weeks in. I started working on this reflection piece before I even secured a job, here are 7 insights I left this round of job searching with.</p><h3>1.) It’s hard to stop making excuses.</h3><p>When I am working in a team, I give it my all, but when the only person I have to disappoint is myself, somehow the excuses just start bubbling up.</p><ul><li>I didn’t save any figma files from my past projects</li><li>My portfolio is ugly because I am limited by the platform I built my site</li><li>My case studies are incredibly wordy and long because I work in enterprise</li></ul><p>Before you know it, you are scrambling on that slippery slope of shifting all blame off yourself and on to the universe.</p><p>Since I was laid off I had all the time in the world, the only thing stopping me from re-creating all my design artifacts and screens was <strong>laziness</strong> and inertia. I grumbled and complained the whole time but retrospectively it was pretty good figma practice. Not to mention since I was creating these artifacts solely for a case study, I could make sure everything was NDA friendly and looked clean and professional. No more need to blame a design system for a wonky-looking component.</p><p>I put my old portfolio in the trash and learned Webflow to re-make my new one from scratch. It felt good to be learning again and by further iterating on my website, I feel it definitely improved. I rewrote most of my case studies to condense them a bit, (but I know it could still be better).</p><p>Looking back at the older version, I was almost ashamed to think that I thought it was good enough only weeks ago. That is a good sign of growth though!</p><h3>2.) Remote is extremely competitive</h3><p>As a Canadian, I suspect it is harder to qualify for many US-based roles. Unfortunately, as the world’s largest economy, the majority of roles I saw on job boards were US-based roles. For the few that do allow international candidates, you are competing against every job-seeking designer in the world. From people who are hiring I have heard anecdotal stories of tens of thousands of applicants for certain roles. Sure most of them are not qualified, but it just makes it all the easier for your application to get lost in the flood.</p><p>Many companies are also slowly rolling out Return to Office (RTO) mandates which further diminishes the supply of remote jobs, only as demand steadily climbs after so many people experienced the benefits of remote working during the height of the pandemic.</p><h3>3.) You are so loved</h3><p>After I found out about the impending layoff, I started to “secretly” look throughout the dead weeks of December and early January in hopes of securing a new job before I had to really tell anyone about it. I felt ashamed to update LinkedIn to announce to the world I had been laid off, even though a negative thought has never crossed my mind when I see them from others on my feed.</p><p>I was floored by all the support I received when I did finally cave in and made that announcement on LinkedIn. So many people I had worked with or crossed paths with in the past came out of the woodwork to support me. It really drove home that point that passive networking is just trying to be a good person and working hard and others will notice. I am incredibly grateful to everyone who checked in on me and offered their support (you know who you are!).</p><p>Getting referrals was also <strong>sickeningly effective</strong> for making it to the next interview step. I cold applied to one company and was effectively ghosted after not hearing back for over a month. I decided to reach out to a former colleague there and I received an interview invite just a few hours after he talked to HR on my behalf. Wild.</p><h3>4.) Rely on your friends</h3><p>While the job-seeking process requires hustle on your part, your support system is what really gets you through it. I am grateful and fortunate to know many great designers who helped me iterate on my resume, portfolio and pitch decks. They are able to give me great advice and act as a sounding board as I wade my way through the rounds of interviews to final competing offers.</p><p>It was crucial to continuously get feedback from people who are willing to be blunt and honest with you. 80% of the content I prepared for presentations or my portfolio ultimately ended up cut out as a result of this process, but that refinement is what made it steadily improve.</p><p>Additionally, just knowing tons of other amazing designers really inspires you. Everyone is so knowledgeable and just being around talented people drives you to improve, even if it’s just to keep up. I had no shortage of inspiration when it came to working on my job hunt artifacts.</p><h3>5.) Companies are being very picky about domain experience</h3><p>This is just compared to my previous experiences looking for a job. I suspect this probably has three main contributing factors.</p><ul><li>A —<strong> I am looking for senior roles, and most teams hire seniors to hit the ground running, not for potential</strong> (as some do for juniors). If a candidate has worked in a certain domain before, they will likely be able to ramp up more effectively.</li><li>B — <strong>Layoffs producing a glut of qualified candidates</strong>. Before it may have been hard to find someone in a specific niche, but with all these layoffs, it is very possible many candidates have a combination of experience that is a perfect fit.</li><li>C — <strong>Metaphoric lines in the sand dividing industries</strong>. We have words for just about every one, EdTech, Crypto, DevOps, InfoSec, GenAI, etc… Each come with their own dictionary of lingo. Additionally, even in design, you have areas such as growth, platform, design systems, marketing etc… Some people just have the experience that lines up better than others.</li></ul><p>Every early interview I was asked if I had experience in specific product areas such as game engines, access management, payroll, developer tooling, containerization, etc. Sometimes I could talk to similar experiences, others I had to be honest and say I know very little about that industry having never worked in it before.</p><p>But every time you hear a rejection, it’s likely not because you were not good enough. In most cases, someone else is just a better fit and there isn’t much you can do about that but move on!</p><h3>6.) Practice makes perfect</h3><p>I have a document where I have written out the answers to over 25 behavioral questions in STARR format and maybe a casual 20 paragraphs to just answer other basic questions. Not necessarily so I can read off it, but just to make sure I have thought through some examples that I can then use in a pinch.</p><p>When I was practicing my portfolio presentation pitch, my husband sat in another room with a blazer overtop his PJs. We had a 45 minute zoom call where I walked through my entire presentation and asked questions. I stumbled through it and he gave me a mediocre score and lots of great feedback.</p><p>Even with all that prep, my first interviews are still awkward and robotic. Interviewing for a job is a very specific skill that you don’t exactly practice often (ideally). But as I did more and more interviews, I found myself improving in both confidence and delivery.</p><h3>7.) Many things are outside of your control</h3><p>Of the 33 places I applied for, 9 had a public round of layoffs in 2024. Additionally, you never know when you are going against internal candidates or if hiring budgets get frozen half way through.</p><p>The only thing you can really do is focus in on the things you can control such as your portfolio, practicing interviews, reaching out to potential opportunities.</p><h3>Final thoughts</h3><p>It was not a fun time looking for a job, but I know I was playing on easy mode compared to many out there. Being a Canadian citizen with a few years of work experience already gave me a huge leg up on the competition.</p><p>Who knows, with the current economic environment, maybe I will be back looking for a new job soon (although I sincerely hope not!). At the end of the day, I feel focusing on doing good work and establishing relationships with the people you work with will always help out in the end.</p><p>I will leave you with a little infographic with the stats of this past experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w0ODvKPaLbQPHSD5uNgq_A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b31de26321c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Complexity in Design]]></title>
            <link>https://medium.com/@yichen.h3/complexity-in-design-7b9f620407ac?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b9f620407ac</guid>
            <category><![CDATA[impedance-mismatch]]></category>
            <category><![CDATA[simplicity-fetish]]></category>
            <category><![CDATA[enterprise-design]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Wed, 22 Nov 2023 15:51:30 GMT</pubDate>
            <atom:updated>2023-11-22T15:51:30.089Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6w1NvukDOk9slrjSsL1ILA.png" /></figure><p><em>This is a rant piece. Some frustrations from a designer working in Enterprise software. Please take it with a grain of salt, thanks!</em></p><h4>Everyone wants simplicity</h4><p>This concept of an “impedance mismatch” has been on my mind these days as I have been working on my portfolio case studies. John Cutler talks about this in his blog post “<a href="https://cutlefish.substack.com/p/tbm-242-the-simplicity-fetish">The Simplicity Fetish</a>”. It refers to this concept that there are certain problems and systems that are inherently complex and it might not be possible (or just incredibly hard) to bend something that requires nuanced communication to a purely transactional, stable and unchanging problem.</p><blockquote><strong>Can you summarize a textbook into a page?</strong></blockquote><p>Sure it’s possible and you could have a high-level idea of the contents, but to assume that you now understand the content would be highly egotistical. In this case, you can’t blame your lack of understanding on the person who did the impossible task of reading 300 pages and consolidating key insights into one page. You can’t blame them for not being able to craft a perfect story because it’s going to be full of holes.</p><h4><strong>How much complexity do people actually want? (very little)</strong></h4><p>It irks me when I see job postings claim they want to see complex problems, but then complain the retelling of the problem “can’t be skimmed in 30 seconds”. Therefore the author isn’t a good storyteller and can’t simplify complexity.</p><p>Turns out most people don’t want to actually understand nuance of complex things and they only want to see ones that <strong>can</strong> be simplified. That is fair, it’s a lot of cognitive load to truly dive into something one has no prior context in.</p><h4><strong>Not everything out in the world needs to be complex</strong></h4><p>Many things could be much more streamlined. The famous tradeoff of clarity and flexibility (from <a href="https://www.howtomakesenseofanymess.com/chapter6/130/ambiguity-costs-clarity-exactitude-costs-flexibili/">How to Make Sense of Any Mess by Abby Covert</a>) comes to mind. Often if you are to simplify, clear things will become more ambiguous, and by being more flexible, you lose accuracy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*Tnqg062ttdhdNFY7JnjrQg.png" /><figcaption>For example, in this image, when you understand a complex problem, the line is not necessarily shorter, it’s just neater and easier to understand.</figcaption></figure><p>Are we just straying into a world where all problems are just vague 2 sentence prompts? At what point do we lose the ability to dive deep into problems because we need everything delivered at the surface level? There is definitely a balance here.</p><h4><strong>Wasting time by saving time</strong></h4><p>Now with technologies such as ChatGPT, we are becoming increasingly reliant on being served information and losing the ability to read through longer-form content and coming to our own conclusions on nuanced topics. Instead of just reading a 5 page explainer, people rather read a one pager and spend 5 hours asking questions to pull out the remaining content. It’s only mildly inefficient but at scale it can compound.</p><p>There is also certain power dynamics at play here, as often it is the higher level decision makers who ask for simplification. This is justified to a certain extent, as the higher up you are, the larger your scope of responsibility. Maybe you really do only have 3 minutes to understand something. The issue is the loss of details through this translation process from high complexity to simple and then re-introducing the complexity as the unavoidable roadblocks appear.</p><h4><strong>I need to work on me</strong></h4><p>How do I simplify the complex things I have worked on better? Having read books like <a href="https://www.axios.com/smart-brevity">Smart Brevity</a> (very digestible book even for ADHD’ers like myself), I definitely understand the power and appeal of getting to the point.</p><p>When I get frustrated I write some rants to get my feelings out and then it’s back to the drawing board. While it’s impossible truly simplify certain things, I know deep down inside my own case studies could be better. At the end of the day, the power dynamics of the people with little time looking for information vs. the people who need to provide the information will not change so we need to all try our best to improve our storytelling skills and hone our balance to find the right fidelity to convey our story.</p><p>I highly recommend checking out<a href="https://cutlefish.substack.com/p/tbm-242-the-simplicity-fetish"> John’s take on this topic</a> as it is what inspired me to get my thoughts on paper.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b9f620407ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Design Hiring Manager Perspectives — The Cake Analogy]]></title>
            <link>https://medium.com/@yichen.h3/understanding-design-hiring-manager-perspectives-the-cake-analogy-6d1bc2bf79b8?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d1bc2bf79b8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[cake]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Thu, 09 Mar 2023 14:19:23 GMT</pubDate>
            <atom:updated>2023-03-09T14:19:23.496Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding Design Hiring Manager Perspectives — The Cake Analogy</h3><h3>You = Baker</h3><p><em>You are a cake baker.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*1T9DBS4oIzy95vLJDS4PhQ.png" /></figure><p>Employers are bakery owners. They pride themselves as establishments where people can visit to buy delicious cakes to enjoy. To be the best bakery on the block, they want to hire the best bakers.</p><p>It can be a risky business hiring bakers because if they aren’t good at baking cakes, they can slow down the other chefs on the team and end up producing low-quality cakes. As a result, they decided that when vetting applications, they would like to <strong>see</strong> a few cakes baked by the applicant before hiring them.</p><h3>Cake = Portfolio Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*fLerE-Ojhej3r1CxKi6wFQ.png" /></figure><p>That cake is a case study in your design portfolio. Employers are looking for beautiful and delicious cakes. If the cakes you put on display looks nice, and smells good, they will likely believe you have great baking skills.</p><h3>Variety of cake</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BH6qa5dpqGV_MiIwDGV1jA.png" /></figure><p>Most bakeries sell more than one type of cake, so you may want to display more than one type of cake in your “portfolio”.</p><p>Generally you want to pick different cakes, as three strawberry shortcakes would only be interesting if you are selling yourself as a specialist in strawberry cakes. Likely you will find the most success if you pick a few cake types that the bakery you want to work for sells.</p><h3>Focus on quality not quantity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RjeVTYB-La9D7k-ldxXHzQ.png" /></figure><p>Sure it’s nice to have 2–3 cakes on display to show your flexibility as a baker, but adding ugly and half-baked cakes just to pad the numbers won’t reflect well at all.</p><p>Displaying only cakes your are proud of ensures that you will be judged only on work that represent you at your best. 1 great cake &gt; 3 mediocre cakes.</p><h3>How to bake a good cake</h3><p>Like with many things in life, it comes down to the ✨<strong>fundamentals</strong>✨ .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*VNBKGBFKpR9DmPJCky2ejA.png" /></figure><p>When it comes to baking a good cake, at the very least you need some basic understanding of:</p><ul><li>What ingredients are needed</li><li>Ratios of key ingredients</li><li>How hot the oven needs to be</li><li>How long to bake the cake for</li></ul><p>In product design, things like visual design, information hierarchy, understanding of heuristics, research skills, prototyping skills etc. are all fundamentals that contribute to good work. While you can read books to learn the basics, the best way to build fundamentals is to bake more cakes (design more things).</p><h3>What makes a cake delicious?</h3><p>In this analogy, the taste of the cake is representing how your design skills are perceived. Similar to taste, there can be a high degree of <strong>individual preference</strong> that exists alongside <strong>societal preferences</strong>.</p><p>For example (I mention this in my <a href="https://medium.com/user-experience-design-1/designing-for-enterprise-vs-designing-for-consumers-36a16f2281c2">other article</a>) Enterprise UX tends to favor much more information density than Consumer UX. You can think of this as comparing a big party cake to a cupcake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*ORAN4LzA0lO43NaW5Zj7nQ.png" /></figure><p>They both NEED to be delicious and look good, but are for different audiences. One could even argue that with the cupcake, bakeries need to sell more and you have less space to work with so you need to be more creative to make the best of it.</p><p>If your portfolio only contains large cakes and you apply to a <a href="https://www.bakedbymelissa.com/">bakery that only sells cupcakes</a>, you might not be as strong of a candidate as someone who has a lineup of beautiful cupcakes in their portfolio. That being said, having amazing large cakes in your portfolio still beats out having mediocre cupcakes (and vice versa).</p><h4>Thinking about the customer</h4><p>The ability to cater to different tastes lies in understanding of the fundamentals. If you know certain customers prefer a sweeter cake, your knowledge of sweeteners will allow you to craft a cake that tastes delicious to that set of customers. The foundational skills are what allows a cupcake baker to pivot to a cake baker quickly if needed.</p><p>In addition to the size of the cake, the flavors you specialize in can make a difference too. You can find success in pursuing the tastebuds of the general public or choose to focus on a specific niche. Do you want to be well regarded as the baker of a popular chocolate cake eaten by thousands or a unique licorice cake that many don’t appreciate but is beloved by a few?</p><p>Keep in mind that most don’t start their career with a specialization, opting to bake popular cakes to build their foundational skills until they find their calling. You need to be a generalist before you can become a specialist!</p><h3>How to hire a good Baker</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*wJ4BVFojHgHSbuuZoWuTxw.png" /></figure><p>Every bakery has their own opinion on cake flavor. Since with your portfolio they can only see cakes you already baked, they can only guess at how they taste based on sight and smell. Just because you have baked a few great cakes before it doesn’t mean you will continue to bake great cakes.</p><p>In addition to the portfolio, they have a few more ways to gain more confidence that you actually have the skills to bake good cakes:</p><p><strong>1.) Look at your years of experience working at other reputable bakeries</strong></p><p>They trust that you know how to interact with other staff at the bakery, and produce cakes that get sold to customers. This could be compared to only have experience baking practice cakes for yourself at home.</p><p><strong>2.) Other bakery staff you worked with before vouch for you</strong></p><p>If other really talented bakers that the bakery trusts can vouch for you and say you are a great baker, it is likely a testament to how delicious the cakes you bake are.</p><p><strong>3.) Behavioral interview</strong></p><p>Interview questions will allow the bakery manager to assess your baking fundamentals.</p><ul><li>“Tell me about the last time you baked a chocolate cake?”</li><li>“Have you ever been forced to substitute an ingredient and how did that impact the cake?”</li><li>“Who is a baker you admire and why?”</li></ul><p><strong>4.) Personality</strong></p><p>No one wants to work with someone who is hostile, unwilling to learn, difficult, have a wild ego, poor communication skills, etc. Aside from your technical baking skills (which is non-negotiable), many employers will also be looking for someone that will work well as a team.</p><h3>Baking bootcamps</h3><p>Some people go to 4 years of culinary school. Some people have just baked so many cakes they got real good at it. You could go to a cake baking boot camp.</p><p>At the boot camp instructors will teach you all the steps to create a passable generic cake.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*gnv_Ki_CGH31uom6jQyejA.png" /></figure><p>The main issue is, everyone else who took the class will end up with a suspiciously similar cake. Now imagine you are the bakery manager examining 10 cakes and sees that 7 of them are almost identical and not particularly exceptional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/1*jwq6kDZyM9ohQU3T1b5cyQ.png" /></figure><p>How do you make your cake stand out!?</p><p>If all you can do is follow ONE set of instructions, you will likely only be able to make one specific, generic cake. But not many bakeries only sell a single cake, they likely want to find someone who has the ability to adapt and bake different cakes as needed.</p><p>If you have no fundamentals and are just looking at other cakes and blindly copying them in an attempt to stand out, you probably will not magically land on the right set of steps that results in a beautiful and delicious cake.</p><p>Once you understand the fundamentals, you can start “mixing and matching” to come up with your secret sauce. A beautiful and delicious cake that showcases your personality and strengths. Something that any bakery owner will rush to get a bite of when they see it.</p><h3>The 4 types of cakes</h3><h4>Beautiful and tasty cake</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*yQ_H0Mp_07Z3N8McgyB39Q.png" /></figure><p>If your cakes are beautiful, any bakery manager will be motivated to interview you to get a taste of your cake. If your cake is also delicious (your design skills are up to snuff), there is plenty of incentive to hire you. They are confident that you would come to bake delicious cakes at the bakery as well.</p><p>Bonus points if your cakes fit the style and taste profile of the bakery.</p><h4>Plain but delicious cake</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*kt4p9IUJoAQVTvfA893eiA.png" /></figure><p>If your cake looks plain (your portfolio looks plain), it will be a harder sell. The bakery owners have so many potential cakes to vet, they can’t possibly taste all of them, they likely will try to taste the prettiest ones first.</p><p>This is where NETWORKING could come in handy. If you can just convince people to take a sniff of your cake. The scent is delicious! They take a bite and think.. “wow, this is a tasty cake”. They just might overlook the fact it looks unimpressive because the flavor of the cake is what will bring repeat customers in the door.</p><p><strong>Note:</strong> A plain cake does not equate to an unappetizing-looking cake. When it comes to portfolios, things like bad grammar, buggy interactions, blurry images, inconsistent styling, etc.. would actively make it look bad.</p><h4>Beautiful but unpalatable cake</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*tKIpxRJsoY3cFXjnFQKwwA.png" /></figure><p>If your cake is beautiful and not delicious, you might get the interviews but then get passed on because they don’t like the flavor. This could be because:</p><p>1.) The flavor is bad — it just doesn’t match up with expectations based on how beautiful it looks</p><ul><li>During the interview process, your performance fell short of what they expected based on how impressive your portfolio looked.</li><li>They were able to sniff out your lack of baking fundamentals. The cake is too sweet or too bland. They are not confident you understand how to bake a delicious cake.</li></ul><p>2.) The flavor doesn’t match their expectations because they specialize in chocolate desserts and you baked a vanilla cake.</p><ul><li>Another applicant baked a beautiful chocolate cake and the bakery rather pursue them.</li><li>Maybe they were looking for someone with specific industry experience or expertise and yours just isn’t aligned. For example they are looking for someone with enterprise banking research experience and yours is visual mobile gaming.</li></ul><h4>Ugly and flavorless cake</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*cKHg47lvjFoTmqPJpjMJWg.png" /></figure><p>If your cake looks bad and tastes bad you are out of luck. NO AMOUNTS OF NETWORKING will convince someone to take a chance on something that looks bad and also tastes bad. You need to work on your fundamental baking skills to at least make your cake taste good.</p><h3>Key takeaways:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*HPJVgzYBkg_jYAyAQVP0fA.png" /></figure><ul><li>If your cake is beautiful and tasty, it’s only a matter of time, don’t give up</li><li>If your cake is plain but tasty, networking is helpful. Working on your visuals skills could make you stand out more in a crowd.</li><li>If your cake is is beautiful and tastes bad, working on the fundamentals will help improve the taste of your cake.</li><li>If your cake is just bad, no amounts of networking will help. You need to bake more cakes to get experience and learn the fundamentals!</li></ul><h4>Now get out there and keep baking!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d1bc2bf79b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Metaphor attempt: Dogs and Work]]></title>
            <link>https://medium.com/@yichen.h3/metaphor-attempt-dogs-and-work-bb27cb6e90a?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb27cb6e90a</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[dogs]]></category>
            <category><![CDATA[metaphor]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Wed, 05 Oct 2022 14:05:53 GMT</pubDate>
            <atom:updated>2022-10-05T14:05:53.125Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing I love about my immediate team at work is that everyone is amazing. It is clear that each and every person I work with has a robust set of past experiences and deep knowledge in many unique areas.</p><p>From these strong individual strengths comes many opinions informed by personal journeys and points of views. When they happen to auto-magically align, it feels like things are a <em>breeze</em>. However when there are disagreements, either real ones or perceived ones due to miscommunication, things can get sticky fast.</p><p>This is especially common for decisions that requires a group of people to <strong>get together</strong> to work their way to a solution. This could be a series of workshops, planning sessions or even just brainstorming. When there are 4+ people in a zoom huddle, how do we make sure everyone can contribute?</p><p>An analogy I want to try making here is picturing the individuals of the team as a group of really strong (and cute) dogs.</p><figure><img alt="A hand-drawn illustration of a pack of dogs" src="https://cdn-images-1.medium.com/max/312/1*oPBYrlXREGv8wc1UhkSDYA.png" /></figure><p>Individually each dog is powerful and capable. They can go fast, especially if they are running towards a goal that excites them.</p><figure><img alt="A hand-drawn illustration of a single dog running" src="https://cdn-images-1.medium.com/max/299/1*ahYJfy_J5E0OvhP7_OpgSA.png" /></figure><p>Team initiatives I see as a mission to get some kind of payload to a certain goal.</p><figure><img alt="A hand-drawn illustration of a box of work on wheels with a dotted line towards a goal flag" src="https://cdn-images-1.medium.com/max/300/1*SeNtwktZwioJPCrlbkD1kw.png" /></figure><p>Imagine this payload is too heavy for any one dog to pull.. Even if I am personally a pretty spectacular dog, I can’t budge this box alone.</p><figure><img alt="A hand-drawn illustration of a dog trying to pull a sled with a box labelled “work” on it" src="https://cdn-images-1.medium.com/max/1024/1*Sfx_dFsBp7AauF5PEqJFow.png" /></figure><p>So now we bring in the <strong>team</strong>. Two things become very important in these <strong>collaboration</strong> sessions:</p><p>1.) A <strong>shared goal</strong> or direction so we don’t have all the dogs bolting off in different directions, potentially breaking the sled, or wasting energy turning it in circles trying to run towards individual goals and making no progress towards a collective goal.</p><figure><img alt="A hand-drawn illustration of multiple dogs all going in different directions and not towards a shared goal" src="https://cdn-images-1.medium.com/max/400/1*dKLu4ezmYz1GYoOniexG0w.png" /></figure><p>2.) Some kind of <strong>framework</strong> or <strong>structure</strong> that can balance out load and incorporate the pulling force of dogs into a cohesive force. So in this case, it could be some kind of harness that all the dogs wear, arranged into a formation that allows the dogs to all pull without hitting each other.</p><figure><img alt="A hand-drawn illustration showing a dog harness and how dogs can go in a single direction when attatched to a sled" src="https://cdn-images-1.medium.com/max/431/1*4E4bHq2bklbCIymF1sFWdQ.png" /></figure><p>For the first one, the concept of alignment becomes really important. As the “guiding dog”, you need to establish clear boundaries and guidance.</p><p>To address these two things, I am working on how to build better habits around:</p><h3>Shared Goalposts</h3><p>In a field littered with squirrels, interesting smells and other dogs, it is easy for individual dogs to get overwhelmed and distracted with other goals.</p><ul><li>Being able to communicate and agree on a shared goal or destination will ensure that all the dogs can be pulling in the right direction.</li><li>Breaking down big goals into milestones are good “checkpoints” that can guide a team along</li></ul><h3>Structured Teamwork</h3><p>You could have a team of dogs that are different sizes, different speeds and endurance. Basically dogs that have different strengths and weaknesses that complement each other. How do you make sure they can all work together so their efforts can effective contribute to moving the sled forward?</p><ul><li>There needs to be some kind of reinforcing structure (such as a dog harness) that can work for the team that can translate the individual effort into a collective effort.</li><li>This structure can’t be too tight or too loose and needs to vary to accommodate different of dogs and goals</li><li>A non-dog example of this could be facilitation techniques and exercises that promote divergence, convergence, conflict resolution and summarizing key takeaways.</li></ul><h3>In conclusion: To achieve big things you need to be a good lead dog</h3><p>It’s not easy trying to lead a pack while still trying to pull your own weight. But by understanding the importance of shared goals and structured teamwork best practices, I am slowly trying to get better at pushing larger initiative forward, things that as an individual would never be possible.</p><figure><img alt="A hand-drawn illustration of a pack of dogs pulling a sled together" src="https://cdn-images-1.medium.com/max/1024/1*NsT18aO2A3b0lBmJF12TJQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb27cb6e90a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on professional coaching]]></title>
            <link>https://medium.com/@yichen.h3/reflections-on-professional-coaching-d60416dff02a?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/d60416dff02a</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Tue, 12 Jul 2022 00:56:48 GMT</pubDate>
            <atom:updated>2022-07-20T12:22:59.744Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a topic I have wanted to write a reflection piece on for a while now, but I have been putting it off as I am still only at the beginning of my professional development journey.</p><p>So please bear with me as I share some early thoughts about my experiences with a professional career coach,<strong> how it differs from mentorship</strong>, and my take on the value of such services.</p><blockquote>Everything in this article is my own opinion</blockquote><h3>Signing up for a coaching service</h3><p>Around 5 months ago, I signed up for a career coach through my partner’s work perks. I was pretty skeptical off the bat because I had recently <a href="https://medium.com/@yichen.h3/my-foray-into-mentorship-part-1-2-how-i-got-into-mentorship-b7e0dfe144fc">spent a good portion of my time as a volunteer mentor</a> and unsure how a career coach could help me in my day-to-day role. I mean, the volunteer mentors I talked to through ADPList were pretty great, and all from my field, could a paid coach be THAT much better? But of course you can’t knock something without trying it.</p><p>The onboarding was fairly straightforward, I took some quizzes on what I am trying to get out of the experience and then was presented with some potential coaches that matched the skillsets I was looking to develop.</p><p><em>This brings me to the first point:</em></p><h3>Diversity matters</h3><p>I was presented with a handful of options but I immediately gravitated to an Asian woman I saw in the list. Sure there is definitely tons I could learn from someone of a different gender and race, but I just felt it in my heart that there are many cultural factors that impact a career that would be hard to understand if you are viewing things from a different frame of reference.</p><p>It’s no surprise to recognize that for many careers, as you climb higher, the demographic starts skewing male and white. While I think the Tech industry is making moves in the right direction, up to this point in my career the majority of co-workers I have interacted with have not identified as woman, and an even smaller portion of them were Asian woman. I personally encountered only a handful of people who looked like me in a leadership role, so I felt a wave of relief when I saw a coach that I felt could relate to that sentiment and fear.</p><p>To my excitement, her background and experiences were also highly relevant with over a decade of professional coaching experience. Without further ado I selected her profile and sent a request for a consultation session.</p><h3>I found a coach, now what?</h3><p>As I alluded to in the opening, I didn’t have strong goals at the start of this experience. That phrase “you don’t know what you don’t know” feels relatable, as I wasn’t quite sure what areas I really needed to work on.</p><p>The good thing is coaches are pretty great at listening and helping you work through your own thoughts. It didn’t take long until she helped me identify some areas of growth that centered around my new role at work as a Design Lead.</p><p>Up until this role, I had been 100% an IC, or Individual Contributor. I was pretty confident in my skills as a product designer and the scope of responsibility that came with that. With my new role as a Lead, suddenly I had a new set of responsibilities around team-wide initiatives. With this expanded responsibility came setbacks that I didn’t know how to handle, but that is where my coach stepped in to help me figure things out.</p><h3>The difference between coaching and mentorship</h3><h4>Mentorship:</h4><p>When I think of a mentor, I often picture someone who is very similar to me but maybe 5–10 years further into their career. Basically someone I aspire to be in the near future. So as an example for me (a Senior/Lead Designer), an ideal mentor would be a Staff Product Designer or maybe a Product Design Manager.</p><p>Their experience and expertise could be useful for me to identify what kind of path I want to take in my career and they can share their unique journey that took them down that path. It is more up to me to find a variety of mentors or really luck out with someone who had almost an identical career path so their experiences and lessons learned is highly relevant to my own.</p><p>If you tell a mentor about the friction you are experiencing at work, they will likely be able to give you some tactical advice on how they have dealt with similar situations in the past. While the advice is functionally similar to a coach, it is unlikely they will be able to clearly explain it as concisely or holistically as a framework unless they happened to have formally learned it.</p><h4>Coaching:</h4><p>Coaching (at least from my recent experiences) focuses more on a coach listening to your story and helping you get to the root of the problem. My coach’s full time job is to attend conferences to learn about professional development, read books and consume content on the topics and then help working professionals in a variety of industries and roles to help them achieve their goals. This gives them a very broad library of frameworks and experiences to work with, compared to a more direct and streamlined career from most mentors.</p><p><em>An analogy I was thinking of is:</em></p><blockquote><em>“It is likely the answer to many of the problems you are experiencing lies in 3–4 books out there, but how do you know what books? Wouldn’t it be great if someone’s full time job was to consume all this content and internalize it so they can listen to your story and provide you the CliffNotes to your specific problems?”</em></blockquote><p>So many of the frameworks and ways of thinking through my experiences provided by my coach are actually things that I can later refer to in books or other publicly available content, but I don’t know if I could have ever found them myself because I don’t have the time to read them all.</p><h3>It’s all about the fit.. like shopping for a dress</h3><p>Generally I think when it comes to “fit”, it is a difficult process to find a great mentor. Not only do you need to ask someone to set aside volunteer time to help you on a recurring basis (ideally bi-weekly but at least monthly) but they also need to have experienced a very similar set of roadblocks to the struggles you are experiencing so their advice is relevant.</p><p>I think of it like shopping for a dress. You can luck out (finding a mentor) by trying tons of dresses on and finding one that is a perfect fit. It’s hard to get it right on the first try and you risk spending hours trying on dozens of dresses that all look great on the rack but are less than ideal on you. But, if you just have a good eye for dresses and get lucky, you can find one for a great price.</p><p>A coach is like a bespoke dress shop where you hire a dress-making expert to tailor a dress for you. You need to give them direction on what you want but they have the skills to help make it happen. They will likely cost much more but you are paying for their expertise.</p><p>With both of these options, one dress-hunting tactic will not necessarily be better than the other, so much of it comes down to how much effort you want to put into finding the perfect outfit.</p><h3>A personal example</h3><p>Something my coach helped me with recently was with an <strong>initiative I was unsuccessfully pushing </strong>(I plan on writing another post on this topic as it’s too long to explain here). I was focused on improving the solution and looking for advice on why I was encountering such unexpected resistance. Because of the way I internalized and explained the problem, a mentor might have tried to share similar experiences and help me further polish the design-fundamentals or pitch for this solution.</p><p>My coach on the other hand was able to look past the “Design-team-specific” elements of this initiative to see that likely it is more about my lack of experience with exerting influence, not the solution itself. Then by providing a framework to deconstruct this scenario, I was able to identify specific areas of growth to push this initiative forward.</p><h3>My verdict: It’s been great, I am looking forward to continuing this experience</h3><p>It’s been just under half a year of bi-weekly coaching sessions but I have learned so much. It has really helped me identify areas of growth and helped me plan an action plan on how to get there.</p><p>Maybe you have tried to find a mentor and not had much success and that is why you want to try something else. A coach’s job is to help with certain professional development skills that is relevant across most industries such as communication, influence, leadership, setting expectations, etc… and even if they have not personally experienced what you are going through, they will likely have helped people similar to you in the past and can rely on that to help you work through your struggles.</p><p>If you are currently experiencing frustrations on the job and lost on what actionable steps you need to take to grow and overcome these struggles, I would recommend talking to your manager about opportunities to find a professional career coach to help guide you through the rough patches. I believe most of the value that comes out of you being much more effective at your job is your employer so why not get them to foot the bill?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d60416dff02a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My foray into Mentorship — Part 2/2: What I learned from volunteering for 100+ free mentorship…]]></title>
            <link>https://medium.com/@yichen.h3/my-foray-into-mentorship-part-2-2-what-i-learned-from-volunteering-for-100-free-mentorship-bfe0aefd442e?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe0aefd442e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[reflections]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[adplist]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 14:45:04 GMT</pubDate>
            <atom:updated>2022-06-09T14:55:28.202Z</atom:updated>
            <content:encoded><![CDATA[<h3>My foray into Mentorship — Part 2/2: What I learned from volunteering for 100+ free mentorship sessions in 2021</h3><p><em>Check out </em><a href="https://medium.com/@yichen.h3/my-foray-into-mentorship-part-1-2-how-i-got-into-mentorship-b7e0dfe144fc"><em>Part 1</em></a><em> if you are interested about how I got started with mentorship.</em></p><p>When I first set up my mentorship profile on <a href="https://adplist.org/">ADPList</a> and opened up some slots, they filled up surprisingly fast.</p><p>ADPList then introduced a feature for mentees to leave reviews for mentors and it was a big confidence boost to receive a nice review once in a while. At one point they even refactored the site and we lost all our reviews (not the greatest UX), but as I was still booking sessions weekly, I quickly collected more reviews which likely helped keep my slots full. I had tons of free time (thanks Covid) so 2021 was a good year to invest that time into learning and growth.</p><p>Due to the nature of the matching process at ADPList at the time, I ended up mostly doing one-off portfolio reviews or giving career advice. The goal of most portfolio reviews was to get a job interview, so the most common questions I got were related to whether an element of a portfolio was desirable or undesirable in the eyes of a potential employer.</p><figure><img alt="An illustration of me on a rocket ship waving" src="https://cdn-images-1.medium.com/max/620/1*m1JMAB3UCldeOO1Q4zv2dw.png" /></figure><h3>Getting mentorship as a mentor boosted my confidence</h3><p>I had opinions on many things, but that is all they were, opinions informed by my own personal experiences. I believe the hiring process at most companies are similar, but still include many preference-driven decisions. I often found myself lacking confidence when providing answers until I got second takes from other senior designers, recruiters or hiring managers. I relied heavily on some of the private mentors-only channels in Design Buddies and booking sessions with more experienced designers through ADPList to get this second opinion on things.</p><p>How this really helped me is I ended up asking more and more questions as I talked to more mentees. Every single time I asked and received feedback from others in the industry, I tucked that data point away for future reference. By the end of the year, I often found the same questions coming up, and now I had some better answers backed by many opinions and data points, not just my own.</p><p>Sure there is still no “100% always-right answer” but I could now share some different viewpoints that can help guide someone to the specific goals they are trying to accomplish.</p><p>At this point, I had also seen so many junior level portfolios that I had a good sense of if they were “good”. I could spot common errors such as stories that don’t connect, content that didn’t add any value, places where they claim one thing and then do something else entirely. Because I had spent so many hours reviewing portfolios and working on them collaboratively with others, I became much better at offering advice and suggestions in addition to just pointing out problems.</p><figure><img alt="An illustration of me looking at my own reflection in a mirror" src="https://cdn-images-1.medium.com/max/291/1*-FzWB9YpsmjBAJmTaOyGcg.png" /></figure><h3>Self reflection was key to learning from this experience</h3><p>One of the things I think was really important to my development was also <strong>writing down</strong> everything I was learning. After around 30 sessions, I had already noticed a trend in the types of questions I was being asked. I started the notion resource <a href="https://www.notion.so/UX-FAQs-3cbed70a2ce244208394a852af79996f">UX FAQs</a> to start writing down my thoughts on these super-common questions.</p><p>By writing it down, I was forced to think through these questions more methodically and also pay attention to the story-telling component of presenting content. Additionally it challenged me to work in new details and insights as I learned more talking to both the mentees and my network of other designers.</p><p>Many of these FAQ topics ended up as fascinating discussion points with other designers where I was able to learn more and understand different takes that come from experiences that contradicted my own.</p><p>I found that the resource was also very helpful to share before mentorship sessions, so anyone interested in chatting with me can first read up on some general thoughts about a specific topic so we can drive deeper in the time we do have to actually chat via a video call. That felt like a much more effective use of time vs. me just repeating the same two paragraphs every time someone asks me “should I take a bootcamp?”.</p><figure><img alt="An illustration of me running away from a purple monster with a flame on its head" src="https://cdn-images-1.medium.com/max/691/1*xtfhUJI8jOfGCpplaphG3g.png" /></figure><h3>Pace yourself to avoid Burnout</h3><p>I do admit, near the end of 2021, I was starting to feel a bit burned out from mentorship. I was averaging at least 2 sessions a week, sometimes up to 4 when people contacted me through email/linkedin/discord instead of ADPList. My partner was feeling a bit sad that instead of continuing a show or game, or grabbing dinner with friends (as the restrictions started to lift), instead I was in a 30 min call that had ran over to an hour because we were just really engaged in the conversation.</p><p>There was definitely a point where it went from feeling fun and exciting to more like an unpaid job that I started dreading… especially when I had to turn down social events because I already had sessions scheduled weeks out. I think it is different for everyone but it took a while for me to find a cadence that worked for me.</p><p>While I have mostly closed my calendar on <a href="https://adplist.org/mentors/yichen-he">ADPList</a>, my door is still open. I try to pace myself so I can get out out more and enjoy the summer. I still touch base with a handful of mentees and it’s been very fulfilling to follow along their success and see all their hard work pay off. Once in a while I also receive the odd request through LinkedIn which I always try to make time for.</p><figure><img alt="An illustration of me shaking heads with a blue guy with the word “job” labelled on its face" src="https://cdn-images-1.medium.com/max/405/1*B1po5U3ZauJR5W67aD_RCg.png" /></figure><h3>How Mentorship helped me land my next job</h3><p>So here I am halfway through 2022 writing a reflection on mentorship. It felt like a good time to take a step back and think about all the events that lead to my current role as the Design Lead of the Transformation Products team at VMware.</p><p>My role prior to this one was as an Individual Contributor (IC). While it is not always the case, I have found most IC roles tend to focus on what we call “craft” in the design space. It revolves around how “good” you are at design, and all the different facets of skills and expertise that contribute to the specific products you are designing. While I had informal mentorship opportunities in work before, it was usually more around specific areas where I had a higher skill proficiency than another designer. This overarching responsibility that was included in the senior+ levels of job descriptions was foreign to me.</p><p>This new role I applied for was as a “Lead” of a small design team, which meant that in addition to the normal IC work, I also had some responsibilities that extended past just “doing design”. One of these was providing guidance and mentorship to my team.</p><p>Now when asked about my past experiences with this skill, I could speak to all the hours I spent giving advice through free mentorship. I talked about having to adapt my listening skills to each individual and how I waded through the unstructured stories and questions to arrive at addressable topics where I could share insights. It also didn’t hurt that I had some impressive stats to back up my claims of the effort I invested into being a mentor.</p><p>I truly believe that without my experience in volunteering as a free mentor and talking to so many different people, I would not have the confidence or proficiency to succeed in my current role.</p><figure><img alt="An illustration of me walking up a hill that is has the word “improvement” on it" src="https://cdn-images-1.medium.com/max/513/1*b2hhmRGwX_ig6t6dehCrsw.png" /></figure><h3>Mentorship is a low-risk way for self-improvement</h3><p>Here I will refer to that Latin proverb “<em>Docendo discimus</em>” which roughly translates to “by teaching, we learn”. This is not just to sound snooty and smart, but also a really apt way to describe the experience of being a mentor.</p><p>I can guarantee that “impostor syndrome” will strike even at the mere thought of becoming a mentor, I know that was definitely the case for me. One thing that really helped me get started is the pivot in thinking from positioning yourself as “someone with answers to all the questions around design” to someone who is here to “share their own personal experiences” that may relate to scenarios others are curious about.</p><p>For example, it’s hard to say “this is how everyone should get jobs”, but contrast that with “this is what worked for me, and others I know who have been successful in their journey”. Every situation is unique and what works for one person may not work for another. That being said, there is still tons of insights that can be extracted from learning about the experiences of others.</p><p>Practicing framing your conversations around sharing an informed opinion over perceived facts will help you navigate the complexities around working as a designer. The whole field is full of contextual problems that often don’t have one correct answer, so the ability to explain multiple options along with your take on the pros and cons can be very helpful for developing your communication skills with coworkers and peers.</p><p>At the end of the day, the role of the mentor is not to tell people what to do but rather help them guide their way through a situation and navigate towards a goal. You are likely there to provide more data points on how you (and maybe others you know) have navigated through similar situations and how that affected the outcome. There will always be trade-offs but perhaps your advice and experiences could help someone else plan out their own trajectory. The risks are actually quite low as long as you make it clear that you are not there to tell someone what to do, but just share your personal advice. Worst case your stories don’t resonate with them and you part ways.</p><p>Lastly, the more you mentor, the more you learn and that will help you build confidence. After all, it’s a different experience answering a question the first time vs. the 50th time. If you don’t know the answer to something, ask around! Many people who mentor also have their own mentors in their community of peers and coworkers. The process will help you identify gaps in your own knowledge and give you ideas of where you could learn more to develop your own skills.</p><h3>Closing thoughts</h3><p>In addition to just learning lots, building my confidence and having a good time, I also found the gratitude I received from my mentees super motivating. Just about every single person I talked to was very appreciative of my time, professional, and went out of their way to thank me afterwards. Additionally, it was so inspiring to see how hard everyone was working to achieve their goals. The best feeling too was when I would get an email after a while with the good news that someone landed a fantastic job.</p><p>All in all I had a fantastic experience with being a mentor and I wholeheartedly recommend it to anyone who is on the fence. Even if you only just got your first job in design, you could be a mentor! I mean, who else has more relevant experience on the topic of “how do you get your first job in design?”</p><p>To get started, it’s as easy as typing up a LinkedIn post saying you are free to chat. Alternatively you can look into applying on platforms such as <a href="https://adplist.org/">ADPList</a> or <a href="https://www.designbuddies.community/">Design Buddies</a> (there are many more I am sure).</p><p>I might not recommend jumping into the deep end like me and opening up your whole calendar (because please, you should enjoy life outside of your profession). If you pace yourself, it’s definitely an investment in improving your own knowledge and skills in addition to potentially giving back to the design community.</p><p><strong>Closing note/shoutout:</strong> As with many things in life, it ended up not being about the destination, but the journey and all the friends I made along the way. A huge shoutout to all those pairs of eyes I had on my FAQ resources and all the times I received amazing advice and insights from all the talented designers I talk to. You know who you are ;)</p><p>Also, if you had a good experience with a mentor, please consider sending them a little thank you note! You will make their day :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe0aefd442e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My foray into Mentorship — Part 1/2: How I got into Mentorship]]></title>
            <link>https://medium.com/@yichen.h3/my-foray-into-mentorship-part-1-2-how-i-got-into-mentorship-b7e0dfe144fc?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7e0dfe144fc</guid>
            <category><![CDATA[adplist]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[reflections]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 14:38:58 GMT</pubDate>
            <atom:updated>2022-06-09T14:45:30.346Z</atom:updated>
            <content:encoded><![CDATA[<h3>My foray into Mentorship — Part 1/2: How I got into Mentorship</h3><p><em>Feel free to skip to </em><a href="https://medium.com/@yichen.h3/my-foray-into-mentorship-part-2-2-what-i-learned-from-volunteering-for-100-free-mentorship-bfe0aefd442e"><em>part 2 </em></a><em>if you don’t particularly care about how I first got into mentorship in the design community and want to read about my learnings.</em></p><figure><img alt="An illustration of myself sadly walking away from a Covid virus" src="https://cdn-images-1.medium.com/max/426/1*4pxcfSJuveUgCB2YNW4drw.png" /></figure><h3>Late 2019, an inciting incident</h3><p>Like many others around the world, I had some pretty exciting plans lined up for early 2020. My partner and I had sold our car, moved out and signed a lease starting in February 2020 in Shanghai. I was working as a product designer on a complex financial modelling product and after months of negotiation and planning, I had managed to convince them to let me work a flexible schedule from the other side of the globe.</p><p>What ended up unfolding was not what we expected, and instead spending my days digital-nomading in any one of Shanghai’s 50+ WeWork offices, I found myself working remotely from my in-laws lovely basement with copious amounts of free time.</p><figure><img alt="An illustration of myself looking at different design communities" src="https://cdn-images-1.medium.com/max/455/1*omJ9KbVt1l4bTzJMc2zwnA.png" /></figure><h3>Discovering more Design Communities</h3><p>Due to how events played out, I found myself stuck at “home” with so much free time. I ended up coming across <a href="https://www.designbuddies.community/">Design Buddies</a>, a Discord design community that started up as the world worked their way through the first wave of quarantines. At this point, I had been part of many IRL &amp; Slack-based communities such as DesignX (based in Toronto), but I was surprised to find Design Buddies filling a slightly different need with a much more casual and open community.</p><p>While Discord and Slack are very similar in functionality, the general target demographic of Discord led to a rapidly-growing, more-engaged design community that skewed younger. For example, in many Slack communities, people used their real name and photo which inadvertently ends up connecting the content they share with their whole LinkedIn career history. There was an underlying incentive to “appear smart” so the conversations felt more robotic and always served a purpose. I viewed my time in these communities more as “professional networking” than as leisure.</p><p>Discord, on the other hand started as a product for gamers. Most people used a nickname and a fun graphic display picture. In a Discord design community, it felt natural to discuss hobbies in addition to asking design-related questions. Discord also did not have a cap on the number of posts before enforcing a paid plan, so the communities could scale to be larger than Slack.</p><p>With all my newfound time, I found myself getting really engaged in the community, and eventually finding many groups of people (friends!) I could talk to about personal things too such as restaurant recommendations, games to play, and exchanging photos of cute pets. They just all happened to be in the design industry as well.</p><figure><img alt="An illustration of myself dipping a toe into a pool labeled “mentorship”" src="https://cdn-images-1.medium.com/max/524/1*N2L7YAMAPAfHgRoNUgXaLQ.png" /></figure><h3>Dipping my toe into mentorship</h3><p>Just because I was engaged in the community, I ended up participating in the first wave of “mentors” in Design Buddies as my ~5 years of work experience at that point was enough to qualify as someone who knows a bit of what it is like working in design. My confidence in being a mentor was pretty low, but the stakes were also not sky-high as it was still a very small initiative at the time. We had a special channel for Mentors in Design Buddies where I could go to get advice or maybe a second opinion on things I wasn’t quite confident in.</p><p>It was later in 2020 when another community called ADPList had started exploring the world of mentorship, something that Design Buddies… was building up a the the same time.</p><p>To those who are not aware, ADPList (Amazing Design People List) was originally just an Airtable list of designers who were laid off due to the uncertainties around the pandemic. They ended up pivoting to the mentorship space and partnered with the mentorship initiative at Design Buddies. As a result, a large cohort of us from Design Buddies were migrated over to the budding ADPList platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hNnnvgQHXccpGmBwTFQvZg.png" /></figure><p>It was honestly pretty cool seeing myself on the home page with a shiny “in partnership with Design Buddies” tag.</p><p>While my path into mentorship was one of being in the “right place at the right time”, I really threw myself into this new role in 2021. I kept a few slots open on my calendar almost every week and they filled up. There were less than a dozen Canada-based designers on the platform at the time so I had a steady stream of bookings.</p><p>In early 2021, ADPList was really pushing the portfolio-review aspect of mentorship, so I would say the majority of people I chatted with were people who were:</p><p>1.) Actively seeking a job in UX (~70%)</p><p>2.) Pivoting into the UX industry and creating a portfolio to apply to jobs (~20%)</p><p>3.) Considering pivoting into UX who had questions (~10%)</p><p>In that first year of this experience, I ended up talking to over <strong>100 people</strong> in a mentorship capacity and reviewed countless portfolios. Some people just wanted to chat and have a sounding board to bounce ideas off of, while others wanted me to conduct mock interviews for practice. Speaking to so many people did wonders for my professional development.</p><p>I will share more on the the experience of how I went from “<em>why would anyone want my advice!?</em>” to “<em>I believe some people might find value in my advice</em>” in <strong>Part 2/2 — What I learned from volunteering for 100+ free mentorship sessions in 2021.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7e0dfe144fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Golf and product design]]></title>
            <link>https://medium.com/design-bootcamp/golf-and-product-design-91457e75fd40?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/91457e75fd40</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[golf]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Tue, 05 Oct 2021 00:29:30 GMT</pubDate>
            <atom:updated>2021-10-05T00:29:30.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Title image: Golf vs. Design" src="https://cdn-images-1.medium.com/max/800/1*i6vffwTXi5EwbfCeVD3GqA.png" /></figure><p>Here I will try to explain some product design concepts using golf as a point of comparison.</p><p>(spoiler: I am not good at golf)</p><h3>1.) Process and tools</h3><h4><strong>Design</strong></h4><p>There are endless <a href="https://uxdesign.cc/a-comprehensive-list-of-ux-design-methods-deliverables-2021-2feb3e70e168?gi=64ab0d659ebf">exercises, frameworks and tools</a> that can be used by designers to brainstorm, identify problems, understand, solution, compare and more.</p><figure><img alt="An illustration of some personas, a wireframe and icons of popular design apps like Figma and Sketch." src="https://cdn-images-1.medium.com/max/400/1*OrInSt5r7_YX0jtmmR6YcA.png" /></figure><p>They all have their unique pros and cons and are well suited to different scenarios. For example, sometimes it helps to create personas, and sometimes you might be able to get away with sets of JTBDs.</p><p>There are generally agreed upon practices and tools that work well for specific situations, but there tends to be a bit of <strong>wiggle room</strong>. Sure you could make wireframes in Adobe Illustrator, but it would probably be easier in Figma.</p><p>Different tools for different jobs.</p><h4><strong>Golf</strong></h4><p>For golf, you don’t need to use a full set of clubs for every course. Some courses you might be able to squeak by with a handful of clubs, and some you might need the whole bag.</p><p>If we include mini-putt, maybe all you need is just a putter.</p><figure><img alt="An illustration of a set of golf clubs in a golf bag." src="https://cdn-images-1.medium.com/max/400/1*MXcvVD6uvMpawbU0d6rvow.png" /></figure><p>Initially, you need to do some research and learning on when to use what club. However, reading about club usage guidelines doesn’t help much unless you also get out there and <strong>start swinging them</strong>. You need to build that muscle memory of how the ball interacts with the different clubs, and how you can affect that with your technique (grip, position, angles, power etc.).</p><p>Once you are familiar with swinging the clubs, you can start confidently identifying when to use what. Next, you can start thinking about optimizing your club set for specific golf courses. If the course is full of sand traps, you might need more wedges to choose from. If you know there isn’t a single sandy area in the course, maybe you can omit some.</p><p>In design it is very similar in that you just have a large set of tools in your toolbox. If you have never used a tool before, you probably won’t have a great grasp of the benefits it brings or how to use it to it’s fullest potential.</p><p>However, as you gain more and more experience using different tools, you will get a better understanding of when to use what, and also how to properly derive the most value from them.</p><h3>2.) Skills and practice</h3><p>The only way to get good at golf is to play lots of golf.</p><figure><img alt="An illustration of a person practicing their golf swings, failing 4 times and succeeding on their 5th attempt." src="https://cdn-images-1.medium.com/max/399/1*Rse0b7Sr5isVmHPzFQ1vPA.png" /></figure><p>You can “drill” or target your practice by repeating specific skills. A good example of this is going to a driving range to practice long drives.</p><p>Sure you know that a specific club you have is ideal for curving left, or curving right.. but you still need to put in the hours to improve your swing so you can get the most out of your fancy clubs. This kind of training will help you improve a specific skill, but that is only one of many you need to become a good golfer. You need to <strong>combine</strong> this together with other skills such as mid range, chipping, putting etc.</p><p>I compare this with “drilling” craft as a designer. For example, you can improve your “eye” for visual UI design by just designing tons of interfaces. Completing the <a href="https://www.dailyui.co/">100 daily UI challenge</a> might not improve your interaction design skills at all, but it sure as heck will improve your visual UI design skills.</p><p>I compare doing full projects designing features to playing full courses of golf. It will be a test of many different skills, identifying the right tool for the right job, and then also learning from putting all the pieces together.</p><figure><img alt="An illustration of a person debating between two different golf clubs." src="https://cdn-images-1.medium.com/max/450/1*7BAOGKOpVXzMERNOzI3sEQ.png" /></figure><p>Learning is more effective and efficient when you drill specific skill sets, but you still need to know how they interconnect and interact with each other. You can practice driving, chipping and putting separately, but your actual games may not fully improve until you put it all together and start playing more actual games of golf.</p><p>It is the same for design. <strong>Don’t stop once you have two portfolio pieces</strong>, you can keep going (but feel free to start applying to junior roles once you have 1–2 solid pieces). The best way to improve a skill is to <a href="https://medium.com/@jamesclear/why-trying-to-be-perfect-wont-help-you-achieve-your-goals-and-what-will-e872a51744a3">practice it</a> every day, so roll up your sleeves and get designing. The more you try, the more experience you have to base future decisions on.</p><h3>3.) External variables</h3><p>Maybe you are an amazing golfer but just got unlucky that it was a rainy day and now the ball is stuck in the mud. Some things are outside your realm of control and that is also the case with design.</p><figure><img alt="An illustration of a person with their golf ball stuck in the mud during a rainstorm." src="https://cdn-images-1.medium.com/max/399/1*uTu2bytD_yRxHmejwphq0g.png" /></figure><p>Sometimes you work hard, do an amazing job, but due to a non-design reason (users, business, engineering, stakeholders, etc.), things don’t work out and you need to <strong>pivot</strong>. In most of these cases, you still have tools at your disposal, but now the environment as changed, and you need to <strong>adapt</strong>.</p><p><strong>Experience</strong> is valuable here because if you have played golf in the rain before, you might have experienced many of the difficulties it brings, and know how to adapt to best handle them. You won’t be nearly as nervous and can potentially mitigate these external variables better.</p><h3>4.) Mentorship</h3><p>Having a good mentor can really help, but you still need to put in the legwork.</p><figure><img alt="An illustration of a mentor giving advice to a mentee on how to golf in the rain." src="https://cdn-images-1.medium.com/max/400/1*CsDc5uoF8wwDShfgV2qX4w.png" /></figure><p>A mentor can help give you tips and suggestions, and also provide critique. If you golf with a good mentor, they can share real-time advice on what is off with your posture, when you could have used a different club, or point out areas where you need to drill in more practice. What they can’t do is practice FOR you and magically improve your skills.</p><p>The same goes for design, where having a good mentor could really help you with identifying areas of improvement, general advice and also moral support.</p><h3>How design is not like golf</h3><p>While there are many similarities, there are also a few key differences.</p><ul><li>Design is a<strong> team sport </strong>whereas golf is a solo sport. You could get good at golf by yourself, but it is very difficult (some might say impossible) to get good at product design flying solo.</li><li>The concept of “<strong>storytelling</strong>” doesn’t exist in golf, being good at golf is easy to prove. As a designer, sometimes the heavy lifting is in the process, not only the results. In addition to delivering results, you should also be good at explaining how you got there.</li></ul><p>Hope you enjoyed this silly comparison. Turns out in general, being a designer doesn’t help you get good at golf, period.</p><p>The key point I want to drive home is that product design is not something you learn overnight. In addition to academic learning, you need <strong>practice</strong>. For most interesting problems in this world, there are little black and white answers, and the fun part is gaining enough experiences to drive your own conclusions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91457e75fd40" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/golf-and-product-design-91457e75fd40">Golf and product 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[What does “after UX” even mean?]]></title>
            <link>https://uxdesign.cc/what-does-after-ux-even-mean-7edc3d4febc4?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/7edc3d4febc4</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Sat, 20 Feb 2021 00:38:53 GMT</pubDate>
            <atom:updated>2021-02-20T04:07:48.713Z</atom:updated>
            <content:encoded><![CDATA[<h4>How viral “top of the iceberg” advice could do more harm than good.</h4><figure><img alt="An opening image showing a “Before and After UX” image and red text stating “Please stop this!”." src="https://cdn-images-1.medium.com/max/1024/1*fyhBgJYE0c9eN2STZ8OLbg.png" /></figure><p>Teisanu Tudor shared a <a href="https://uxdesign.cc/i-disguised-as-an-instagram-ux-influencer-for-4-months-this-is-what-i-learned-about-our-community-4a4b4e8844b">riveting account of how they pretended to be an instagram UX influencer</a> a few months back. From their experience, it seems that unfortunately, lots of popular content positions UX as this “happy, easy, 10-step-quick-learn discipline”.</p><p>As with any popular industry, thought leaders of varying levels emerge and establish their presence on common social networks. For example, LinkedIn is a newer phenomenon that combines the typical social-media <a href="https://www.vocabulary.com/dictionary/clout#:~:text=When%20you%20speak%20of%20someone,He&#39;s%20got%20clout.%22">clout</a>-chasing and idea-flaunting with actual network-building and learning opportunities.</p><p>The rising popularity of “<strong>before and after</strong>” UX shots is slightly worrying. You might know the ones I am talking about.</p><figure><img alt="An picture of example Before/After UX post." src="https://cdn-images-1.medium.com/max/874/1*rhNUMUI9sovvOh2xQnYL2A.png" /><figcaption>An example of a popular format for “before/after UX” images found on LinkedIn</figcaption></figure><p>I am not trying to call out anyone in particular, but my main concern (shared with many commenters on these posts) is the focus of these posts <strong>can’t possibly be about the user experience without any</strong> <strong>CONTEXT</strong> of the goals that informed the “after” design.</p><p>Most designers agree there is often no single “correct” answer that just works for every scenario. One of the main skills a designer brings to the table is the ability to tackle these “it depends” situations where <strong>multiple variables, stakeholders, and goals need to be aligned or balanced</strong>.</p><p>Here is a great post I came across from an experienced design leader <a href="https://www.spillthebean.org/design-overview/brian-lin">Brian Lin</a> explaining this concern.</p><figure><img alt="A screenshot of a LinkedIn post from Brian Lin." src="https://cdn-images-1.medium.com/max/533/1*yt-4P-xLTDdsRmMRtcogOQ.png" /></figure><p>The before/after example shared is a very common post format I see. Speaking specifically to the one I shared, the debate between Cards vs. Lists (or even Tables) have existed since the dawn of modern interface design. In fact, <a href="https://uxdesign.cc/ui-cheat-sheet-list-vs-grids-48151a7262a7">many authors have covered this exact topic in depth</a>.</p><p>With no context, someone new to UX might make the erroneous assumption that: <strong>Cards are BETTER than Tables…</strong> without consideration for the important context that informed this design.</p><figure><img alt="A Card View design example" src="https://cdn-images-1.medium.com/max/247/1*jrSOeA8XGCBe6JxbJbf3Kg.png" /><figcaption>A beautiful lil’ card</figcaption></figure><p>Sure, this design might <strong>look nicer</strong>. It is incredible what some colours, shapes and graphic touches can do to enhance the visuals. But <strong>WHY </strong>does the “after” design look like this?</p><p><strong>Context</strong> is what determines the metrics used to measure the success of a design. Without including the context, it is almost impossible to determine which is better out of two options as there are very little criteria to compare with (outside of general visual appeal).</p><p>Just off the top of my head, here are some (of many) important considerations to think about when working on a design similar to the one in the example.</p><p><strong>Who are the people using this design?</strong></p><ul><li>How will their unique experiences and expectations influence the way they interact with this design?</li></ul><p><strong>What are their wants and needs?</strong></p><ul><li>Are they browsing the information or searching for something specific?</li><li>Are they trying to use this information to make a decision?</li><li>Do they want to interact with the information to perform a task?</li><li>Do they typically need to see multiple elements to compare or do they tend to focus on one at a time?</li></ul><p><strong>What are the typical cases and what are the edge cases?</strong></p><ul><li>How many items are on this list? Are usually between (1–5), (100–1000), or (10,000+)? Designing to display a few items is very different than designing to show many.</li><li>Will they be viewing this data on a mobile device? A computer screen? A TV? AR/VR?</li></ul><p><strong>Technical limitations</strong></p><ul><li>What technologies are being used to build this design and what limitations come from that?</li></ul><p><strong>Business wants and needs</strong></p><ul><li>Does the design need to drive some business KPIs and metrics?</li></ul><h4>An example of context:</h4><p><strong>What if </strong>many of the users tend to <strong>scan</strong> through these items to find something?</p><p>Let’s take another look at that “after” UI and add some more items to it.</p><figure><img alt="A card view example with 14 items" src="https://cdn-images-1.medium.com/max/753/1*9jDNKyeXfl5L-RPtFbnf1g.png" /><figcaption>Now we have 14 items being displayed</figcaption></figure><p>Suddenly it becomes much harder to scan, doesn’t it? (not even considering the need to “filter” items).</p><p>If the main use of this design is to quickly look through the list of items to find something, perhaps the “before” UI with the boring table seems a bit more attractive now.</p><figure><img alt="A List View design with 14 items" src="https://cdn-images-1.medium.com/max/835/1*Rcvdu-Uv_Dxax9mVJhCiNA.png" /><figcaption>The same 14 items in the “before UX” view</figcaption></figure><p>This of course, is just a very one-dimensional slice of the context pie. When designing for multiple interested parties, there are often layers upon layers of different things that need consideration.</p><blockquote>The Problem: People who are new to UX might expect designers to just take old designs, go work alone in a dark cave for a while, and <strong>magically</strong> emerge from it with a “good UX.”</blockquote><p><strong>This is very scary</strong>. It undermines all the great work UX designers globally are doing to push the importance of user-centered design processes. It is also very misleading to new designers who risk falling into the trap of stylish mockups = usable experience.</p><p>Our work as UX designers is not as simple as a before/after, and decisions in design should have intent, purpose and rationale. It would be lovely to see are more <strong>conversation about the process and thought</strong> that went into an “after” image, rather than just the image itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*4PpAiQZdvcwBQbpb" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7edc3d4febc4" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-does-after-ux-even-mean-7edc3d4febc4">What does “after UX” even mean?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enterprise UX is amazing. Change my mind.]]></title>
            <link>https://uxdesign.cc/enterprise-ux-is-amazing-change-my-mind-210dd9cff968?source=rss-facd03d2fd36------2</link>
            <guid isPermaLink="false">https://medium.com/p/210dd9cff968</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Yichen He]]></dc:creator>
            <pubDate>Sat, 16 Jan 2021 12:24:27 GMT</pubDate>
            <atom:updated>2021-01-16T12:24:27.446Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Why this under-represented but widespread design field comes with lots of unique and interesting challenges.</em></h4><figure><img alt="A illustration of the meme “change my mind” featuring a man holding a cup of coffee with the sign: Enterprise UX is amazing." src="https://cdn-images-1.medium.com/max/1024/1*q0wM3ms2kEm4U1fBeifTAA.png" /></figure><p>As promised, here is a follow-up piece to my previous post — Part 1: The <a href="https://uxdesign.cc/designing-for-enterprise-vs-designing-for-consumers-36a16f2281c2">differences between enterprise and consumer UX</a>. This follow-up is a bit less objective and instead, deeply rooted in my personal experiences and<strong> why I personally enjoy </strong>working in Enterprise UX.</p><h3>You get to break things down… So you can build it back up</h3><figure><img alt="A man with a wrecking ball, knocking down a problem" src="https://cdn-images-1.medium.com/max/750/1*N8cZtbb10tRKUr2aAumnEA.png" /></figure><p>Breaking down a large messy workflow into smaller chunks can be quite difficult. There is nothing quite like the decades of baggage that many enterprise organizations bring to the table. Even understanding some problems requires dipping your toe into many subject matters to map things out.</p><p>Only once you <strong>understand how everything connects </strong>can you start identifying and organizing work into manageable pieces.</p><p>You <strong>continuously learn </strong>more about the reasons behind every goal and limitation you encounter (which are <em>many</em>). This <strong>broadens your understanding </strong>of many areas that are closely interconnected to your specific project as well as how other members of your organization work. You get to build proficiency in connecting the dots and looking at projects from a systems-level perspective.</p><p>It is tough to always be learning, but you will often <strong>not be alone</strong>. A team of subject matter experts will likely be there to help you understand, and it can be incredibly rewarding when things seem to click and you enjoy a brief “<strong>aha</strong>” moment.</p><ul><li>Sometimes it comes from an off-hand comment a <strong>user </strong>makes when they demonstrate their day-to-day work processes.</li><li>Sometimes it comes from <strong>developers </strong>explaining to you how various databases are redundantly storing data and introducing inconsistencies.</li><li>Sometimes it comes from talking to many <strong>PMs</strong> and noting that they all want the same thing but are just expressing their needs differently.</li></ul><p>As you learn and start seeing the bigger picture, you see a giant web of interconnected regulations, technical constraints, business objectives, timeline pressures, user needs, user wants... And more! While this is the case for most UX projects, the enterprise space is somewhat unique in the dizzying layers of complexity because you are likely designing for a very specific set of users who have high technical knowledge and opinions about how they would like a solution to work.</p><h3>Complex solutions for complex problems</h3><figure><img alt="A person holding a puzzle piece with UX written on it" src="https://cdn-images-1.medium.com/max/750/1*ON52p1Ce2SMYut3L2ym5Qg.png" /></figure><p>Complexity is <a href="https://www.intercom.com/blog/the-hidden-cost-of-design-complexity/">often born out of standardization and regulation of things that are<strong> not easily lumped together</strong></a>. Workflows that start out simple can easily get chopped up and mushed into stiff boxes for the sake of consistency, accuracy, and accountability.</p><p>It’s likely that the solutions you try will not be a simple “rule of thumb” interaction based on some best practices from mature design systems (hello <a href="https://material.io/design">Material</a>). The fun will come from communicating with all your stakeholders and users, mixing things together, taking cues from other products and cherry-picking elements that could fit your unique user flow.</p><p>You will often feel like <em>Leonardo da Vinci</em> when after multiple failures.. you “discover” something that shows promise to the users. Something that you have never seen in a Medium post before because your use cases and constraints might be just that <strong>unique</strong>. You might feel like a creative genius having successfully balanced so many different variables and limitations to come to a feasible solution.</p><h3>Documentation for days</h3><figure><img alt="A girl standing on top of a stack of documents holding a pen" src="https://cdn-images-1.medium.com/max/542/1*QD4kuE2wCJb1bgjEI_VNJA.png" /></figure><p>I am a huge documentation nerd. Many I have worked with will testify that my happy place is a well-structured Confluence page that is properly linked out and cross-referenced. I realize my quest for order may be seen as a bit <strong>overkill</strong> when projects are not as complex, and therefore I am happy to find a need for it in many Enterprise UX projects.</p><p>Like most UX projects, enterprise design comes with tons of stakeholders and it is crucial to keep everyone on the same page. You also don’t want to <strong>constantly be having meetings</strong> just to keep people up to date. This is where documentation pulls its weight.</p><p>I derive a great sense of pleasure from being able to see the <strong>progression</strong> of a design through many iterations. For each iteration, I generally like to write down:</p><ul><li>Our understanding of the goals for this round</li><li>What we hypothesized would help achieve them</li><li>What ended up working</li><li>What changes does this new knowledge inform?</li></ul><p>The value of documentation is directly correlated with how big a project grows. The more people you work with, the longer the project, the more features you cover, the more complex flows are and the more iterations you do… these factors and more all tend to swell, especially in enterprise UX. It becomes more important than ever to have a good log of <a href="https://uxdesign.cc/documenting-is-designing-how-documentation-drives-better-design-outcomes-3ebd87a33d57"><strong>when and why decisions are being made</strong></a>, as well as whose <strong>inputs drove that decision</strong>.</p><p>I have found that stakeholders, users and team members<strong> love to see their feedback </strong>tracked and addressed (with rationale on why it was or was not incorporated). It helps them to understand the design team’s efforts and progress and drives home the value of the UX process.</p><p>Using the popular quote “<strong>history tends to repeat itself</strong>”, design teams tend to gain much more confidence in<strong> future decisions </strong>when they feel they have a decent understanding of past decisions and the compromises that they each came with.</p><h3>Goals that I vibe with</h3><figure><img alt="A person holding a plushie that has “goals” written on it" src="https://cdn-images-1.medium.com/max/350/1*hOtWttpZ87svmEMA4YToAA.png" /></figure><p>A large goal that spans across many enterprise software is to <strong>optimize digital workflows</strong>. For example, the three key things my current company offers are solutions for <strong>managing, modernizing and securing</strong> an organization’s IT infrastructure.</p><p>This is a goal I can really get behind as many of our solutions are designed to help alleviate very <strong>manual, boring and error-prone tasks</strong>.</p><h4>Some examples of solutions I have personally worked on include:</h4><ul><li>Optimizing VM loads for large virtualized environments</li><li>Managing security and updates for mobile devices</li><li>Automating calculations for modelling investment portfolios</li><li>Migrating windows services such as Azure AD.</li></ul><p>Sure these sound about as<strong> boring </strong>as “solutions” get.</p><p>But let’s look at my current project... in the event of an organization service switch or acquisition, it is usually a lot of hard work migrating thousands of users from one IT service to another. If anything goes wrong, it could result in security breaches, loss of data, and downtime that can result in massive productivity and business losses.</p><p>Every extra minute wasted on a poorly functioning workflow that increases avoidable errors adds up to more stress for our users. Just think of the overtime and headache that admins would suffer if important data was lost or migrated incorrectly.</p><p>Being able to iterate on solutions that instill peace of mind for IT admins and their users to efficiently and successfully migrate an IT service can free up their bandwidth to address other responsibilities. Heck, it might even allow them the time to drive their kids to soccer!</p><p>This is something I feel very proud of, that my hard work in iterating through many different ideas, combined with the feedback and insight with my team and our users can result in a more usable product that saves our users time and helps them to do their job successfully.</p><h3>Less murky ethics</h3><figure><img alt="A block with the word “ethics” carved on it being cleaned" src="https://cdn-images-1.medium.com/max/750/1*NhuzFmq1flONRo7bEKgaCw.png" /></figure><p>One of the big issues that designers around the world are coming to terms with is <a href="https://www.ethicsfordesigners.com/"><strong>design ethics</strong></a>. The emergence of better tracking and analytical tools kicked off the uncomfortable rise of <a href="https://darkpatterns.org/">dark patterns</a>.</p><p>A great example of this was in travel booking sites, where the data showed that invoking a sense of urgency by displaying “<em>X other people are also looking at this deal</em>” would push a user to be more <strong>reckless</strong> with their purchasing decision.</p><p>Other tactics weaponize your preference and usage data, then feed you designs that are psychologically designed to<strong> prey on your emotions</strong> to incentivize certain behaviours.</p><p>For the most part, Enterprise software wants the user to interact with it as <strong>little as possible</strong>. The results speak for themselves in the sense that users shouldn’t be using it unless they need to address an issue or accomplish a task. <strong>There is no extra incentive to keep users “engaged”</strong> as we want them <em>in and out</em>, hopefully with a feeling of satisfaction for having accomplished what they entered the app to do.</p><p>When we do use psychology, it is usually to accomplish a functional purpose of either garnering attention (for an error that they need to address) or to hint at the next steps in a particular workflow. For the most part our goals as enterprise designers align with the user’s desire to<strong> get stuff done</strong> in a secure, efficient, and accurate manner. Nice.</p><h3>Opportunities</h3><figure><img alt="A person staring off into a sun. The sun has “opportunities” written on it." src="https://cdn-images-1.medium.com/max/956/1*90w_uFd9G64rvHvrCNFEyg.png" /></figure><p>Lastly, I mentioned this in my <a href="https://uxdesign.cc/designing-for-enterprise-vs-designing-for-consumers-36a16f2281c2">other article</a>, but there are so many <strong>OPPORTUNITIES</strong> in Enterprise UX. Not only are your users counting on you to help them do their jobs, but the industry as a whole is counting on you.</p><p>Enterprise UX is still seen as the underdog. You know there is long road ahead when for many projects, <a href="https://www.uxpin.com/studio/ebooks/future-of-enterprise-ux-consumerization/"><strong>the goal is to have “consumer-grade” UX</strong></a>.</p><blockquote>I have lost track of the times when a stakeholder pulls out a mobile app (with 1/20th of the features our project include) and asks me “<strong>can our product look like this?</strong>”.</blockquote><p>While the level of complexity we work with can be on a whole different level, I still think it is a fantastic <strong>goal</strong>, as “Consumer” UX isn’t all about the end product. It is also about the user-centric methods that are vital in an industry where a user’s opinion of a product is instrumental in their success. Just because we can get away with less usable experiences in Enterprise does not mean we should just assume the status quo when we feel that more could be done to fight for the user.</p><p>The cool thing about being the stragglers in a race is there is little to lose and tons to gain. Any success you achieve can be seen as a success for enterprise designers around the world! It’s pretty exciting to have that potential to elevate the reputation of a whole area of design.</p><p>I hope you enjoyed this piece. I love my current role as a UX designer for Enterprise IT solutions and just wanted to share some of the reasons why. However, that is not to say I don’t want to learn more about consumer UX (or other types of design!). <strong>Design for all products/services is amazing</strong> and each comes with its own set of challenges and rewards.</p><p>Most of what I wrote here are reflections of my personal experiences. Feel free to let me know if you have any feedback!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*8f6Ii6IkikO1X2XD" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210dd9cff968" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/enterprise-ux-is-amazing-change-my-mind-210dd9cff968">Enterprise UX is amazing. Change my mind.</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>