AI as a diagnostic for team design

Across the last few posts, I’ve been exploring AI as a diagnostic rather than a destination - not because it creates new organisational problems, but because it applies pressure to existing ones.

Signals such as stalled decisions and costly dependencies are rarely isolated. When you look at them together, a deeper pattern begins to emerge. Decision bottlenecks often appear where authority has been separated from execution. Dependency friction shows up where team boundaries don’t reflect how work actually flows. In both cases, the issue is not effort or intent, but alignment between team design and the outcomes the organisation is trying to achieve.

Many organisations are structured around history: functions, systems, reporting lines, or legacy architecture. Over time, teams adapt to make that structure work. They coordinate more, escalate more, and rely on relationships to keep progress moving.

That adaptation has a cost. Teams may be empowered to decide, yet still unable to act without negotiating across multiple groups. Others may own components without owning outcomes. Responsibility fragments, even when individuals are highly capable. What AI exposes is the gap between how teams are organised and how value needs to flow.

This does not automatically require a wholesale reorganisation. More often, it calls for clarity: aligning teams more explicitly to outcomes, reducing avoidable coupling, and ensuring that authority and accountability sit with those responsible for delivery.

AI is not forcing a new structure into existence. It is revealing where the current one no longer fits the work it is being asked to support. And that is why it can feel destabilising. Not because it introduces chaos, but because it removes the comfort of slack and makes structural misalignment visible.

Seen this way, the opportunity is not to reorganise around AI, but to treat the friction it surfaces as actionable feedback on team design.