It’s Friday (not that Saturday workloads care about Fridays, but that’s another post for another day). We’re tired from a long week of contract negotiations, client interviews and many, many rounds of client creative reviews. However, that won’t stop us from discussing the merits of user-centered design with a non-believer or two.

I’m continuously discussing with peers, family, the dog and the lamppost that I speak to so frequently about the idea that if a “user” (or, to be nice, customer) doesn’t need/want something then you’d be hard-pressed to convince me it belongs in the aesthetic or functional specifications of your Web entity.

How, then, do we find ourselves so often tinkering and playing and working through pieces of functionality or designing widgets and cogs which were not listed in the initial requirements? How do we end up in a place where we, as the vendor, are answering for the client, rather than the client answering why they’ve chosen a specific direction?

It’s befuddling to look at the listed goals of a project only to warp drive three or four months into the future and realize that along the way you picked up some odd passengers.

I think we need to be better at saying “no”.

“The client pays the bills”, you say.

Yep. They also asked you for your expertise in designing and building their online entity. Think of the user. Ask your client to think of their clients. Ask yourself if you’re part of the solution… or part of the problem. It’s okay if you are, but make sure you’re comfortable where you ended up.

And, if you’re strong enough and have had waaaay too much coffee, shout from the top of the rolling cubicle chair without arms, “Back, non-believers!”

Enjoy the weekend.