<?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 Kalen Wong on Medium]]></title>
        <description><![CDATA[Stories by Kalen Wong on Medium]]></description>
        <link>https://medium.com/@yellowcurry?source=rss-b135835194a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*YtOzIOtFPr3buov5mybWnw.png</url>
            <title>Stories by Kalen Wong on Medium</title>
            <link>https://medium.com/@yellowcurry?source=rss-b135835194a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:46:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yellowcurry/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[Feedback That Adds Color to UX Designers Lives]]></title>
            <link>https://medium.com/disfordesign/feedback-that-adds-color-to-ux-designers-lives-14cf01a170ea?source=rss-b135835194a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/14cf01a170ea</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-feedback]]></category>
            <category><![CDATA[design-critique]]></category>
            <dc:creator><![CDATA[Kalen Wong]]></dc:creator>
            <pubDate>Sun, 17 May 2020 20:46:21 GMT</pubDate>
            <atom:updated>2020-05-17T20:46:21.911Z</atom:updated>
            <content:encoded><![CDATA[<p>As an artist and UX designer, human behaviors and psychology fascinate me. I’m especially interested in how people communicate their needs and expectations to others. One way I explore this is by asking people to share highlights of their jobs. Once, a hair stylist gave this example of a typical dialogue with his customers:</p><blockquote>Stylist: “So, how would you like your haircut today?”</blockquote><blockquote>Customer: “Hmmm… not too long and not too short, you know?”</blockquote><p>UX designers, particularly in the enterprise space, receive a good volume of feedback and requests from non-design disciplines. Sometimes these spark inspiration, other times you really wish you had a magic wand. For example, it is not uncommon to be asked to design a data table that’s packed with a world of information, yet it’s essential that it is readable, scalable, mobile-friendly, and after all, accessibility-compliant.</p><p>A good sense of humor helps me get through tough days. Here are some quotes I have collected over time and my responses to them, followed by some general tips.</p><h3>“I like blue (as our app color), it is neutral.”</h3><h4>Initial reaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nfo0MeWdGx0iKX31f_aoUg.png" /></figure><h4>Actual response</h4><p>“It’s true that blue does appeal to quite a group of audiences, particularly in many business applications scenarios, which makes it a good color option to explore.”</p><h3>“We shouldn’t ask people what they want. Didn’t they say people don’t know what they want until you show them?”</h3><p>(Regarding building feature without user research)</p><h4>Initial reaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Cwa99xcYks3A3jWxcwPlQ.png" /></figure><h4>Actual response</h4><p>Yes, the quote does inspire many of us to rethink how a question could be reframed without invalidating the importance of user research.</p><p>An understanding of human needs is the foundation of any product innovation, and user research helps us learn this at a deeper level. User researchers are investigators trained to uncover areas that might not be apparent, or have otherwise been overlooked. Whether any designs or prototypes will be used for tests are dependent on the research method being used. A usability test is commonly used to challenge assumptions and identify potential issues in the design, but it does not tell us why a person feels a certain way and what motivates them.</p><h3>There’s a lot of wasted white space. Can we…?</h3><h4>Initial reaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-H0aXrD8yjjeJsUBIbyNDA.png" /></figure><h4>Actual response</h4><p>Designers use white space for many good reasons, such as to help establish an information hierarchy and the relationships between visual elements. In applications with dense data in particular where users are expected to quickly grasp lots of competing information, a good balance of white space will help them navigate, focus, and prioritize. This breathing space is also proven to reduce eye strain, improve readability and comprehension.</p><h3>“Don’t copy (the competitor’s work), but we want similar. You know, same but different.”</h3><h4>Initial reaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Kwfu5kHYtMHVWxm1tBXWw.png" /></figure><h4>Actual response</h4><p>Thank you for providing the reference. What are our common areas, such as product direction, target users and customer scenarios? From these, do you think we can learn from the competitors’ products? And what are some competitive advantages and differentiators of ours we should highlight?</p><h3>“Apple/Facebook/Google is doing this.”</h3><h4>Initial reaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E4K3mC98BR9m2XFPS5fIkw.png" /></figure><h4>Actual response</h4><p>That’s a good point of reference. Would you mind sharing what you think their success factors might be that we can learn from? Especially if they have solved the exact problem we are having, and that data supports the resolution. Can you elaborate more and provide more evidence if and when you have them?</p><h3><strong>Practice Exercises:</strong></h3><p>Here are a few other examples I’ve encountered; try paying attention to your initial reaction when reading them, and then see how you might respond so that it builds a complimentary, rather than confrontational, relationship with your partners.</p><blockquote>Designer: “What’s the user story/scenario?” PM: “The user wants to see this feature in the UI.”</blockquote><blockquote>“It is boring, can we add more icons/colors?”</blockquote><blockquote>“If I can make wireframes, I don’t need you guys.”</blockquote><h3><strong>Tips on responding to design feedback</strong></h3><p>Handling feedback well takes skills and practice. The following are some tips for designers based on my personal experience:</p><p><strong>Acknowledge with an open heart</strong> — Whether the feedback comes from pure gut feelings or as part of a work agenda is less important; what matters is that you acknowledge diverse opinions, value different point-of-views, and can empathize with their unique situations. Accept the feedback with an open mind and heart, and thank the person who offers it.</p><p><strong>Focus on relevant facts and what’s possible</strong> — In UX, we understand facts speak volume, but not all facts given to you are relevant to the contexts at hand. For example, a design can be very successful for a consumer whose goal is to subscribe to a music channel, but it might be totally inapplicable for a data scientist who needs to analyze a prediction model. Help direct the conversation by focusing on what’s contextually relevant and possible.</p><p><strong>Ask for clarification and seek to understand </strong>— Don’t be afraid to ask clarifying questions and specifics, as both parties can learn in this information exchange. Display your ability to listen and your intention to understand, but be careful not to come across as questioning their motives. For instance, instead of “What do you mean by wasted space?”, try “By wasted space, do you mean we can purpose that area for something else? What features do you have in mind? We can brainstorm some ideas.” By helping others elaborate their point, you help both succeed.</p><p><strong>Inspiring, not defending </strong>— Though defending design is one of our required skill sets, designers can benefit from treating every negative feedback as a seed of inspiration, rather than a disagreement that needs mitigation. This is because every feedback points to a human reaction to an experience. And while this emotional response may not apply to your current design, it can be a good reference point for the future. Think to yourself, when the same brand is being repeatedly referenced as a design gold standard, what does it really mean and what can you learn from it? To take this even further, try turning a reaction to feedback into an open conversation that stimulates more inspirations.</p><p><strong>Final thoughts</strong></p><p>The nature of iterative design means we will never run short in feedback intake. As designers, we often feel like we’re being put on the spot, and have to give the world an answer. This is not the case. Designing alongside with many different disciplines only means we have more opportunities to see from other point-of-views before the product hits the market. Remember, that every feedback has a good seed, and nurturing these seeds will only help us grow. Enjoy the ride, and have some fun along the way!</p><p>Editor: Heather Thompson</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14cf01a170ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/disfordesign/feedback-that-adds-color-to-ux-designers-lives-14cf01a170ea">Feedback That Adds Color to UX Designers Lives</a> was originally published in <a href="https://medium.com/disfordesign">D is for Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Desirable traits of UX designers in the Enterprise space]]></title>
            <link>https://medium.com/disfordesign/desirable-traits-of-ux-designers-in-the-enterprise-space-6af3b89ea6da?source=rss-b135835194a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6af3b89ea6da</guid>
            <category><![CDATA[ux-designer-soft-skills]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[enterprise-ux]]></category>
            <dc:creator><![CDATA[Kalen Wong]]></dc:creator>
            <pubDate>Thu, 06 Feb 2020 23:13:41 GMT</pubDate>
            <atom:updated>2020-02-11T21:23:14.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BYNbatjZxypyH0XoZfCLTg.png" /><figcaption>Photo by <a href="https://unsplash.com/@youxventures?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">You X Ventures</a> on <a href="https://unsplash.com/s/photos/design-team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplas</a>h</figcaption></figure><p>Designing at organizations developing enterprise applications requires an enhanced set of qualities and skills to be the most successful. A design education might prepare you with the necessary marketable hard skills, but strengthening your soft skills will better position you for more opportunities and on-going growth. I’ve seen the good and the bad, as well as experienced the ups and downs, and have found the following three traits to be valuable in navigating this complex yet fun workspace.</p><h3>Proactivity</h3><p>Proactivity — the ability to look ahead, anticipate, learn from, and apply the knowledge going forward — is critical. This is particularly true in the enterprise UX design space where there are always more problems than designers can solve. However, I’m not referring to the ability to seek ways to further improve the UI and UX. I am referring to the ability to look beyond the art board and identify opportunities that further benefit the broader team and the business.</p><p>Let’s walk through an example. Say you are tasked to design an app experience. You followed best design and research practices, covered user scenarios &amp; exceptions, turned in your deliverables, and then the product ships. Project can be closed, yeah? It depends.</p><p>If you simply want the project experience or a piece to add to your portfolio, yes. But if you want to grow your design impact and influence, it’s important to reflect on the entire process. Ask yourself, “What went wrong? Did the tool break, were any guidelines missing? What went right but could have been better?” Then come up with a plan on how to improve them. Suggestions include capturing in a wiki article what you learned and/or going back to your partners to foster a better relationship. There are plenty of opportunities for a designer, but to be an expert designer, your goal is to never stop improving so you can continue to make contributions outside your art boards.</p><h3>Positivity</h3><p>Designers can get discouraged from frequent setbacks and rejections, but we need to know that engineers and partners look to us to create the best possible user experience. Since this is about designing emotion, we can’t create a positive outcome if we aren’t in the right state of mind from the start.</p><p>A designer with a positive mindset <strong>sees the potential in and through every problem</strong>, and can guide others by sharing their design vision along with offering design solutions.</p><p>But how do we put ourselves into a positive mindset when everything seems broken? Consider these truths as you explore your own solutions:</p><ul><li><strong>Designing enterprise UX is a marathon</strong>,<strong> </strong>not a sprint, and your deliverable is NOT the finish line. Your goal goes way beyond delivering that pristine mockup. Your goal is to keep iterating, keep moving forward by offering solutions of different shapes or forms that dance with the rhythm of business.</li><li><strong>It is NOT about you</strong>. Rejection is hard only if you are fixated on a particular design outcome. Criticism is difficult to swallow only if you don’t realize that design is the result of collective effort, especially in the enterprise space. It is not a reflection on you if your designs aren’t shipped.</li><li><strong>It IS about you</strong>. Yes, it is also about you after all. In the grand scheme of things, you are the one that people care to work and establish relationships with. Your positive energy is the key to success, and makes a world of difference.</li></ul><p>As design discipline continues to gain impact and influence in engineering organizations, a designer’s role in exuding positivity does not only foster collaboration, it helps to build stronger, more successful teams.</p><h3>Humbleness</h3><p>Arrogance stems from immaturity, insecurity, and a lack of experience. Arrogant designers build walls with partners while humble designers build long-lasting collaborative relationships.</p><p>Here are some characteristics of humble designers:</p><ul><li><strong>They listen with intent </strong>— Designers who are comfortable with their skills also recognize their own limitations. They seek and receive feedback with an open mind and demonstrate a thoughtful response.</li><li><strong>They treat everyone with respect </strong>— they understand engineering might have conflicting priorities, and strive towards a balanced outcome, e.g. between delivering in the short-term and aligning with the long term design vision.</li><li><strong>They appreciate teamwork</strong> — they acknowledge the contribution of others and celebrate the group’s success.</li></ul><p>Designing is leading, and humbleness is an important trait of a leader. A good way to see humbleness in action, is to observe the behaviors of leaders who inspire us and earn our respect. A quote from Lao Tzu:</p><blockquote><em>“To lead the people, walk behind them.”</em></blockquote><h3>Conclusion</h3><p>In the enterprise UX design environment, we have many opportunities to grow beyond just learning hard design skills. The scale and impact of the enterprise space challenges us to see from new perspectives and exercise different sets of soft skills. Proactivity expands our horizons, positivity builds a collaborative team, and humbleness makes us better leaders. While these three traits are by no means representative of the only important qualities of a UX designer, they will surely go a long way to pave a long-term, successful career.</p><p>Editor: Heather Thompson</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6af3b89ea6da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/disfordesign/desirable-traits-of-ux-designers-in-the-enterprise-space-6af3b89ea6da">Desirable traits of UX designers in the Enterprise space</a> was originally published in <a href="https://medium.com/disfordesign">D is for Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX design in and for enterprise — best practices for new designers]]></title>
            <link>https://medium.com/@yellowcurry/ux-design-in-and-for-enterprise-best-practices-for-new-designers-75f381e99bf0?source=rss-b135835194a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/75f381e99bf0</guid>
            <category><![CDATA[ux-careers]]></category>
            <category><![CDATA[enterprise-software]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Kalen Wong]]></dc:creator>
            <pubDate>Sun, 04 Feb 2018 06:40:31 GMT</pubDate>
            <atom:updated>2020-02-06T23:29:57.713Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Tips for new UX designers designing complex applications in the enterprise world.</strong></h4><p>Our team designs a cloud infrastructure platform for experts who manage the world’s largest data centers. Once, a junior designer a couple of months into her job came proposing a color change to our standard notification message. Not wanting to limit her creativity, I responded, “Good idea, but how about we first focus on helping users to achieve X?” Another time she enthusiastically suggested that we apply new animation to the indicators. “I think these will add delight to the users!” Acknowledging her enthusiasm, I said, “Yes, but not if we have not helped them accomplish their goal.”</p><p>I have been there, excited about the design possibilities but suggestions resulting in rejection after rejection. I blamed the system’s limitations and processes, without realizing that designing at scale is a different game. It requires different skill sets and expectations to succeed.</p><p>In the hope of helping designers who are new to this domain, I am sharing some insights I have learned over the years of working in similar capacities.</p><p><strong>“Customer delight” carries a different meaning</strong></p><p>Let’s take a moment and understand who are these enterprise users. Many of these applications serve people at their jobs. Applications are the tools they use, often 8 hours a day. They are NOT the users who swipe pictures for their next hot date, nor walk around catching Pokémon. In my case of designing for highly skilled experts, they use the products under pressure. Something is at risk if tasks are not performed precisely right. “Delight”, therefore, often means getting a job done without hiccups, or being able to recover from errors. These users will thank you for alerting them about anything they need to pay attention to without missing a beat.</p><p>Does this justify deprioritizing visual or motion design? No, what I am suggesting is raising awareness of what delight means to an enterprise user as opposed to a consumer, using this awareness to guide us in better directions and help prioritize deliverables.</p><p><strong>Caution using consistency for consistency-sake</strong></p><p>Consistency is important to make users feel a sense of familiarity, and it helps optimize system performance. However, applying without caution in enterprise design can lead to risk of user errors. For example, the more familiar a user is with a layout or pattern, the more likely s/he acts based on procedural memory. In enterprise or business applications, it is common to see a myriad of workflows that look and behave similarly but serve entirely different functions. Again, in many cases users use these tools for long hours, and their goal is to get things done without error. Any risks of user error warrants usability tests be conducted and design be reevaluated.</p><p>Fear of getting resistance running usability tests? Remember an expert user’s error is very costly to a company (perhaps more than a consumer app user’s where an one-off monetary compensation can apply), and errors might not be easily reversible. Leverage this when presenting the need for testing, and design alternatives that acknowledge consistency as a tradeoff.</p><p><strong>Different application of creativity</strong></p><p>Designers who come from consumer applications design or a startup environment often feel constrained. The general perception is that the enterprise application designs lack creativity and the development is slow due to people and processes.</p><p>What is creativity? It is our ability to transcend what we can imagine, and to turn things around. Creativity is “medium-agnostic”. We will be limiting ourselves if we can’t see design beyond a physical or digital product. As a designer within a larger ecosystem, you will soon realize the need to design processes and solutions around your work where you apply creativity differently and it returns different outcomes. The outcomes may be less tangible compared to a portfolio piece, but they provide invaluable experience for your career growth.</p><p>While I am not defending bad processes and inefficiencies, I am encouraging you to seek to understand before jumping to conclusions. Ask yourself, why do things seem slow? Slow as compared to what? Are project scale and user impact driving the needs for processes and people and do I have alternative solutions? I know this very much sounds like the concerns of a program manager, but a designer in our space does inherently require you to share the mindsets of many others. This leads to my next point.</p><p><strong>Empathy beyond users</strong></p><p>Human-Centered Design schools taught us to put users in the center and practice empathy for users. Great, but far from sufficient. Your success in designing for enterprise requires strong collaboration with many others. Therefore it is important to practice empathy for everyone you work with. Empathy breeds empathy. The more you you listen to everyone with intent, and to make an effort to acknowledge their needs, the more likely your design voice will be heard as well.</p><p>It also helps to think that not only are we designing products, we are simultaneously designing the world around us. We are designing for humans <em>with</em> humans. Have we put ourselves in the shoes of our developers, program managers, and stakeholders like we do with our users? Did we deliver to everyone — including ourselves — the best experience possible?</p><p><strong>Speaking your company’s research language</strong></p><p>To deliver design successfully at scale, it is often required that you influence teams of people and get them on the same boat. It is a very difficult but critical task. In addition to extending empathy to your partners as suggested above, we need research to support our design. Note that I am not only referring to presenting your design with data, I am referring to presenting the right type of data and research that your company values and practices. For example, online travel or shopping websites lean towards using A/B testing as their primary design evaluation tool. In that case, numbers constitute your common language. In the case of enterprise or business applications design, where there may be a heavier emphasis on qualitative research, user feedback or behavior is your primary language. Of course, ideally we will have data sources and types to support our design, but an awareness of which data type to highlight in your conversation still applies. Targeting your audience by speaking a common language and sharing common values will help you get the rapport you need to deliver your design.</p><p><strong>Final words</strong></p><p>Designing enterprise applications within a large organization is a speciality. It requires special skill sets and mindsets to succeed. It challenges us to design beyond digital mediums and to apply a broader category of people skills. It is an area that takes time and some reflection to appreciate, but the benefit is long-term. We benefit from the unique constraints and complexities that push our creativity to a new height, and a chance to impact both the users and the community at large. I am not suggesting one design environment or product type over another, I am suggesting that new designers put on a new lens, to apply human-centered design concepts creatively, and to be open to new skills and perspectives.</p><p>Editor: Pedrito Maynard-Zhang</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75f381e99bf0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>