I’m looking for any standard job titles that might help me better define and clarify a project role. I started to custom develop the role and title, but thought I’d see if there is any industry standards first. We have a set of inter-related projects, each with its own project manager, all operating as a program under a program manager. The role with the undefined title is this: We have one individual that is a strong subject matter expert in almost all of the projects in this program. This person acts as a consultant to the projects and works with the PM’s to set overall business strategy and objectives for these projects, acting s a liaison the key stakeholders. This person could be labeled as a Business Analyst, but the role seems to be much more strategic. This person essentially represents and helps to determine overall strategy for the program. We’re trying to distinguish this role from the program manager. The program manager is more focused on meeting the objectives versus setting them. The program manager is focused more on process than content. Titles that I’ve considered so far: Program Consultant, or Lead Business Analyst, or Lead Consultant. Any parallel situations out there? Saving Changes...
The first thing that popped out to me would be that if the person you are trying to define is actually setting objectives and you think of the person as determining overall strategy for the program - isn't the person actually the Program Sponsor? Saving Changes...
Anonymous
This person is really serving as a subject-matter-expert and consult *for* the Project Sponsor, actually hired by the Project Sponsor. Saving Changes...
Andy JordanPresident| Roffensian Consulting S.A.Cherry Grove, AB, Canada
I have had similar roles on my programs before, but no real consistency in titles. I have seen consultant type titles, but usually more 'Business Consultant' or maybe 'X consultant' where X is the department / initiative title / etc rather than project consultant. I have also had clients who prefer to think of the role as a governance one with titles that reflect that. I even had one client who called it Customer Advocate based on the logic that the role was to ensure that the end product met the client expectations. However I have to say that regardless of title I haven't yet found one that is easily understood by everyone on the program and I therefore insist on a simple role summary - 4 or 5 bullet points rather than a full role description that will at least provide everyone with a high level view of what the role is designed to achieve. Hope that helps! Andy Jordan, President, Roffensian Consulting Inc., www.roffensian.com Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
I think you answered your own question. Just call the role "Subject Matter Expert." This is a commonly used title for someone who has knowledge useful for a project, but does not have any explicit authority over the project. Saving Changes...
Wayne, is that not just the extended way of saying Consultant?
Rich why not stick to what everyone knows. There are a number of titles for specific rolls,just like that of Project Manager. just as long as everyone is aware of what his/her roll is. Does it really matter? Saving Changes...
Anonymous
Thanks to all for your input. I know that, for many people, a title is irrelevant. But in situations where it is causing confusion, it needs to be addressed. We settled on "Lead Business Consultant", created a rather extensive RACI chart to show that role versus several other roles, and then made the chart available to all. Saving Changes...
Wouldn't you try to fit the word 'architect' into the role title somewhere? Program Architect or somesuch if you can't come up with a more appropriate first word - Strategy Architect? The Consultant title sounds like they react when asked, whereas your first-off description of the role sounded a bit more strategic / pro-active than that. Saving Changes...
