<?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 Olga F on Medium]]></title>
        <description><![CDATA[Stories by Olga F on Medium]]></description>
        <link>https://medium.com/@UXDOlga?source=rss-126731307438------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AIzGj3DJD0G78uA8lKm52Q.jpeg</url>
            <title>Stories by Olga F on Medium</title>
            <link>https://medium.com/@UXDOlga?source=rss-126731307438------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:27:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@UXDOlga/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[Has Job Hunting Changed for Designers? 0.167% Success Rate, 6 Months, 10 Lessons.]]></title>
            <link>https://medium.com/@UXDOlga/has-job-hunting-changed-for-designers-0-167-success-rate-6-months-10-lessons-7d8f5d1d8811?source=rss-126731307438------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d8f5d1d8811</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[job-hunting-tips]]></category>
            <category><![CDATA[job-search-tips]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Olga F]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 23:53:31 GMT</pubDate>
            <atom:updated>2026-01-31T23:53:31.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1W60g8oHg51oy6nHCrK7OA.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><p>Whilst on a career break which started in July 2025, I’ve applied for <strong>~600 design roles in the past 6 months</strong>. I always thought that applying for jobs is a full time job in itself. However, this time it felt the hardest in my career. In 2019 I managed to get multiple offers just in a few weeks since leaving my previous role. In 2025–2026 the end-to-end process took up to 6 months. Many factors are in play: economic and global instability forcing some companies to lower salary brackets, design market saturation and high expectations from prospective employers due to the rise of AI technologies.</p><p>In the beginning, I wasn’t picky at all applying for 20+ roles on a daily basis, and later on decided I needed to be more strategic in my choices. I’m sharing 10 key lessons which I’ve learnt through my experience and which might help my design colleagues who are on the hunt for the next role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oq1Nm6_LNr5QRdNDYGWnYQ.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 1. Career strategy</strong></h3><p>For designers who are in the beginning or in the middle of their career — <strong>be strategic in your career choices</strong>. Next time you’re looking for a role, think not just one step ahead, but 2 steps ahead. Which role would you be able to land after this one?</p><p>My project and company choices were sometimes dictated by life circumstances beyond my personal preferences, and so this time looking for the next role some companies couldn’t see what value I could add to their projects. I worked across multiple sectors, did mobile app design and web design, worked on B2C projects and B2B projects, and the only important thing for the majority was the most recent experience (i.e. last couple of years).</p><p>The times when all you needed was a design portfolio and a few successful commercial projects is gone. Now it’s the time when companies want to hire a designer who:</p><p>- truly understands their business domain because they’ve already worked in the same industry before (and, ideally, very recently);</p><p>- has worked in the same vertical (B2B or B2C or both);</p><p>- has worked in international teams which are geographically spread;</p><p>- has excellent soft skills and is able to communicate design ideas;</p><p>- constantly learns new things;</p><p>- their most recent experience more or less matches the new company. I.e. If you previously worked for a start up, other start ups will be more interested in hiring you than big organisations due to the dynamics of each type of the company;</p><p>- is closely aligned with the company’s values and culture.</p><p><strong>Tip: </strong>Pick the business domain you’re comfortable with and are curious about, and stick with it. Your career progression (if it’s something you’re interested in) will be accelerated by being consistent with the business domain choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zApn5tQcfcUU1OpZbBByCg.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 2.</strong> <strong>Competition</strong></h3><p>Reaching the wow factor during an interview has become harder due to many talented and experienced designers looking for a role at the same time as you. Sometimes, you are competing on 0.5% of difference so building up all necessary skills to succeed is something that you need to invest time in.</p><p><strong>Tip: </strong>Look around for new tools that you can utilise in the design process. Especially now, in the age of AI at the workplace continuous experimenting isn’t optional. As Jakob Nielsen’s second law of AI says: <strong><em>You won’t lose your job to AI, but to someone who uses AI better than you do</em>.</strong></p><h3><strong>Lesson 3. Applying for roles</strong></h3><p>Trust your gut when you’re reading a job description. In summer 2025 I’ve read so many job posts, and they all felt the same (as were probably generated by AI). I couldn’t tell if company A produces a different product from company B. I’ve applied for roles at times which didn’t truly appeal to me, and when I got a “Thank you for applying” rejection email, I was actually relieved. Applying for roles that you like at companies that you like is very important.</p><p>Some companies would put an optional field to submit a cover letter. Writing cover letters is not my favourite activity, however, in those cases when I actually could come up with a few meaningful paragraphs for the cover letter, I did receive an invitation for the first round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-NRbji871yYdsBW-s6HNA.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 4. Job boards and other sources</strong></h3><p>LinkedIn is a great place to look for roles but it’s not the only one. In the UK, there are other decent job boards such as <a href="https://www.reed.co.uk/">Reed</a>, <a href="https://uk.indeed.com/">Indeed</a>, <a href="https://www.totaljobs.com/">Totaljobs</a>, <a href="https://www.welcometothejungle.com/en">Welcome to the Jungle</a> to mention a few which sometimes have a different selection of roles or roles appear earlier there.</p><p>I’d like to highlight that if you are interested in the financial services sector, there’s a specialised website called <a href="https://www.efinancialcareers.co.uk/">https://www.efinancialcareers.co.uk/</a>.</p><p>Hackajob.com wasn’t massively helpful as it sent multiple and persistent irrelevant “interview requests” from companies which rejected my direct applications or sometimes it would send me roles not related to design at all.</p><p><strong>Tip:</strong> Set up daily alerts from each service, install mobile apps as sometimes the selection of the roles would be different from their web equivalent and spend a couple of hours on a daily basis to apply.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vtSjocNCFV5Bgz96mdStJA.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 5. CV</strong></h3><p>Figma is great for many things but not for designing your CV. Don’t get me wrong — it’s easy to create a beautiful summary there using styles and auto-layouts and export it into the PDF. But that PDF size will not go any lower than 1.1 MB. I’ve tried various apps to compress Figma-generated CVs, and couldn’t reduce the size down. The thing is that some internal portals where you upload your CV do not accept files larger than 1MB, in fact it has to be around 900KB on your drive to get through. A designer’s CV in Word or Google Docs isn’t something I could settle with. I did create a version in those apps but the result didn’t make me feel happy.</p><p>My solution might not be for everybody — I remembered my time in print design where I started my career, and embraced Adobe InDesign which is typically used for putting together books and magazines for print. And voilà — after exporting my CV the size of it was only 52KB. It had beautiful styles, including gradients, and the layout I was looking for. Once I got it exported, I had it on my phone and could apply for the roles while travelling on the tube or a train.</p><p><strong>Tip: </strong>ask AI to review your CV. Explain the context of the next position you’re applying to, copy and paste job spec into the AI agent, upload your CV and ask for recommendations on how to improve it. You might not agree with everything so take those tips with a grain of salt and incrementally improve your contributions for each role you had in the past.</p><h3><strong>Lesson 6. Portfolio</strong></h3><p>Making your portfolio presentable, reflecting latest UI trends, well-structured with clear outcomes for each project is something you need to invest time in. There are platforms such as Webflow and Framer which provide templates or allow you to create your own style using AI or not. However, I found that those platforms lack flexibility sometimes in terms of having different layouts per different project or interaction design. Experiment by using AI to generate code for you, and see if you can build your portfolio from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ig0_FkyJU_OfnSPHtTWqqQ.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 7. Interviews</strong></h3><p>Being interviewed and interviewing your next potential team and hiring manager is a way of meeting new people who are already established in their careers. In this round of job hunting I’ve met a lot of very nice people and strong professionals and have learnt about their experiences.</p><p><strong>Red flags to watch out for:</strong><br>- If a recruiter or a hiring manager moves your interview a few times or doesn’t show up at all, it’s not a good sign. I had experiences like that about 3 times, and the outcome was not successful. For you as a candidate it’s a sign that the hiring side cannot manage their time well, and, frankly, it’s a blessing that they didn’t hire you.</p><p>- “We have high standards here” could be a way to tell you that you are not a good fit for the role which might sound like you are not good enough. It’s just poor communication. Watch out for statements like this, be aware of your own strengths and weaknesses, and don’t take such comments close to the heart. Good feedback could sound like: “Based on the role and responsibilities we’re hiring for, we think the area for improvement is X” which gives you an actionable insight.</p><p>- If a hiring manager doesn’t like you asking too many questions or asking difficult questions, it also tells you that they won’t be happy if you do the same on the job. For me personally, it’s a huge red flag, it shows the immature state of design in the organisation as on each and every project there are multiple questions to be asked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s91R23vg7IKr1K6pPWuuhw.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 8. Interview questions</strong></h3><p>I feel that some interview questions are designed as traps. We can all prepare and give an example of how we dealt with a difficult situation on a project following a STAR method.</p><p>How do you prepare to answer informal and innocent questions such as “What are your hobbies?”. If you happen to sound more enthusiastic about a hobby rather than your work projects, the interviewer could read you as someone who doesn’t care about a role or a company you’re applying for. For me, these are two different things. Hobby is something that you do in your free time, where no one is there to judge the end result of what you’ve done (apart from yourself), while work is always about problem-solving, delivering results and satisfying needs of users and stakeholders. By definition, it would have more logic, thinking and pressure built into it.</p><p><strong>Tip: </strong>Make sure you also have 5–10 questions up your sleeve to ask every interviewer. They might answer some of your questions while they tell you about the role, expectations from the role or the company, and it will leave you with a few questions to ask at the end. Having those questions handy will give you an opportunity to learn more about the role, team structure, company culture, ways of working or anything else you’d like to know before you join. It will also present you as someone who is interested to find out more and engaged with the opportunity.</p><p><strong>Another tip: </strong>Make sure to let a hiring manager or senior stakeholders tell you about the company, even though you’ve done your own research and you have a clear understanding of the company’s services and a challenge. I made this mistake when I said that I had done my research and I was already aware of what the company did, thinking about efficiency and saving time for other questions. However, it didn’t land well as your counterpart could read as not willing to listen, not enthusiastic enough or simply self-complacent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*opsrww8KJmQ2B2XCSf5LUQ.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 9. Technical issues during the interview</strong></h3><p>Most interviews are run remotely, even though you might be expected to come in person to the office when you are hired. Make sure you’ve tested your interview set up. By that I mean:</p><ul><li>Is your face lit well enough?</li><li>Are you dressed professionally or are you wearing pyjamas or a Hawaiian shirt?</li><li>Are you in a quiet place or is there a lot of background noise?</li><li>Is your laptop charged?</li><li>Do you have a stable internet connection?</li><li>Is your microphone functioning well?</li></ul><p>Think of successful YouTube influencers. If you ever watched a tech-related video on YouTube, notice how their office or studio looks, how an influencer comes across, what they are wearing and how they speak. You want this level of presentability.</p><p>In one of my stage 2 interviews in summer my laptop got overheated due to the temperature outside and crashed (and having a lot of Figma tabs opened didn’t help the case either). I had to move to a different room, and needless to say that the flow of the conversation was interrupted. I didn’t progress to the next round.</p><p>Even though the interviews are remote, there are high expectations of you as a candidate, and being able to have a professional interview set up is important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ty53QodIP4xlL6skhfBnKw.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><h3><strong>Lesson 10. Prepare for unexpected</strong></h3><p>Sometimes companies and hiring managers will not know that they are hiring for the wrong role. I’ve observed and experienced first hand how a few companies were looking for a Lead Designer to begin with, only later realising that they actually need a Head of Design (someone with more experience in design management and in the business domain) which I wasn’t a fit for (yet). Think about your job application process as a design challenge which goes through the double-diamond phase, and be mindful that the hiring company could be in the first half of their diamond.</p><p>I’ve seen some companies looking for a designer for the last 6 months +. I’m not quite sure what their game is. However, if they are not able to fulfil the role for this long, it’s either a case of unrealistic expectations or they don’t know who they are looking for. You could deliver a project within the same timeframe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uMTnhO-EcaKVCZ47v90lJg.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><p>To sum up, if you’re applying for a senior or a lead designer role, check out the full set of elements that can make your application process successful.</p><ol><li>Start with the career strategy and think about what you want to achieve with your career.</li><li>Analyse your skillset and where you stand in terms of the competition.</li><li>Register on a variety of the job boards, install mobile apps and set up daily alerts.</li><li>Check out your CV and ask AI to review it (you’d get a lot of recommendations which will incrementally improve your CV).</li><li>Carefully read the role description and be honest with yourself if it’s a good fit for you before applying.</li><li>Put effort into designing (and if needed, re-designing) your portfolio, make it stand out among other applications.</li><li>Prepare a list of questions to a recruiter / HR partner, a hiring manager and a panel of stakeholders.</li><li>Prepare a list of scenarios and answers to the questions which might be asked of you.</li><li>Prepare your technical set up and a suitable outfit for the interview.</li><li>Prepare yourself for unexpected.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8h5E8PA3GCNPg3e_c5S22A.png" /><figcaption>AI-generated image (Midjourney)</figcaption></figure><p>My personal statistics in this round of job hunting was:</p><ul><li>~600 applications (direct and through agencies / consultancies)</li><li>Conversion rate to get to the call with the recruiter: 5.68%</li><li>Conversion rate to meet a hiring manager: 54.5%</li><li>Conversion rate to meet a hiring panel: 33.3%</li><li>Conversion rate to meet a senior leader: 33.3%</li><li>Conversion rate to get a job offer: 50%</li><li>Overall success rate per application: 0.167%</li></ul><p>Good luck with job hunting! Let me know your thoughts in the comments or if you have any other useful tips to share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d8f5d1d8811" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build great enterprise tools, 9 UX tips]]></title>
            <link>https://medium.com/ft-product-technology/build-great-enterprise-tools-9-ux-tips-817e34123aaf?source=rss-126731307438------2</link>
            <guid isPermaLink="false">https://medium.com/p/817e34123aaf</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[internal-tools]]></category>
            <category><![CDATA[enterprise-ux]]></category>
            <category><![CDATA[enterprise-product]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Olga F]]></dc:creator>
            <pubDate>Tue, 02 Apr 2019 14:16:41 GMT</pubDate>
            <atom:updated>2019-04-02T16:21:25.267Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HqjzEuLGZY4qBkUb_PwupQ.png" /><figcaption>By Olga Shevchenko, Senior User Experience Designer at The Financial Times</figcaption></figure><p>Designing, developing and delivering internal products from scratch can be challenging for several reasons. Your team might receive too many requirements from stakeholders, and you’d need to consider how to build a user-friendly product and deliver on a business goal or your users might be scattered globally having different processes and tools in place that manifests in different user needs and user journeys. If you are designing, developing or responsible for the success of a new enterprise product, here are 9 practical tips to navigate the challenges this may bring.</p><p><strong>Tip 1: Start with the basics — consider your users.</strong><br>First of all, figure out who your users are. Sometimes, a user and a stakeholder is the same person, sometimes your stakeholders manage your users and sometimes your users are the real customers of your company. If your user and a stakeholder is the same person, feel free to set up usability testing sessions with them, as well as workshops, for collecting business requirements. If your stakeholders manage your users, you might receive a list of business requirements from them and uncover unexpected challenges from users conducting user research activities. The needs of senior stakeholders (who potentially fund the project) and managers might be very different from the needs of users who will work with the tool on a daily basis. To be able to ship a tool that satisfies the needs of both groups and delivers a certain business outcome, it is crucial to walk your stakeholders through the summary of insights and prepare your proposed solutions to issues that have been raised by users. Building a great digital product alone might not solve all the problems, and keeping unanimous understanding of business process and business jargon among users aligned with the user experience of the product is essential for the success of the initiative, your team and your company.</p><p>You need to know if you are building a product for 5, 20 or 100 people and whether your users are located in the same building with you or they are scattered globally. Knowing how many users you’ve got gives a better ability to decide what feedback to take on board. If you only have 5 users, getting similar comments from 3 people is ample. But if you get similar feedback from 3 people and you’ve collected feedback from 100 users, that makes it a less valid case when trying to get your product prioritised. Another aspect that will be affected by the amount of users is creating ‘personas’. A persona, from user research perspective, is a created character that represents an audience segment and is based on the motivations, habits and preferences of the real users. If your product is mature, the personas should be based on various types of qualitative and quantitative research. Personas help teams to better understand who they are building products for. It is more likely that a product used by 5 people will have only one persona but if you’ve got 100 users, you are more likely to have at least 3 personas. Working with remote teams might bring additional challenges for usability testing sessions and quality of the feedback. If you are showing a prototype to someone who is based on another continent, ask them to share the screen with you first and then send the link to the prototype. Kindly explain that you need to see where your participant clicks as it will give you an insight you are looking for.</p><p>It goes without saying that internal products should follow the minimum accessibility standards but you need to find out if your users have any particular type of disability and adjust accordingly. One of the conditions that will affect designs of your tools is colour blindness. <a href="http://www.colourblindawareness.org/colour-blindness/">The Colour Blind Awareness organisation</a> sheds light on the numbers: colour blindness affects approximately 1 in 12 men (8%) and 1 in 200 women (0.05%) in the world.</p><p>You can use <a href="https://www.getstark.co/">Stark plugin</a> for Sketch or Chrome extension <a href="https://chrome.google.com/webstore/detail/a11y-color-blindness-empa/idphhflanmeibmjgaciaadkmjebljhcc">A11Y — Color blindness empathy test</a> to better understand how your designs will work for different conditions of colour blindness. Although these tools might not emulate conditions with the accuracy of 100%, they will give you a good idea what works and what doesn’t.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iz2QIqBlSESXi9VS3BBj8A.png" /><figcaption>On the left there are different states of the health score indicators mockup, on the right the same states of the health score indicators being seen by people with protanopia (screenshot from Stark plugin for Sketch)</figcaption></figure><p>Another condition that will affect user experience of your products is motor disability. There might be users who may not be able to use the mouse at all or may have limited ability to control the mouse or the keyboard. Also consider if your users will be using voice-activated software.</p><p><strong>Tip 2:</strong> <strong>Understand and collaborate with your own team<br></strong>Teams that build enterprise tools for their colleagues might not have any experience working with a UX designer or user research team. Be prepared to explain what you do and what the benefits of robust user experience are for the business and users. Organise the sessions with the team to share the insights from user research, ask your team members to help you taking notes so they can see how it works first hand. The best comment I’ve got from an engineer on the team was: “I initially thought that the product was invented by the product manager and has no practical use. But now I understand why we are building it”.</p><p>Alignment inside the team plays a vital part. The process that works very well for one of my teams is the following: Every Monday a business analyst, a product owner and a product designer catch up for 30 minutes to discuss our priorities for the next week; on Tuesday a tech lead, a business analyst, a product manager and a product designer catch up for a 30 minute pre-planning session to go through the tickets that need to be put forward into the planning session on Thursday; on Thursday the whole team has an hour long planning session to go through the tickets and discuss them in more detail. The team can challenge any ticket and if there are not enough details, it will not be moved into ‘To Do’ list. Without pre-planning this session in the past we would spend 30 minutes discussing just one ticket, simply because we couldn’t agree on priorities. You can think: “Oh, it sounds like a mini waterfall process!”, and you might be right but there are no right or wrong answers when it comes to what process would work best with the talent you have in your own team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AQDWxu7pJJCKp9syrdgKgQ.png" /><figcaption>Example of collaboration process diagram for the team.</figcaption></figure><p><strong>Tip 3: Build relationships with your stakeholders and users</strong><br>If you are building a product for the global team, consider time difference and arrange meetings or usability testing session at a time which is convenient for your colleagues. Sometimes you’d need to have a call at 7 am or at 7 pm but nothing builds the connections better than respecting the working hours of your colleagues.<br>Consider the culture of the team you’re building the products for. What are they like? What hours do they work? What equipment do they use? What are their essential tools? How is their day structured?<br>The benefit of designing internal tools is that you know your users by name and can say ‘Hello’ when you see them in the office.<br>Your stakeholders might have never worked with a UX specialist before too so invite them to the meetings where you talk about user research and demo your work in progress. Try to get involved in the meetings that your stakeholders have with each other, and clearly communicate that you will be there only to observe, to get a better context for your project and to hear their feedback, ideas and thoughts.</p><p><strong>Tip 4: Follow a user-centred design process</strong><br>It doesn’t matter if you are designing a boutique product for a small group of people or millions of users, there is always a question: “Are we solving the right problem?” User research might uncover the gaps in the process which can’t be solved simply by building a new tool. In this case, escalate the issue to senior management. It may be that these user problems can’t be solved through technology alone and business processes or team practices might be better candidates for change. In my experience, regular surveys, usability testing sessions, card sorting and contextual inquiry activities work best but, of course, you might need a completely different set of methodologies depending on your audience, product and timelines.</p><p><strong>Tip 5: Think twice about copy</strong><br>How you label the UI components, blocks of information and calls to action is crucial for a robust enterprise product experience. Are your users native English speakers? Is English their second or third language? Are they foreign language speakers or second language speakers? Foreign language speakers occasionally use English for business, while second language speakers are more likely to live in an English speaking country and use it daily. The difference is massive as native English speakers might pay more attention to copy and labels while second and foreign language speakers might be less picky about the labels but read and understand them literally without being able to freely interpret based on the meaning. In one of our usability testing sessions we’ve had a prototype with an experience of assigning a stakeholder to the account. This part of the experience was at the bottom of the page under the label called ‘Contacts’ and the empty state just had a plus icon without any label. Additionally, above this section there were several checkboxes with the word ‘stakeholder’ in one of them. The task was spelled out as “Please show me how you would assign a stakeholder to the account’. Native English speakers easily found the section with the contacts and proceeded with the tasks, while participants with English as a foreign language were looking for a word ‘stakeholder’ on the page and were scrolling up and down the page several times trying to interact with the wrong part of the experience. Needless to say, we’ve changed the label to ‘Stakeholder contacts’ and changed the confusing copy in the section above making the experience 100% clear.</p><p><strong>Tip 6: Build responsive tools</strong><br>The majority of users access internal tools on desktop, and some teams don’t have laptops or are reluctant to use the company’s internal digital products on their personal devices. Consider the functionality of the tool being easily translated into mobile without massive dev effort. I wouldn’t call it mobile-first approach in design, but definitely mobile-friendly. Your users might use the tools you are designing on the commute, while travelling abroad or during the meeting. In this example, you can see that the functionality of the checkpoints is identical both on mobile and desktop, apart from a small tweak in the size of the buttons on mobile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojJBwexSqti9RLak0erDtg.png" /><figcaption>Checkpoints in the contract section have the same behaviour both on mobile and desktop.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VxUj7GQubvuHP3tsjHNN1w.png" /><figcaption>The only difference in UI is the size and position of the buttons ‘Save checkpoint’ and ‘Cancel’.</figcaption></figure><p>It is simply cheaper to build the tools responsive as it cuts down the cost of development, and you will have a competitive advantage over other enterprise product solutions which are provided off-the-shelf but do not behave responsively.</p><p><strong>Tip 7: Surprise and delight users<br></strong>Traditionally, enterprise tools look very functional and dry as historically they have been built with a minimum design effort. Business-oriented tools for slicing data and producing various reports are rarely built with the intent to look and behave in a ‘fun’ way. It is great to see that Salesforce introduced animations with the bear in their Lightning UI and other tools like Monday.com and Asana have some amusing animations bringing more personality to their products.</p><p>Who said the internal products need to be boring? You or a member of your team can design small delightful interactions which will not distract the users from performing their tasks or create fun illustrations to mitigate experiences in cases of getting an error. Your users probably browse other digital products and apps in their free time and have seen products with great UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPwRCo18dn3c7R4lWfRYtQ.png" /><figcaption>Colourful illustrations designed for different error scenarios.</figcaption></figure><p><strong>Tip 8: Consider the whole ecosystem</strong><br>The product you are working on is very likely not the only one your users utilise on a daily basis. There are at least 5 other digital products they have on their laptops and phones for a professional use (Google docs, email clients, calendars, messaging apps, HR portal), if not more. Think about what user journeys are like when your users interact with several products and switch between them. How about integration with other internal systems? Would it be beneficial to the users if your new product deep links to other off-the-shelf products? <br>If you have Salesforce as your main enterprise system for the sales teams and you have a couple of internal tools, how valuable it would be that all the systems ‘talk’ to each other?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IIqfktrFjQYmRy-e81-jJw.png" /><figcaption>Example of ecosystem of the internal tools with the main product that exchanges data and deep links to other products.</figcaption></figure><p><strong>Tip 9: Refer back to the purpose of the initiative</strong><br>When trying to balance different requirements, think about the purpose. What is your team trying to achieve by delivering a tool? What is the purpose of it? What is the mission of your team? Why do you all keep coming back to work and keep doing what you are good at?</p><p>A mission of my team reads “The Internal Products Team helps the FT to work smarter and better serve our customers”, and this is what I keep in mind when I talk to users, design experiences or participate in discussions.</p><p>While designing and building internal tools you will have plenty of input, and it might be overwhelming. Stakeholders, users, your team, your UX peers. The main takeaway is when you are getting feedback or insights that contradict each other, bring it back to your team and collectively try to answer a question: “What is the right thing to build to solve the problem?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=817e34123aaf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ft-product-technology/build-great-enterprise-tools-9-ux-tips-817e34123aaf">Build great enterprise tools, 9 UX tips</a> was originally published in <a href="https://medium.com/ft-product-technology">FT Product &amp; Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>