Forget Users, Think People

We have a problem in this industry. We live in a world where we constantly think about the “users” of our software. In that identification, we dehumanize the People that are using our system. While this is a small detail, we have to remember one thing…

Words Matter.

Everywhere I look, in proposals, requirements, and manuals, the People that use the system are referred to as Users.

Not Writers.

Not Publishers.

Not Creators.

Not People.

It is pervasive. We hold User Conferences. We write User Manuals. We assign User IDs.

The cruel thing is that we don’t do it to ourselves. There are developer conferences. The creators of the software get to be People, why not those who have to live with the software?

We even try and perfect the User Experience.

Why are we not working on the Human Experience?

Why do we insist on calling the People whom our software helps users? We aren’t pushing a drug. If we were, more People would be willing to use it.

imageDrugs are addictive. Content Management software is not.

One thing that we do have in common, aside from calling People “users”, is that we have to push People to use the software. We have to convince them to take that first step in using the software. People view the software as dangerous, a risk, something to be avoided.

We need to change this approach. As Content Professionals, we need to think of everyone as People. The first step is to change the way we talk.

I am not trying to help users.

I am helping People.

One Little, Two Little, Three Little Interfaces

Several weeks ago, I promised a reader [EDIT: Read the comments here.] to discuss why I would think twice before adding a TaskSpace interface to a solution that already included an eRoom interface. Aside from the obvious that TaskSpace is a brand new interface and could most likely use service pack or two, I am always hesitant to provide too many interfaces into a solution. There are times for it, but it is important not to add them just because you can.

Continue reading