Author: John Dean

Effective Change Management in the UK University Sector

Posted on | by John Dean

UK universities are managing funding pressure, shifting student expectations, digital delivery and estate decisions simultaneously – inside governance structures built for consensus rather than pace. Change in higher education is rarely blocked by a lack of good ideas. It is slowed by the number of people who legitimately need a say.

Five strategies, each with an institution that has made it work.

Engage stakeholders early, and keep engaging

Faculty, administrative staff and students all hold a legitimate stake, and a change that surprises any of them will be contested. The University of Suffolk ran a comprehensive curriculum review through advisory panels drawn from departments and student bodies. The collaboration produced ownership – and better programmes than a smaller group would have designed.

In a sector where academic autonomy is a principle rather than a preference, consultation is not a courtesy. It is the mechanism by which change becomes possible at all.

Use technology to widen access, not just to digitise

The Open University has spent decades demonstrating that online delivery can serve students whose commitments make attendance impossible. The lesson is not “put courses online” – it is that technology earns its place when it removes a barrier a particular student actually faces.

Build continuous improvement into the institution

The University of Manchester collects real-time student feedback on courses through digital platforms, which has driven immediate changes to teaching and content. The significant word is immediate. Annual survey cycles tell you what last year’s students thought; real-time feedback lets you fix it while they are still there.

Develop leaders who can actually run change

The University of Warwick runs a leadership development programme specifically equipping leaders with change management skills, which has underpinned campus expansion and new academic offerings. Academic leadership is usually earned through scholarship rather than programme delivery – so the capability has to be deliberately built, not assumed.

Put student wellbeing inside the change, not alongside it

The University of Edinburgh expanded mental health provision including 24/7 counselling and peer support, and saw measurable improvement in satisfaction and retention. Wellbeing is often treated as a parallel workstream. Retention data suggests it belongs in the business case.

Why this matters commercially

These strategies improve operational efficiency and academic provision, but the return runs through students: engaged students succeed, and successful students build the institution’s reputation. In a competitive sector, that is the outcome the change is ultimately for.

Change Specialists supports educational institutions through exactly this kind of transition – supplying the delivery capability while the institution keeps ownership of decisions that are properly academic.

See also Why NHS Transformation Needs Culture Change and How Independent Experts Elevate Internal Teams, or talk to us.

Further reading: Office for Students

Change Management in Financial Services: Regulation, Rates and Digitisation

Posted on | by John Dean

Financial services is among the most heavily regulated sectors in the UK, and among the fastest changing. Regulatory reform, interest rate movement and continuing digitisation each demand structural change – often at the same time, and usually against a deadline set by somebody else. Change management here is not an improvement discipline. It is a compliance one.

Regulatory change is constant, and non-compliance is expensive

The FCA’s operational resilience rules, in force since 31 March 2022, require firms to demonstrate they can prevent, adapt to, respond to, recover from and learn from operational disruption. That is not a documentation exercise – it is a demand for evidenced organisational capability.

The Basel III framework, phased in from 2023, requires substantial change to risk assessment and capital allocation. Failure to comply carries severe penalties, which puts a premium on getting the implementation right first time rather than iterating towards it.

What both have in common: the deadline is externally imposed and immovable. A programme that slips does not simply deliver late – it delivers a firm into breach.

Interest rate movement forces operational change at short notice

Bank of England rate decisions ripple through mortgage rates, loan structures, investment strategy and risk models. Each movement requires firms to recalibrate financial models, revise product offerings and re-confirm regulatory compliance – frequently within weeks.

The change management challenge is not the recalculation itself. It is doing it across multiple systems, teams and customer communications simultaneously, without disrupting service. Firms that handle this well have the capability in place beforehand; the ones that struggle are assembling it while the clock runs.

Digitisation changes infrastructure, skills and culture together

Digital adoption in financial services demands comprehensive change to IT infrastructure, team skillsets and organisational culture – not one of the three, all of them.

Open Banking, in force in the UK since 2018, requires banks to share customer data securely with third-party providers. That mandated significant change to data management practice and cybersecurity posture, and it is a good illustration of the pattern: a regulatory requirement that is really a technology programme, that is really a culture change.

Institutions that manage these transitions well convert a compliance obligation into improved operational efficiency and customer experience. Those that treat it as a box to tick get the cost without the benefit.

