Leading high stakes engineering programmes from chaos into launches that hold their date.
See the work →I'm at my best where the stakes are real and the path isn't obvious. Certified SAFe and Scrum practitioner, coaching teams, fluent with engineers and the boardroom alike. I keep complex programmes moving and everyone aligned on what's next. Based in Ireland, working with distributed teams across time zones.
AWS Cloud Migration for a Telecom Ecommerce Platform.
A Data Driven Case for Scope Over Schedule.
Restructuring refinement and reporting so leadership decided in the room, not three days later.
Building the handoffs between three teams that had never worked together, for a payment integration with zero room for error.
Building dependency visibility across vendors outside my control, so a slipping localisation partner never became a missed release.
Holding a single release to a higher bar than the rest of the portfolio, because every user was the beta this time.
A few of the tools I use repeatedly across programmes, shared here in a generic form.
Project Pack
SOW, SOP, Gantt chart, change control log, dependency map and RAID log — everything needed to set up and run a project.
Open pack →Programme Toolkit
Finance toolkit, decision rights, steering pack, options paper, programme charter, OKRs and KPIs — governance and reporting in one place.
Open toolkit →Team Health
Agile health check and employee engagement survey — tools for measuring and improving delivery culture and team wellbeing.
Open templates →What I Bring
One coherent plan across many teams, with the dates that hold.
Certified SAFe and Scrum practitioner at the team and programme level.
Surfaced early, owned visibly, never a launch-day surprise.
Translating between engineering reality and the boardroom.
Distributed teams, kept motivated and unblocked.
From fuzzy intent to a sequenced, fundable roadmap.
My WoW — Way of Work
I look for the structure that is missing before I look for the process that is broken.
I would rather bring leadership two honest options than one comfortable guess.
Data should end an argument, not start one.
A programme is only as stable as its weakest dependency, so that is where I look first.
