The Project Support Office: Build It Right, the First Time

This blog was updated March 2025

Here's a trick question: What do you call a group that supports project management in an organization?

If you answered Project Support Office (PSO), Project Management Office (PMO), Program Management Office, Hybrid PMO, Portfolio Management Office or an Enterprise Project Management Office...you are right.

It doesn't really matter what you call it. What truly matters is what you deliver. What products and services are you providing? If you're consistently delivering value and benefits to your organization, that's what we call success. And the place to lay the groundwork for that success is ... from the ground up.

For example, when you're developing and implementing a PSO—an organizational entity primarily designed to support a key project or program—you need to consider the essentials: processes, people, tools, and technology. It's just like with any project management function.

Here are a few tips from my experience:

• Sponsorship - Just like any project, a PSO or any project management group needs a strong sponsor, a real champion in your corner. This person needs to know the organization inside and out and have the influence to help the PSO thrive.
• Involving the Right People - There are two key groups of people who are essential to your success. First, there's the PSO team itself. These are the folks who work directly with your "customers" – the project managers and project teams. They need the skills and know-how to provide effective support. Ideally, they've been project analysts or project managers themselves, so they've "walked the walk." They should be skilled in facilitation, process development and improvement, and have a good understanding of PM tools. The second group is that core team of "customers" who will help you develop the PSO's processes, tools, and techniques. This not only gets you the buy-in you need, but it's also a crucial part of effective organizational change.
• Process - One of the biggest mistakes I see is over-engineering the processes. Many of us remember those days of massive process manuals that filled up binders, but those days are gone. Today, processes need to be lean and adaptable. You don't want to create a process only to hear someone say, "Can we get the light version?"
• Technology - A solid technology strategy is a must for any PSO. Without it, you'll end up with a hodgepodge of project management tools – spreadsheets, project management software like Microsoft Project and Open Workbench, and even enterprise project/portfolio management systems. A technology strategy helps you choose the right tools to support your processes. Never buy technology and then try to make your processes fit it! Instead, build your processes first and then select the technology that best fits those processes.

Bottom line – Build it right, and you'll succeed.

FAQs

What are the key differences between a PSO and a PMO?

While the terms are often used interchangeably, there can be subtle differences. Generally, a PSO focuses on providing direct support to project managers and teams, while a PMO might have broader responsibilities like setting standards, managing resources, and overseeing governance.

How does a PSO support project management within an organization?

A PSO provides a range of services, such as developing templates and tools, providing training and coaching, facilitating collaboration, and offering administrative support. This allows project managers to focus on delivering their projects successfully.

What are some common challenges in implementing a PSO, and how can they be overcome?

Some common challenges include resistance to change, lack of buy-in from stakeholders, and difficulty in demonstrating value. These can be overcome by strong leadership, effective communication, and a focus on delivering tangible benefits to the organization.

How can I ensure the success of my PSO?

Success factors include strong sponsorship, a skilled and experienced team, efficient processes, appropriate technology, and a focus on continuous improvement. Regularly evaluating the PSO's performance and making adjustments as needed is also crucial.

What are some examples of how a PSO can add value to an organization?

A PSO can improve project delivery rates, reduce costs, increase efficiency, and enhance stakeholder satisfaction. It can also contribute to building a stronger project management culture within the organization.

How can I measure the effectiveness of my PSO?

You can measure effectiveness through metrics such as project success rates, on-time and on-budget performance, stakeholder satisfaction, and the number of projects supported. It's important to establish clear goals and track progress towards them.

What are some resources available to help me establish and manage a PSO?

There are many resources available, including books, articles, online communities, and professional organizations like the Project Management Institute (PMI). You can also seek guidance from experienced consultants who specialize in setting up PSOs.