Of Titles, Age and Angst - Page 1

Feb 25, 2009

Esther Soloveichik

In the world of business and technology consulting, a person’s capabilities often are measured by his title. His aptitude and wisdom appear to grow in stature as the title loses its activity-based nature and assumes the mantle of hierarchical power.


Although developers, data analysts, systems integrators, database administrators, et. al. can possess great vision and often provide cross-functional solutions and business advice, these role-bearing titles present a picture of singular talents. The manager (provide your own descriptive prefix), on the other hand, is appreciated as the one with multiple talents and the business view. Furthermore, a person with no pecking-ordered-title finds his standing diminished with age. Those charged with hiring frequently look askance at a candidate with many years of experience and no “Pooh-bah” in his title.


During my twenty-five plus years of business and technology consulting, I have accumulated and discarded many titles, most with connotations peculiar to the organizations bestowing them. These titles seldom translated across organizations, and rarely translated across specialties within the same organization. The most illustrious title I managed to snare was team leader. That may sound pretty lame for a practice manager, but it had panache in the “Wisdom of Teams” mentality of the time.


In leading the development team within the technology consulting group of a regional accounting firm, my status and the status of my associates mirrored the hierarchy of the accounting establishment. Billing rates were tightly tied to one’s rung on the titular ladder. I quickly switched to market-driven billing rates for my team members. Technology was changing fast, and certain skills were in high demand. An associate on my team could have multiple billing rates, depending on roles played and her evolving expertise. This was good for the bottom line and good for personal growth, but unfathomable to the accounting side of the business.


I suggested we let our team members choose alternative titles that we could use for marketing activities. At the time, I was intrigued by two business owners with cards anointing one as President on Mondays and Wednesdays and the other as President on Tuesdays and Thursdays. The two claimed it was a great conversation opener. Given the staid business climate I operated in, my suggestion did not take.


I proceeded to write promotional resumes for each member of the team. These pieces were short, playful and demonstrated multiple software lifecycle roles for each associate. Team members preferred the promos to their resumes, partly because they were infused with personality, and partly because results eclipsed titles. My own promo began with “Esther likes to say, ‘They pay me to think'.” You can well imagine the comments that provoked. (I came to the concept of creating desired perceptions without titles through personal experience.)




Several years into my career, I accompanied a practice manager to a manufacturing client in Chicago. He introduced me and said, “Esther handles our clients in the Loop.” With that simple statement, he conveyed my responsibility to make sure the client’s needs were met. I believe my official title at the time was systems analyst. Shortly thereafter, I accompanied another manager to a financial risk management firm in the Loop. He referred to me only in the context of: “When we get back to the office, I’ll tell Esther to do this, and I’ll tell Esther to do that.” His declaration made me his personal factotum.


At one point, the organization I worked for launched an in-house contest to come up with a new phrase for the acronym TQM, to replace “Total Quality Management.” Suggestions were published in the company newsletter, and associates could vote. I submitted the acronym TQtM, with the phrase “Think Quality, think Mother.” This entry was accompanied by an article, where I expounded on the qualities of and need for a project Mother, a non-gender-specific person who would give the project team its roots and then its wings.


All reference to this contest soon disappeared from the company newsletter. I ran into the editor, and asked about this oddity. She told me the contest was suspended, because Mother was winning. While I espoused unconventional titles, the organization was not attuned to my way of thinking. As team leader, I opted to stay in a cube, rather than move to an office. This confused people. An eccentric title with no trappings of success projected the wrong visual cues. Managers sat in offices; mail was delivered to offices. I sat in a cube; ergo, no mail delivery.

Page 1 of 2

Tags: XML, Microsoft, software, management, marketing,

0 Comments (click to add your comment)
Comment and Contribute

Your comment has been submitted and is pending approval.



 (click to add your comment)

Comment and Contribute

Your name/nickname

Your email


(Maximum characters: 1200). You have characters left.