When it works
A product team works when the ownership of a product fits inside a team of five to twelve people who can build and operate it together.
It also works when what exactly has to be built is not settled yet. There is a direction, and it is clear what the product has to do, but what it looks like exactly and what the team has to build for that is still open. In a product team you bring together experts who each arrive at one solution from their own expertise.
The limits of five and twelve have a reason. Below five, waiting time goes up as soon as somebody is away. Above twelve, the lines of communication between people become too numerous to work efficiently.
When it does not work
When the ownership does not fit in one team. If the product is too big for twelve people, you cut it into pieces after all and the handover comes back. If the demand is too small to fill five people, the team becomes a name without work and people fall back on their old roles.
When what has to be built, and how, is already settled. Then there is no trade-off between experts needed, and a team that looks for a solution together adds nothing there.
And when you want to fit the product team into how your organisation works today. Then you get a team with a new name inside old agreements. The movement goes the other way: you adjust your organisation so that it can fully carry the way a product team works.
What it solves and what it creates
It solves the handover. The work does not wait for another team to move on, and nobody has to explain a half finished solution to whoever has to take it over.
It holds on to quality. A choice that saves time during the build but makes operation heavier comes back to the team itself and not to an operations team that did not make it. A team that carries what runs in production sets itself a higher bar for quality.
It lays bare the dependencies on the rest of the organisation. Teams that have to deliver something to the product team still exist, and for a product team starting out that is often the biggest stumbling block. The team works on scope within a horizon of a few weeks, while the rest of the organisation works on plans with a horizon of months to years. The team then experiences the organisation as inflexible, and the organisation experiences the team as cowboys.
It creates dependency on what the teams share. Each product team chooses its own solutions, and without agreements about that, standards drift apart and the same work is done more than once.
What it means for your organisation
Because the team is already there, you have to set up fewer projects. Work that used to need a project to put people together now goes to a team that already exists.
The work that is about scheduling people drops sharply. Demand management that looks for capacity per request, and meetings that assign people to projects, largely fall away. Application management also ends up in the teams, with whoever built it.
That shifts the profiles. Team lead, application manager and project manager are roles in the governance. Product owner, product manager and scrum master are roles inside a team. For the people in those jobs that is a different assignment, and that shift is often the biggest change this model asks for.
What it asks of your governance
A portfolio that frees up budget on the basis of the goals that have to be met, and not on the basis of a worked out solution. What gets built and how is for the team to decide. The request therefore arrives at the team and not at a layer in between that works it out first.
Agreements with the teams that have to deliver something to the product team, and those agreements belong in the portfolio decision itself. If the delivery is only asked for afterwards, a horizon of a few weeks collides with a plan of months.
Shared agreements about what teams choose themselves and what stays common. A community of practice holds those together, because that is where the people who make the choice sit.
Without projects, project reporting disappears too. What there is to see is about the product and not about progress against a plan, and that asks for different figures from the ones you get today.
What it means for your people
Whoever used to do one step in the chain now contributes to the whole. That asks for broader work, and it asks that somebody picks up the phone when it stops in the middle of the night, for what they built themselves.
Managers steer less on tasks and more on the result of the product. That is a different craft, and it does not grow by itself out of the old job.