Ask the Community: How Do You Shift From Functional Teams to Value-Driven Teams?

Teresa Torres and community members explore how organizations moving from functional or platform teams (back-end, web, mobile) to cross-functional, value-driven product teams can make the transition. Functional structures cause slow handoffs and constrain what is possible for customers. Two practitioners share experiences: one used a diagram to show teams gaining autonomy despite added release complexity, and another described a claims-journey team that learned through early design sprints, role clarity, and early dependency discovery, while legacy budgets and incentives created friction. Torres argues the shift will feel slower at first because people revert to handoffs, and recommends deliberate collaboration habits. The piece matters because restructuring teams is often the first step toward outcome-driven product work.

01Key takeaways

• Cross-functional teams gain autonomy by owning the skills needed to deliver a full value stream.
• Expect the transition to feel slower at first, as teams tend to recreate handoffs within the new structure.
• Use a design sprint or similar shared activity early to align on customer problems and surface assumptions.
• Define each member's role clearly, such as who decides what to build and who drives research.
• Identify legacy system and architecture dependencies early, before they become blockers.
• Align budgets and incentives with the new team outcomes, or the old functional structure will pull teams back.

02Key sections

Why functional teams struggle

Teams organized by function hand work across each other, which is slow and lets early decisions constrain later options. Cross-functional teams aim to contain every skill needed to deliver customer value.

Using a diagram to show the benefit

One leader drew a before-and-after picture of team structure to help engineers see the autonomy gained, while acknowledging new complexity in code reviews and releases.

Lessons from a new claims team

A cross-functional team benefited from a clear strategy and a design sprint, but early work split by skill failed until the team reorganized around customer journey parts.

Role clarity and hidden dependencies

Ambiguous roles slowed decisions, and legacy systems and documentation gaps surfaced late. Incentives still tied to functional budgets created contradictions for the team.

Teresa Torres's guidance

Expect slow early progress and a tendency to recreate handoffs inside teams. Practices like involving everyone, working out loud, and socializing help build collaboration.

03From the post

“When an organization shifts from delivery or feature teams to product teams, the first step is often a change to team structure. Delivery and feature teams are often structured by function—front-end teams, back-end teams, mobile teams, etc. These teams can rarely deliver value on their own. Instead,”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.