All models Team model

Platform teams

One team builds what the other teams work on top of.

The platform team does not deliver functionality to the business but to the other teams. Its clients sit inside the IT organisation. Often those are services that SysOps runs, but it can just as well be a client module or a document service that several teams use.

When it works

Two questions come first: can this service be run centrally, and does that move your strategic plan forward? If that plan says the waiting time between the application teams and SysOps has to come down, that points to self service through a platform team. Digitalisation makes that possible more often than it used to.

A platform team works when it counts for your organisation that there is one solution, one approach, one definition and one responsibility around a service. Teams that each build their own variant today often do fine work within their own use. The question is whether uniformity and the gain from doing a number of activities centrally weigh more.

It works when you treat the platform as a product, with users who choose it because it makes their work easier, not because it is compulsory.

And it works when the teams can use it themselves without anyone stepping in. That is the heart of it: a team gets going itself instead of waiting for the platform team’s plan.

If self service is not feasible, you steer the service through demand management. Then it is still open how the team works. It carries out the activity itself, it joins a team temporarily to bring its expertise in, or it trains team members so the dependency gets smaller.

When it does not work

When the service is woven into the logic of each product. An invoicing module looks shared, but with a fixed subscription, with pay per use and with commissions paid out to external sellers, invoicing is each time a part of the product itself.

One module for those three becomes a series of exceptions, and the platform team becomes the queue for every new revenue model. The platform then better delivers the building blocks: an environment to keep transactions, a secure connection to the payment service, and a fixed way to write audit trails.

When only one team really uses it, it is not a platform but a split-off, and it only adds a handover.

When the platform is imposed instead of chosen, teams build around it. Then you have the cost of the platform without the return.

What it solves and what it creates

It solves repetition. What every team would solve differently stands ready once, and the knowledge about it sits in one place.

It creates a queue. As soon as a team needs something the platform does not yet offer, it waits. A platform that offers no self service becomes the new bottleneck.

It creates a client relationship inside your own organisation. The other teams become customers with expectations, and a customer who does not feel heard builds around it or escalates. That is new for an IT organisation where everyone used to sit on the same side of the table.

What it asks of your governance

A place of its own in the portfolio, with priorities of its own. A platform team that only gets leftover capacity falls behind its users within a year.

Agreements about what the platform promises, and a way for teams to say what they are missing.

One list of work and one way to prioritise. A platform team has several internal clients, and their requests come in by two routes: through demand management, and from the self service itself, because there too work is left over that someone picks up by hand, alongside the improvements to the platform. Without that one list, whoever shouts loudest decides.

What it means for your people

People work further away from the business, and are told less often what their work is for. That asks for a different way of making visible what they contribute.

Platform work asks for people who think from how another team uses their work. That is a craft of its own. Someone who builds excellently does not therefore enjoy it automatically, because the satisfaction comes from a colleague who can move on and not from a user who sees something new.

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.