(Note: Imagine a sleek Solved. logo overlaying the bottom right of that hero image... it just pulls the whole room together, doesn't it?)
I remember sitting in a cramped, windowless conference room about seven years ago, staring at a whiteboard that looked like a toddler had tried to map out the London Underground. We were launching a massive "process improvement consulting" initiative for a client, a non-profit that was doing incredible work but was, frankly, drowning in its own success.
My job was to assemble a "dream team." I pulled a designer from one department, a data person from another, and a project manager who was already juggling three other things. On paper, they were perfect. In reality? It was a disaster.
We spent the first three weeks just trying to figure out how each other worked. "Oh, Sarah doesn't check Slack after 4 PM," or "Mike needs a three-day lead time for any data requests." By the time the team actually started "performing," the project was halfway over. We wasted so much time on the "getting to know you" phase that we barely had enough left for the "actually doing the work" phase.
I’ll be honest... I felt like a total failure. I thought I was being a "resource optimizer." (Yikes, I even used that phrase back then. Please don't hold it against me.) I thought moving people around like chess pieces was the peak of operations consulting.
I was wrong.
Fast forward to today, and the conversation has shifted. Everyone, from Fortune 500s to the local non-profits we love to serve, is talking about Persistent Teams. And if you’re wondering why your operations still feel "sticky" or slow despite having great people, this might be the missing piece of the puzzle.
The "Project Team" Trap
In the traditional world of business, we’re taught to build teams around projects. A project pops up, we grab "available" people, we do the work, and then we blow the whole thing up and send everyone back to their "home" departments or onto the next random project.
It sounds efficient, doesn't it? It's not.
Every time you assemble a new team, you’re hitting the reset button on human dynamics. You're forcing people through the "Forming, Storming, Norming, Performing" cycle all over again. (If you’ve ever sat through a meeting where two people spent forty minutes arguing over how to format a spreadsheet, you’ve lived through the "Storming" phase.)
Persistent teams, on the other hand, are groups of people who stay together across multiple projects. Instead of moving people to the work, we move the work to the people.
Why This Matters for Your Operations (The Real Talk)
When I talk to business owners about process improvement consulting, they usually want to talk about software or fancy dashboards. And sure, I love a good dashboard as much as the next guy. But the biggest operational bottleneck in most organizations isn't the software... it’s the Cognitive Load.
1. Reducing the "Communication Tax"
Think about your own team. How much time is spent on "meta-work"? That’s the work about the work. It’s the "Hey, did you see my email?" or "Who is responsible for the final sign-off on this?"
Persistent teams develop a shorthand. They know each other’s rhythms. They know that when Brenda goes quiet in a meeting, she’s actually processing a complex problem, not ignoring the conversation. When you have that level of familiarity, the communication tax drops to nearly zero. You start operating at a speed that feels almost like telepathy. (Okay, maybe not telepathy, but at least like a well-coordinated dance instead of a middle school mosh pit.)
2. Trust as an Operational Lubricant
We talk a lot about team engagement strategies here at Solved. Why? Because trust is the ultimate lubricant for operations.
In a persistent team, trust isn't just a "nice-to-have" culture perk; it’s a functional requirement. When people stay together, they feel safe enough to fail, to iterate, and to call each other out when things are going sideways. They aren't worried about looking "good" for a project manager they’ll never see again in three months. They’re invested in the collective output of the group.
The "In the Trenches" Reality: Why This Is Hard
I’m not going to sit here and tell you that switching to persistent teams is as easy as flipping a switch. If it were, everyone would do it.
The biggest pushback I get from leaders, and to be fair, I’ve had these same thoughts, is the fear of losing flexibility. "But Brett, what if I need Mike’s specific skill set on this other project for just two weeks?"
The "old me" would have said, "Go for it! Move him over!"
The "Solved. me" says, "Stop. Think about the cost."
When you pull Mike out of his persistent team, you aren't just losing Mike’s hours. You're breaking the rhythm of his current team. You're forcing them to compensate for his absence. And you're forcing Mike to pay a "switching cost" as his brain tries to jump between two completely different contexts.
(To be honest, we usually overestimate the "uniqueness" of a skill and underestimate the value of a team’s momentum.)
How Persistent Teams Fuel Scalability
If you’re a growing non-profit or a small business trying to scale, persistent teams are your secret weapon. Why? Because they create a predictable "unit of delivery."
Instead of wondering, "How long will this project take?" you can look at your team and say, "This team has a velocity of X. We know they can handle this." It makes your operational consulting and planning much more grounded in reality rather than wishful thinking.
We’ve seen this work wonders in everything from software development to ministry teams. In fact, we recently wrote about how ministry teams need operational rhythms that last, and persistent teams are at the core of that sustainability.
Getting Started: The "Don't Break Everything" Approach
If you’re feeling inspired (or at least slightly curious), don't go out and reorganize your entire company tomorrow. That’s a recipe for a mutiny. Trust me... I’ve tried the "big bang" approach, and it usually ends with me eating a lot of humble pie.
Instead, try this:
- Identify one "Persistent Pilot": Pick a small group of 3-5 people. Give them a series of related projects over the next six months. Don’t break them up.
- Use Tools like DiSC: Help them understand each other’s communication styles early on. (We’re big fans of using DiSC to navigate tough conversations.)
- Measure Outcomes, Not Just Hours: Look at the quality of work and the speed of delivery in month five compared to month one. I bet you'll see a massive leap.
- Protect the Team: As a leader, your job is to be the "shield." When other departments try to "borrow" a team member, say no. (It’s hard, I know. But it’s worth it.)
The Moral of the Story
At the end of the day, operations isn't about moving boxes on a screen. It’s about people.
We’ve spent so many years trying to make people act like machines, interchangeable and perfectly efficient. But humans don't work that way. We work best when we feel connected, when we understand our role, and when we have a "tribe" we can rely on.
Persistent teams are just a fancy way of saying "let’s let people be people." When we do that, the operations side of things tends to take care of itself.
I’m still learning this, by the way. Even as someone who has been in the "operations consulting" game for a while, I still catch myself trying to "optimize" people. It’s a habit. But every time I lean into the power of a stable, engaged team, the results speak for themselves.
If you're struggling with team turnover or project delays that just won't quit, maybe it's time to stop looking at your processes and start looking at your team structure.
I'd love to hear your thoughts. Have you tried keeping teams together long-term? Did it work, or did they eventually want to kill each other? (Hey, it happens.) Reach out to us at Solved. Operations & Management Solutions: we’re always down for a "real talk" conversation about the messy reality of leadership.
Let's get it Solved.
: Brett
