Menu

Preparing for questions we shouldn’t get

by Jared Spool

Today, I got this question from one of our clients who is just in the nascent stages of firing up their usability efforts:

Can you point me to any research that speaks to the value of redesigning a website or application to make it more usable? As you can probably tell from this question, we’re trying to develop an answer to a questions that our team will be asked; for example, “What value do we get from making our website a great website or making an application easier to use? How do you prove that value?”

Of course, I pointed them to the usual suspects, including this book and this article, but I think the real answer lies in this part of my response:

The simple answer is, if someone asks you that question, they aren’t the people you want to work with. Somewhere, within your organization, there has to be someone feeling tremendous pain because some system is unusable. Maybe it’s a support manager who has an overworked and underpaid staff answering calls that could be avoided? Maybe it’s a salesman who is spending too much time futzing with his sales ordering system instead of on the phone getting more orders?

Somewhere, someone is not happy. Find that person and determine how much their unhappiness is costing the organization (either in time, money, or resources). Then you’ve got someone who will intrinsically know the value of making the application more usable and *will tell you* why it needs to be done.

That’s the strategy I recommend.

It’s natural to want to be prepared for questions. Yet, are there questions that we shouldn’t be asked in the first place? Are their questions that, when we are asked them, tell us that we’re talking to the wrong people?