Project Support Offices: Structure, Growth, and Innovation
This paper provides a comprehensive overview of Project Support Offices (PSOs), distinguishing them from traditional project management offices and examining their types, missions, and structural configurations. The paper covers five structural models — virtual/real, temporary/permanent, reactive/proactive, enterprise/functional, and hub-and-spoke — before outlining the four key elements required to establish a PSO. It then traces the five phases of PSO growth and maturation, from an informal initial level through a fully optimized continuous-improvement stage. Finally, the paper examines how PSOs encourage organizational innovation by fostering collaborative cultures, enabling early-stage strategic thinking, and promoting adoption of advanced technology.
- Introduction to Project Support Offices: Defines PSOs and outlines three core types
- Mission of PSOs: Three mission statements aligned to PSO types
- Structure of PSOs: Five structural models for organizing PSOs
- Methods to Establish Project Support Offices: Four key elements for PSO establishment
- Growth and Maturation of PSOs: Five-phase PSO maturity model explained
- Role of Project Support Offices in Encouraging Innovation: How PSOs foster organizational innovation
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- The paper systematically classifies PSO types, missions, and structures using clearly numbered lists, making complex organizational concepts easy to follow.
- Each section maps directly onto a practical dimension of PSOs — from design to establishment to maturity — creating a logical, progressive argument.
- The concluding section on innovation ties the technical content to a broader strategic rationale, giving the paper a clear applied purpose beyond pure description.
Key academic technique demonstrated
The paper demonstrates effective use of classification and comparison as an academic technique. Throughout, it introduces a category (e.g., PSO type or maturity phase), defines its distinguishing features, and contrasts it with adjacent categories. This method keeps the argument organized and ensures each concept is anchored to its unique characteristics before the next is introduced.
Structure breakdown
The paper opens with a definition of PSOs and a typology of three kinds. Subsequent sections address mission statements, five structural models, establishment methodology, and a five-phase maturity model. The final section pivots to strategic value by analyzing PSOs as drivers of organizational innovation. The structure moves logically from descriptive foundations to prescriptive and evaluative analysis, typical of an undergraduate management or project management course paper.
Introduction to Project Support Offices
A Project Support Office (PSO) is different from a project management office. A PSO can be understood as a provisional or long-lasting organizational unit that provides a range of services to support project teams accountable for a defined group of projects (Wysocki, 2011). There are three kinds of PSOs.
The first is the directive PSO, in which project managers are administratively linked to the PSO and are allocated to projects from it. In general, this structure is designated for enterprise-wide projects. The second is the controlling PSO, in which the components, templates, and procedures are all provided by the PSO, and all project managers — regardless of their resident department — are expected to use them. The third is the supportive PSO, which provides whatever assistance and specialist expertise the project manager or team members may require when requested (Wysocki, 2011; Pemsel and Wiewiora, 2013).
Mission of PSOs
There are three possible mission statements, corresponding to the three types of PSOs. The first mission is linked to the directive PSO: to provide general management and administrative support to a defined program. This is the characteristic mission statement of a PSO providing administrative support for a program comprising a set of related projects. Once the program is complete, the PSO disbands.
The second mission statement is linked to the controlling PSO: to establish and monitor compliance with the project management methodology. The third mission, linked to the supportive PSO, is to provide an extensive set of support services to all project managers on an as-requested basis (Wysocki, 2011).
Structure of PSOs
Project Support Offices can be organized according to several different structural models, each suited to different organizational contexts.
A virtual PSO carries out all the functions and roles of any other PSO; however, its personnel are assigned to business units rather than centralized. These PSOs are largely available when their services are needed and do not perform routine functions. Aside from a director or an administrative support individual, the virtual PSO does not include any other budgeted staff. By contrast, the real PSO has a budgeted workforce of professionals, which may include numerous project managers. Staff perform a variety of routine roles — for instance, project appraisals and software assessments. These appraisals are an effective means of monitoring adoption of the methodology and identifying best practices. The real PSO's strength lies in providing reliable project support services to project teams (Wysocki, 2011).
Temporary PSO structures are created to serve the administrative and managerial needs of large projects. These projects are broken down into smaller sub-projects, each assigned a project manager who is accountable to the program manager via the program office. All other PSO structures are permanent and provide services to a continuously changing portfolio of projects (Hill, 2013).
The reactive PSO structure closely aligns with the virtual PSO model, while the proactive PSO structure aligns with the real PSO model. The real PSO can be proactive because it has the workforce to perform leadership roles across a range of projects, thereby enhancing project management processes and practices. The reactive PSO, lacking such a workforce, simply responds to requests for assistance (Pemsel and Wiewiora, 2013).
PSOs within an organization can operate at either the functional or enterprise level. At the functional level, PSOs are generally accountable to an enterprise PSO (where one exists) and provide services within a specific discipline. At the enterprise level, PSOs must serve all disciplines. They are typically well-funded and well-staffed, have visibility at the project portfolio level, and may participate in strategic planning roles (Wysocki, 2011).
PSOs can adopt a hierarchical structure, particularly in large organizations. At the central office — the "hub" — a high-level enterprise PSO sets policy and standards for the entire organization and reports to a C-level executive. Business unit PSOs serve different functional areas and take their policy and standards direction from the hub (Pemsel and Wiewiora, 2013). The hub typically comprises strategically oriented senior project executives. At the end of each "spoke," divisional PSOs carry out operational roles for the unit they represent. Within the framework established by the hub, each divisional PSO has the freedom to develop and implement its own policies and standards, provided they remain compatible with the hub's requirements (Rosenhead, 2015).
Always verify citation format against your institution’s current style guide requirements.