When I talk to developers I often hear a similar question, “Do you think I can become good at design/user experience?” My answer is always yes. I see the art in the code, devs attention to detail, the desire to make great things…but it wasn’t until this week that I discovered a way to accurately explain an easy way to digest it.
It’s this potentially contentious moment where I see opportunity:
Designer: “Hey, this click transition is not a good experience for the user.”
Developer: “But it’s not broken; I just tested the code.”
So I say to all my devs out there:
Bad user experience is a bug.
Working code is absolutely necessary to user experience, but there’s more to it. Building experience means facilitating the best ‘feel’ for your audience. You can begin by making the feature/page/experience you’ve created a bug to be checked. Pin it into whatever bug check-in software you’re using. If what you’ve made doesn’t feel enjoyable, simple, clear or trustworthy, mark it.
Now, go test it. Pull up the page for Rich in accounting, Cindy in sales, someone close in proximity, who has a fresh perspective; watch them use it. If it’s a complicated application, write up a little script that explains the task you are testing. There’s a good chance you’ll see what needs to be improved just by observing but ask a few questions also.