Your delivery process isn’t broken. Your business outgrew it.

I was on a call recently with an agency leadership team that, on paper, had everything figured out. They had a solid client base, a team of about twenty-five people, and an agency delivery system that had clearly been built with care over time. They had detailed schedules, defined roles, regular resourcing conversations, and even a traffic manager whose job was to keep everything moving.

If you looked at it from the outside, you’d probably think, “This is exactly what a growing agency is supposed to look like.”

But when they started talking about how things actually felt day-to-day, a different picture emerged. People were spending hours every week talking about resourcing. Project plans were constantly being blindly adjusted. Work was sitting in queues longer than it should. And even though everyone was busy, there was this underlying sense that they weren’t moving as efficiently as they used to.

At one point, someone asked whether what they had was fixable or whether their entire model was starting to show its age.

That question tends to show up when something deeper is going on, because most teams don’t jump straight to “maybe our model is obsolete” unless they’ve already tried a few other things that didn’t quite land.

The system that got you here

What they were describing is something I’ve seen play out over and over again.

At some point in an agency’s growth, you realize that just winging it isn’t going to cut it anymore. You start putting structure in place. You define roles more clearly, introduce tools that help you track work and manage expectations, and you build out a system that makes it possible to handle more clients and more complexity without everything falling apart.

For a while, that system works really well. It gives people direction and it creates the operational consistency you need. In the end, that consistency helps you scale in a way that feels intentional rather than chaotic (even if it is always you build chaotic).

The problem is that most teams treat that system like it’s permanent. It isn’t. It’s just a snapshot of what worked at a particular moment in time, based on the size of your team, the type of work you were doing, and the level of experience you had in the room.

As a business evolves, that context changes. The work gets more complex, the volume increases, and the team becomes more experienced. What used to feel helpful can start to feel heavy, but instead of questioning whether the system still fits, most teams just keep adding to it.

They add more meetings to stay aligned. They add more oversight to stay in control. They introduce new roles to manage the growing complexity. All of it makes sense in isolation, but over time, it creates a kind of drag on the entire organization.

When coordination starts to take over

One of the things that stood out most in this conversation was how much time the team was spending talking about work instead of actually doing it. They had a weekly resourcing meeting that ran well over an hour, followed by a company-wide meeting where people walked through their task queues. There were additional touchpoints throughout the week to keep things on track.

None of those meetings is inherently bad. In fact, they’re all pretty standard. The issue was that the meetings had become necessary for the team to function at all. People weren’t leaving those conversations with clarity so much as with a temporary alignment that would need to be re-established a few days later.

That’s usually a sign that the system itself isn’t providing enough direction. When that happens, teams compensate with conversation. They check, recheck, and validate decisions that should be straightforward, not because they’re incapable, but because the structure around them doesn’t give them enough confidence to move independently.

When roles stop making sense

The other thing happening, which made everything more complicated, was how roles had evolved.

In this case, account executives were also functioning as project managers. That’s not unusual, and in many agencies it works just fine. The challenge was that a traffic manager had been introduced to help coordinate work across the team, but the responsibilities between those roles were never fully redefined.

What you end up with in that situation is a lot of overlap without a clear shift in ownership. The people closest to the client and the work are trying to manage scope, timelines, and priorities, while someone else is trying to optimize how work is distributed across the team. Without a shared understanding of who makes which decisions, it starts to feel like people are stepping on each other’s toes.

From the outside, it can look like a people problem. In reality, it’s a structural one. Everyone is doing what they think is right based on how their role has been defined, but those definitions no longer line up with how the work actually needs to happen.

When the system stops telling the truth

At the same time, the team had invested heavily in their tools and data. They had detailed schedules, reporting in place, and a strong emphasis on forecasting and utilization. The intention behind all of that was solid. They wanted to understand capacity, protect their team from burnout, and make better decisions about hiring and planning.

The problem was that the data coming out of the system wasn’t something they fully trusted.

Baselines were being adjusted in ways that made it hard to track what was originally planned. Tasks were sitting in queues even when they weren’t actionable. People were working around dependencies because they needed to keep things moving, which meant the system no longer reflected reality.

Once that starts happening, the system becomes less of a source of insight and more of a record of what people hope is true. Leaders compensate by asking more questions, digging into more details, and creating more opportunities to “check in,” which adds even more overhead.

It’s a frustrating place to be, because you’ve invested in the right things, but they’re not giving you what you need.

When experience pushes back

One of the more subtle signals in situations like this is how experienced team members respond.

As teams mature, the people doing the work develop stronger instincts. They understand the flow of a project. They know where things tend to go wrong. They’re capable of making good decisions without needing every step spelled out for them.

So when they start pushing back on the level of detail in schedules or the number of touchpoints required to move work forward, it’s worth paying attention. That pushback isn’t about avoiding accountability. It’s usually about the system not matching the reality of how they work best.

If your most experienced people feel slowed down by the structure you’ve put in place, there’s a good chance that structure was designed for a less experienced version of your team.

What’s actually going on with your delivery process

When you zoom out, none of this is about a broken process.

It’s about a system that was designed for a different stage of the business and never fully adapted as the business grew.

The natural reaction is to try to fix the symptoms. Maybe you hire new talent. Maybe you introduce a new tool. Maybe you tighten expectations around how schedules are maintained. Those things can help at the margins, but they don’t address the underlying issue.

The real work is stepping back and asking whether the way you’ve structured delivery still makes sense for where you are now. That means looking honestly at how decisions are made, where work gets stuck, how roles are defined, and what your team actually needs to do their jobs well.

It often leads to simplifying rather than adding. Fewer meetings instead of more. Clearer ownership instead of shared responsibility across too many roles. Systems that reflect how work actually flows instead of how you wish it would.

None of that is particularly comfortable, especially when it means admitting that things you invested in are no longer helping. That’s the part people tend to avoid.
But it’s also the part that fixes the problem.

T L; D R - If your delivery process feels heavier than it used to, your system hasn’t kept up with your business. More coordination won’t fix it.

If you’re in that spot, you can work with me. I help teams figure out what’s actually going on and build a delivery model that fits how they operate today.