But wait, isn’t everything we do for users? Nope!
I’m really beginning to hate the term “user.” It has become mainstream. Much as we say “google it” when we mean “search for something on a search engine,” “user” has become synonymous with anything we do in the design/development/product world.
There are two situations where I really want to see the term go away.
User Stories for System Implementations
User stories in a backlog are amazing. They are often written something like this: “As a <insert user>, I need to be able to see all of the currently open tables in the restaurant…”
That user could be a host who wants to seat some guests. Or that user could be a manager who wants to know when to start releasing servers to go home. Depending on the user, that story is going to change dramatically.
But what about features in the backlog that don’t have a “user”? I often hear everything in the backlog referred to as a user story, and it’s simply not true. For example, “As a <insert user>, I need to have Google Analytics added to the website to track movements…” is something that would never be written.
When the Audience Isn’t a User
Another scenario I’ve seen a lot has to do with designers talking about an audience—not a user. I recently attended a portfolio review for college seniors, and while some of their work was interface-related, other pieces were more focused on traditional design, such as components of a marketing campaign or a restaurant design.
Without fail, all of the students started to describe the pieces in their portfolio with a statement about who the “user” was. To my ears, though, it sounds a bit funny to describe an invitation to a fundraising event as something designed for a “user.”
As a design community, we need to expand our language to more accurately describe audiences. Users are a specific type of audience. Guests, visitors, patients, customers, etc. are also specific–but different–types of audiences.
Calling everybody a “user” diminishes the value of the term.