PMO Setup and Design
Mandate before org chart
A PMO is a service organization, so design begins with the demand it must serve: organizational strategy, portfolio complexity, culture, regulatory load, and the decision-making gaps leaders actually experience. Capture this in a mandate or charter stating purpose, scope, authority, services, customers, funding, and success measures. Without an explicit mandate, the PMO drifts into work nobody asked for.
Key design choices:
- Type/role - a continuum from supportive (templates, coaching, advice), through controlling (compliance, gate reviews, standards enforcement), to directive (PMO staff directly manage projects). Type is a design decision about authority, not a measure of maturity.
- Operating model - centralized, federated/decentralized, hybrid, or a center of excellence that sets standards while delivery stays in business units.
- Placement - the reporting line determines whose priorities the PMO serves; too low limits authority, too high loses touch with delivery.
- Service catalog and staffing - each service needs an owner, a competency profile, and a cost.
- Governance interfaces - portfolio, program, and project boards, plus finance and audit.
Traps. Questions often imply that a more controlling PMO is a better PMO; in reality a mismatch between mandate, authority, and culture is the classic failure mode. Another trap is designing structure before assessing needs, or copying a model from another organization. Watch also for the assumption that a PMO must launch every service at once - phased introduction is usually safer.
Rule of thumb: form follows function. Derive services from assessed need and mandate, then choose structure, placement, and staffing to deliver them; pilot and expand rather than launch big.