Insights / Service experience

People, process, tools: why the order matters

By Lawrence Abeyta · · 4 min read

My first IT job was at ENTEX Information Services, back in the previous century. (Yes, I just dated myself. Moving on.)

ENTEX ran help desks, deskside support, and networks for large companies, and three words were everywhere: people, process, tools. They were on posters. Managers said them in meetings. Team leads said them when something broke. It was in the DNA of the company.

Siemens acquired ENTEX in 2000, and the posters are long gone. The principle has outlasted both, and I have used it on every service I have built or repaired since.

Most projects run it upside down

Here is the usual sequence. A service is underperforming. Someone sees a demo. The tool gets bought. The process gets bent to fit the tool's defaults. The people get a training session and a go-live date.

Six months later the service has the same problems, plus a license fee.

I'm not against tools. I have made a career out of implementing them. The problem is where they sit in the sequence.

It's a stack, not a stool

People, process, and technology usually gets drawn as a triangle or a three-legged stool: three equal things to keep in balance. The idea is commonly traced to Harold Leavitt's work on organizational change in the 1960s.

The version I learned is ordered. Network engineers will recognize the idea from the OSI model, where seven layers run from the physical cable up to the application, and each layer depends on the one beneath it. No application can fix a bad cable.

Services work the same way:

  1. People. Who does the work, and who does it serve? What do they need, and what are we asking them to carry?
  2. Process. How does the work move between those people? Where does it wait?
  3. Tools. What makes that process faster and more consistent?

A tool can't fix a process designed for the wrong people. A process can't fix a team that is understaffed, untrained, or unconvinced. When a service fails, troubleshoot it the way a network engineer would: start at the bottom.

The layer I added

Over the years I added one thing: experience. It is not a fourth layer. It wraps the other three.

The person using your service never sees your org chart, your workflow, or your platform. They see one thing: what it was like to get help. That is the test of whether the three layers worked, and it is where customer experience and human-centered design earn their keep.

What about AI?

Here is the honest caveat. Sometimes a new tool changes what is possible in the layers beneath it. AI is the obvious example. It is a real disruptor.

It doesn't flip the stack. It means you run through it again. What does this change for the experience? For the process? For the people? Adjust, measure, repeat. That loop is what I mean by continuous transformation.

The order is also the order you think in, not a ranking of importance. Great people with no tooling don't scale either.

Why the order is an advantage

Anyone can buy the same tools. Your competitor can license the platform you just bought. What they can't buy is people who understand the service and a process built around them. Those two layers are the hardest to copy, so that is where the advantage lives.

It also explains most services that aren't delivering what they should. The cause usually sits a layer below where the money was spent.

Four questions, in order

  1. People: Who does this work, and who depends on it? Have we asked them what is broken?
  2. Process: Can we draw how the work flows today, as it happens and not as it is documented?
  3. Tools: Which of the remaining problems can a tool solve?
  4. Experience: How will we know the person on the other end is better off, and what will we measure?

Those are the first questions we ask at iter8 Tech when a service isn't delivering what it should. The answer is rarely the tool.

Not bad for something I learned from a poster.

Is a service not delivering what it should?

Start with the people, and a conversation.