It’s funny when we get into a debate with a client about their own audience. We often find out in these situations how much both sides don’t know about the customer.

In these cases, we lean on both the statistical data and the experience we’ve collected and take a shot at running tests to see how close we can get. We usually get pretty darned close.

But what happens if the client isn’t willing to disclose certain information or the audience is not allowed to see the new interface design until it goes out to beta?

Design to the user.

It’s at the point where I say this in my sleep. I design user experience. It’s based on the user and their experience. End of story. I don’t design applications or Web sites or software UI to meet the specifications of a machine or a database. That’s left to the capable hands of the back-end development team.

What I expect them to return to me is the data the USER needs in order to make the EXPERIENCE as painless as possible.

Our lives are filled with applications that spit out millions of data points and while a user’s interaction is much more savvy on the Web than it was ten years ago, it’s not so savvy as to correctly guess at what they’re supposed to do without some sort of roadmap.

It’s still ok to hold hands and it’s still ok to give them a map.

Keep the user experience useful.