Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Project management and PMO

Setting up and strengthening a PMO

A useful PMO does not produce reports: it gets decisions made. Our consultants help put in place the governance, rituals and indicators that make your projects clear and open to arbitration.

Our principles

  • Governance suited to your maturity
  • Indicators that trigger decisions
  • Skills transfer planned from the outset
In brief

A PMO (Project Management Office) is the structure that gives leadership a reliable view of its projects and the means to make trade-offs between them. Management Square consultants help design and deploy it, or strengthen it, according to your level of maturity, with one objective: decisions taken in time on accurate information.

Scope

How we contribute

  1. Maturity assessment

    Review of your management practices: roles, rituals, tools, quality of the information reported. We identify what is really holding back decision-making before proposing anything.

  2. Designing the target PMO

    Choice of model (project, programme or enterprise PMO), scope, mandate and service offering. A PMO without a clear mandate quickly becomes a project secretariat.

  3. Governance and committee structure

    Governance bodies, roles and decision paths: who arbitrates what, on what basis and at what pace. We streamline the existing committee structure before adding any new body.

  4. Indicators and dashboards

    A small set of reliable indicators on timelines, costs, risks, workload and expected value, built from data your teams already produce.

  5. Management tooling

    Framing, selection and configuration of the project and portfolio management tool, starting from your processes rather than from a vendor's feature catalogue.

  6. Operational PMO

    Strengthening your teams with experienced PMO staff on a programme or a portfolio, with transfer of method so that the organisation remains autonomous when we leave.

Page contents

Why so many PMOs disappoint

Many organisations already have a PMO, and many complain about it. The criticism is almost always the same: the project office collects, consolidates and circulates, but nothing changes in the way projects are decided. Project managers see it as an administrative burden. Leadership sees it as yet another dashboard, rarely up to date on the day it is needed.

The cause is rarely the competence of the people. It lies in the mandate. A PMO asked to “monitor projects” produces monitoring. A PMO asked to inform three specific decisions (which projects to launch, which to strengthen, which to stop) organises itself around those decisions, and everything else follows: the information to collect, the frequency of check-ins, the format of reports.

This is the starting point of our work. Before talking about method or tools, we clarify with you the decisions the PMO must make possible and the level of the organisation at which they are taken.

The three PMO models and how to choose

There is no single PMO model, but a family of structures whose role varies according to the power given to them.

  • The supportive PMO provides templates, good practice and help on request. It suits organisations where projects are autonomous and the priority is to harmonise practices without adding weight.
  • The controlling PMO checks the application of a common framework: milestones, mandatory deliverables, phase reviews. It suits situations where differences in practice create risks or prevent consolidation.
  • The directive PMO manages projects directly and assigns project managers. It suits critical programmes, when leadership wants single accountability for delivery.

To this first reading is added that of scope: a project, a programme or the entire portfolio. A directive enterprise PMO has nothing in common with a supportive PMO attached to a single project. The choice is made on simple criteria: the maturity of project managers, the risk level of the portfolio, the culture of the organisation and, above all, the real support of leadership. For a detailed definition of these notions, see our glossary entry on the definition of the PMO.

Our approach: start small, on real decisions

Our consultants work within your teams; decisions remain yours. We advise against deploying a complete framework in one go. A methodological framework delivered as a single block is often bypassed. We prefer a path in three stages.

A short assessment. Interviews with leadership, project managers and business teams, review of existing governance bodies and materials. The findings fit in a few pages: what works, what is missing, and the action priorities.

A minimal foundation on a pilot scope. A common project sheet, a risk register, a progress check-in at a fixed pace and a dashboard reduced to the essentials. The aim is for a first steering committee to decide on the basis of this foundation, and for everyone to see the difference.

Gradual extension. Widening the scope, adding resource and dependency management, then linking with project portfolio management when the organisation is ready to make trade-offs between projects rather than simply monitor them.

Throughout the engagement, we work in pairs with your teams. A PMO designed by consultants and handed over to a team that did not build it does not survive their departure.

What a good PMO dashboard contains

