01 4 pieces
Customer experience and service ecosystems
Treating services as a system, not a journey, and treating the customer experience as the visible edge of that system. Cybernetics, complexity, the Viable System Model in practice.
The brief is usually the surface of the work.
CX transformations, service redesigns and AI adoption programmes often turn out to be structural before they are technical.
Applying psychology and systems thinking to service and organisation design, and building better experiences for customers and for the teams delivering them. My work digs into how organisations and teams are built and whether they actually work. Advisory, fractional, and contract engagements.
Body of work
All writing → Four themes my work keeps coming back to.
02 7 pieces
Capability and organisational design
Looking at what it takes to build a design, strategy, innovation or delivery capability inside an organisation that really delivers on its ambition, not just following the ways it has always been done before.
03 4 pieces
AI adoption and the future of design
Adopting AI is an organisational act before it is a technical one, and most organisations aren't ready for it and don't know what to do with it. Notes from the question underneath the hype.
04 1 piece
Human flourishing through design
What it would mean to take flourishing as the goal of design, not problem-solving. Borrowing from positive psychology and trying to apply it to the world around us.
If you are reading me for the first time
Start here.
From passive maps to active models: introducing the Universal Service Graph
Something has been irritating me about org charts for years. They show you who manages who, and that’s it. But that’s not how organisations…
The shape of your teams: When structure fights purpose
This is the fourth in a series exploring design capability as a system. The previous posts looked at why scaling design is harder than it…
Service Design Needs to Evolve. Here’s Where I Think It Should Go.
This post is about the future of Service Design, why I think the practice needs to evolve, and what we can practically do about it.
For people thinking about working together
Three shapes of engagement.
- Contract project A defined piece of work with a defined output. Capability diagnostics, AI adoption programmes, service architecture.
- Advisory retainer A standing relationship. Two to three days a month, for design and product leadership wanting a thinking partner.
- Fractional role A named position inside the team, usually two to three days a week, three to twelve months.