PMO Assessment
Assess the environment, not just the PMO
An assessment establishes a factual baseline of current capability so design and improvement are evidence-based. Scope it deliberately: the PMO itself (services, skills, processes, tools, perception), the delivery system it serves (project, program, and portfolio practices, data quality), and the surrounding environment (strategy clarity, governance, culture, sponsor behaviour).
Methods include document review, sampling of processes and artefacts, data quality checks on schedules and benefits registers, structured stakeholder interviews and surveys, facilitated workshops, and benchmarking against a reference model. Maturity models such as OPM3 or P3M3-style frameworks give a common language, but they are diagnostic instruments, not targets.
Traps. First, confusing capability (the organization can perform a practice) with maturity (it performs it consistently and measures it). Second, treating a maturity score as the objective - reaching a higher level is meaningless if it fixes no real problem. Third, interviewing only sympathetic stakeholders and calling it consensus. Fourth, ignoring data quality, which makes every performance metric suspect. Fifth, letting the assessment become an audit of individuals rather than a system diagnosis.
Worked example. A PMO scores low on benefits management. Before building a training programme, the assessment asks why: are benefits never defined at approval, or defined but never tracked? If the latter, the gap is a governance interface, not a skills gap - and the fix is a gate requirement, not a course.
Rule of thumb: for each gap, state the observed evidence, the consequence in business terms, and the root cause. A gap with no consequence is a preference, not a priority.