All models Team model

Central with local delivery

One way in for the whole organisation, delivery close to the business.

The request comes in at one place and is assigned from there to whoever can carry it out, in the business unit, the site or the country it came from. The service desk is the best known case: one number, one email address and a portal, and behind it someone who records, classifies and prioritises every report.

When it works

This model works when a goal in your plan is only achievable if you keep it together in one place. If the plan says the organisation has to be better protected against digital attacks, then everything to do with malware and phishing comes in through one way in. That gives a faster response, knowledge that builds up in one place, and a view of whether you are meeting the goal.

If you spread that across the local units, you spread the goal as well. Nobody says in a steering group that security is not important, and still each unit weighs its importance against its own daily work. What you achieve is then no more than the sum of those weightings.

A second case is simpler. The whole organisation has to be able to use the same way in, and at the same time you want the delivery done by people who know the local situation.

The central side takes in, distributes and follows up, and carries out as little as possible itself. A password that needs resetting the service desk handles itself. A fault in the network goes to the network team, a bug in the software to the team that built it, a new laptop to workplace management. Whoever distributes that is a dedicated person, a team lead or a rule in the system.

When it does not work

When the way in becomes the queue itself. One place where everything comes in is also one place where everything can sit, and then the business has called a number and still has no answer.

When the central side also starts deciding how something is solved, the local side loses its reason to exist and only the delay is left.

When the requests are too different to judge centrally, the intake becomes a pass-through with a cost and without value.

What it solves and what it creates

It solves findability for the business. One number, one form, one place to go, wherever the answer comes from.

It creates a handover with every request. Everything that comes in has to be understood, weighed and passed on, and every step in that costs time and can lose something.

What it asks of your governance

One set of priority rules that central and local both follow. Without those rules the central side decides what is important and the local side what happens first, and that is rarely the same thing.

A view of lead time across the whole chain, not only of the central step. A fast intake for a request that then sits for three weeks is not a fast intake.

What it means for your people

The people on the central side do work that rarely gets noticed when it goes well and always gets noticed when it goes wrong. That asks for recognition that does not come by itself.

The local people get work assigned instead of taking it on themselves. Whoever experiences that as control builds a channel of their own, and then you have two ways in.

Which choice in your strategy does this model make possible, and which does it make harder?

Put that question to us A 30 minute conversation.

Other team models

Where does your plan get stuck today?

In a 30 minute conversation we choose the first step together.