<?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 Eshita Gupta on Medium]]></title>
        <description><![CDATA[Stories by Eshita Gupta on Medium]]></description>
        <link>https://medium.com/@eshitagupta?source=rss-f05152fcbdba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*YO-MLvttH9FHofxzfUUoXg.jpeg</url>
            <title>Stories by Eshita Gupta on Medium</title>
            <link>https://medium.com/@eshitagupta?source=rss-f05152fcbdba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:18:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eshitagupta/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[Challenges in Enterprise UX beyond the prototype]]></title>
            <link>https://uxplanet.org/challenges-in-enterprise-ux-beyond-the-prototype-c567117d88f1?source=rss-f05152fcbdba------2</link>
            <guid isPermaLink="false">https://medium.com/p/c567117d88f1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Eshita Gupta]]></dc:creator>
            <pubDate>Sat, 02 May 2020 19:04:18 GMT</pubDate>
            <atom:updated>2022-05-05T10:49:47.828Z</atom:updated>
            <content:encoded><![CDATA[<p>Working with an enterprise business solution company, I realized, A user experience designer has to wear multiple hats, Particularly in enterprise solutions, understanding “How enterprise companies are conducting UX research and opting design process in culture.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zft2OnY47dvqQkbROZ1nsg.png" /><figcaption>Illustration by undraw</figcaption></figure><p>We look at five significant challenges that UX specialists will have the possibility to face and propose some solutions to get over them.</p><h3>1) Usually enterprise software is highly specialized and complex</h3><p>As an enterprise UX designer, we have to deal with specialized software tools that are born to support specific domains,<em> for example, Testing, Security, Development, DevOps, cloud, mainframe, etc. </em>Which is not always a favorable condition for every designer.</p><blockquote><strong><em>Solution:</em></strong><em> To overcome this challenge, </em><strong><em>Domain research </em></strong><em>can be your savior. it helps to get familiar with your product domain and will take you one step closer to the </em><strong><em>“Empathy stage”. With Domain research you can talk in a common language with engineering teams along with users/customers.</em></strong></blockquote><h3>2) Design Process into product Development life cycle</h3><p>Development and business teams work in sprints, and mostly they do not opt for the design process.</p><p>As a result, the process of user experience design has to compromise in some or other ways. Unconsciously we become a part of the deadline race.</p><blockquote><strong><em>Solution: “Design Sprint” can fix this challenge. Introduce your design sprint 1 step before starting the development sprint. Equal collaboration throughout the dev cycle is the best way to overcome this challenge.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*kEXwoHgOjszl_INgT0D_cQ.gif" /></figure><h3>3) User research culture</h3><p>Enterprise is the most profitable industry because of its customers’ relationship. However, doing regular user research is difficult for designers in an enterprise. Several causes behind this, Listing down a few of them.</p><h4>Stakeholder’s assumptions are strong:</h4><p>Product owners/stakeholders are born with the product. It is easy to assume how they use the product will be the same as the user will do. A misconception is that they think they are their users. But that is not true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*igE_vpULrjjGtUqAu4KY4Q.gif" /></figure><h4>Fear of change:</h4><p>From a business perspective, changing products is expensive. Holding a very hesitant response towards product design is a curse for user experience research. Even a one Little enhancement change has to pass through a lengthy approval channel. “Touch me not plant” would be a perfect example to understand.</p><h4>Lack of user research awareness:</h4><p>As said,<strong> </strong>Half-knowledge is dangerous. So for the inclusion of user research in the process, the cross-functional team needs to know the impact o research.</p><h4>Lack of Dedicated Budget and resources for research:</h4><p>Very few organizations hire dedicated resources for user experience research. Where it should not be optional for any product.</p><h4>Customers come with big names= Billon $$$ DEALs:</h4><p>When is user research not a part of the process, Who is going to tie the bell first?</p><p>Happy Happy path from the past 25 years of production. Release after release, sprint after sprint, but nobody is bothering about the pain of users.</p><p>For business, cracking/sustaining a deal is most important. Sometimes they keep aside the user’s concerns<em>. </em>In an established enterprise, Customer and sales advocates are usually in a good relationship since they are long time crime partners and advocate their legacy product in such a way that they convince the fact</p><blockquote>“Compromising with UX is cheaper than fixing it Until the product is not broken”</blockquote><blockquote><strong><em>Solution: User research is a culture it cannot build overnight. Cultural change needs trust and trust comes with the continuous effort of emergence. No worries start with a baby step. Nobody will set the stage for you. You have to take the lead so let’s see how to start.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*cYh4nzzlqmFjkq-hU22xag.gif" /></figure><ol><li>Make a short road map plan and share it with your stakeholders and team.</li><li>Start user research with your friends or colleagues.</li><li>Try to evolve your small research work into your design decisions.</li><li>Do not forget to document each research work. Always keep “As is” and “To be” scenarios handy with you.</li><li>Start Defending the design with research findings.</li><li>Iterate and modify the road map plan periodically.</li></ol><h3>4-Team Collaboration 🇮🇳 🇺🇸🇬🇧 🇮🇹</h3><p>There is no single person who has all the query’s answers. In these big fat enterprises, teams are scattered all over the world, and synchronizing them all together is quite a tedious task. Filling the communication gap between the team is even more significant due to two common reasons listed below.</p><p>🌐 <strong>Geolocation: </strong>Time difference and response turnaround time are substantial and responsible for changing the perception of conversation.</p><p>🌐 <strong>Tool licensing variance: </strong>Centralization, the usage of tools, is a big problem and causes understanding gaps.</p><blockquote><strong><em>Solution:</em></strong><em> In an enterprise, to come out of it you have to become a Team Player. </em><strong><em>Communication and the right attitude</em></strong><em> is the key to become a good one. </em><strong><em>Be proactive!</em></strong><em>. If you are an introvert like me, start research work over coffee with friends and colleagues.</em></blockquote><h3>5-Not Ready for Evolution</h3><p>Since the product has been used for decades, at an enterprise, most users are more product familiar than developers and designers. It is one of the reasons users are hesitant to change. Another one is sometimes technology-based software products’ users are so techie in nature that s/he don’t want simple things to use.</p><blockquote><strong><em>Solution:</em></strong><em> Break the wall. start digging small holes and make your own space. Humans are made for change. Change is the only thing that is constant. So make it happen. It is not impossible who itself saying “I-m-possible “</em></blockquote><h3>Conclusion :</h3><p>The good news for new UX Enterprise designers is that the enterprise industry has a steep learning curve. But it’s not going to start from your joining date, you have to be little patience in this industry but don’t be comfortable with the environment. The industry is ready for the experiment, so fire up your skill and be your hero.</p><h3>Thank you for reading ❤️</h3><p>Stay Creative &amp; Keep Learning — Eshita Gupta</p><h4>One clap, two claps, three claps, fifty?</h4><p>By clapping more or less, you can give me a signal of which story stands out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*AG7GnBJkRIXx88KWIUtyqQ.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c567117d88f1" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/challenges-in-enterprise-ux-beyond-the-prototype-c567117d88f1">Challenges in Enterprise UX beyond the prototype</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>