Category: Delivery practice

A Project Management Office is the backbone of consistent delivery – standardising practice, holding governance, and making sure projects serve the strategy rather than merely existing alongside it. Done well it raises the success rate of everything it touches. Done badly it becomes an administrative layer that reports on failure without preventing it.

What a PMO delivers

• Standardisation and consistency. One methodology across projects makes delivery predictable and comparable, and reduces the risk of each project inventing its own way to fail.
• Governance. Structured approval, monitoring and reporting, so projects stay aligned to strategic goals and meet regulatory obligations.
• Resource optimisation. The right people on the right projects at the right time, which prevents bottlenecks and lets the organisation respond when priorities shift.
• Risk management. A framework that identifies risk across the lifecycle, and a culture that surfaces it early rather than at the point it becomes an issue.
• Stakeholder engagement. Regular, transparent reporting – which is what builds the trust that lets a PMO deliver difficult news and be believed.

Five things that make a PMO effective

1. Clear objectives, aligned to the organisation

A PMO should not operate in isolation. It is the bridge between individual projects and the business objectives that justify them. Define its scope and objectives explicitly – that is also what makes its own performance measurable.

2. Robust, standardised methodology

Adopt and standardise on proven methods – PRINCE2, Agile, or a deliberate combination. The value is less in which one than in everyone using the same one, so that risk, progress and quality mean the same thing across the portfolio.

3. A dashboard giving real-time visibility

Leadership cannot make timely decisions on month-old information. A dashboard covering status, risk, budget and timeline – integrated with the systems already in use – turns reporting from a backward-looking exercise into something that can actually change an outcome.

4. A culture of continuous improvement

An effective PMO is not static. It learns from completed projects and revises its own practice – through audits, feedback and honest retrospectives. A PMO that never changes its own methods is not applying the discipline it enforces on everyone else.

5. Genuine stakeholder engagement

Communication is the single attribute most closely tied to project success. Regular engagement keeps everyone working from the same picture, and establishes the channels that matter most when something goes wrong.

The two roles that carry it

The PMO Manager sets strategic direction and owns the implementation of standards, governance and resource management. This role decides whether the PMO delivers value or merely produces documents.

The PMO Analyst provides the analysis, reporting and administration – tracking performance, monitoring risk, and maintaining compliance with the standards. It is the role that makes the Manager’s picture accurate.

Both need investment in training and development. A PMO enforcing methodologies its own people are not current in loses credibility quickly.

Where Change Specialists fits

We work with leadership teams to define PMO objectives, select and embed the right methodologies, build dashboards that integrate with existing systems, and establish the review cycles that keep a PMO improving. We supply the capability – your team keeps the reins.

See also Programme Health Check and The Role of a Programme Director, or talk to us.

Further reading: Infrastructure and Projects Authority

For organisations undertaking large-scale transformation the stakes are high, and the risks span operational, financial, regulatory and reputational ground at once. Without a structured approach, the result is disrupted workflows, unforeseen cost, and damage that outlasts the programme.

The risk landscape

• Operational disruption. New systems and processes hit productivity, particularly where adoption is slow or the design does not match how work actually happens.
• Financial risk. Cost overruns, unexpected resource demands and delay, which on a large programme can reach the point of challenging financial stability.
• Regulatory compliance. Major change can create compliance exposure inadvertently – a new system that does not align to the regulatory framework it operates under.
• Reputational impact. A failed or badly executed change damages stakeholder trust, and takes customer loyalty and employee engagement with it.

Five things that mitigate it

1. A comprehensive risk assessment at the outset

Examine risk across people, processes and technology before the work starts. Identify likely impacts, assess their magnitude, and decide the mitigation. Building a risk profile early is what allows resource and attention to go where they are actually needed rather than where the noise is.

2. Agility built into the process

Rigid processes stop an organisation responding to what emerges. Flexible planning and short iteration cycles let teams react to the unexpected without losing the destination – which reduces downtime and allows course correction while it is still cheap.

3. Stakeholder alignment

Transformation risk is usually human risk. A disengaged workforce or a misaligned leadership team will undermine the best-planned programme. Everyone from the executive to the front line needs to understand what the change is for. Alignment reduces resistance; shared purpose is what carries the work through the difficult middle.

4. Monitoring and control that works

