What's your advice for drilling down on use-case for our real time communications iPad app for co-viewing docs together?

We have been collecting usage data on the home button from about 750 websites we manage across North America in an effort to try to determine if it is necessary or not. While each website is different, and much of the data is statistically insignificant, we have started to operate with a few assumptions. 1.) Most users, particularly younger users, recognize the logo as a way to get to the home page. 2.) Websites without home buttons seem to get a comparable amount of traffic to the home page as those that do not. We don't see a significant difference between having a home button or not. 3.) Websites without a home button often will see an increase in direct traffic from returning users during a session indicating that users who do not know the logo is a route to the home page will instead clear the address bar back to the root domain to get back home. Based on our research, we have decided to omit the home button in most instances. Although when it is present, it is often used, most users seem to understand how to get to the home page regardless of the inclusion of a home button. With the complexity of modern websites, we are usually pressed for space in the header and can better use the real estate that would be dedicated to the home button for other UI elements. That said, if the audience for our website skews older, we will still include the home button. Our research has indicated older users are less familiar with the concept of the logo being a home button.

It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.

Khuram's reference to what I call the "gap technique" is spot on. Few people will rate something 10/10 or A+. This gives you the opportunity to ask them how to achieve that highest rating. Once you do that: "Shut up and listen!" :) -- One of the worst mistakes is to get a participant talking (and many people talk way too much) but then to cut them off even though they're giving you substantive information (obviously, if it's drivel, then you do want to move on). You also have to assess those you survey: some are founts of information and insight while others have nothing to say. All are not created equal, as it were. In all surveys, whether in person or on-line, I recommend open-ended (i.e., unprompted) questions (where possible) followed by close-ended (i.e., prompted answers) questions. In other words: What is your favorite brand of cookie (with no list specified)? Perhaps they say Oreos. Later on, after they've forgotten that, you have a list: Which is your favorite cookie brand: a) Little Debbie; b) Mrs. Fields; c) Oreo; d) Duncan Hines? Now if those two don't match up, how valuable are these answers? So that gives you the ability to test for validity. Once you present the prompted answers, you've poisoned the well, which is why they have to come later. Hope this helps and should you have any questions, I would welcome the opportunity to discuss with you. Best, Steve

Stop thinking you don't have the skills to do something. You can learn anything if you decide to, but assuming up front that you can't (forever) is dangerous. my2cents

UserTesting can be instructive in terms of understanding whether people understand your copy, CTAs, and intended flows but generally, I've found the quality of their panels to be pretty low. You're almost always getting people who are not your actual users, so the feedback can only be generally applied as above. I find whatever web analytics package or packages you're using are generally able to provide much better insights. I also really do believe in *real* user panels. Buying pizza or offering small financial incentives to real users to click through new flows where they are talking out loud or answering specific questions is going to give far more actionable insights than anything else. What I like to do is take my best guesses as to what's not working or what I'm looking to improve and then discover/validate via real in-person customer panels. Happy to talk through this in more detail with you in a call.