All models Team model

Stable teams mirroring the business

Each team faces a fixed segment of the business.

The business sees the IT team as its fixed partner. That closeness means the team knows how its business partner works, which saves analysis time. The business does not have to explain how it works to someone new over and over. Many IT organisations are set up this way today, often grown organically.

When it works

This model works when your business consists of recognisable domains that each have their own rhythm and their own priorities, and when most of the work stays inside one such domain.

It works when closeness weighs heaviest. A team that knows how its business partner works needs less analysis and builds the wrong thing less often, because it hears the question behind the question.

It only works with supporting units behind it. A mirror team presumes knowledge of all the software and hardware its client uses, and that is rarely sustainable in one team. An expert team around a package keeps the relationship with the supplier and has a network in the mirror teams. The mirror team itself often holds one analyst profile who picks up the needs and passes them to that expert team.

When it does not work

When the domains in your business keep shifting, the team structure lags behind reality and every request becomes a question of alignment.

When most of the work cuts across domains, this model moves the coordination outside the teams instead of solving it.

What it solves and what it creates

It solves findability. The business knows who to go to, and the team knows who it works for. That saves searching and waiting on both sides.

It keeps the complexity of the IT organisation out of the client’s view. Packages used by several businesses, the standards, the technology underneath: all that stays behind the single point of contact.

It creates dependency as soon as a request touches several domains. Then two or three teams have to lay their plans over one another, and usually nobody owns that.

It creates a tension between client focus and efficiency. You want to serve the business without putting an abundance of people and knowledge in every team, and every piece of knowledge you add is a gain for the client and a cost for the organisation.

It creates dependency on the central departments, and that is where the greatest risk of this model sits. Closeness and a personal relationship collide with work the team has to hand over, because at that central department this request is not at the front of the queue.

Priorities then start moving through escalation to management. The central team works on a product without client contact and so holds no long term line. And an organisation of us and them appears that nobody wanted.

What it asks of your governance

A portfolio that looks across the domains, because otherwise each domain optimises for itself. And a place where the work that goes beyond domains is assigned and followed up.

Demand management between the mirror teams and the central departments, with priorities visibly settled. Without that they move through escalation, and then the relationship with the client has become a means of pressure.

Agreements about what stays shared: the technology underneath, the standards, and who decides when two domains want something different.

What it means for your people

People build deep knowledge of one segment of the organisation. That is valuable, and it has a downside: whoever carries that knowledge alone finds it hard to move out of that team.

Someone who sits in one domain for a long time sees less of the rest. The craft moves on outside their field of view, and their experience grows narrower as it grows deeper. They only notice that when they end up somewhere else.

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.