Once underway, track progress, identify risks as they surface, and act. Detailed metrics keep a clear view of programme health, so intervention happens early rather than after the setback is visible to everyone.

5. Post-implementation evaluation

The end of a project is not the end of risk. A thorough review of what worked and what did not turns one programme’s experience into the next one’s advantage. Organisations that skip this step repeat the same mistakes at greater scale.

Managing risk, not avoiding it

Every transformation carries risk; the aim is not to eliminate it but to see it early and hold it. Organisations that plan for risk from the outset do not merely survive change – they come out of it more capable of handling the next one.

See also The Importance of a RAID Log and Programme Health Check, or talk to us.

Further reading: Association for Project Management: what is risk management

Success in change management is rarely a set of tick boxes. Numerical benchmarks are useful, but they routinely fail to capture the real impact of a change – particularly where it involves culture or restructuring. KPIs tell part of the story. They are not the story.

Why KPIs alone are not enough

KPIs are snapshots. They tell you whether deadlines were met, budgets held, adoption rates reached. What they miss is the softer half – morale, cultural alignment, whether behaviour actually changed.

A KPI might show high compliance with a new system. It will not tell you whether people feel empowered by it or resigned to it. It will not measure trust in leadership, or engagement after the programme team has gone. In our experience those intangibles decide whether a change lasts.

The qualitative half

• Cultural alignment. Does the change fit the organisation’s values? Do people recognise themselves in the new vision, or is it something being done to them?
• Stakeholder sentiment. Direct feedback from every level, through surveys, interviews or focus groups. It shows whether the change is building trust or spending it.
• Behavioural shift. How people actually work day to day. Are teams interacting, collaborating and deciding differently? That is the only real evidence adoption happened.
• Change fatigue. Long programmes cause burnout. Regular pulse surveys let leaders adjust pace and support before disengagement sets in.

The quantitative half, recalibrated

Numbers still matter. They just need to measure longer-term objectives rather than immediate ones.

• Adoption and proficiency. Not just who is using the new system, but how well – whether people are finding better ways to work with it, or the minimum that avoids attention.
• ROI, measured later. Assessed after a set period rather than at go-live, when the number is still theoretical.
• Engagement and retention. Rising engagement or falling turnover after a change is strong evidence it landed well.
• Productivity over time. Which distinguishes genuine improvement from a temporary spike followed by stagnation – a pattern worth watching for.

A blended approach

Use both. Together they tell you not only whether a change was implemented, but how it was internalised, experienced and sustained – which is what lets an organisation scale what worked and stop repeating what did not.

True success shows up across the organisation, from culture through to productivity. The aim is not that change happens, but that it endures.

See also Programme Health Check, or talk to us.

Further reading: Infrastructure and Projects Authority

A RAID log – risks, assumptions, issues and dependencies – is one of the few programme artefacts a sponsor should genuinely care about. Done properly it is the clearest single view of what could go wrong and who is dealing with it. Done badly it is a spreadsheet nobody opens.

Why it matters from the sponsor’s seat

Risks. Identified early enough to mitigate rather than absorb, with everything visible in one place and mitigation progress trackable.

Assumptions. Documented and revisited, so they can be tested as the programme moves rather than discovered to be wrong at go-live. Understanding which assumptions carry weight is what makes contingency planning possible.

Issues. Logged as they arise, assigned to a named person, and resolved rather than discussed.

Dependencies. Identified inside and outside the programme, so a delay elsewhere is assessed for impact rather than arriving as a surprise.

What each entry needs

Risks: description, potential impact, likelihood, mitigation plan, owner.

Assumptions: description, consequence if it proves false, the date it will be validated, owner.

Issues: description, effect if unresolved, priority, resolution plan, owner.

Dependencies: description, what happens to the programme if it is not met, due date, owner.

Every category ends with an owner. That is not administrative tidiness – an entry without a named owner is a note, not a control.

What a sponsor should look for

• Completeness and clarity. Entries complete, described without ambiguity.
• Regular updates. A log reflecting last quarter’s position is worse than none, because it looks like control.
• Ownership. Every entry owned, and owners actually held to it.
• Realistic plans. Mitigation and resolution plans that are actionable, and revised as things change.
• Prioritisation. Ranked by impact and likelihood, so attention goes where it matters rather than to whatever was logged most recently.

