Organisational Competences (IPMA OCB)
What the domain tests
Organisational competences (IPMA OCB) shift the lens from the individual to the enterprise. The exam tests how an organisation governs projects, programmes and portfolios, how its management systems align, and how the PMO helps build durable organisational capability.
Core rules
- OCB describes what an organisation must be competent in, not what an individual must know. It complements ICB4 rather than replacing it.
- Governance sets direction, decision rights, accountability and assurance. Without clear governance, a PMO becomes a workaround.
- Management systems include processes, methods, tools, templates, roles and information flows. They must be integrated across project, programme and portfolio levels.
- Organisational competence is observable in consistent behaviour: prioritisation happens, benefits are tracked, risks are escalated, lessons are reused.
- The PMO is often custodian of OCB elements, but custodianship is not ownership; business leaders own governance outcomes.
- Assess before designing: use OCB to identify gaps, then sequence interventions by value and feasibility.
Worked example
An organisation has a portfolio register but no decision forum. An OCB assessment shows governance weak while methods are strong. The PMO does not rewrite templates; it establishes a portfolio board with a charter, decision thresholds and a standing agenda, then measures whether stage-gate decisions are made on time. Reasoning: the constraint was governance, not documentation, so the intervention targeted the organisational competence gap.
Traps
- Treating OCB as another individual certification syllabus.
- Copying a maturity model score without evidence.
- Designing processes that leaders do not use.
- Separating portfolio governance from programme delivery.
- Letting the PMO own benefits that business owners must own.