My Chief Technology Officer pulled me aside a few years ago during a particularly chaotic sprint cycle. We had fourteen things in flight. Nothing was shipping. My team was exhausted, frustrated, and somehow more behind than they’d been the month before.
He looked at me and said one word: “Thrashing.”
I had no idea what he meant. He explained it the way engineers explain things — precisely, without ego — and it changed how I manage teams, structure priorities, and think about my own personal productivity forever.
Here’s what thrashing is. Where it comes from. What it’s costing your organization right now. And nine specific things you can do — starting this week — to stop it.
What Is Team Thrashing? (The Concept Most Leaders Have Never Heard)
In operating systems, thrashing is a specific, documented failure state.
A computer processor can only actively work on one task at a time. When more tasks demand attention than the processor can handle, the operating system begins switching rapidly between them — constantly loading and unloading state. Each switch has a cost. That cost accumulates.
At a certain threshold, something counterintuitive happens: the processor spends more time switching between tasks than actually completing any of them. The system bogs down. Progress stalls. The machine is running at full capacity — and producing almost nothing.
That’s thrashing. Not laziness. Not lack of effort. An overcrowded system collapsing under the weight of its own task-switching overhead.
Sound familiar?
When my CTO named it for me, I immediately applied it to every team I had ever led — and found it everywhere. Thrashing is not a tech team problem. It’s a universal leadership problem. And it may be the single most underdiagnosed cause of organizational underperformance.
5 Signs Your Team Is Thrashing Right Now
Before the fixes, the diagnosis. Thrashing shows up in predictable patterns. Here are the five most common:
- The 80% Graveyard You have a dozen projects sitting at 80% completion. Everyone is busy. Nothing ships. The half-built work consumes mental overhead, dominates every status meeting, and delivers zero value. Eighty percent done is not done. It’s expensive inventory that isn’t moving.
- The Priority Carousel Leadership keeps rotating the top priority — weekly, sometimes daily. The team pivots. Abandons previous work mid-stream. Starts the new thing. Then leadership pivots again. Nobody finishes anything because the finish line keeps moving. This isn’t agility. It’s thrashing.
- The Meeting Loop The same decisions get relitigated in meeting after meeting because no one owns the resolution. You leave the meeting and nothing changes. You schedule a follow-up. The follow-up ends without a decision. The loop continues. The cost is invisible — time, trust, and momentum, hemorrhaging.
- The Hero Firefighter One or two people spend their entire week responding to crises, being pulled in every direction. They’re celebrated for responsiveness. They never build anything. The system rewards their thrashing and punishes deep work. That’s backwards — and it signals a broken culture.
- The Diffusion Problem The team has too many strategic goals to remember, let alone pursue. No individual contributor can answer: What is the one thing I should be working on today that would move the needle most? If they can’t answer it in ten seconds, they’re thrashing.
What Thrashing Is Actually Costing You
Organizations don’t think of thrashing as a financial problem. They should.
It kills Killer Outcomes. In our SPARK framework — the model used to assess Most Loved Workplace® certified organizations — the K stands for Killer Outcomes. It’s not about being busy. It’s about delivering results that matter. Thrashing organizations are filled with activity and starved of outcomes. Teams that never complete anything can’t point to wins. They can’t build momentum. They can’t attract the talent that wants to work on things that ship.
It destroys Systemic Collaboration. The S in SPARK is Systemic Collaboration — the coordination that makes an organization more than the sum of its parts. Thrashing breaks this. When everyone is context-switching and scrambling, proactive communication collapses. Silos form. Dependencies get missed. Teams start optimizing for their own survival over shared outcomes. The system becomes less than the sum of its parts.
It creates invisible burnout. The brutal and counterintuitive truth about thrashing: it feels like maximum effort. Your people are working at full capacity. They are exhausted. And they have almost nothing to show for it. The gap between effort and output is demoralizing. Your most talented people start asking: What is the point? Then they leave.
It signals a leadership problem — and the data proves it. Based on Best Practice Institute research, validated across 1,800+ Most Loved Workplace® certified companies: organizations where employees have clear priorities and see their work lead to real outcomes show dramatically stronger employee loyalty — people stay far longer. The inverse is equally true. Teams that thrash, churn.
You Are Also Thrashing (The Personal Version)
Before you fix your team, look at yourself.
Do you have more than three “top priorities” this week? Do you finish your workday having context-switched through ten different tasks and completed none fully? Do you have a backlog of 80%-done projects in your personal workflow — drafts unsent, decisions unmade, proposals needing one more revision that somehow never happens?
Personal thrashing is not a character flaw. It is a system design problem. You have allowed more demand into your queue than your capacity can process. The solution is not to work harder. The solution is to aggressively reduce the queue.
9 Ways to Stop Thrashing — In Your Team and Yourself
These are not theoretical. They are operational. Start this week.
- Enforce a WIP Limit (Work In Progress) Cap the number of active projects per team to fewer than the number of people on the team. Not active projects per person — active projects total. This forces real prioritization. It will be uncomfortable. Do it anyway.
- Make Completion the Metric — Not Activity Stop celebrating the firefighter. Stop rewarding context-switching. Start tracking what ships, what closes, what reaches 100%. Make done the only scoreboard that counts. Your team reorganizes its behavior around what you measure.
- Apply the “Finish First” Rule Every Monday Start every week with one non-negotiable: identify the project closest to completion and finish it before starting anything new. Build the habit of closing loops. Over time, the 80% graveyard shrinks and your team starts to feel what momentum actually feels like.
- Kill the Priority Carousel Commit to no more than three organizational priorities per quarter — and hold the line. When the inevitable urgent thing emerges that “has to become the new priority,” the answer is not to add it. The answer is: what comes off the list? If nothing comes off, it’s not a priority. It’s a wish.
- Kill Your Personal Maybe List That thing you’ve been “almost ready to decide” on for three weeks — decide it now, or remove it from your queue entirely. Indefinite deferrals are thrashing overhead disguised as prudence. Make the call.
- Protect Deep Work Time as Non-Negotiable Context-switching has a re-entry cost. Every interruption costs you not just the interruption time, but the reorientation time. Block two-hour minimums. Treat them as immovable. A calendar that has no protected deep work blocks is a thrashing machine.
- Name the Thrashing Out Loud The most powerful thing a leader can do is give the team permission to name the pattern. When you’re in a meeting relitigating a decision already made, say: “This is thrashing. We decided this. Let’s move.” When a team member is pulled five directions simultaneously, say: “You’re being asked to thrash. Let’s fix the queue, not add to it.” Naming the pattern disrupts it.
- Structure Collaboration — Don’t Leave It to Chance Thrashing thrives in organizations where cross-functional communication is reactive. When you build Systemic Collaboration — regular, intentional coordination between functions — you eliminate the hidden dependencies and missed handoffs that generate the fires that cause the thrashing in the first place. Prevention is cheaper than firefighting. Always.
- Audit Your 80% List Right Now Open a blank document. Write down every project, initiative, or deliverable you are personally aware of that is between 60–90% complete. Count them. That number is your thrashing load. If it’s more than three, you have a structural problem — not an effort problem. Prioritize finishing the list before you add anything new.
The Organizational Payoff of Stopping Thrashing
Most Loved Workplace® certified organizations don’t look chaotic. They look focused. Their people can tell you, clearly, what the organization is trying to accomplish. They can tell you what they personally are working on and why it matters. They can point to things they finished.
That clarity is a leadership decision, made consistently — to reduce the queue, enforce completion, and protect the conditions that allow deep work to happen.
The organizations that do this see dramatically stronger employee loyalty. They consistently out-innovate competitors. Their employees become the most credible recruiters for the next generation of talent — because they actually love where they work, and it shows.
That is the opposite of thrashing. That is what Killer Outcomes and Systemic Collaboration look like when they actually function.
Where to Start (One Action, This Week)
Here’s your single action item:
Find the one project on your team’s list that is 80% done and has been sitting there for more than 30 days. Assign it. Finish it this week.
That’s not a small thing. That’s how you break the pattern.
And if you want to understand how your organization scores against the full model — whether your culture is building the conditions for Killer Outcomes or inadvertently creating the conditions for thrashing — start with a Most Loved Workplace® certification assessment.
It’s not a survey. It’s a diagnostic. It will tell you clearly where the bottlenecks are and what to do about them.
→ Start your assessment: certcheck.mostlovedworkplace.com
Frequently Asked Questions
What is thrashing in team management?
Team thrashing is when a group of people has more active priorities than it can effectively process simultaneously. The term comes from computer science, where thrashing describes a processor that spends more time switching between tasks than completing them. In teams, thrashing looks like constant task-switching, dozens of half-finished projects, repeated meetings that produce no decisions, and high effort with low output. It is one of the most common and least diagnosed causes of team underperformance.
What causes team thrashing?
The primary causes of team thrashing are: too many simultaneous priorities set by leadership, no enforced work-in-progress limits, lack of clear ownership on decisions, a culture that rewards firefighting over deep focused work, and reactive rather than structured cross-functional collaboration. Most thrashing is a leadership design problem — not a talent or effort problem.
How does thrashing hurt organizational performance?
Thrashing destroys two of the most critical drivers of organizational performance: the ability to deliver meaningful outcomes (what Most Loved Workplace® calls Killer Outcomes) and the ability to collaborate effectively across functions (Systemic Collaboration). It also creates invisible burnout, because employees expend maximum effort for minimal visible results — which erodes emotional connectedness, accelerates turnover, and degrades the employer brand over time.
What is the difference between being busy and thrashing?
Being busy means high activity with real progress toward completion. Thrashing means high activity with almost no completion — because the overhead of constant context-switching consumes most of the productive capacity. The key diagnostic question is not “Is my team working hard?” but “Is my team finishing things?”
How do you stop team thrashing?
To stop team thrashing: (1) enforce a work-in-progress limit across the team, (2) make completion — not activity — the primary performance metric, (3) implement a “finish first” rule at the start of each week, (4) commit to no more than three organizational priorities per quarter, (5) protect deep work time on all calendars, (6) name thrashing patterns explicitly when they occur in meetings, (7) build structured (not reactive) cross-functional collaboration, (8) eliminate indefinite deferrals from personal and team queues, and (9) audit all projects currently sitting at 80% completion and close them before starting anything new.
What is the SPARK framework and how does it relate to thrashing?
The SPARK framework is the organizational model developed by Most Loved Workplace® and the Best Practice Institute to identify the drivers of exceptional workplace cultures. SPARK stands for Systemic Collaboration, Positive Vision for the Future, Alignment of Values, Respect, and Killer Outcomes. Thrashing directly undermines two SPARK dimensions: K (Killer Outcomes) because thrashing organizations complete little and deliver less, and S (Systemic Collaboration) because constant context-switching breaks down the proactive, structured communication that high-performing teams depend on.
Can individuals thrash, not just teams?
Yes. Personal thrashing occurs when an individual has more active priorities, tasks, or open decisions than their cognitive capacity can process cleanly. It shows up as a long backlog of 80%-complete work, an inability to identify one clear daily priority, constant reactive task-switching, and a chronic sense of busyness without accomplishment. The same fixes apply: reduce the queue, enforce completion, protect deep work, and eliminate indefinite deferrals.
What is Most Loved Workplace® certification and how does it help with thrashing?
Most Loved Workplace® certification is an organizational assessment — not a survey — based on Best Practice Institute research validated across 1,800+ certified companies. It measures the drivers of exceptional workplace performance, including the clarity of priorities, quality of cross-functional collaboration, and degree to which employees experience real Killer Outcomes in their work. Organizations that go through the certification process receive a diagnostic that identifies exactly where structural problems like thrashing are occurring — and what leadership needs to do to fix them. Start at certcheck.mostlovedworkplace.com.