What good practice looks like

• Regular review meetings with key stakeholders present, not a log updated privately before a board.
• Integration with other tools – dashboards giving real-time visibility rather than a document someone remembers to circulate.
• Scenario planning for high-impact risks, with contingency worked out before it is needed.
• Proactive identification – and rewarding people for surfacing risks early rather than treating it as bad news.
• Transparency – accessible to everyone relevant, with changes communicated promptly.

That fourth point is the cultural one, and the one most often missed. If raising a risk is treated as pessimism, people stop raising them – and the log becomes a record of what everyone already knew.

Maintained properly, a RAID log gives a sponsor genuine control rather than the appearance of it.

See also Programme Health Check and Taking Over a Programme, or talk to us.

Further reading: Association for Project Management: what is risk management

Here is a truth many organisations overlook: a great Project Manager is not automatically a great Change Manager. Nor the reverse. They are two distinct skillsets, and conflating them is one of the most common – and most expensive – staffing mistakes in transformation.

Two different jobs

Project Managers drive tasks, timelines, budgets and deliverables. Their discipline is control: knowing what is due, what it depends on, what it costs, and what happens when one of those moves. A good one keeps a complex thing on the rails.

Change Managers engage people, manage resistance and secure adoption. Their discipline is influence: understanding who is affected, what it costs them personally, why they might not cooperate, and what would make them willing. A good one gets a change accepted rather than merely installed.

Both are demanding. Neither substitutes for the other. Someone brilliant at holding a plan together may have no instinct at all for why a department is quietly refusing to use the new system – and someone superb at bringing people with them may let the critical path slip while doing it.

The “bolted on at the end” problem

Too often we see programmes where change management is added late – a communications plan and some training in the final quarter, after the build is done and the go-live date is fixed.

By then the decisions that determine adoption have already been taken. Which processes changed. Whose job got harder. Who was consulted and who found out. A change workstream introduced at that point can only manage the reaction to those decisions, not influence them – and the outcomes are rarely achieved.

What good looks like

The two roles working together from the start, with equal standing. The Change Manager involved when scope is set, not when it is signed off. The Project Manager treating adoption as a deliverable rather than a downstream consequence of one.

That does not always mean two people. On smaller initiatives one person can genuinely cover both, and some practitioners are strong in each. But it should be a deliberate decision made on evidence – not an assumption that whoever is running the plan will handle the people side as well.

Get the right capability for both roles

If you are serious about the outcome rather than the milestone, staff both disciplines properly. Change Specialists supplies the right people for the right job – and is direct about which one you actually need.

See how CS Flex works, or talk to us.

Further reading: Association for Project Management: what is change management

Senior executives face constant pressure to make sure large-scale programmes deliver value, stay aligned to organisational goals and avoid costly overruns. A programme health check is a structured review that identifies risk, strengthens governance and keeps benefits on track.

Why health checks matter

From an executive seat, three things justify the exercise: strategic alignment, so the programme is still contributing to organisational priorities; risk mitigation, addressing problems early rather than explaining them late; and value realisation, tracking whether the benefits case is being delivered.

They address three recurring failures: programmes not delivering the outcomes promised, stakeholder misalignment causing delay and friction, and no real visibility of risk, finance or progress.

The methodology

1. Preparation – define objectives, gather documentation, identify stakeholders
2. Assessment – review governance, finances, risks and benefits through data analysis and stakeholder engagement
3. Reporting – a concise, actionable report with prioritised recommendations
4. Follow-up – monitor progress and support implementation of what was recommended

What it delivers, with numbers

Better decisions. A public infrastructure programme introduced empowered governance, removed decision bottlenecks and saved six weeks on critical milestones.

Proactive risk management. A digital transformation avoided £500k in rework by addressing supply chain risks identified during fortnightly reviews.

Value-driven outcomes. A retail chain’s benefits tracker underpinned a £5m revenue increase and kept effort aligned to strategic goals.

Seven things that make the difference

