Multiple Project Leaders: Roles and Definitions

Challenges exist when there are multiple leaders within a defined project.  From a project management theory perspective the project manager should be THE 'leader'.  However, what happens if a team member is designated the project lead?  What does that mean? Has that dimished the responsibilities of the project manager? Is he/she only an adminstration role? 

I read an interesting blog on this topic - see link below.  However, I don't think the discussion went far enough.   Every business has its unique spin upon positions, titles, responsibilities.  It is very reasonable to assume that some key team member may bring the expertise to the project that enriches the project processes and deliverables.   It may be a senior developer, an expert business analyst or subject matter expert, or a committed business sponsor possibly acting as a champion and spokesperson for the project. 

My solution to ensure clarification of leadership is really quite simple.  Early in the life of the project, the project manager should create and communicate a Roles and Responsibilities chart.  This can be as simple as a spreadsheet or matrix in a Word document.   For each major project team role -- project manager included,  it declares the expectations, roles, and responsibilities.  This can be built in a collaborate environment as needed.  When shared with the team, confusion is lessened and expectations are set.  While I have not used this technique with every project, it is a valued approach to bring a team together and allowing me, the project manager, to present my leadership over the project.  I can reaffirm the roles and responsibilities of the project manager.   Additionally,  I promote that these other 'leaders' can focus upon their natural duties where benefit can be obtained.

What's your approach?

Link to original "PM Voices" blog