Skip to content

Life. Adventure. Consulting. Technology.

Healthcare

An IT Delivery Portfolio of 5 Programmes and 24 Projects

Five programmes, twenty-four projects and roughly £40 million, spanning infrastructure, clinical systems, telephony and cyber security — run under one governance model in a healthcare environment.

Five programmes. Twenty-four projects. Approximately £4 million. Infrastructure modernisation, clinical systems, telephony transformation and cyber security, all running at once inside a healthcare organisation where the day job is patient care.

Governance first

Twenty-four projects across that many technology domains cannot be held together by goodwill and status meetings. I established a portfolio governance framework: a portfolio board with senior stakeholder representation, standardised reporting across every project, and clear escalation paths for risk and issue.

That replaced fragmented arrangements where each area reported differently, and gave leadership a single coherent view of IT delivery for the first time.

Infrastructure modernisation

The infrastructure programme addressed critical technical debt across servers, storage and network. I led prioritisation on risk, business impact and interdependency with the rest of the portfolio — server refresh and virtualisation, storage consolidation, and network upgrades to carry growing clinical application demand. Each project was sequenced to minimise disruption to clinical services while delivering measurable improvements in reliability and performance.

Clinical systems

Several projects enhanced clinical information systems, from upgrades and new module deployments to integration improvements between applications. I worked closely with clinical stakeholders so that changes aligned with clinical workflow and implementation schedules respected the operational demands of patient-facing services, with dedicated clinical leads embedded in project teams throughout.

Telephony

The telephony programme migrated voice communications from legacy analogue systems to modern digital telephony, added unified communications, and improved call handling for patient-facing services. The logistics across multiple sites were the hard part: critical communication channels, particularly those supporting emergency operations, had to stay up throughout.

Cyber security

Security ran as a theme across the portfolio rather than only in the projects named after it — endpoint protection, vulnerability management, awareness training and incident response capability. I made sure security considerations were embedded in every infrastructure and systems deployment in the portfolio, so new estate arrived secure by design rather than being retrofitted later.

Resource and budget

A £4 million portfolio needs financial discipline and honest resource allocation. Portfolio-level resource planning surfaced shared requirements and conflicts early enough to rebalance proactively. Financial tracking was standardised with monthly forecasting and variance analysis, which gave early visibility of budget pressure and made trade-off decisions informed rather than reactive when priorities moved.

Communication

The stakeholder community spanned clinical departments, corporate functions and executive leadership, and they do not need the same information. Reporting was layered accordingly: detailed operational reporting for programme leads, summary dashboards for senior leadership, and targeted updates for the clinical stakeholders affected by specific projects. Everyone got what they needed without drowning in what they did not.

What changed

The portfolio delivered substantial improvement across infrastructure reliability, clinical system capability, communications and cyber security — within budget, and with minimal disruption to critical healthcare services.

Consistent standards across all twenty-four projects are what made that possible. At this scale, the governance is not overhead sitting on top of the delivery. It is the thing that makes the delivery survivable.

Work of this kind usually starts with a conversation about what is actually going wrong.

Discuss a project