• Involve stakeholders early. A healthcare digitisation programme overcame resistance by involving end users in early design – faster adoption, fewer disruptions.
• Set measurable objectives. A marketing transformation replaced vague goals with KPIs such as “20% increase in website conversions”, which made tracking possible at all.
• Strengthen governance. A financial services programme introduced regular governance meetings and reduced bottlenecks.
• Use data, not opinion. Dashboards tracking cost variance and resource utilisation reduced delays by 15%.
• Focus on benefits realisation. A clear benefits plan secured £2m in savings tied to strategic goals.
• Build in continuous improvement. Retrospectives improved resource allocation and accelerated deployment by 20%.
• Communicate transparently. A government housing project secured additional funding after presenting its risks openly rather than burying them.

Two programmes, two outcomes

Early intervention. A £10m digital transformation was facing delays and budget concerns. The health check strengthened governance and clarified roles. It delivered successfully on a revised timeline.

Risk ignored. A £15m infrastructure programme overlooked early warnings about scope creep. It failed to deliver its objectives. The warnings were there; nobody acted on them.

Not a diagnostic – a strategic enabler

For senior executives, health checks are not merely diagnostic tools. They keep programmes on course, protect value, and turn findings into decisions. Prioritise them for critical programmes, and use what they surface to inform strategy rather than to file a report.

Change Specialists carries out programme health checks for UK public and private sector organisations, and holds places on the Crown Commercial Service DOS7 and G-Cloud frameworks. See also Taking Over a Programme, or talk to us.

Further reading: Infrastructure and Projects Authority

Stepping into a programme director role and inheriting an existing programme is daunting. The first few weeks are critical: establishing the real current state, identifying the gaps, and setting up what follows. This is the checklist we use – what to do, and what good and bad look like at each step.

1. Establish programme status

Run a health check: review scope, budget, timeline and key milestones; assess whether deliverables are genuinely on track; identify the high-priority risks. Meet the key stakeholders to understand their expectations and what success looks like from where they sit. Then read the history – previous status reports, minutes, and the rationale behind the major decisions.

Good looks like: clear, consistent progress reporting. Stakeholders share an understanding of the goal. Risks logged, tracked and mitigated.

Bad looks like: missing or inconsistent reports. Stakeholders expressing confusion or disagreement about the objective. Risks undocumented or ignored.

2. Establish governance

Identify the decision-making bodies and set the reporting cadence and escalation paths. Document who is accountable, responsible, consulted and informed, and make sure every governance body has terms of reference. Set the meeting structure – programme board cadence, and the purpose and frequency of stakeholder engagement.

Good looks like: documented governance with clear decision-making authority. Meetings that make decisions. Escalation paths understood before they are needed.

Bad looks like: no formal framework. Meetings that discuss but do not resolve. Decisions made without transparency or a record.

3. Key documents

Review – or create – the programme charter, business case, risk and issue log, programme plan, communications plan, stakeholder register and change control process.

Three matter more than the rest. The charter aligns everyone on purpose and direction. The risk and issue log is what turns problems from surprises into managed items. The change control process is what stops scope creep becoming budget overrun.

Good looks like: documents current, consistent and accessible. Decisions and their rationale recorded. Stakeholders actually referring to them.

Bad looks like: missing or outdated documents, no central repository, stakeholders unaware they exist.

4. Key roles

Establish or review the programme sponsor, programme manager, risk manager, PMO and workstream leads. The sponsor keeps the programme aligned to strategic priority – without an engaged one, nothing else on this list will save it. The risk manager reduces uncertainty. The PMO provides consistency and transparency in reporting.

Good looks like: roles clearly defined with capable people in them, all engaged and clear on their responsibilities.

Bad looks like: roles unclear, duplicated or unfilled. Poor engagement. Communication breaking down between people who should be talking daily.

5. Early wins

Identify and deliver quick wins to build momentum and confidence. Focus on the low-hanging issues and risks that have been lingering – the ones everyone knows about and nobody has owned.

Good looks like: stakeholders noticing tangible progress within weeks. Morale improving as long-standing problems get addressed. Risk levels stabilising.

Bad looks like: analysis paralysis. Stakeholders frustrated at the absence of visible progress. Risks continuing to escalate with no mitigation.

The difference is in the detail

Taking over a programme is a challenging but rewarding opportunity to bring clarity, alignment and momentum. Work through this systematically and you will establish the status, the governance and the documentation, with the right people in the right roles.

The difference between good and bad is usually in the detail: clear communication, robust governance, and managing proactively rather than reacting.