Where Change Specialists fits

  • Regulatory compliance – understanding and implementing new regulation, with the evidence trail regulators expect
  • Operational adaptation – adjusting internal systems and processes in response to rate movement and economic change
  • Digital transformation – from planning and execution through to training and culture

We supply the expert capability. Your teams keep control of delivery – which matters more in regulated environments than anywhere else, because accountability cannot be outsourced.

See also Mitigating Risk in Large-Scale Change and How Independent Experts Elevate Internal Teams, or talk to us.

Further reading: FCA: the Consumer Duty

Running an Effective PMO: Benefits, Practice and the Roles That Carry It

Posted on | by John Dean

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

The Importance of a RAID Log from a Programme Sponsor Perspective

Posted on | by John Dean

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

Measuring Success in Change Management: Beyond KPIs

Posted on | by John Dean

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

Mitigating Risk in Large-Scale Change: A Proactive Approach

Posted on | by John Dean

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

Understanding the 7 R’s of Change Management

Posted on | by John Dean

Change is constant, and leaders are routinely asked to steer transitions that shape the organisation’s future. The 7 R’s provide a framework for making sure a change has been properly thought through before it is committed to – and for knowing afterwards whether it worked.

1. Reason – why is the change being requested?

Whether it is driven by market dynamics, technology or an internal problem, identifying the reason is the first test of whether the change is necessary at all. When Nokia shifted focus from mobile phones to network infrastructure, the reason was unambiguous: intense competition and falling market share made a strategic pivot unavoidable.

Start with a detailed analysis of the underlying need, and engage stakeholders to build the case rather than announce it.

2. Risk – what are the risks involved?

Every change carries risk, and assessing it early is what makes mitigation possible. The Exxon and Mobil merger posed significant operational and cultural risk; proactive assessment was central to a smooth integration.

Assess with cross-functional teams, and build a plan that includes contingency and regular monitoring.

3. Resources – what is required?

Human, financial and technological. When Amazon launched AWS it required substantial investment in both technology and skilled people, planned in detail rather than discovered along the way.

Align resources to the change objectives and allocate enough to avoid the bottleneck you can already see coming.

4. Return – what is the expected benefit?

Evaluating expected outcomes is what justifies the change and makes it measurable afterwards. IBM’s move to a services-oriented model in the early 2000s was driven by an expectation of higher margins and renewed market relevance.

Define the metrics before you start, and make sure they align to strategic goals rather than programme convenience.

5. Responsible – who owns it?

Accountability decides whether anything happens. During General Electric’s digital transformation, named leaders were appointed to specific aspects of the transition, which put ownership somewhere concrete at every level.

Assign clear roles, and make sure those leaders are empowered and supported rather than merely named.

6. Relationship – how does it interact with everything else?

Understanding dependencies avoids conflict and duplicated effort. Microsoft’s integration of LinkedIn required careful coordination with existing projects to capture the synergies and avoid collisions.

Map the related initiatives and establish a mechanism to manage the interdependencies – they will not manage themselves.

7. Review – how is success measured?

Metrics and KPIs that evaluate the effectiveness of the change confirm whether the objective was met, and generate the insight that improves the next one. Starbucks revamped its store formats to improve customer experience, and measured it through satisfaction scores, sales data and market growth.

Build an evaluation framework using both qualitative and quantitative measures. See Measuring Success Beyond KPIs for why the qualitative half matters.

A blueprint, not a checklist

Worked through properly, the 7 R’s make a change initiative strategic and supportable rather than merely approved. The value is not in ticking each one – it is that a change failing any single R is a change worth stopping before it starts.

See also Programme Health Check and Mitigating Risk in Large-Scale Change, or talk to us.

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

Leveraging the MoSCoW Method for Effective Prioritisation

Posted on | by John Dean

Every project runs out of time before it runs out of requirements. MoSCoW is a structured way of deciding what actually has to be there, and of making that decision visible and agreed rather than settled quietly by whoever shouts loudest.

What MoSCoW means

  • Must have – critical. Without it the project has failed. Not “important” – failed.
  • Should have – important but not vital. Its absence significantly reduces value or usability, but the thing still works.
  • Could have – desirable. Enhancements whose absence does not affect success.
  • Won’t have this time – agreed to be out of scope for this release. Not rejected: deferred, deliberately and on the record.

