Most Slow Organizations Are Doing Too Many Things

Most slow organizations are doing too many things at once. Speed comes from deciding what not to do, and from someone senior enough to say it out loud.

Tangled paths resolving into one straight line, cream on charcoal

When a team isn’t moving fast enough, the usual question is “How do we move faster?”

A better question is: What are we doing that is not on the path?

Most slow organizations are working hard. They’re just doing too many things at once.

Nobody decides to be slow

It happens one yes at a time.

A new market looks promising, so it gets a small team. A big customer asks for a feature, so it goes on the roadmap. Two options look good and nobody wants to pick, so both get funded. A leader wants a new dashboard, so an analyst spends a month on it.

Each yes made sense in the room where it was given. That’s what makes this hard. There’s no single bad decision to point to.

But every yes adds work. It adds meetings and handoffs, and it competes for the same people. A year later the team is working on twelve things that each matter, and nobody is looking at the total.

From the outside, it looks like ambition.

What pushing harder does

When that team falls behind, the usual response is to push harder.

Let’s say revenue starts slipping. The pipeline review goes from monthly to weekly. A daily standup appears. Forecast accuracy becomes a project. A new consultant is hired. Another new consultant is hired. Two more people get hired to do more of the same.

Everyone is working. Nobody has asked what’s not on the path.

Pushing harder makes a team faster at what it’s already doing. It doesn’t help anyone figure out what to stop.

There’s also a cost to the culture. People learn that looking busy and stressed counts as contributing. A focused team working on one important thing, with room to think, looks underused. So it gets handed more.

You end up punishing the focus you need most.

Focus is a strategy question

A list of priorities isn’t a strategy. Everything on the list matters. That’s why it made the list. Strategy is the decision about where the list stops. What’s above the line gets people and money. What’s below it doesn’t. If nothing is below the line, no choice was made.

Here’s a test you can run in your next leadership meeting:

Name three things we decided not to do this year, and why.

If the room can’t answer, you have priorities. You don’t have a strategy yet.

Priorities cost nothing to hold. A strategy costs something specific to someone specific. That cost is how you know a choice was actually made.

Why no is so hard to say

If all of this is clear, why do organizations keep saying yes?

Because a yes and a no don’t cost the same people the same amount at the same time.

A no is immediate and personal. Someone’s project ends. Someone’s team gets smaller. Someone has to say it out loud to a colleague who had good reasons. Everyone remembers who said it.

A yes spreads its cost out. It shows up months later as a missed date, a stalled project, or a team that’s always behind. By then, nobody can trace it back to the moment it was given.

So people keep saying yes. That’s what the setup rewards.

Changing that takes someone senior enough to own the no’s in public. When the person at the top says out loud what we’re not doing, the people below them don’t each have to pay the price for the organization’s focus.

That’s a big part of the job. It’s also the part that’s easiest to avoid.

Big goals need more focus

I’m not arguing for lower standards or smaller goals. I’m arguing against staying busy to avoid making choices.

Big goals need more focus than small ones. The bigger the goal, the more it costs to spread people across work that doesn’t serve it.

Otherwise you end up where a lot of organizations are. Everyone is busy. Nothing is fast enough. And no one can name what would have to stop for that to change.

Try it on something real

Write down everything your team is working on right now. All of it, including the small things.

Next to each one, write the goal it serves. If you can’t name one, circle it.

Pick one circled item and stop it for a month. Tell people you’re stopping it and why. Then watch what happens to the work that’s left.

Then ask your leadership team the same question. What would we stop?

If you can’t name it, the problem isn’t effort. You haven’t decided what to stop.

You don’t have a real strategy until you can name what you won’t do. Speed comes after that.

Written by Aaron Edgell

Growth executive. Builder. Writer.

Get new essays and notes by email.

One email when I publish something new.

Previous:
Next: