Tag Info

Hot answers tagged

7

welcome. The website has a clean design and is certainly focused right in there to registration. However, here's a few thoughts I had: From the homepage alone, I don't know enough about it to just give my email address and be signed up. Registration is free for the Beta (which is only explained on another page), but are there any other fees? What happens ...


3

The only thing you need to do is to collect 3-5 users and conduct a simple user test. Preferably some of the users that would actually be among your end users - but that's not that important right now. Ask them, one by one, to carry out a certain task on your app. Observe! Don't tell. When they struggle: Ask why. When they succeed: Ask why. I can assure ...


2

User Experience Design is more than quantitative site analysis - by its nature as part of the design process it involves making subjective decisions on aspects where it is difficult or impossible to get data, and must take into account a balance of factors which make up the experience gestalt. UX design takes a holistic, multidisciplinary approach to the ...


1

Personally I would favour both. As you say the beta channel approach can lead to issues with power-users not doing things standard users might, in the simplest example a power user might know not to put text in a field asking for a number so you may miss the errors that would indicate you forgot to validate the entry until it goes live and lots of ...


1

For me it sounds like your are doing customer development rather than user treting, because you need feedback about the product value and its actual use. Anyway the methods of custdev are similar to user research, not before concept phase like research but after beta phase. We just ended our beta phase and did this: . focus groups with some users . ...


1

I would do two things: The first would be to carry out an observation with around 8 users, asking them to "think aloud" throughout. This will give you a good idea of what users might think when they start using your app. If it looks like the protocol is distracting the user, tell them to only comment when there is something they don't like/understand. ...


1

We are missing some very essential information here. "Who is your main user group"? If you think of it, the answer to you basic question is quite logical. Would it be smart to have a doctor to review a health insurance application form? No way. Likewise, a domain expert can really ruin the user experience for a novice user. Terminology, mental model, ...


1

The questions that are useful for one application aren't necessarily useful for another. Use the survey to validate points that you are most uncertain about and which are most critical to the success of your application. Only you can know what those are, so you will have to come up with them. Some advice though is that the longer you make it, the more ...



Only top voted, non community-wiki answers of a minimum length are eligible