<?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 Hollie Phillips on Medium]]></title>
        <description><![CDATA[Stories by Hollie Phillips on Medium]]></description>
        <link>https://medium.com/@hphillips.ux?source=rss-e2c7cfb60db7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I_H3m5aZfw7m3VgEEsM0xw.jpeg</url>
            <title>Stories by Hollie Phillips on Medium</title>
            <link>https://medium.com/@hphillips.ux?source=rss-e2c7cfb60db7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:12:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hphillips.ux/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[The Impossible Job Demands of UX Design]]></title>
            <link>https://uxplanet.org/the-impossible-job-demands-of-ux-design-8e96e612b997?source=rss-e2c7cfb60db7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e96e612b997</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-careers]]></category>
            <category><![CDATA[ux-jobs]]></category>
            <dc:creator><![CDATA[Hollie Phillips]]></dc:creator>
            <pubDate>Wed, 12 Jun 2019 15:48:51 GMT</pubDate>
            <atom:updated>2019-06-12T15:48:51.323Z</atom:updated>
            <content:encoded><![CDATA[<h4>And How to Deliver On Them</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ObIOipWJcY86iE-bBCZ7Sg.png" /><figcaption>Based on business vector created by <a href="https://www.freepik.com/free-photos-vectors/business">freepik — www.freepik.com</a></figcaption></figure><p>On first read (and probably second and third too) this will appear to be quite a daunting list — one full of paradoxes and contradictions. How can one (and the same) person possibly hope to meet these requirements? Imagine the following section headings as excerpts from an <em>honest</em> job description.</p><p><strong><em>“Candidate must be:”</em></strong></p><h3>Both a Strategic and a Tactical Thinker</h3><p>It’s “big picture” vs. “small picture;” a “20,000 ft. view” vs. being “in the weeds”…There are many apt phrases to describe this difference in perspective, and most people have a preference. However, as a user experience designer (and this is actually the <em>best-case scenario</em>, as I’ve described <a href="https://uxplanet.org/ux-will-happen-anyway-tactics-vs-strategy-76c52d0ed25b">what the worst can look like</a>), you won’t often get the luxury of choosing your operational elevation; one day you’re designing a discrete form interaction, and the next, you’re creating entire user journeys for your company’s product offering. The shift can get dizzying. The upshot is that the special kind of personality that appreciates this variety would also be hard pressed to choose one vantage point over the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOG69fYzvSEPIwcg7fYPhA.png" /><figcaption>What’s your preferred vantage point? (Based on vectors created by <a href="https://www.freepik.com/free-photos-vectors/chess">freepik — www.freepik.com</a>)</figcaption></figure><h4>How to Deliver</h4><p>The good news is, strategy and tactics come baked into a mature UX design process. That means that you <em>need</em> a mature UX design process. Read more about <a href="https://uxplanet.org/ux-will-happen-anyway-tactics-vs-strategy-76c52d0ed25b">what that looks like</a>.</p><h3>A Generalist AND a Specialist</h3><p>This juxtaposition is similar to the “big vs. small picture” perspective, and applies especially, though not exclusively, to UX professionals in a senior or management role. It’s an understatement to say the field of user experience design is broad; imagine maintaining working familiarity with every aspect of it. Further, if part of a small team, you certainly won’t always have the capacity to delegate all the work to others. You’ll still have to occasionally get your hands dirty, all while staying up-to-date on all of the disciplines for which your team is responsible.</p><h4>How to Deliver</h4><p>Unfortunately, proficiency with the minutiae and managing that minutiae comes mostly by experience. There are only shortcuts insofar as there are shortcuts with learning something new. In a way, being on a small or one-person team is the shortest path to becoming proficient in many areas of UX design, as well as learning how all the pieces come together. In the event you are silo-ed in your function as part of a larger team, build your UX design muscles with online video courses, UX resources, and of course, by shadowing team members.</p><h3>Equal Parts “Right-brain” and “Left-brain”</h3><p>Although modern psychology has <a href="https://www.verywellmind.com/left-brain-vs-right-brain-2795005">debunked the mythos</a> of each hemisphere having primary domain over either “logical” or “creative” characteristics (the whole thing works together), the “left/right brain” metaphor is still useful in describing those who lean more toward their visually creative “side” versus those who are decidedly more analytical. Regardless, how the brain is <em>actually</em> wired matters little to the UXer, who must constantly straddle the divide between being an artist and being a scientist. It won’t be enough to simply be a designer (as many of us start out); the job will demand that you marry the artsy, emotive aspect of your personality with a rational, analytical one. This is vital to the creative problem-solving that is required daily. After all, both the form (aesthetics) and the function (organization, interactions) of a website or app will determine its success — or lack thereof.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*K1Nla4ZuMilfXC7WB0HWtg.png" /><figcaption>Instead of wondering whether a brain is creative or logical (it’s both), we could examine individual strengths — and an individual can be both. (School vector created by <a href="https://www.freepik.com/free-photos-vectors/school">freepik — www.freepik.com</a>)</figcaption></figure><h4>How to Deliver</h4><p>This one is a bit trickier. It’s hard to completely disregard one’s natural abilities. However, one is always at liberty to further develop<em> </em>existing abilities or even to cultivate new ones. I’m no neuroscientist, but it’s apparent that at least some measure of what people are good at, and by extension, how good they will become, is determined by what they <em>prefer</em> doing. If I prefer drawing pictures to doing algebra (I suspect I may be in the majority here), and possess even a modest amount of talent, chances are good that I’ll become much better at drawing than solving equations. Does that mean I can’t also learn to solve challenging equations? The important takeaway here is the knowledge that you shouldn’t walk into a UX design career with the expectation that you will <em>only </em>be functioning in a creative capacity, and that hopefully you can embrace and develop your logical “side” — and vice versa.</p><h3>Both an Introvert and an Extrovert</h3><p><em>Introvert</em>, because you have to get work done. Seriously, you have art to create and science to perform.</p><p><em>Extrovert</em>, because getting feedback from users is essential, and because you will probably have to present your designs and findings to your team. Let’s not forget that you will probably also be a UX evangelist at some point in your career, which implies a lot of business user interface (pun intended).</p><h4>How to Deliver</h4><p>Similar to whether a person is more co-called “right-brained” or “left-brained,” each has their natural inclination. The level with which a person is comfortable with both introversion and extroversion is a function of personal and career development. Simply put, it comes with practice. The same programs that help with public speaking, for example, will come in handy with UX presentations.</p><h3>Multilingual</h3><p>Because the nature of UX design puts it in the epicenter of many disciplines, you’ll need to be a polyglot — not in the sense of standard languages and dialects — but with different jargons. You’ll not only need to be able to speak them conversationally, but with a sense of the actual meanings of terms, which implies having a certain measure of exposure, if not experience, in those different domains/industries. Examples include the language of business, the language of technology, the language of visual design, and most importantly, the lingo or jargon of the end users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbZ0X4U6iOfsMhsM6P4kQA.jpeg" /><figcaption>Background photo created by <a href="https://www.freepik.com/free-photos-vectors/background">rawpixel.com — www.freepik.com</a></figcaption></figure><h4>How to Deliver</h4><p>The best way to learn a foreign language is by submersion. Likewise, the best way to learn jargon is to associate with those outside of your domain. This contact can be a byproduct of working in a large company, or it could come by way of a “transfer” between industries, such as in the case of a programmer becoming a UX designer. It mostly requires that you have an open mind and willingness to learn, even if it means actually opening and reading that business document that was attached to that massive email thread, or learning to read a bit of code.</p><h3>Conclusion</h3><p>It’s all about balance — and experience. Most of the items included in this list are not realistic entry-level proficiencies, as much as they are ongoing objectives that will develop in parallel with your years as a UX designer. Consider them expectations, <em>of</em> you, and <em>for</em> yourself…seeds that will bloom in one of the most challenging and satisfying careers out there.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e96e612b997" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/the-impossible-job-demands-of-ux-design-8e96e612b997">The Impossible Job Demands of UX Design</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empathy by the Numbers: Breaking Down A UXD Contradiction]]></title>
            <link>https://uxplanet.org/empathy-by-the-numbers-breaking-down-a-uxd-contradiction-214a8e9d789a?source=rss-e2c7cfb60db7------2</link>
            <guid isPermaLink="false">https://medium.com/p/214a8e9d789a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[uxd]]></category>
            <dc:creator><![CDATA[Hollie Phillips]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 17:07:51 GMT</pubDate>
            <atom:updated>2019-04-15T19:55:54.717Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ckd-adza-HgKsXuSpScHiA.png" /></figure><p><em>Two foundational principles of user experience design seemingly exist in opposition to each other.</em></p><p>As I was mentally sifting through the bedrock of UX design in my continued quest to better define what it is, and uncover any nuggets of insight along the way (I have a lot of time to think on my commute through the rolling hills of Middle Tennessee, and thus the geological metaphor), it occurred to me that two core features — <em>empathy</em> and <em>data analysis </em>(specifically, of user data) — perplexingly coexist in seeming opposition to each other. And yet, here they are working together somehow as pillars of the discipline. What <em>is</em> the relationship exactly?</p><h3><strong>Empathy</strong></h3><blockquote>:the action of understanding, being aware of, being sensitive to, and vicariously experiencing the feelings, thoughts, and experience of another of either the past or present without having the feelings, thoughts, and experience fully communicated in an objectively explicit manner. <a href="https://www.merriam-webster.com/dictionary/empathy">source</a></blockquote><p>Any seasoned UXer would be hard-pressed to argue that empathy isn’t central to <a href="https://uxplanet.org/ux-will-happen-anyway-tactics-vs-strategy-76c52d0ed25b">strategic user experience design</a>. My goal as a UX designer is to understand not only who the user is, but insofar as possible, put myself in her shoes and go for a short stroll in her world — learn her day-to-day workflows, discover her primary goals as well as her pain points. I’ll learn that her work environment is too noisy and that the air conditioner is set too high (let’s be honest; it almost always is). On the surface, it’s easy to conclude that all of this is a simple <em>data</em> gathering activity, but there’s nothing simple about simulating the experience of another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y85mLojnueeP4uiyVTZLmA.png" /><figcaption>The challenging art of getting inside someone’s head… <a href="http://&lt;a href=&quot;https://www.freepik.com/free-photos-vectors/people&quot;&gt;People photo created by freepik - www.freepik.com&lt;/a&gt;">source</a></figcaption></figure><h3><strong>User Data</strong></h3><blockquote>On the best of days, I can design a solution right up to the lunatic fringe of possible scenarios — but not always.</blockquote><p>It’s equally as difficult to argue against the importance of data in the UXD process. Because I need to understand how users are interacting with my software in order to identify design features or identify problems in that interaction, for example, I’ll look at user analytics, interview customers, and conduct usability tests. I’ll look for patterns. Eventually however, the cold, dispassionate face of numbers will rear it’s head, and I will need to make a problem statement based on the likeliest scenarios supported by my data, and propose a solution, to the inevitable exclusion of an “acceptable” percentage of users. On the best of days, I can design a solution right up to the lunatic fringe of possible scenarios — but not always.</p><h3><strong>The Persona</strong></h3><blockquote>The UX researcher works their magic, just as a forensic sculptor works the clay over the spaces of an ancient skull.</blockquote><p>This data collected from a group of users using a particular set of tools tells us about behavior patterns in relation to the application. When we vary the toolset, or examine the numbers from a slightly different angle, a different dataset begins to emerge; we start to learn about the individuals. We start to scratch the surface of their hidden world. The dominant human features across this sample surface, and begin to coalesce.</p><p>The UX researcher works their magic, just as a forensic sculptor works the clay over the spaces of an ancient skull — empathy guides their hands, and covers the gaps. What forms is a face, an archetype supported by a framework of numbers: the <em>persona</em>. Empathy has uncovered hidden insights in the data, resulting in an image of not only a group of people, but of an individual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8yutshO_21AlHjit85Bs7Q.jpeg" /><figcaption>This particular persona probably liked to see her own name (and titles). <a href="https://upload.wikimedia.org/wikipedia/commons/6/69/Judith_of_Thuringia_-_forensic_facial_reconstruction_-_infograph.jpg">source</a></figcaption></figure><p>Throughout this process empathy has served as data gathering tool, as a data analysis tool, and finally as a sculpting (design) tool.</p><p>Philosophical considerations aside, what does all of this mean practically?</p><h3><strong>Empathy as a Data Gathering Tool</strong></h3><blockquote>Maybe eventually someone will invent an AI capable of empathy…but until then, it’s the UX designer’s job.</blockquote><p>There are myriad of ways to gather data, but the toolset isn’t complete without empathy, a less objective but more human approach. I can use a software solution to capture empirical data such as click-throughs, but as of the publication of this article at least, there isn’t a better approach than my senses and discernment as a human being for collecting observational data. Sure I can record a user in her environment, but I still have to analyze that footage to collect those important data points such as size of workspace, lack or preponderance of personal effects, and of course, room temperature. (In fact, for that last data point, I <em>am </em>required to be<em> </em>in the same room, as my camera doesn’t at present time capture infra-red information.)</p><p>Any time I’m gathering observational data — and wish to do so effectively — I need to employ empathy. I need to know that details such as the amount and type of personal effects is significant, because those details will reveal something to me about that person and perhaps their mindset as they interact with the software. Maybe eventually someone will invent an AI capable of empathy, enabling it to detect the significance in the human details, but until then, it’s the UX designer’s job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoJbRi3Vg1VPBZx1q_eVtw.jpeg" /><figcaption>Empathy helps uncover unexpected considerations of a persona. <a href="http://&lt;a href=&quot;https://www.freepik.com/free-photos-vectors/business&quot;&gt;Business photo created by freepik - www.freepik.com&lt;/a&gt;">source</a></figcaption></figure><h3>Empathy as an Analysis Tool</h3><blockquote>Only a human understands the frustration behind not being able to find what you’re looking for.</blockquote><p>As almost everyone in the tech industry knows by now, it’s not simply enough to gather data. It has to be organized and visualized in a meaningful way. I can get meaningful information on my user set by identifying behavioral patterns in the analytics data, but I probably can’t tease out the “why” behind those generalized behaviors; for that, I need to drill down to individuals, and I can accomplish that by examining her discreet actions in the application, either through the analytics (supposing they’ve been implemented on a discreet enough level), or through user testing sessions. A robot can identify that a user searched multiple times before making a selection; only a human understands the frustration behind not being able to find what you’re looking for.</p><h3><strong>Empathy as a Design Tool.</strong></h3><blockquote>Empathy is especially important when I’m designing an interaction for which there is no immediately discoverable precedent</blockquote><p>Thus far, we’ve talked about empathy as a way of understanding and analyzing; here’s the part where the concept presents itself more as an art than a science. No doubt the industry’s collective experience provides the UX designer guidance even in this by way of common design patterns, best practices, established mental models. However, no amount of experiences can account for every unique persona and use case that will ever arise. There will always be gaps in the data, and general unknowns.</p><p>Here it becomes vital that the designer connect with that persona in order to complete its model based on the context of what <em>is</em> known. This is especially important when I’m designing an interaction for which there is no immediately discoverable precedent (as often occurs in highly complex, proprietary software). Although there may be multiple ways I can conceive of for the user to accomplish the same task, eventually I’ll have to choose one based on what my gut tells me this user will find the most intuitive and/or least disruptive. Ideally in these situations, I can later confirm (or invalidate) my choice with the addition of user testing data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*FFWLYKcLdlU2Le7kU4gCxA.jpeg" /><figcaption>Assuming the destination is the same, sometimes it’s not obvious down which path to send the user.</figcaption></figure><p>Another example of designing empathetically is the ever-increasingly relevant design trend, personalization. There’s really no pragmatic reason for greeting a user by name upon login, but I know I would feel better about the whole experience if it were me seeing my own name.</p><h3><strong>Conclusion</strong></h3><p>Empathy can be a feeling or an understanding. In the domain of user experience design, it’s the ability to comprehend both the qualitative <em>and</em> quantitative insights provided by the data, resulting in a persona. It is the uniquely human perspective that plays a role in user research and UI design, not in opposition to, but cooperatively with, the numbers — just another of the many balances between the heart and the head that is required by the profession.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*hca-18nraWN-BW1_49EKtw.jpeg" /><figcaption>It’s a walk the UX designer is accustomed to taking. <a href="https://dg19s6hp6ufoh.cloudfront.net/pictures/613043430/large/photo.jpeg?1468263666">source</a></figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=214a8e9d789a" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/empathy-by-the-numbers-breaking-down-a-uxd-contradiction-214a8e9d789a">Empathy by the Numbers: Breaking Down A UXD Contradiction</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Will Happen Anyway: Tactics vs. Strategy]]></title>
            <link>https://uxplanet.org/ux-will-happen-anyway-tactics-vs-strategy-76c52d0ed25b?source=rss-e2c7cfb60db7------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c52d0ed25b</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[uxd]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hollie Phillips]]></dc:creator>
            <pubDate>Fri, 01 Mar 2019 17:22:34 GMT</pubDate>
            <atom:updated>2019-03-01T18:46:46.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wrggIdpSS_E3JbRkLYet7Q.png" /><figcaption><a href="http://www.freepik.com/free-photos-vectors/abstract">Source</a></figcaption></figure><p>Some time ago, as I solidified my role as a UX designer, and focused most of my efforts on all the user-centered design deliverables that entailed, I still found myself with a healthy helping of UI design tasks. So I continued producing visual design and interaction on a small-scale, reactive basis, according to the needs of the development team. It turns out, this wasn’t a bad thing, as the crafting of the user experience doesn’t end with flow charts and wireframes, and inevitably unplanned feature requests will happen. I began to refer to these activities as “tactical UX design,” as a thing not <em>apart from</em>, but <em>part of</em> the overall UXD workflow.</p><h3><strong>Tactical UXD</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*7sT0JttierfJnU7Y9tiJRw.png" /></figure><p><strong>What It Is</strong></p><p>Tactical UXD is the day-to-day UI design that is necessary before and during product development. It presents in the form of small feature requests and unplanned enhancements, such as bug fixes or critical missed requirements. “Tactical UXD” <em>is</em> largely analogous to “UI design,” except for the “UX” component of the term, which implies a greater role in a larger strategic picture; it’s a discipline that doesn’t get enough love in terms of overall importance in relationship to other user experience design components. (The fact that UI design is often mistaken for UX design doesn’t address that gap; rather that’s a misunderstanding with tomes of analysis and frustration already dedicated to the topic.)</p><p>Because my job responsibilities as a UX designer at a small organization still included UI design, when I wore my “UI designer” hat, the <em>user-centric</em> gears still turned. When I collaborated with developers on active tickets, I was mindful to do so in a way that ensured that those new feature designs took into account the context of the user we were building them for. Even for these small features, I still wanted to understand “for whom am I designing?” and “what problem does it solve?”</p><p>Strictly speaking, someone in a UI design role may sometimes have the luxury (or misfortune, depending on the individual) of focusing only on the necessary design and interaction that is requested of her, through requirement documentation or development tickets. However, even with these smaller enhancements, context is a big benefit to designer and end-user alike, and should not be ignored.</p><p>If more upstream user research and data isn’t readily available, it’s still helpful to question the requirements in order to understand their value to the end-user. Hopefully, these requests can be understood in the broader context of a product for which more user information <em>is</em> available. If a full UXD process is in place, the UI designer can refer to the personas for that product and apply them to one-off requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQtkWNRFfwaQTHfc2OIvdg.png" /><figcaption>A new take on the old iceberg. Based on vectors by <a href="https://www.freepik.com/free-photos-vectors/water">vvstudio</a></figcaption></figure><p>Since a UI designer plays an important role in the tactical execution of a UXD strategy and should strive to integrate into it as much as possible, where should she draw the line with involvement? On the ubiquitous “UX Iceberg” visualization (which is, in turn, is just a friendlier visual metaphor for the Jesse James Garrett <a href="http://www.jjg.net/elements/pdf/elements.pdf">diagram</a>) UI design is often equated with the “Surface” component. However, in my experience, I have met few UI designers whose responsibilities, in practice, were limited to “visual design” (VizD). There’s usually more than a little interaction design (IxD), sometimes information architecture (IA), and if she knows what’s good for her (and she can get away with it) a little user research — if she is not <em>also</em> the front-end developer, that is! The line is already blurred, so let’s call it something else: tactical UXD.</p><p><strong>What It Isn’t</strong></p><p>If tactical UX is not <em>simply</em> visual design done in a vacuum, it is <strong>not at all</strong> a substitute for a full user experience design process, even if for many years (and still in many companies) “UX” is still equated with “UI.” In these environments, deliberate user experience <em>design</em> is neglected until so late in the process that it often falls to the UI designer — or the front-end developer, as often no distinction is even made between those two roles. It’s no surprise that development teams and recruiters began to combine these responsibilities into one-and-the-same position, a contributing factor as to why so many “converted” UX designers actually cut their teeth in programming. Many picked up on the fact that being handed a directive to design from already completed requirements, with no customer context, on top of the already immense responsibility of coding, resulted in a lot of missed-marks, shelf-ware, and just generally bad UIs. (I’ve dedicated a separate <a href="https://uxplanet.org/why-you-might-be-set-up-for-failure-in-your-ux-position-3071e4f9b84c">article</a> to the topic).</p><h3><strong>Strategic UXD</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*tvnDiepGdSYoe0AUgJy_DQ.png" /></figure><p><strong>UX Will Happen Anyway</strong></p><p>Strategic UXD is the user experience design process when executed in a <em>deliberate</em> and <em>user-centric manner</em>, from ideation to launch. Just as tactical UXD is somewhat analogous to UI design, “strategic user experience design” seems synonymous with “user experience design” itself — nearly a circular definition in fact — until one pauses to consider that user experience “designs” occur naturally as a by-product of any product design process, regardless of whether anyone is guiding that process. Users are sure to have <em>some sort </em>of experience, and chances are very high that a thoughtless or ill-fashioned experience will be a bad one. Thus, there is “user experience design,” and there is “Strategic User Experience Design.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NWtA6xISiGq2NxY_yQHe1g.png" /><figcaption>Wild, untamed UX in their native environment. Ride at your own peril. <a href="http://www.freepik.com/free-photos-vectors/nature">Vector source</a></figcaption></figure><p><strong>Tactics as Strategic Component</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*QqGsgc_A7CVeoZ0V7eyu2A.png" /></figure><p>Strategic UXD is equivalent to deliberate UXD, and it also <em>incorporates</em> tactical UXD. This is because a successful strategy relies upon a successful execution. Think of it like a river flowing down a mountain: the whole body of water is named “UXD Strategy.” (I know, weird name for a river, but bear with me.) Some tributaries lie upstream, while others feed in downstream, though all of them are contributing to this river. Similarly, there may be a division of contributing roles upstream (product vision, user research) vs. downstream (interaction and visual design), but each player is conscientiously contributing to the overall UX strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83fcKsDTtTst98232pSZYg.png" /></figure><h4><strong>Product Management: Strategic UXD’s Older Supportive Brother</strong></h4><p>Another consideration is the role that product management plays in the success of a UXD strategy. This topic is gaining considerable momentum as professionals in both domains recognize the interconnectedness. Many of the upstream UXD activities are either dependent on product management processes, or are one-and-the-same. For example, product managers are well positioned to develop personas. Then of course, there is the simple fact that a positive user experience ultimately depends on whether the business goals are aligned with user needs, something only product managers and business owners can ensure at a product’s early stages (though the UX designer can and should offer input and research data).</p><h3><strong>Potential Points of Failure</strong></h3><p>1. Obviously, if there IS no UXD strategy in place, the user experience will evolve in a happenstance fashion, either by non-UX individuals upstream, or an ill-equipped UI designer/front-end developer at the end of the process.</p><p>2. There <em>are</em> designated individuals responsible for each phase of the UXD, but for whatever reason, they are not communicating (different departments, bureaucracy, etc.). For example, the personas and scenarios developed by a product manager never flow downstream into the UI designer’s hands.</p><h3><strong>Conclusion: Strategic UXD = Good UXD</strong></h3><p>Strategic UXD is simply conscientious, deliberate UX design, which includes curious, competent UI designers, their UX counterparts, and anyone else who is contributing to the Strategic UX stream. Failure to recognize this results in unpredictable experience design results, usually at the cost of the end-user.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c52d0ed25b" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/ux-will-happen-anyway-tactics-vs-strategy-76c52d0ed25b">UX Will Happen Anyway: Tactics vs. Strategy</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Might Be Set Up for Failure in Your UX Position]]></title>
            <link>https://uxplanet.org/why-you-might-be-set-up-for-failure-in-your-ux-position-3071e4f9b84c?source=rss-e2c7cfb60db7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3071e4f9b84c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[uxd]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-design-process]]></category>
            <dc:creator><![CDATA[Hollie Phillips]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 17:16:14 GMT</pubDate>
            <atom:updated>2019-01-28T17:16:14.248Z</atom:updated>
            <content:encoded><![CDATA[<p>So, you’ve just landed a new UX design job, but something is amiss. Whether this is your first gig, or many gigs into your career, you may find yourself in a particular situation that often times will prove to be incompatible with the very job responsibilities you were hired to fulfill.</p><h3><strong>UX As A Discipline</strong></h3><p>Before detailing that situation, it’s important to call a few things to mind about the nature of user experience design. Broadly speaking, UX design, or UXD, is most effective when treated as a discipline — as opposed to a single role or career path. It spans the entire product design and development process, from ideation to release, and eventually maintenance. In the ideal scenario, the user’s needs are considered at every stage of a product’s lifecycle.</p><p>Because of this broad application across processes that aim to transform an abstract idea into a “concrete,” releasable product, UXD activities can similarly be categorized into the <em>strategic</em> (abstract in scope) and the <em>tactical</em> (concrete in scope). Both kinds of activities are necessary for a successful user experience.</p><h3><strong>The Problem: Stuck in Tactical UX</strong></h3><p>With that in mind, we can delve into the details of your current situation, and begin to understand why it might be a big problem. The situation is this: your position is in the technology organization of a company, as opposed to the product, business or marketing organization. In other words, you answer to the same middle or upper management as the development teams, meaning that your organization is mainly focused on <em>tactical</em>, technology-related concerns (or else believes it is best-positioned to make choices on behalf of the user). While good UXD takes the technology aspect into account, it shouldn’t be the primary or only consideration.</p><p>When you are part of a technology organization, any change you will be able to affect on a product will be in the capacity of a UI designer, on a <em>tactical</em>-level, at the end of the production line, so to speak. You will likely not have been present in earlier discussions wherein a user was analyzed, and her needs teased out of the data — or know whether these conversations even took place at all. You won’t understand the reasoning behind the business decisions, nor will you have insight into any underlying use-cases. You will be given requirements you don’t understand, often with wireframes and interaction instructions already provided, and yet be tasked with delighting the end-user.</p><p>While it’s true that the user interface is fundamental to a digital experience, it is itself a product of the process, and its ability to delight users is only as effective as the deliberate thought and planning that went into it. By the time you have the opportunity to contribute, many hands will have — knowingly, or more likely unknowingly — already fashioned the user experience.</p><p>In this limited, <em>tactical</em> function of UI designer, as you deliver on interaction and visual design, you’ll be doing so on a reactive basis, according to the needs of the developers, who in turn are responding to requests made of them. Under more ideal circumstances, this would be a perfectly natural and expected step of the experience design process — but this part should never be a substitute for the whole.</p><p>A reasonable person may be wondering at this point why a company would be so short-sighted when it comes to the lack of a deliberate user experience design process, which would seem to indicate a general indifference to their own customers’ satisfaction. There are a myriad of reasons, but most often, said companies don’t have a mature <em>product</em> design process, and so aren’t doing the due diligence of properly researching their customers and addressing the right needs. In that context, hiring a UX designer into the technology organization makes as much sense as anything else. User experience design is an extension of core product design activities, and so is dependent upon them being at least somewhat in place (another topic for another time).</p><p>By extension, many technology-centered companies are convinced that the development organization is equipped enough to anticipate and address these customer needs, an assumption that all too often results in consumer products that are designed by programmers, and which either miss the mark with the user base, or prioritize compatibility with the current technology platform over the end-user’s experience…or both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8wmjC20yFw8Q6JqXLhb75w.png" /><figcaption>Courtesy of vectors created by rawpixel.com</figcaption></figure><h3><strong>What Now?</strong></h3><p>If you do happen to find yourself in this situation, it is neither the end of the world for you, nor for your career. I have worked in this capacity, and I have known others who were content enough to be in a similar situation. What it DOES mean is that <strong>if you are being held accountable by your employer for the full user experience, good or bad, and you are not enabled to deliver on those expectations, you are being set up for failure. </strong>Assuming you aren’t content with the circumstances, what is a UX professional to do, aside from updating her resume?</p><p>If you work for a small- to medium-sized company, your options are:</p><p><strong>A. Hunker down and just do the work. It’s a paycheck, after all.</strong></p><p><strong>B. Retroactively create the strategic user-experience deliverables</strong>, such as personas, use-cases, user flows, sitemaps, etc. — if only for your own benefit — while taking on the role of a UX evangelist.</p><p>If you work for a larger company, where Option B might be fairly problematic, you have these additional options:</p><p><strong>C. Determine whether your company is large and segmented enough that you can treat your particular branch or sector as its own small business entity</strong>; if so, proceed with Option B.</p><p><strong>D. Seek out a centralized product, business or marketing unit</strong>, and bide your time until they have a UX designer opening.</p><p><strong>Option B: Create UX Strategy</strong></p><p>For the sake of productive discussion, let’s assume you choose Option B. Here’s how you would proceed:</p><p><strong>1. Talk to others internally (leadership, management, developers, <em>everyone</em>), to learn as much as you can about the product’s end-user.</strong> If there isn’t a clear idea about who that end-user is, expect (and accept) other unusual, but equally valid answers, such as <strong>shareholders</strong> and <strong>internal stakeholders</strong>. These are all users, after all, and technically, you <strong>are</strong> solving a problem for them (another good topic for another time). Plus, you have the added benefit of having created some concrete evidence as to why you can’t please the <strong>actual</strong> end-user of the system, if you are to be held accountable. If you are displeased with the result of this research, and have an extra amount of determination and ambition, then…</p><p><strong>2. Insert yourself into as many brain-storming discussions as possible with the decision-makers.</strong> Crash meetings. Ask questions about the product. Make suggestions, and make documents that no one has really asked for, including primers on user experience. And for the sake of your success in all of this effort, <strong>find an internal advocate!</strong> This last point is key; if you can’t get anyone with influence on your side, change toward user-centered design is very unlikely, and though your battle may be a good one, it is likely futile.</p><p>If you keep asking enough “why” questions to the right people to formulate your UX self-deliverables, others are going to take interest in that documentation, see the value in what you’re doing — at which point they might just become <em>real </em>deliverables — and you can start to see UX practices permeate existing thought processes.</p><h3><strong>Conclusion</strong></h3><p>Best-case scenario: As UX design practices become implanted into your company’s culture, they could actually help to grow the company’s strategic capacity. You might end up turning decision makers into user-centered design thinkers. Eventually, management may make provisions for a product or UX design department that doesn’t answer to another internal organization, or at the very least redefine your responsibilities to include participation in the ideation and research phases. And if none of this pans out…hopefully you’ve learned something new, gained some new perspective, and can enrich your resume.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3071e4f9b84c" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/why-you-might-be-set-up-for-failure-in-your-ux-position-3071e4f9b84c">Why You Might Be Set Up for Failure in Your UX Position</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>