That last category does more work than people expect. “Won’t have this time” is what converts an argument into a decision, and it is the reason MoSCoW reduces scope creep rather than merely describing it.

When to use it

  • Project initiation – sets expectations and defines scope by separating essential from deferrable before anyone is committed.
  • Requirement gathering – the process itself surfaces disagreement between stakeholders early, while it is still cheap.
  • Sprint planning – backlog prioritisation, so development effort goes to the critical features first.
  • Resource allocation – so the genuinely critical work is never the thing that ends up understaffed.

Five things that make it work

  1. Keep stakeholders in the room. Prioritisation done without them is a list, not an agreement, and it will be reopened later at the worst moment.
  2. Be realistic. Overcommitting to “Must haves” is the commonest way this fails – if everything is a Must, nothing is prioritised and the method has achieved nothing.
  3. Review regularly. Priorities move as a project proceeds; categories set once and never revisited stop describing reality.
  4. Define the boundary explicitly. Write down what separates a Must from a Should on this project, or the categories will mean different things to different people.
  5. Document the decisions and the reasoning. Not just what was agreed but why – which is what protects the decision when it is challenged three months later.

What it looks like in practice

A software development project

  • Must: user authentication and authorisation – secure access is not negotiable
  • Should: advanced analytics and reporting
  • Could: customisable interface themes
  • Won’t this time: third-party integrations, planned for the next release

A new system implementation

  • Must: data migration from the old system – without it there is no continuity of service
  • Should: staff training on the new system
  • Could: automated workflows
  • Won’t this time: integration with legacy systems being phased out anyway

Note what is a Should in the second example: training. That is a common and revealing call – the system works without it, but adoption may not. Where training lands in a MoSCoW list tells you a good deal about whether a programme has understood the difference between delivery and adoption.

See also Why Good Project Managers Are Not Always Good Change Managers, or talk to us.

Further reading: GOV.UK Service Manual: agile delivery

What Makes a Great Interim Specialist (And How to Spot the Wrong One)

Posted on | by John Dean

Not all interims are created equal. If you are hiring interim change or project expertise, the difference between a good one and a poor one is not visible on a CV – and it will cost you a quarter of the programme to find out.

Here is what actually separates them.

They hit the ground running

A good interim needs context, not handholding. They should be productive inside a fortnight – reading the landscape, identifying who actually makes decisions, and working out where the real constraints sit. If someone still needs managing after a month, you have hired capacity rather than capability.

They bring solutions, not just issues

Anyone can produce a RAG-rated list of what is wrong. That is the easy half, and it is often what a struggling programme already has plenty of. A good interim arrives with the problem and a recommended route through it, having already worked out what it would cost and who would need to agree.

They fit the culture, but are not afraid to challenge

This is the hardest balance. An interim who cannot read the organisation will be ignored. One who assimilates completely stops being useful – you brought them in precisely because they can see what people inside cannot.

The good ones earn enough credibility to be listened to, then spend it on saying the thing nobody in the room wants to say.

They focus on outcomes, not politics

Every large programme has politics. A good interim understands them well enough to navigate, but is not participating in them. They have no career to protect inside your organisation – which, handled properly, is one of the most valuable things about them.

They leave your team stronger, not dependent

This is the one that matters most, and the one least often checked for. The test is simple: when the interim leaves, can your team carry on?

A good interim transfers method, documents decisions, and makes sure someone internal owns each thing they set up. A poor one becomes indispensable – which looks like value while they are there and like a problem the day they leave.

The wrong interim

The warning signs are consistent:

  • Talks a good game but cannot evidence delivery when asked for specifics
  • Spends more time managing perceptions than moving the work forward
  • Creates dependency rather than capability
  • Presents problems upward without having thought about the answer

How we approach it

Change Specialists supplies proven change and project people into complex environments. Our test is the last one on the list: clients should be better equipped after an engagement than before it. We supply the capability; the client keeps the reins.

See how CS Flex works, or talk to us about the capability you need.

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

The Role of a Programme Director: Why Choosing the Right One is Critical

Posted on | by John Dean

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.

What the role actually demands

Visionary leadership

Exceptional communication

Resilience and adaptability

Decisiveness, coupled with humility

Stakeholder and relationship management

Commercial acumen

What the programme director role actually demands.

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