Change Specialists supplies experienced programme leadership into complex environments, including through the Crown Commercial Service DOS7 and G-Cloud frameworks. See also The Role of a Programme Director, or talk to us.

Further reading: Association for Project Management: what is programme management

Programmes are large-scale initiatives spanning multiple projects, stakeholders and organisational functions. At the helm sits the Programme Director – a role of considerable influence, carrying responsibility for whether the strategic objective is actually met.

A strong Programme Director can steer even an unwieldy initiative to a good outcome. The wrong one puts time, budget and outcomes at risk. So what actually makes a good one?

Visionary leadership

A Programme Director has to understand the big picture – not only the programme, but how it aligns to the organisation’s wider strategy. Good ones anticipate risks, market shifts and internal constraints while keeping sight of the end goal.

The skill underneath: strategic thinking and the ability to articulate a vision. Objectives have to be communicated so that people at every level are working towards the same thing.

Exceptional communication

Programme management hinges on communication. Directors deal with senior executives, external partners and delivery teams, and must explain complex ideas in a way that lands with all of them.

The skill underneath: influence, negotiation and emotional intelligence. Navigating organisational politics, handling conflict and motivating teams takes both empathy and firmness.

Resilience and adaptability

No programme goes precisely as planned. Whether it is a shift in market conditions or internal resistance, a good Programme Director keeps composure, adjusts course quickly and maintains confidence across the team.

The skill underneath: problem solving and staying solution-oriented under pressure. That is the clearest difference between an average Programme Director and an outstanding one.

Decisiveness, coupled with humility

Programme Directors make difficult decisions, often on incomplete data and with stakeholders pulling in different directions. They need to be decisive – and humble enough to seek advice, ask the experts, and admit when a pivot is needed.

The skill underneath: sound judgement and collaboration. Treating listening as a strength rather than a weakness is what separates effective decision-making from destructive rigidity.

Stakeholder and relationship management

Programmes depend on buy-in across a wide group. Building trust and making sure every party feels heard reduces friction before it becomes obstruction.

The skill underneath: networking, conflict resolution and diplomacy. Balancing competing needs requires someone who can act as a bridge-builder.

Commercial acumen

Programmes represent significant investment. Directors need to understand the financial, commercial and regulatory dimensions of what they are running – which is what delivers value for money, budget discipline and compliance across the lifecycle.

The skill underneath: financial literacy, risk management and market awareness.

From good to high-performing

The attributes above describe who to look for. What separates a high performer from a merely competent Programme Director is narrower than it sounds – and it is behavioural, not technical. It comes down to three things: the questions they ask, the environment they create, and how they handle people.

They ask the right questions

High performers treat meetings as opportunities to uncover insight, align people and remove obstacles – not to receive status updates. Five questions do most of the work:

• “What does success look like for this initiative?” – clarifies the objective and aligns the team on it
• “What are the risks we are not talking about?” – exposes the blind spots people are avoiding
• “How can I support you in achieving this?” – shifts the Director from inspector to enabler
• “Are we solving the right problem?” – challenges the assumption everything else rests on
• “What will this decision mean for our stakeholders?” – keeps the perspective human, not just operational

They create the right environment

A programme succeeds on more than tasks and milestones. High performers build psychological safety, so people raise concerns and challenge assumptions without fear. They break down silos so teams work to shared goals rather than isolated ones. They champion the programme upwards to keep leadership aligned. And they treat failure as learning rather than blame, which is the only condition in which people will try something different.

They demonstrate genuine soft skills

Empathy – actually listening, and understanding the pressure a team is under. Influence – building consensus in politically charged environments. Emotional intelligence – managing their own reactions while staying attuned to everyone else’s. And patience, because transformational change takes longer than anyone plans for, and teams need to stay motivated across the whole of it.

Becoming a high-performing Programme Director is not about having all the answers. It is about asking better questions, creating the conditions in which good work is possible, and leading people who are being asked to change how they work.

The bottom line: invest in the right talent

The role is not for the faint-hearted. It demands a balance of hard and soft skills, vision and pragmatism, leadership and humility. Organisations that invest in the right Programme Director gain a real edge – better outcomes, better stakeholder relationships, and a programme that stays aligned to the strategy that justified it.

For complex transformation, there is no substitute for seasoned programme leadership. See how CS Flex supplies it, or talk to us.

Further reading: Association for Project Management: what is programme management