top of page

Everyone’s Busy, But Nothing’s Moving

24 minutes ago
6 min read

When effort masks misalignment - and burnout becomes the operating system.


This is the third post in a quarterly series exploring the problems organizations bring us, and what’s often really going on underneath them. The first post looked at why so many organizations conclude they have a strategy problem when something else is actually breaking down. The second explored decision paralysis - what happens when discussion replaces commitment. This entry continues that thread.


Ask most leadership teams whether their staff are working hard, and the answer is immediate: yes. Everyone’s stretched. Everyone’s carrying a lot. Everyone’s giving it their all.


Ask the same teams what’s actually moving, and the answer takes longer to arrive.

This is one of the strangest patterns we see in organizations that care about mission. Calendars are full. Slack is buzzing. People are staying late, apologizing for slow responses, opening laptops after the kids are in bed. The whole system radiates effort.

And still - somehow - the same projects keep resurfacing on the same agendas six months apart, with the same status: “in progress.”


From the outside, this reads as commitment. From the inside, it feels like drowning.


A Familiar Scene


An operations manager at a mid-sized nonprofit described it to us this way. She’d been in her role for four years. She was, by everyone’s account, the person who made things happen - the one who knew how the organization actually worked, who could find the missing file, who remembered what was decided in the meeting no one wrote up.


She loved her job. Or she had.


Operations team managing multiple projects and competing priorities

Somewhere in the last eighteen months, she’d noticed something shift. She was working harder than ever. Her calendar was full six weeks out. She was CC’d on almost every project the organization was running. And when she sat down one Saturday to try to sort out why she felt so behind, she realized something that stopped her.


“I couldn’t remember the last time I had finished anything,” she said. “I’d worked on hundreds of things. I hadn’t finished any of them.”


Everything she touched was “in progress.” Everything was moving. Nothing was landing. And somewhere in the middle of the workflow - between the meetings she supported, the check-ins she coordinated, the vendor calls she made, the follow-ups she chased - the actual completion of work had quietly become someone else’s job. Except no one had told her whose.


She didn’t tell her boss any of this. She was too tired, and she wasn’t sure how to say it without sounding like she was complaining.


The Pattern: Effort Without Movement


There’s a version of hard work that looks like productivity and functions like a treadmill. It’s not the same as being busy. Everyone is busy. What we’re describing is the specific pattern of chronic effort that produces motion but not progress - the sense that everyone is fully deployed, and yet almost nothing is actually finishing.

What’s happening underneath is a specific mismatch between two kinds of work. Some people on the team are wired to clear paths - to remove obstacles, coordinate handoffs, make it possible for others to act. Others are wired to close - to push work all the way to done, to a specific standard, without leaving loose ends. Both kinds of work are essential. But in most organizations we see, they are radically unevenly distributed. One or two people carry the path-clearing burden for the whole team, and the closing work either gets skipped, deferred indefinitely, or routed back to the same one or two people.


In the Working Genius framework, these are two different geniuses, and they belong to two different people. Enablement is the instinct to provide the right kind of support at the right time to help others move. Tenacity is the drive to bring things to completion, to a defined standard, without leaving loose ends. Healthy teams have both, and distribute both. Overwhelmed teams have one person doing both, for everyone, indefinitely.


The Cost: Burnout as the Operating System


When one or two people become the organization’s Enablement infrastructure, several things start to happen at once.


The organization loses the ability to launch anything new, because it will “have to go through” the person who is already at capacity. Meanwhile, that person can’t stop, because if they do, the whole system slows visibly - and they know it, and everyone knows it, and no one wants to be the one to say it out loud.


The failure mode is that nothing ever visibly breaks. Bandwidth doesn’t collapse; it just quietly narrows. Meetings that used to run twenty minutes take forty. Response times slip from a day to three days. The organization starts turning down opportunities without quite realizing it’s doing so - “not now,” “let’s revisit next quarter,” “we’d need to think about how we’d resource it.” The refusals sound thoughtful. They’re actually symptoms.

And underneath, the person doing the work is exhausted in a way that looks - from above - like dedication.


Leadership sees a team that’s committed, hardworking, full of people who go the extra mile.


Staff experience a team that has structurally organized itself around the willingness of a few people to absorb what leadership hasn’t finished designing.


That gap is where good people quietly decide to leave. Not immediately, and not dramatically. They just start updating their resumes on the weekends they used to spend catching up on work. And when they do leave, the organization concludes it has a hiring problem - which it does, but not the one it thinks.


The Insight: This Is a Work Design Problem, Not a Resilience Problem


Team reviewing workflow and work distribution to identify organizational bottlenecks

Most organizations that recognize this pattern respond to it in one of a few predictable ways. They invest in wellness programs. They encourage people to “set better boundaries.” They run a workshop on time management. They hire another person to help.

None of these fix the problem. Some make it worse.


Wellness programs don’t fix work design. Boundaries don’t fix work design. A time management workshop is a particularly frustrating response, because the people most affected are, almost by definition, extraordinary at time management - that’s part of how they became the bottleneck. And hiring more people without changing the underlying pattern usually just produces more people to overload.


The uncomfortable truth is that burnout in these environments isn’t a signal that a person is failing to cope. It’s a signal that the organization has organized itself around a distribution of work that guarantees a few people will carry most of it. That’s a design decision, whether it was consciously made or not. And the only real fix is to unmake it.


That means asking a different set of questions than the ones most organizations ask.


A Better Starting Point

These questions don’t require a new HR strategy. They require an honest look at whose willingness is currently propping up the system, and what that willingness is costing them.


A Clear Next Step


If you’re reading this and recognizing your operations lead, your chief of staff, your most-relied-on program manager - you’re not alone. This pattern is one of the most common we see, and it almost never looks like a work design problem from the inside. It looks like a team full of dedicated people.


A brief conversation can help you sort out whether:


  • You need to redistribute a specific kind of work that’s currently concentrated in one or two people, or

  • You need to add capacity in a specific genius - Tenacity, most often - that your team has quietly been missing for years.


If you’d like to explore that, we invite you to reach out to CSR for an initial conversation. No pitch. No prep work required. Just a chance to name what’s actually hard, and see what might help.


Looking Ahead


In the next post in this series, we’ll explore what’s really happening when organizations conclude they need “better people” - and why hiring, turnover, and culture-fit problems are so often role-design problems in disguise.


About the Author


Patrick Larkin is a seasoned Nonprofit Consultant with over 25 years of leadership experience across various institutions. With a foundation in public horticulture and museum management, he has served on the board of the American Public Gardens Association and as a Peer Reviewer for the American Alliance of Museums. Patrick honed his skills in fundraising, board development, and strategic planning, continually focusing on aligning organizational missions with public needs. He is a Certified Working Genius Consultant.




 
 
 

Comments


bottom of page