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