The temptation is to measure everything. A useful dashboard answers few questions, but it answers them reliably.

  • Where are we? Progress against committed milestones, not declared percentage of completion.
  • What are we risking? The few major risks, their owner and the action under way.
  • Do we have the means? Effort consumed and effort remaining, pressure on scarce skills.
  • Is it still worthwhile? A reminder of the expected value and the assumptions on which it rests.
  • What needs to be decided? The trade-offs requested of the committee, framed as choices.

The last line is the most important. A dashboard that asks for no decision is an activity report. When contractual commitments weigh on the project (penalties, payment milestones, obligations of result), we recommend including them in the risk register on the same footing as technical risks.

The mistakes we help you avoid

  • Tooling before organising. A portfolio management tool deployed on unclear processes freezes the disorder and discourages teams.
  • Asking the same of every project. A three-month project and a three-year programme do not justify the same level of formality. We propose a framework with several levels of requirement.
  • Confusing PMO with control. A project office perceived as a police force only receives tidied-up information. It must provide a service to project managers in order to obtain honest data.
  • Forgetting change. Setting up a PMO alters working habits and balances of power. We address this dimension with the methods of change management.

How to measure the success of a PMO

Success is not read in the number of reports produced. From the framing stage, we agree with you on a few observable signs: the share of projects whose status is known and up to date, the time between a problem appearing and the decision that deals with it, the share of committee decisions actually applied, and the perception of the project managers themselves. This last point is often neglected. A PMO that project managers call on spontaneously has already won the essential battle.

These indicators are tracked during the engagement and after we leave. They also serve to adjust the set-up: a PMO is a living structure, whose mandate evolves with the maturity of the organisation.

Typical work

What our consultants contribute to

Assessment report

Findings, maturity level and action priorities ranked by effort and by benefit.

PMO charter

Mandate, scope, service offering, roles and operating rules approved by leadership.

Management kit

Templates for project sheets, committee minutes, risk registers and dashboards.

Skills development plan

Training and support pathways for project managers and the PMO team.

Insights

Further reading

All insights
Milestones, trains or hybrid: which IT programme management model should you choose?

An IT programme management model describes the way a programme plans, measures progress, allocates decisions and organises its teams. Management Square compares here three models in common use (milestones and work packages, trains or value streams, hybrid) on these four dimensions, and indicates the situations each one suits best.

Read the analysis
The signs of poorly prepared change management, spotted at the stages of an IT project

Change management in an IT project brings together the actions that prepare the users of an information system to work with it, from scoping to the aftermath of go-live. Management Square shows here how to spot, document by document, poorly prepared change (users absent from scoping, impacts discovered in testing, unnamed change agents, go-live without support), and what remains to be done.

Read the analysis
When to hold a project lessons-learned review, and when to forgo it

A project lessons-learned review is the examination, by those who took part in it, of what a project or a phase teaches for the future: end-of-project review, retrospective in an agile approach, post-incident review. Management Square offers a decision guide here: when to hold it, what to focus it on, whom to bring together, which conclusions to keep and to whom to entrust the follow-up, and when to forgo it.

Read the analysis

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is a PMO for?

A PMO gives leadership a consolidated and reliable view of projects, standardises management practices and prepares trade-offs. Its usefulness is measured by the decisions it makes possible: launching, redirecting, strengthening or stopping a project at the right time.

What is the difference between a project, a programme and an enterprise PMO?

A project PMO supports a single project, often a large one. A programme PMO coordinates a set of projects linked by a common objective. An enterprise PMO covers the organisation's entire portfolio and links projects to strategy. The right model depends on your size, your maturity and the level of decision you want to inform.

How long does it take to set up a PMO?

The duration depends on the scope and the starting point. We proceed in stages: a short assessment, a first foundation of governance and indicators on a pilot scope, then gradual extension. This approach produces visible results before the full deployment is complete.

Do you need a tool to start a PMO?

No. A tool accelerates a PMO that works; it does not replace absent governance. We recommend first stabilising the roles, rituals and indicators, then choosing the tool that serves them.

Can Management Square provide PMO staff to strengthen our teams?

Yes. We work on PMO design as well as on operational support for a programme or a portfolio. In both cases, the transfer of skills to your teams is part of the engagement.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.