Governed Brenntag's global IT/OT network segmentation program through HCLTech, separating OT and production environments from corporate IT across a worldwide estate.
Coordinated site stakeholders, Smart Hands, Fortinet procurement, delivery and installation. 152 sites across 19 countries delivered before the green program transitioned to an internal resource.
Led program governance across twelve workstreams during the E.ON to MVM carve-out, covering the migration of 2.5 million customer records, SAP IS-U, BW and PI, an Avaya contact centre and IT service transition.
Defined scope and deliverables, coordinated cutover planning across seven go-lives, governed risks and dependencies, and provided executive-level reporting.
I started in IT close to the ground supporting users, operating infrastructure, troubleshooting systems and learning what actually happens when technology meets the real world.
Over the next two decades, the problems got bigger. So did the teams, budgets, technologies and expectations.
Today, I lead complex IT programs and projects across countries, companies and technical domains. But the technical background never disappeared. I still want to understand what's being built, why it's being built, what can go wrong and what the people doing the actual work need to get it delivered.
Understand the technology, understand the business, get the right people talking to each other, and keep things moving.
I'm comfortable discussing strategy with executives in the morning and working through a technical dependency with engineers in the afternoon.
No theatre. No unnecessary complexity. Just get the right things done.
TECHNICAL BY ORIGIN
Infrastructure and IT service delivery came before project management.
GLOBAL BY EXPERIENCE
Programs and projects delivered across industries, countries and multicultural teams.
PRACTICAL BY NATURE
A plan matters. What happens when the plan meets reality matters more.
DELIVERY BY MINDSET
Scope. People. Risk. Money. Technology. Deadline. Make them work together.
I like complicated projects. Simple ones tend to get boring.
04 / CAREER JOURNEY
I didn't start by managing IT. I started by doing it.
More than two decades in technology from hands-on support and infrastructure to global IT, transformation and security programs.
2003-2008
01 / THE FOUNDATION
Learning technology from the inside.
Autodesk. IT support. Networks. Servers. Backup. Remote access. Users with problems that needed solving now, not next week.
Technology only matters when it actually works for the people who depend on it.
2009-2013
02 / SERVICE DELIVERY
Technology became responsibility.
E.ON. VIP environments. SLAs. Business impact. Accountability. Team leadership.
150 VIP users → 750 customers → team leadership
2013-2016
03 / INTO PROJECTS
From keeping systems running to changing them.
TectumIT → MODIT → HPE / E.ON. Infrastructure projects, cloud migration, datacenter delivery and the E.ON One-to-Two enterprise separation.
The technology was still familiar. The scale wasn't.
2016-2021
04 / GLOBAL DELIVERY
One project became twenty-six.
Aptiv. New sites. Closures. Migrations. VMware. NetApp. Databases. Cloud. ServiceNow.
26 infrastructure projects · $3.1M TCV
2021-2024
05 / PROGRAM LEADERSHIP
Bigger programs. More moving parts.
BASF → Norsk Hydro → MVM → Palfinger. Infrastructure transformation, cybersecurity, enterprise carve-outs, service transition and global delivery.
$200Mlargest program12workstreams97team members7go-lives2.5Mcustomer records
At this point, I wasn't managing projects around technology anymore. I was managing complexity.
NOW
06 / SECURITY AT SCALE
592 sites. 71 countries. One global security program.
HCLTech / Brenntag brought the technical and program-management sides of my career back together.
152 sites across 19 countries delivered.
Different role. Bigger map. Same principle: understand what's happening, bring the right people together, and get it delivered.
Projects are about technology, money and deadlines. But mostly, they're about people.
After more than two decades in IT, I've collected a few stories, opinions and lessons that never quite fit into a project status report.
WHEN THINGS GO WRONG
Three hours before the customer handover, the production server disappeared.
One of the Wintel engineers accidentally deleted a production server roughly three hours before a customer-facing handover meeting.
The timing was particularly impressive: three days later, the end client's own customer was due on site to see the newly delivered facility and its pre-production environment.
So no pressure. :)
There are moments in a project when another meeting, another escalation or another beautifully formatted status report isn't going to help. We assessed the situation, got the right technical people together, rebuilt what needed to be rebuilt, and completed the handover.
There's still one industry I'd love to add to the list: Aerospace.
Not because it sounds impressive. Because it's one of those environments where engineering, technology, precision, risk and teamwork all have to work together.
Reaching the stars would be a pretty decent project milestone.ON AI
The tool isn't the interesting part. What people do with it is.
I don't think AI wakes up one morning and decides to enslave humanity. It doesn't have ambition. People do.
People once drove horse-drawn carriages for a living. Today we have taxi drivers.
The vehicle changed. The need to get somewhere didn't.HOW I WORK
Competence matters. Ego doesn't help.
I like people who know their stuff. I like direct communication. I like meetings that have a reason to exist. I don't expect engineers to speak management, and I don't expect executives to understand a network diagram. Part of my job is making sure they can still make good decisions together.
I'll challenge an idea when I think it's wrong. I'll change my own when someone proves me wrong. When something goes sideways, I'm much more interested in “How do we fix it?” than “Whose fault was it?”