Slow Decisions Are Expensive

A people problem you put off does not go away. Everyone else just starts working around it.

I think it’s safe to say that we’ve all been in those situations.

We’re sitting in a meeting, reading an email thread, or listening to someone on the team vent, and you just know where the conversation is leading.  Something you don’t want to confront but you know you’ll have to.

But you let it slide in the hopes it’ll get better. You don’t want to micromanage everything, right?

Two times stand out for me, because from the inside they looked nothing alike. One was a slow burn that wore on the team for years. The other ended with us losing a leader and our biggest client on the same day.

Hired Fast, Fired Slow

For a long stretch of our history, we made people decisions backward. We hired fast, and we fired slow. It should be the other way around.  

Hiring fast is the easy mistake to spot in retrospect. I shared previously that I had an overly ambitious growth plan for the company that resulted in some rushed decisions. Firing slow is harder to see, because it usually starts with something that feels like a virtue. You like the person. You have invested in them. You tell yourself it is a rough patch.

Sometimes it is a rough patch. That is exactly what makes this hard.

The Slow Burn

The first person was a good person, then and now. When their work got done, the quality was excellent.

Getting it done was the problem.

They procrastinated. They avoided the hard work and took the easy wins, and when a chance came to do something other than the core of the job, they took it. They recognized the issue, felt guilty about it, and in us found sympathetic ears.

We all do these things, by the way. I get it. *guilty*

As a team, we understood their challenges, so we kept making allowances. Client work backed up and timelines slid. We did our best to cover the gaps, moved work around, and kept going. For at least two years.

Everybody liked this person. But helping had turned into a standing arrangement, and work that belonged on one desk routinely landed on another. The question underneath it was fair: why doesn’t the same latitude apply to the rest of us?

We had let an exception become part of how the company ran, without ever saying out loud what it cost everyone else.

My partner Chris has written about the idea that at Sanctuary it is our work, not my work. Accountability runs across the team, peer to peer, not only from management down. When one person gets carried, the team gets let down, and the people letting them down are the owners who will not act.

When we finally made the change, productivity jumped almost right away. The team had routed around the bottleneck for so long that the workaround felt normal. The person landed somewhere better suited to the kind of work they do best, without the same pressure. Not because we were bad or they were bad. It just was not the right place for them.

We thought we were giving someone more time. We were asking everyone else to pay for it, and quietly resenting the person we said we were protecting. That wasn’t fair to anyone.

The Shock

The second story is harder and more embarrassing to share. 

We hired an A-player. A leader. Brilliant, enthusiastic, and they did great work. They wanted the autonomy to run their group, and I wanted to give it to them.

But over time, they grew frustrated with the job. With me. With the circumstances we were in as a company. 

Some of that was earned, because we had things to improve. But they also stopped owning some things that were theirs to own. They blew off meetings they felt were unimportant. There were angry outbursts and open conflict. 

We would periodically resolve issues and move on.

At the same time, they became territorial about our biggest client. Somewhere between 60 and 80 percent of their time went to that one account. They cut me out of meetings. They wanted to own the relationship.

I let that happen. It was our biggest client, and I told myself that was just what the account needed.

That client ran on emergencies. Approvals would come in at noon on a Friday for something that had to launch by 7 a.m. Monday. Something was always late, and then it was always urgent. My team member saw this as being responsive. I saw poor planning, the kind we had managed out of every other client relationship by setting expectations and working ahead. We clashed over it, but I never held the line the way I had with everyone else.

So the emergencies rolled downhill. Weekend emails. Slack messages assigning work due Monday. The people who reported to this leader were being treated like personal assistants instead of being taught and guided.

I heard rumblings, but nobody came to me directly. Looking back, expecting people to complain about their own manager was unrealistic. I should have been asking better questions. Instead, I was busy with other things. I had delegated the authority, I trusted the person, and they assured me they were stabilizing the client.

That was the distinction I missed. Giving someone authority does not mean stepping away from the standards they are expected to uphold. The missed meetings, the repeated conflict, the closed-off client relationship, and the pressure on the team were one problem, and I kept treating them as four small ones.

Then one day we lost both. They told the client they were leaving Sanctuary and went to work for them. We lost our biggest client and a leader in the same day, with a very short window to hand off the work.

We got through it. We did not have to lay anyone off, and within a matter of months we had replaced that business with healthier clients. But it was destabilizing, and it was scary.

A few years later, that client went out of business. An occasional emergency is part of serving clients. A relationship built on constant emergencies isn’t healthy for anyone, the client included.

Same Failure, Two Shapes

From the inside, these two did not feel related. One took years. The other escalated over about a year, got acute in the last three or four months, and then went off all at once.

It was the same mistake. I saw a pattern, found reasons to wait, and let other people adapt to it. In the first, it was quietly moving work between desks. In the second, it was accepting that one person controlled a major relationship and that the team would absorb the client’s urgency.

I was afraid of the conversation. I was hoping it would get better. I had my head in the sand. That is my part, and I own it.

It does not excuse the people involved from theirs. Someone whose work keeps landing on a colleague’s desk is not meeting a fair expectation. Someone trusted to lead still has to show up to the meetings, develop their people, manage the client’s expectations, and work inside the culture. Those standards don’t get waived because a person is talented, well liked, or attached to a big account. The whole team is owed the same standard.

If we had faced the second situation squarely, I believe we would have planned an exit from that client. The dollars were great, but the relationship was eating capacity, keeping us from growing, and wearing on the team. A planned transition would have worked for everybody. Instead, we absorbed one that worked for nobody.

What We Do Differently Now

Jim Collins calls it confronting the brutal facts. Knowing the principle is easy. Telling a rough stretch from a real problem while you are in the middle of it, especially with someone you like or trust, is the hard part.

We hire more slowly, and we work to get an honest answer about fit inside the first 90 days, said out loud, on both sides. A clean, early answer beats years of forcing a fit. Sometimes the honest answer is a different seat, and some of our best people found their role that way.

EOS gives us a shared language for whether someone is right for the seat they are in. How to Be a Great Boss by Gino Wickman and René Boer pushed me to treat managing people as the job, not something that happens when there is time. And we use a three-strike rule, so a repeat problem gets named instead of patched over and forgotten.

I also watch for the patterns that used to be easy to explain away: one person controlling a client relationship, after-hours demands becoming routine, a team going quiet about their manager, the same conflict coming back after we thought it was settled. When I see a couple of those together, it is time for the conversation, not another month of hoping.

Slow decisions are expensive, and most of the bill gets paid by people who never had a say in the delay. Knowing a conversation is needed is rarely the hard part. Admitting how much the company has already bent to avoid it is.

Kelly Brown

CEO & Managing Partner

What to Read Next

11/11/2026

There have been many times over the last 20 years when we received news that felt like a disabling punch in the jaw. Every business has setbacks and challenges. I’m talking about the type of…

Read More

10/27/2026

I’m not going to mention names, but I’m friends with one of our largest competitors in our local area. It’s been this way since the early stages of our business, and we continue to be…

Read More

10/26/2026

You can set the expectations for a meeting. Everyone in the room has to choose to honor them. We have a lot of meetings at Sanctuary. I would love to have fewer. I would also…

Read More