Program management in matrix organizations works little different than managing a regular project. While a program owner handles the WBS and the schedule, work packages are delegated to departments with focus on delivery. More background information can be found in my last article.
This article reflects on the two main roles contributing as actors in the planning process and how their goals compete with each other. In the given scenario we are facing following main roles:
- Program planner: a.k.a. program manager, program coordinator, project manager, etc.
- Department manager: a.k.a. resource manager, team lead, manager, head of, etc.
Both roles are having competing goals to effectively drive their business (as show in following figure).
The program planner has goals similar to a project manager. This is time, budget and quality. Whereas the department manager has to develop business, drive innovation, manage the team and increase profitability
As you might imagine, those goals compete each other with regard to prioritization. Let’s view an example:
- A program manager delegates two work packages to departments X and Y. Both tasks depend on each other (X need to be finished before Y might start).
- Now, department X is having work packages of 6 different programs to be delivered and two key resources fall out.
- What is the basis for the department manager to prioritize? Maybe it is profitability or team management? Most properly it is not the same that the goal of a single program manager.
- Let’s assume a prioritization has been done. Who needs to be informed now? Or should I better ask: ‘Who is going to be informed?’
For sure, there are a lot more centers of conflicts. But these competing goals are the top reason for conflicts. It has happened to me in almost every project I have conducted over the last years. And there is only one resolution: Transparency. We need to resolve those independent planning platforms for a program and a department.
If you are interested how to bring up an integrated solution that establishes transparency into each role’s planning and highlight any deviations that might occur, stay tuned here or visit my session on the Microsoft Project Conference (#mspc12) in Phoenix, AZ, March 20th to 22nd (abstract for session #pc310).
You’ve read about the two contributing roles and their competing goals. Within the next article, let’s break down the goals into tasks relevant for program management in matrix organizations.