When a team’s output starts to slip, the instinct in most conference rooms is to look at the people first, wondering whether someone has lost focus, taken on too much, or simply stopped putting in the effort they used to. That instinct makes sense on the surface, but it tends to point leaders in the wrong direction, because the research on organizational speed consistently traces the slowdown back to structure rather than effort, and to the friction that quietly builds up around decisions long before any individual gets the chance to make one.
The slowdown rarely announces itself all at once. It tends to show up first as meetings that multiply without anyone consciously deciding they should, then as approvals that bounce between two or three people because no one is entirely sure who owns the call, and eventually as a broader sense that everyone is working hard while comparatively little is actually moving forward. Leaders often respond by asking people to manage their time better or communicate more clearly, when the real fix has much less to do with individual behavior and much more to do with how decisions are structured across the team in the first place.
Where the Friction Actually Lives
Research on collaborative dysfunction published in MIT Sloan Management Review found that many teams fall into what the authors call a hub-and-spoke pattern, where heavy reliance on a small number of formal or informal leaders routes nearly every decision, large or small, through the same overloaded people, which slows the group down while simultaneously exhausting whoever sits at the center of that network.
That pattern only gets more pronounced as organizations grow. McKinsey’s research on organizational decision-making found that growing complexity, layered across product, functional, and regional lines, gradually clouds accountability until leaders can no longer delegate decisions cleanly, which is precisely the condition that produces the duplicated meetings and looping email threads that eat up a team’s week without producing much in the way of forward progress.
The Meeting Is Rarely the Real Problem
It has become common to blame overloaded calendars for a team’s sluggish pace, and the numbers back up the frustration. Harvard Business Review’s widely cited research on meeting culture found that executives now spend close to twenty-three hours a week in meetings, more than double what they spent in the 1960s, and that this shift carries real costs for innovation and organizational performance rather than simply being an inconvenience people complain about at the coffee machine.
The more useful way to read that finding is not that teams need fewer meetings as a goal in itself, but that meetings have quietly become the default mechanism for making decisions that a single accountable owner could have made in an afternoon. Once ownership is unclear, a meeting becomes the only socially acceptable way to move a decision forward, which explains why calendars keep filling even as leaders repeatedly promise to protect people’s time.
Naming the Behaviors That Create the Drag
FutureThink’s Unlock Simplification Behaviors workshop is built around this exact gap between how slow a team feels and what is actually causing it, and it works by asking a group to name their biggest time suck and then map the behaviors sitting underneath it before anyone is allowed to jump to a fix. The session follows a deliberately structured sequence:
- Each team names a specific time suck they are experiencing, something concrete enough that everyone in the room recognizes it immediately.
- The group maps the complexity behaviors driving that time suck, focusing only on what sits within their own sphere of control rather than issues they cannot influence.
- Participants separate tactics, which are one-time fixes, from behaviors, which are repeatable patterns worth changing for good.
- Each person writes a personal “I will” statement committing to one new behavior, and the group discusses exactly when and where they will put it into practice.
That structure matters because it stops teams from treating speed as a personality trait some people simply have and others lack, and instead treats it as a set of behaviors that can be named, practiced, and changed.
Speed and Quality Move Together
One of the more persistent myths inside organizations is that moving faster necessarily means cutting corners, but the data tells a different story. McKinsey’s research on decision quality found that respondents who described their organization’s decisions as fast were nearly twice as likely to also describe those same decisions as good, which suggests that the conditions producing speed, namely clarity of ownership and a willingness to act on available information, are the same conditions that tend to produce better outcomes.
That correlation is worth sitting with, because it removes the excuse leaders often reach for when a team asks for more clarity or fewer approval layers. Slowing down in the name of caution is not automatically the safer choice, and in many cases the extra time is simply absorbed by structural friction rather than converted into better judgment.
What Leaders Can Do About It
Agile teams recover much of their lost speed not by adding new processes on top of old ones but by directly challenging the standing rules and habits that no longer serve a purpose, a pattern documented in Bain’s research published in Harvard Business Review, which found that removing unnecessary bureaucratic drag restores energy to a team faster than almost any other intervention leaders typically reach for.
The most useful place for a leader to start is with clarity of ownership rather than a mandate for more effort. Naming who actually decides, giving that person the standing to act without convening a meeting, and being honest about which behaviors are quietly slowing everyone down will do more for a team’s pace than any new tool, tracker, or productivity framework layered on top of the existing structure. Teams rarely move slowly because they lack drive. They move slowly because the structure around them has never been asked to justify itself, and once it is, the pace tends to take care of itself.
Sources
- MIT Sloan Management Review, “When Collaboration Fails, and How to Fix It”
- McKinsey & Company, “Untangling Your Organization’s Decision Making”
- Harvard Business Review, “Stop the Meeting Madness”
- McKinsey & Company, “Three Keys to Faster, Better Decisions”
- Harvard Business Review, “Bureaucracy Can Drain Your Company’s Energy. Agile Can Restore It.”