All models Team model

Supporting forms

Bringing knowledge from the teams together, with a community, a guild or a Center of Excellence.

A community of practice, a guild or a Center of Excellence cuts across the teams. They bring together knowledge that sits scattered through the organisation, record ways of working and connect people in the same craft. In a community or a guild people stay in their team and do this alongside it. A Center of Excellence can also be a standing unit, with people of its own.

When it works

These forms work when there is knowledge that arises separately in every team and is complete in none of them. A community or a guild brings that together without your having to rearrange the teams. If you choose a Center of Excellence with its own people, that is an intervention in the structure.

They work when there is a goal attached that comes from the strategy. A community that only meets to catch up rarely keeps that going for long.

The question each time is what the form has to solve. If you are moving to product teams, a community keeps connected the people who used to sit in the same team and are now spread across product teams. Learning from each other, coaching and mentoring, and often a team lead is the driving force who keeps that alive.

A step further it is about standards, ways of working and tools you want to bring into line. Then you start from your strategic plan and the form gets the responsibility to turn a goal from it into a way of working. A Center of Excellence that sets up the governance for the move to a composable architecture is an example of that.

When it does not work

When there is no shared problem, there is no community. You can bring together people who do the same work, but without a shared question it stays a meeting.

When the group gets too large. The more people at the table, the slower the agreements come and the more it looks from the outside like a lot of people and a lot of time.

When the form becomes a decision committee without anyone having agreed to that, a shadow structure appears next to the real one.

What it solves and what it creates

They solve the scattering of craft knowledge, and they make standards possible that people stand behind because the people who work with them made them.

They create a second claim on the same people. Someone in a team and in a community has two agendas and one calendar.

They also create a reputation. From the outside the organisation sees a lot of people, a lot of time and little visible result.

And it stays non-committal. What the group agrees still has to be put in place in every team, and with a form that grew from the bottom up nobody is obliged to do that.

What it asks of your governance

An agreement about time. Without reserved hours the team work always wins, and that is the right outcome too when nothing has been agreed.

A mandate that is named: what may this form decide, what does it advise on, and who decides when the advice is not followed. Without that it stays advice that every team may weigh for itself.

What it means for your people

People get a place to take their craft seriously, apart from their daily assignment. For many craftspeople that is the reason to stay.

It does ask that their manager really gives that time. Otherwise it is a favour that has to be fought for again every time.

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.