Skip to main content

the user feedback myth

Soliciting Web site user feedback. Posting online surveys. E-mailing listservs. Pulling together focus groups. Is this the long and the short of the plan for guaging the effectiveness of your Web site?

If so, you will be rewarded with a wide scattershot of commentary, much of which is neither accurate nor usable.


always crashing in the same car: recurring mistakes and misuses of the web


In fact, implementing this ilk of "user feedback" can be detrimental to your site's health.

Think about it. If you were overseeing the construction a classroom building, would you conduct focus groups and surveys to determine what materials should be used, where the doors and stairways should go, how strong the load-bearing walls should be?

No? You would rely on qualified architects?

Then why on earth would you open the door for individuals who have no understanding of how the Web works to step in and have a direct hand in your site design?

When this type of free-form user feedback enters the site design process, it sets certain machinery into motion that is difficult to manage or to stop:


  • You now have a deluge of recommendations, few if any of which have come from individuals knowledgeable of the Web. You must now wade through these, looking for what is sensible and usable. And figure out what to do with the rest.

  • The more disruptively opinionated of your users - and all Web sites have these - now have the expectation that they can step in and change the course of your Web site by popping off a few comments.



There is a better way. To get truly useful feedback, you must conduct usability studies.

Conducting a usability study does not have to be a difficult or complex. You do not need to set up a bank of video cameras, purchase expensive software, or wade through stacks of data. You also don't need to employ a great raft of subjects. Remember, all users of your site have much in common, so, even if your resources are limited to conducting only three or four studies during a design or evaluation process, you will be far better off than investing time in the scattershot approach.

What precisely is a usability study? Follow these references to learn more:

Popular posts from this blog

facebook, time to grow up

Originally published on August 28, 2006 I appreciate how Facebook has enabled me to connect with colleagues, and (younger) family members in a manner that is both informative and expressly cordial. It attracts students like Nutella attracts chocolate lovers, and because of that, I see interesting potential here. In fact, one of our faculty members at Penn State plans to try running his human-computer interaction course through Facebook this fall . Definitely worth pursuing.

the case for incremental redesign: part ii

If you are in any way responsible for a Web site, you should have some understanding of the principles of Extreme Programming . Cultivated as a discipline of software development, it is a combination of ensuring that designs remain uncomplicated, centering changes around user requirements, and employing the concept of the "Whole Team." The result is that small changes are released as they are needed - and endorsed - by the client. Not surprisingly, Extreme Programming speaks well to Web management. Consider its core values: simplicity, communication, feedback, and courage. These are the bedrock incremental redesign. Simplicity - Integrate all site changes in small doses. Avoid tectonic disruption of the entire Web presence. Document faithfully, but do not get bogged down in over-documenting. Or overplanning. Leverage reusable objects. Better yet, get the site into a content management system - one that is scaled to its requirements. Eliminate unmanageable code morass by fol...

how to make the worst of your content management system

I recently heard tell of the following activity, parading as content migration to an enterprise level content management system. I am not making this up: Copy large volumes of Web-content-to-be, page by page, into separate Dreamweaver files containing the design (created and sliced up in FireWorks) Copy/paste said Dreamweaver files into content wells of the content management system Repeat this activity ad infinitum until an entire Web presence is constructed in this fashion always crashing in the same car: recurring mistakes and misuses of the web When I heard this, something inside me snapped. Aside from the stunning inefficiency inherent in creating all these disparate Dreamweaver files, this activity points to a fundamental lack of understanding of what exactly a content managment system is. In the interest of quelling this misunderstanding in others, here follows a list of what not to do with a CMS: Dump a bad Web site into a good CMS. If your organization's Web presence is a ...