Skip to content
Knowledge beta

Slow, Siloed Teams

Problem Organizational Design Team Dynamics

Every meaningful delivery crosses three team boundaries, waits behind two other teams' backlogs, and lands in a release you weren't invited to plan. Ownership is fuzzy, cognitive load is through the roof, and the architecture looks suspiciously like the org chart.

This is what Conway’s Law looks like in motion. Your team boundaries became your communication channels, your communication channels became your dependencies, and your dependencies became the architecture every change now has to negotiate. The slowness isn’t a discipline problem or a headcount problem; it’s a structural one. The org chart is doing exactly what org charts do, and you’re paying for it in coordination tax.

Countermeasures

You can’t fix a structural problem with process improvements. The leverage move is to redesign teams around the flow of value they own, not the functions they belong to. Team Topologies gives you a working vocabulary for stream-aligned, platform, enabling, and complicated-subsystem teams. Cognitive load becomes the hard constraint on how much any one team can carry. Get the boundaries right and the coordination tax drops; get them wrong and no standup cadence saves you.

Workshops

  • Organizational Design — the primary move. Reach for this when the pain is structural: teams organized by function, not flow, and every change requires cross-team negotiation.
  • Change Vision & Strategy — often paired with Organizational Design when the redesign is significant enough to need its own change program. This workshop builds the guiding coalition and communication plan that keeps the redesign from stalling mid-flight.
  • Agility for Leaders — reach for this when the silos are process-driven rather than structural. Leaders learn to protect flow across team boundaries with better decision rights, smaller batches, and tighter feedback loops.

Resources