How I deliver
Method · Governance · Practice

How I lead technology
delivery.

I bridge business intent and engineering reality. Over 15 years I have delivered software on the vendor side and the customer side, in product and in custom development. Choose a principle below and see where it shows up across everything I do.

15+Years in enterprise IT
7Industries served
3Countries aligned

Your call

0 of 6 played
Highlight

What I bring that is hard to find
in one person.

Select a card to read more.

How I build trust with the client

How I build trust with the team

What I stand for,
when it gets hard.

These do not change from one project to the next, especially when a project gets difficult.

How values turn into
daily practice.

Five capabilities
I am hired for.

What I actually do, where I have done it, and which values and principles drive each one.

Seven steps on
every engagement.

It is a loop: the last step feeds the first.

From the first estimate
to support after go-live.

The areas of the delivery lifecycle and how I am involved in each. Select an area, filter by my role, or walk through them in order.

Decisions at the right level,
nothing waiting for a meeting.

The structure I set up on every programme.

Forums and escalation

From strategic direction down to the escalation path.

RACI matrix

Who is responsible, accountable, consulted and informed for every deliverable and decision, agreed at the start.

RAID log

Risks, assumptions, issues and dependencies, reviewed every week in the PM sync, each with an owner and a date.

PMO status report

The template I ran with the PM team on fixed-price delivery. Select a line to see why it is there, and change a status to see how the overall picture moves.

Real situations,
what I did and learned.

Step through each one: the situation, the pressure, what I did, what I took from it.

Working on something complex?

If this is how you want your next programme to be run, let's talk.