Scott Berkun has some very interesting insights about the distinction between Project Managers, in the traditional sense and definition of the term, and Project Trackers, who may have the title of project manager, but essentially only gather actuals and create reports for sponsors and management without actually leading project teams during execution. Scott also provides a handy set of questions that can help one determine exactly what role a PM is playing on projects.
I have made this distinction for years in the PM courses that I teach at the University of Wisconsin-Milwaukee. The analogy I use to describe a "Tracker" is of another position in large organizations - that of an auditor.
An auditor (internal or external) looks at the past to reconstruct financial transactions and report to management and others (government regulators, for example) that such transactions were proper and within limits set by management, regulators, and others with control over the organization. A project tracker has the same role: collecting actuals (project data), analyzing the data, and producing reports for management, sponsors, and other controlling parties. I tell my students that although these individuals may perform an important role, they are usually not leading or managing projects with authority as we would usually expect from people holding the PM title.
There is another insidious problem that I've seen in the past and warn my students and clients about: that of the hybrid PM/Tracker. The hybrid has a number of problems that are hard to rectify successfully:
- They have responsibility for project outcome, but no real authority when authority must be exercised. These types are the perfect foil for falling on their swords when things go bad (when in truth, others should have fallen); or get routinely second-guessed or countermanded when they try to exert authority or make project decisions.
- They cannot spend project budget or engage/acquire resources without running gauntlets of permission, sign-offs, and over-justification of need.
- While they may be told that they have authority for project decisions, they are squelched the minute that they try to make one.
I advise my students that the hybrid scenario is one that they must avoid at all costs - it won't be worth it not only for the project, but their careers as PMs, managers, or project team members. I also strongly suggest to them that the time to establish project authority issues is when the project is in its initial phases (or in the job interview, if that's the case). I usually suggest the following approach with sponsors and managers:
- You can describe your style of project management to sponsors and managers, making it clear that you expect to have day-to-day authority with respect to leadership and project management issues. You should sell your skills at leadership and decision making versus spinning scenarios that make you look like a power-hungry control freak.
- If the reception to your description is lukewarm-to-chilly, then ask the sponsors what exactly they expect from you and your role. This is a good way to ferret out sponsors and managers that want a easily-jettisoned scapegoat if things don't work out as planned, not a project manager. Others may indicate that they only want a tracker, which is fine if that's what you want to do - at least it is brought to the table up front.
- If you receive responses that leave the issue in limbo, think again before accepting the role. The time to define the project and other leadership roles is up front, not as you go along in the project. There is too much risk of getting up future mornings and as you look in the mirror and brush your teeth, wondering how much authority that you really have that given day. a bad place to be, believe me.
The essence of this is clear: if you're going to be held accountable and responsible for project outcomes, you have to have the authority to lead and make decisions. If you're a pure tracker, the point is moot. If you're in a hybrid situation, you're in trouble, so is your project and most likely, your organization.
Comments