People vs. Titles

In the midst of the giant reorganization at work, I have been thinking about the difference between people and titles. Specifically, the fact that in large organizations, titles are expected to do work. That is, I (David) am not asked to do something, I (Process Engineer) am asked to do something.

Who cares? I do. I am expected to do things because I hold the title of "Process Engineer", not because I want to do them, or am even able to do them. As a result, we have a bloated system of competency tracking and development that defines what the person holding the title should be able to actually do. After all, it is the person who does the actual work, not their title.

Unfortunately, this puts everyone in a bind. A large organization needs defined roles with titles to prevent chaos, but rarely does a job description fit an individual's strengths and desires perfectly. So we are forced to fit square pegs in round holes, or at best elliptical pegs in round holes.

The take-home message? Beware titles. Remember that when you ask for work, an individual will do it, not a title. When you are doing work, remember that others are usually just looking at your title, not you as an individual (unless they're reading this blog). Overall, keep in mind that you work with people, not titles