Most programs do not fail because of the wrong methodology. They fail because nobody owned the structure — and the people accountable for delivery ran out of bandwidth before the program ran out of problems.
Programs that produce watermelon reporting — green on the outside, red underneath — are not hiding incompetence. They are hiding a structural problem: the governance, reporting, and escalation infrastructure was never properly built, so the people accountable for delivery are managing perception instead of reality. Missed gates follow. Escalations accumulate and consume leadership bandwidth. Teams stop surfacing problems because nothing happens when they do.
I'm Anthony Thompson. My career has been spent embedded inside major transformation programs — not as the Program Manager, but as the specialist carrying the load that makes the Program Manager's role viable. My prior program management experience means I understand exactly where that bandwidth runs out, and what needs to be in place before it does.
I work as a span-breaker. The role exists at the intersection of governance design, structured reporting, stakeholder management, and on-the-spot problem solving — the territory that exceeds a single PM's capacity on any complex program. I carry that load so the PM can lead.
"After 20 years inside major programs, the pattern is consistent: the methodology is rarely the problem. Getting people to actually do things differently — and stay that way — is where it gets hard. That's the work."
— Anthony ThompsonI am familiar with Agile, Scrum, Waterfall, and the full range of delivery methodologies. In practice, the methodology is rarely what determines whether a program delivers. Disciplined execution, clear accountability, and the human work of getting teams to operate differently under pressure — that is what determines it.
A consistent side effect of well-structured embedded support: Program Managers have fewer escalations reaching them, teams develop capability under delivery conditions, and the program reflects well on the people accountable for it. That is not the primary objective, but it is reliably what happens.
Remote-first. Location agnostic. The programs I work in are global. Effective embedded support does not require physical presence — it requires structured communication, disciplined follow-through, and the professional writing and verbal communication skills to resolve barriers and influence outcomes across distributed teams. AI tooling is applied practically where it adds genuine value to program delivery.
Available for direct engagement, as overflow capacity for consulting firms requiring specialist program support, or through Expert360.
Governance frameworks, reporting architecture, status pack design, risk and issue registers, and the meeting and communication cadence structures that give leadership accurate signal — not managed perception. Includes structured team routines designed to drive pace and urgency rather than add overhead.
Structured stakeholder engagement, workstream accountability tracking, leadership decision support, and escalation management. Communication planning and execution — written and verbal — that surfaces real issues and resolves barriers rather than managing them upward. Workshop facilitation where cross-functional problem solving is needed.
Cutover planning, checkpoint tracking, Business Continuity Planning scenario development, hypercare governance, and the structured coordination that converts a go-live from a crisis management exercise into a managed transition. Project execution and coordination across interdependent workstreams.
UAT strategy positioned at the business and technology interface — functional and non-functional requirements, testing planning, and business process readiness. This is the strategic piece where programs most commonly fail. Early rigour here — before the go/no-go decision — pays the highest dividend. Prioritisation and decision-making frameworks applied throughout.
Change impact assessments, stakeholder engagement strategies, and communication planning and execution — particularly where OCM accountability has drifted or is inadequately resourced. Professional written and verbal communication embedded throughout, including leadership communication that supports effective decision making and sustained adoption.
A key specialisation: working with less experienced project and program managers to develop the interpersonal effectiveness and technical delivery skills required for high-pressure initiative environments. Independent program diagnostics where governance failure, reporting drift, or stakeholder misalignment require an objective external view and a structured recovery path.
The governing principle: PMO provides the framework and the tracking. Workstreams own execution. This distinction — consistently maintained — is what separates embedded support from another layer of overhead. This is not a handle-turning role. The value is realised in complex programs where structured thinking and sound judgement determine the outcome.
Book a Call →Most engagements begin through a direct referral. If you were sent here by someone, that is the right starting point. A 30-minute conversation will establish whether the fit is right and what the engagement structure should look like.
Available for direct engagement, as overflow capacity for consulting firms requiring specialist embedded program support, or through Expert360. Remote-first delivery across global teams. Part-time or full-time. Typically 3 to 6 month engagements, with portfolio-scale capability across single or multiple concurrent programs.
Work directly with Transforming Performance. Typical engagements are 3 to 6 months, part-time or full-time, scoped to program need. Client references available on request.
Available as bench capacity for consulting firms requiring specialist embedded program support on client engagements. Discreet, professional, experienced at operating within firm structures.
Listed on Expert360 for organisations sourcing verified independent specialists through the platform.
Remote-first. Location agnostic. Global teams across multiple time zones supported. No requirement for on-site presence — structured communication and disciplined follow-through deliver the outcome.