{"id":1534,"date":"2017-04-13T16:27:21","date_gmt":"2017-04-13T16:27:21","guid":{"rendered":"https:\/\/www.walkme.com\/blog\/?p=1534"},"modified":"2023-05-02T15:41:46","modified_gmt":"2023-05-02T15:41:46","slug":"ux-methods-low-users-short-time","status":"publish","type":"post","link":"https:\/\/www.walkme.com\/blog\/ux-methods-low-users-short-time\/","title":{"rendered":"Part 1: UX Methods for a Short Time to Market and Few Users"},"content":{"rendered":"This is the worst UX scenario for Designers and Product Managers alike.\n\nCircumstances have given you a tight deadline to meet and little access to users for feedback. How, then, do you approach this project, UX wise?\n\nThis is exactly the situation UX Combos were created for. After acknowledging your limitations, it can decisively help you select the right UX methodologies. This blog post will cover the UX methods included in the UX Combo for low access to users and a short time frame.\n\nThis is the first of a series of blog posts we will be writing on each of the four UX Combos.\n

Refine your UX today using WalkMe\u2019s onscreen guidance.<\/a><\/em><\/strong><\/p>\n\n

What\u2019s Your Combo of UX Methods?<\/h2>\nEvery product is created over the course of a product timeline. At each stage\u2014research, design, and testing\u2014multiple UX testing methods can be used to improve the product. The problem is that there are a lot of methods to choose from, but not all of them are fit for every scenario.\n\nSome options might get you the best feedback on your product, but take too long to complete before a product launch.\n\nSome may be quick to finish, but require interactions with users that are not always accessible.\n\nA UX Combo takes into consideration the most important parameters for choosing UX methods, namely, access to users and time to market, and narrows down which methods are fit for your circumstances. The final combination is your UX Combo<\/strong>.\n\n\"user\n\nToday, we\u2019ll be discussing the UX Combo used when you have low access to users and a short time to market. But also be sure to check out the deeper look at UX Combos with the links below:\n\nWhat’s Your UX Combo?<\/a>\n\nPart 1: UX Methods for a Short Time to Market and Low Access to Users<\/a>\n\nPart 2: UX Methods for a Long Time to Market and High Access to Users<\/a>\n\nPart 3: UX Methods for a Short Time to Market and High Access to Users<\/a>\n\nPart 4: UX Methods for a Long Time to Market and Low Access to Users<\/a>\n

UX Combo for Low Access to Users & Short Time to Market<\/h2>\nWhen users are hard to access, and you have a short time to market, you\u2019ll need a UX Combo that is quick to finish and only requires the resources you already have.\n\n\"user\n\nThere are four methods that make up this UX combo:\n
    \n \t
  1. Stakeholder Interviews (no users involved)<\/li>\n \t
  2. Concept Design (no users involved)<\/li>\n \t
  3. Concept Testing (with users)<\/li>\n \t
  4. Post-launch Usability Testing (with users)<\/li>\n<\/ol>\nLet\u2019s dive into each one to understand what you need, what you will gain, and what to expect, deliverables wise.\n\n\"UX\n

    First UX Method: Stakeholder Interviews<\/h2>\nStakeholder interviews are done to understand the business needs and how you will measure success by determining Key Performance Indicators (KPIs).\n

    Before You Start<\/h3>\nMake sure you have an agenda before you begin. Prepare questions that are specific to each stakeholder\u2019s domain (e.g. business, technical, etc.) and how they expect the product to serve them or their interests.\n\nFor example, a business stakeholder may be interested in achieving specific results, while a technical stakeholder may stress the need for a \u2018light\u2019 implementation that doesn\u2019t overload the database.\n\nYou\u2019ll also need to prepare your questions to promote design differentiation and priorities. Discussing these options will help you obtain the detailed need from the targeted stakeholder, as opposed to the non-directive \u201cwe want more\u201d approach.\n

    Limitations<\/h3>\nWhile stakeholder interviews are extremely helpful for your UX Combo, they\u2019re all about what the company wants to get from the product. They ignore both user needs, and how they want to get it. Therefore the stakeholder interviews are a baseline\/guidelines for your work, but not the end of it.\n

    What to Focus On<\/h3>\nDuring the interviews, it is critical that you maintain a clear focus on the business need—rather than the solution. Engaged stakeholders (especially founders) tend to quickly jump to solutions, but your understanding of their need will ultimately give you a deeper perspective to base your solution on.\n\nNext, learn and define how success will be measured. Set specific KPI\u2019s and plan how these will be measured. This point doesn\u2019t always come up at early stage, but for sure will come up later, after launching, so you better plan for it.\n\nStakeholder interviews are also the best time to address any elephants in the room, e.g. we don\u2019t currently have any users, we\u2019re not sure about our target audience, etc. Allow room for concerns and worries to be expressed. Then use this time to address these issues.\n\nFinally, stakeholder interviews should be used to confirm levels of involvement and commitment from your stakeholders, meaning, do they expect to be involved in any stage? Just the end result? Setting the right expectations here can solve a lot of misunderstandings later, and can also point you to the people that are truly involved, when you need support\n

    What You Gain<\/h3>\nBy conducting stakeholder interviews in this manner, you\u2019ll be able to gain:\n