[Sigia-l] Are you ready for it?

[Jeff Lash]

Some things I liked in Tog's article, some things I didn't, but one
potential obstacle I can see...

Job titles are usually defined by Human Resources departments. Especially in
larger organizations, there are more restrictions on job titles. Usually the
second or final word in the title defines the level of
experience/responsibility.

For example, "Architect" might only be used by senior positions, while
"Designer" or "Developer" might only be used by regular or junior positions.
A "Software Architect" might just be a more experienced "Software Developer"
but perform the same basic duties. And a "Financial Analyst" and "Business
Analyst" in two different departments in the same company would have very
different duties but be at the same level in the org chart.

For multiple-word titles, common ending words are: Architect, Specialist,
Analyst, Designer, Developer, Consultant, Engineer. Often, the first word or
two is up to the individual group or department to decide. (e.g. "Usability
Specialist" or "Human Factors Engineer" or "User Interface Consultant")

Plus, most companies I am familiar with are trying to *consolidate* job
titles, since in recent years it has become more difficult to recruit
candidates, organize departments, and compare relevant salary data with a
hodgepodge of different names.

So, even for people who agree with this and want it to change might not be
able to make it change. Of course, we can call ourselves whatever we want,
regardless of what the official title is, but if the employers and business
cards don't change, does it really make much of a difference?

Jeff
--
http://jefflash.com