Why Your Team Stays Stuck (It Is Not What You Think)

Written by Jonathan Bonanno | Aug 19, 2026, 9:29:55 PM

The organizational design research behind accountability gaps and what actually fixes them.

The problem is almost never the people. It is almost always the conditions they are working inside.

Think about the last time your team hit a wall. Maybe it was a project that stalled because nobody was sure who had authority to move it forward. Maybe it was the same accountability conversation you have been having for six months, with different people but the same outcome. Maybe it was a capable, willing team member who keeps dropping the ball on something that should be straightforward.

The instinct in those moments is to look at the people. To ask whether the right person is in the role, whether expectations are clear, whether the motivation is there. Those are reasonable questions, but organizational research suggests they are usually the wrong questions to start with.

When teams stay stuck, when the same problems surface across different people, different quarters, different initiatives, the cause is almost always structural. The conditions were never designed for the outcomes the organization needs. Conditions outpredict people, consistently, across industries and organization sizes.

 

Research across organizational contexts consistently shows that work design conditions, including role clarity, autonomy, task significance, and feedback structures, predict performance outcomes more reliably than individual motivation or effort levels.

Hackman, J. R., & Oldham, G. R. (1976). Motivation through the design of work: Test of a theory. Organizational Behavior and Human Performance, 16(2), 250-279.

 

The Three Design Failures That Produce Stuck Teams

Industrial-Organizational psychology research on work design points to three structural failures that reliably produce the patterns most teams experience as people problems. None of them require difficult people to create. All of them will persist until the design changes, regardless of how well the team is managed.

Unclear role boundaries. When roles are not clearly defined at the edges, where one role ends and another begins, who owns the decision versus who provides input, teams fill the gap with informal negotiation. That negotiation takes time, creates friction, and produces inconsistent outcomes. Over time, work routes to whoever steps up, which is not a stable or scalable structure. It is a pattern that burns out the people who step up and creates passivity in those who do not.

Undefined decision rights. Decision rights answer a simple question: who is authorized to do what without escalating? When that question is unanswered, teams default upward. Decisions pile up at the level of whoever holds implicit authority, usually the most senior person available, and that person becomes the bottleneck. This is not a trust problem. It is an architecture problem. The organization never specified where decisions should live, so they migrate to safety.

Workflows that route work back to the top. Some workflows are designed, explicitly or implicitly, to return to a central point for review, approval, or correction. That design makes sense in certain high-stakes contexts. Applied broadly, it creates organizations where output speed is capped by the throughput of one or two people, and where the team never develops the autonomous competence the organization needs as it scales.

 

Studies on role ambiguity in organizations consistently find that unclear role definitions are among the strongest predictors of reduced performance, increased stress, and higher voluntary turnover, effects that compound over time.

Morgeson, F. P., & Humphrey, S. E. (2006). The Work Design Questionnaire (WDQ): Developing and validating a comprehensive measure. Journal of Applied Psychology, 91(6), 1321-1339.

 

What Workability Actually Means

Workability is not a cultural concept. It is not about psychological safety in the abstract, or about whether people feel good about coming to work. Workability is a design concept: the degree to which the organizational conditions you have built allow people to do the work they are supposed to do, without constant friction, ambiguity, or the need for intervention.

A high-workability organization is not one where everything runs smoothly because people are exceptional. It is one where the structure itself produces the outcomes the organization needs, where ownership, accountability, and sustainable performance are natural results of how the work is designed, not things that have to be enforced or re-established repeatedly.

The distinction matters because it changes what actually needs to happen. If the problem is people, the solution is people management: hiring, coaching, accountability conversations. If the problem is conditions, the solution is design: clarifying role boundaries, specifying decision rights, redesigning workflows. Those are different interventions. The first is harder, more expensive, and less durable. The second is designable, repeatable, and scalable.

 

Organizational research on work design finds that employees in high-clarity, high-autonomy roles report significantly higher engagement, lower role conflict, and more consistent performance than those in ambiguously defined roles, even when compensation and management quality are held constant.

Grant, A. M. (2007). Relational job design and the motivation to make a prosocial difference. Academy of Management Review, 32(2), 393-417.

 

The Pattern Behind Every Stuck Team

The teams that stay stuck are not full of underperformers. They are full of capable people working inside systems that were never designed for them to succeed without constant oversight, follow-up, and intervention. The friction is structural. The accountability gaps are structural. The burnout that follows is structural.

The starting point for changing that is not a new training program or a harder performance conversation. It is a clear-eyed look at what the organizational conditions are actually producing and what they need to be designed to produce instead.

That work is designable. It starts with seeing the system clearly enough to know what to change.

ZIAversity Q3, Designing Conditions for Workability, opens September 24-25. Jonathan walks through this framework live on August 20 in a free webinar. No pitch. Open Q&A. Save your seat at talentbyzia.com/ziaversity