I built this site for my clients.

Whatever I hand over at the end of an engagement, a report, a roadmap, a deck, has to be short enough to read and long enough to be honest, and it never quite manages both. It doesn’t go deep enough for the person defending the roadmap, or the person defending the budget, or the person who has to keep it running once everyone else has moved on. And it’s only true for as long as the situation that produced it holds.

Some of what I know settled into place only after an engagement had ended, too late for the deliverable. It lives here instead.

What I actually do

I help organisations work out what is actually going on, and what to do about it.

Most transformation effort is spent before anyone can see the system it’s meant to change. The work here starts from the other end: see your own system clearly first, where value moves, where it stalls, which constraint is really binding, then put effort only where it pays.

The knowledge to solve your problems already lives in your people, the people inside the system see it more clearly than any outside expert can. My work is getting it said out loud, connected to each other, and written down in a form a leadership team can act on.

What turns an engagement is usually already inside the organisation, known, but scattered, and not yet said clearly enough to act on. From there, the people who have to live with the change design it, and it moves in small steps, because an organisation is not a machine; it pushes back, it surprises, and the only way to find out what works here is to try something here.

Twenty-five years of this, most of it inside large organisations in the middle of real change.

Where the work has happened

Absa Bank · Barclays · Deloitte · Capgemini · Owens Corning · Vodafone · JCI · JLL Technologies · Gartner · Pfizer · Microsoft

Financial services, pharma, manufacturing, technology, professional services.

About the writing here

The articles are written for people already doing this work. What they answer is the harder question: why this way, why now, and what it actually changes for your team once you do it. They’re written to be read in pieces, out of order, by different people who each need a different part of the same answer. This is meant to be the evidence. Read one and see if it holds up.

The shelves hold two territories: scaled agile, SAFe as it actually runs inside large organisations, and enterprise AI: strategy, governance, data, agents, and the people who work with them.

Morné Wiggins