New answers tagged

3

Try to find users that are likely to use your product/service and interview them to see their attitudes towards your idea. You can also survey your target users to gain additional information on their opinions. You can also try something like an A/B test. Try 2 or 3 variants of your subscription plan/idea, distribute them evenly among subscribers and see ...


2

I think your next step here should be focusing on the improvement of the current features. If you have already discovered that "most calls point to issues that could be solved by improving current features, rather than introducing new ones," then adding new features doesn't make much sense here from a UX standpoint. Instead of wasting your, designers, and ...


0

Without really knowing any of the information that you have on hand, I can suggest some basic strategies that you can consider for feature prioritization, which you can combine to create a weighted feature list that should suit your purpose. For each of the categories listed there are a number of different ways in which you can score the features (old or new)...


1

You've answered your own question here (although, ahem, you might want to rephrase it into a question). User research shows that the priority is improving features you already have. Prioritise that before adding another feature. At the heart of great UX is a long, fiddly, detailed, often boring, Continuous Improvement Process


0

Some believe that the best way to determine what should be built is to observe users in the wild before deciding on features. Watch them as they do their work, without directing them. What tasks do they perform most often? Which ones give the most trouble? What do they never do? Discovering these patterns should provide some obvious directions for what ...


0

In my opinion the study on the CSR you did is a good starting point. If you have the chance to interview the users, try to understand why do they needs those features, which additional features they could want or imagine.


0

We usually do user testing in early stages using low/high fidelity prototypes/wireframes to find design issues earlier and avoid dev rework. so it will take long time for us to create prototype which handles all real time scenarios.so we usually use some real time scenarios to do user testing.. Since you are redesigning, you will get analytics information ...


0

Most tests are based on systems where the user has a number of choices in terms of the tasks they wish to perform - Even on a simple website the user can choose to find information about X, look at pictures of Y, contact the owners... etc. Each of these tasks has it's own complexity - How does the user find out how to contact the site owners? Do they use a ...



Top 50 recent answers are included