As web designers we consider ourselves champions of the users needs, but at what cost?
It was 2010 and I was speaking at a conference in Oslo, Norway. I was on stage presenting to a room full of UX designers from around the world. The talk was going well and the audience was enthusiastic, but I knew that was about to change.
Taking a deep breath I announced to the room “as web designers we need to remember that business requirements are more important than user needs.” Unsurprisingly there was a sharp intake of breath and the twitter backlash commenced.
My point was that ultimately we are employed by the client and not by the user. We are paid to create a website to support the business, not the end user.
The response on twitter was impassioned. People felt that putting the needs of users first was the best way to fulfil business requirements. After all, happy users lead to a profitable business.
Most of the time this is true, but not always. Occasionally there are scenarios where users want one thing but the business needs another. In such cases it is important to prioritise the business requirements.
At least that is how I see it. I know many believe this is short term thinking on my part. That given time the benefits of nurturing users will ultimately help the business. They also argue that putting business needs first can be used as an excuse for the client riding roughshod over users.
The question is what do you think? It’s the next debate topic for the podcast:
This house proposes that web designers should acknowledge that business requirements are more important than user needs.
Do you agree with me that business needs are our number one priority, or do you think that is a dangerous road to go down? Have you examples of where user and business needs clashed, and if so how did you resolve it? Let us know in the comments.
- How to create a pattern library and why you should bother
- Design convergence is not a dirty word
- 5 exercises to engage clients and stop you wireframing alone