Loading
Loading
Issue 08 · 2026
An entity sends project managers on accredited courses and is then surprised that the portfolio did not improve. Maturity is not an individual certificate. It is five capability axes measured at work: concepts, knowledge domains, skill, tools, and professional presence. This report states what is measured before training, and when the deficit sits in the system, not in the person.
Executive brief
01
A course raises knowledge. Maturity shows in a decision taken in a bad week, not in an exam passed in a quiet one.
02
Five axes: concepts, knowledge domains, skills, tools, and professional presence. They are not reduced to a scheduling tool.
03
Before training, measure behaviour on a live project: scope, risk, a variance report, and a conversation with the indicator owner.
04
If the project has no charter and no indicator owner, training will teach a language that has no place in the meeting.
05
One person’s gap is a development path. The same gap in five managers is a system: authority, data, or cadence.
06
Professional presence — clarity, humility before the figure, and the ability to say “this is out of scope” — is measured. It is not taught on a slide.
07
The development path is bound to a project, not to a learning platform. A certificate ends the path if needed; it does not start it.
08
An institutional assessment tool is useful if it produces a decision: who is developed, who is moved, and what is fixed in governance.
01
Saudi organizations expand their portfolios with Vision programmes, capital projects, and internal transformation. Demand for a “project manager” rises, so training is bought as a quick fix. Six months later the close is still weak, reports are cosmetic, and scope grows because nobody says no.
The training did not fail because it was poor. It failed because the entity measured attendance, not behaviour, and because the manager returned to a system that does not ask for a charter or an indicator owner. Knowledge without an operating demand is forgotten.
02
Capability is assessed on five connected axes. Weakness on one shows in the meeting as general weakness. Do not collapse the axes into one score before you see where the hole is.
| Axis | What it means at work | A sign of weakness |
|---|---|---|
| Core concepts | Distinguishes project from operations, and output from effect. | Runs daily work and calls it a project. |
| Knowledge domains | Scope, time, cost, quality, stakeholders, risk. | Masters the schedule and ignores stakeholders. |
| Skills | Facilitation, scope negotiation, writing variance without cosmetics. | Sends minutes and does not close a decision. |
| Tools and techniques | Uses a tool because it serves a decision, not because it is available. | A crowded board with no management question. |
| Professional presence | Clarity, fidelity to the charter, and saying “out of scope”. | Pleases everyone, so the project expands until it fails. |
03
Choose a live project for each manager, not a case study. Watch four pieces of work across four weeks.
Is there a text that says what will not be done? If not, the course will teach a charter template that is filled once and forgotten.
Did the manager log a risk and close it with an action, or is the register a list refreshed before the committee?
A report that says: we are late for this reason, the option is this, and the cost if we ignore it. Not a green percentage with no sentence.
Can the manager name the objective’s indicator and its owner? If not, the problem sits above scheduling skill.
04
The manager knows the method and fails because the sponsor adds a demand every week. Fix the sponsor, not the certificate.
Actual cost does not arrive on time, so the report is invented. Train the data source first.
Committees meet and do not close. A skilled manager becomes a minutes coordinator.
The same person is project manager and operations manager for the same activity. The method will not unwind that conflict.
05
Individual maturity: one person’s ability to run a project on the five axes. Institutional maturity: charters, indicator owners, and a cadence that imposes the same behaviour on everyone. Training ten managers in an immature entity reproduces ten methods.
06
An assessment on the five axes from a live project, not from a self-survey alone.
Develop, move to a fitter role, or fix governance before any learning.
One behavioural target on the current project — such as a written monthly variance close — before any certificate.
After the behaviour appears. The certificate records capability; it does not create it.
07
An assessment that does not change a decision is a burden. Three legitimate uses: assign projects by capability, not availability; build an individual development path; and expose a governance gap if the pattern repeats.
An illegitimate use: a public ranking that humiliates the team, or an automatic bonus link from a single score that hides weak professional presence.
A precise tool shows where we stand. Courageous management decides what to do about standing there.
08
The report draws on axes common to project-manager capability assessment — concepts, knowledge, skill, tools, professional presence — as they appear in professional maturity tools and in how portfolios actually run inside Saudi organizations. It is a decision frame for HR and the project office, not a course syllabus, and not a substitute for field assessment.
The report does not recommend a named certificate and does not offer ready-made scores. Scores are built on the entity’s own sample.
NIRROV works with organizations that want strategy, operations, and digital delivery to move as one system.