Skip to main content

I am not a big fan of job titles.  We have had some staff additions and changes in the last couple of months and one of the most frequent questions has been “What’s their new title?”  Frankly I do not care!  I am fine with people picking their own title and would rather spend my time concentrating on the work we need to get done.

I suppose my dislike of titles has to do with one of my philosophies of work.  I think when an organization has a vision, operates as a team, and strategically sets out to accomplish it, that everyone’s job on the team is to see that the vision is accomplished, regardless of a person’s title.

Titles to me are too specific. They seem to indicate a defined area of focus.  I realize some people need that for clarity and I understand the need for specialization around an area of work or skill sets, but I prefer a job description to a title.  I like for a person to understand the goals and objectives for the position, and even more than that, the overall vision of the organization and for them to realize how they are a key part of the organization’s success. That is hard to capture in a specific job title.  Job titles tend to lead to the phrase and thought, “That’s not my job.”

I realize job titles are cultural, so we will keep using them, but I do not have to like something just because everyone else is doing it.  I almost wish we could start calling everyone “Team Player” and if they need a big title to feel good or to dress up a business card, maybe we could title them “Director of What’s Required”.

Do you like job titles?  Does your title truly capture the entire role you play in your organization?

Related Posts

Ron Edmondson

Author Ron Edmondson

More posts by Ron Edmondson

Join the discussion 6 Comments

  • Dan says:

    Well, I’m a sailor, so basically my title is “Squid”, but I would think that if you have hired a guy to do a job, he probably has a title of some kind, right? It’s probably a necessary evil, isn’t it?

    For us lay-people, titles are fun but unnecessary. It will just go to our heads for the most part, or maybe that’s just me.
    .-= Dan´s last blog ..Autumn Resolutions =-.

  • Stu Ramsey says:

    I am smack in the middle of re-aligning our organization to focus our attention on meeting our strategic goals and the title debate has entered the equation for some of my key staff.

    Although titles are certainly part of society in today’s world, I would rather have a title that told everyone what our organization’s initiatives are – Chief Operations Officer, Chief Financial Officer, etc don’t define what we are trying to accomplish.

    How about Chief Member Service Officer – as our focus is serving our members. Chief Team Officer – another focus is providing a great environment for our team (employees, board members, volunteers). If we are going to have to have titles let’s tell the story of what is important in our organization.

    In the end, call me whatever you want. All I care about is being given the opportunity to make a difference.

  • I agree…especially on a ministry staff. When you have a staff opening, then you tend to look for someone to fill that particular role. Naturally, everyone has strengths and weaknesses, but I’m a firm believer that you hire the right people and they’ll create their role.

    That being said, “and other tasks as assigned” is in my job description.
    .-= Jonathan Haskell´s last blog ..Thank God for Dirty Dishes =-.

  • Ron,

    I am totally smitten with the “Director of What’s Required” title. Go for it.

    Churches can be tough places to deal with the “title” thing, and even tougher in which to make changes. (We fall to our knees asking Jesus to “Change Our Hearts” but what we really mean is “Change Everyone Else’s Heart So Mine Can Have a Good Rest:-).

    So here’s a thought for today: Have a good sit-down with the staff and share your discomfort and why. Then, ask each of them to go off and come back next week with the answers to the following:

    1. What are all of the “things” that you do and the results that you see in your particular ministry?

    2. When you define “teamwork”, what does it really look like operationally?

    3. Are we doing #2 according to your definition? If not, what would you like to see happen differently and what are you willing to do to support that?

    3. If you could make up a title that describes what you really accomplish in #1, what would it be? (Disallow Director, Coordinator, and other traditional titles that imply hierarchy or get people into “Who will sit at your right hand” mode). Really, “Minister to or Minister of” has worked quite well in other situations in which I’ve been involved.

    Thanks for putting this out there…you aren’t alone.
    .-= Steve roesler´s last blog ..Four Ways to Help People Learn =-.

  • Trey Medeiros says:

    I dont like Job titles either. Nor do I like the implication that because you have seniority youre better qualified to do the job. Be a team player and if you have seniority learn how to accept a fresh perspective.

  • Jon says:

    I like job titles to a point. To get around the “It’s not my job” thing, just make sure the job description has something in it called “Other”. 🙂