Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.
Having a framework that allows you to model the PMO's processes and tailor them to match organizational needs can make corporate project management more valuable. This approach is based on a proven methodology named Business Model Generation, a strategic management canvas for developing new or documenting existing business models visually. We are now going to apply it to a PMO.
This is important, because many PMOs start small. Their main concerns are usually tied to monitoring and reporting project results to assist senior-level decision-making. However, as time passes, people think the PMO must absorb new features and responsibilities to remain competitive.
But growing a PMO in size doesn't necessarily mean we're improving project governance and corporate results. Maturity is the key to success. And a lean PMO is much better than a large bureaucratic PMO. Take a look at The Project Management Office in Sync with Strategy to see examples of this in practice.
Setting up a lean PMO is easier than keeping it lean. If you followed the steps mentioned in previous posts, you already have a strong PMO implementation plan with all the basics. Don't be tempted to add new functions to your PMO unless they are strictly necessary to the value you want to provide.
The most important characteristic of a lean PMO is that it is customer-centered. So, the first step is to identify your customers. Then, you have to uncover their needs to define the PMO's value proposition.
In my organization, for example, we can spot five customer groups that our PMO wants to serve:
Teams and team members
Suppliers and contractors
Once you know your customer groups, the next step is to identify their needs. These audience needs could look something like this:
Senior management: Reliable information that helps them make decisions
Project managers: Coaching, mentoring and support
Functional managers: Resource management
Teams and team members: Training and competence development
Suppliers and contractors: Logistical information and fair contract administration
Once we understand our stakeholders and their needs, we can develop a value proposition, which we will discuss in the next post.
Meanwhile, I invite you to review the following business model canvas and consider how this could be used to build a lean PMO:
Courtesy of Alexander Osterwalder and Yves Pigneur
For instance, does the PMO have revenue streams? If not, can we think of something better to substitute instead? What about channels and customer relationship -- do these apply to PMOs? Can a PMO develop alliances? Find out in my next post.