Cross-Functional Collaboration: Breaking Down Silos
Organisational silos — where teams optimise for their own goals without adequate coordination — are one of the most consistent sources of waste, conflict, and poor customer outcomes.
Why Silos Form
Silos are a natural response to organisational structure. If engineering is measured on tickets closed and marketing on leads generated, neither naturally optimises for customer outcomes that require both to work together. Silos are a structural and incentive problem, not a character problem.
Cross-Functional Teams
The most effective remedy: organise around outcomes rather than functions. A cross-functional product team includes engineering, design, product management, and sometimes marketing and data — all working toward a shared outcome.
Shared Goals and OKRs
Setting shared OKRs across teams that must collaborate creates joint accountability for outcomes. If marketing and engineering share an OKR, they are incentivised to collaborate rather than optimise independently.
Communication Bridges
- Regular cross-team syncs — representatives from each team who share context and surface dependencies
- Shared channels in Slack/Teams for cross-functional topics
- Embedded roles — a technical PM embedded in a commercial team, or a marketing partner embedded in a product team