Service Architecture

Service design is 10% design, 90% creating the conditions for design to happen.
Lou Downe — Former Director of Design, UK Government

Lou is right — but creating the conditions is only the beginning. The harder, rarer work is building the architecture that makes those conditions permanent.

Ambiguity is the starting point. Clarity is the outcome.

My Method — Five Layers

Foundation

Deep Listening

The real problem lives in the human dynamics underneath — not the problem they present. This baseline is everything.

It starts before any deliverable, any workshop, or any framework. I listen not just to the stated problem but to the personalities, temperaments, politics, and gaps between what people say and how they actually work. Until you establish this baseline, any intervention will fail on contact.

Layer 1

Human Landscape

I make myself someone they trust before I make myself someone who challenges them.

I assess the human landscape before I touch anything else — calibrating tone, cadence, level of candor, and degree of closeness for each person. This is not social strategy. It is the precondition for everything that follows.

Layer 2

Harmonization

Creating conditions where people see their own dysfunction clearly enough to choose differently.

I vocalize how I work, establish shared ways of working, and create conditions where people experience what effective function actually feels like. Those lightbulb moments are what make real change possible. Without them, the rest is futile.

Layer 3

Service Scaffolding

The right tool applied to the right part of the system.

With trust established and the human landscape stabilized, I assess which parts of the system need which tools — journey maps, blueprints, insight snapshots, measurement frameworks, personas, strategy documents. These are operational infrastructure — a durable structure built to function without intervention.

Layer 4

Process

Now we do, and we collaborate.

The architecture that was invisible becomes shared. The system that was reactive becomes manageable. The organization stops running on memory and starts running on structure.

A durable structure facilitating repeatable patterns of effective functioning. Built to operate without intervention.

Each engagement calls for its own architecture type depending on what is needed most.

For example, an organization running millions of dollars of daily operations on Excel sheets and phone calls, with no shared visibility into what was happening or why. What it needed first was not a solution. It needed to be able to see itself. I created a Clarity architecture. That is where I always start.

Let's talk about your organization