Stop training your team to ignore you

It’s a painfully familiar pattern.

An agency-founder walks into a Monday meeting with a new idea: A new service line / rebrand / new system to try / partnership that could change everything / Yet another AI initiative. The founder is giving it everything and the wheels begin to turn. Tasks get assigned. Someone sets up a Slack channel. Project Plan… Trello board… more spreadsheets than is reasonable.

Six weeks later it is the Mary Celeste of initiatives. The Slack channel has gone silent. The shared doc hasn’t been touched since week two. More urgent things happened. Newer, shinier things took over. No-one killed the initiative, or announced its demise. It just quietly faded to nothing.

I see this happen over and over in the agencies I talk to. In some it happens multiple times a quarter. The founders who even think about it often chalk it up to  the usual reality of running a busy business. Things get started. Not everything works out. You move on.

But there’s a cost to this pattern that almost nobody talks about. It’s not the wasted effort, although that’s real enough. It’s what it teaches your team.

What your team is actually learning

Every time you launch something with enthusiasm and then let it quietly die, your team draws a conclusion. Not consciously or maliciously, but they still do. They learn that your priorities aren’t really priorities. That this week’s big idea will probably be replaced by next month’s big idea. That the safest response to any new initiative is to wait and see whether it survives.

Discuss this in the LinkedIn thread →

That sounds like laziness, but it is perfectly rational. Everyone is busy. Everyone has limited energy. They’ve watched the pattern repeat enough times to know that investing properly in the early stages of a new initiative is a risk – because there’s a fair chance it’ll be abandoned before it goes anywhere.

It’s easy to get frustrated when our team doesn’t buy into our ideas, but that lack of buy-in is often something we’ve trained into them. And the signs are usually there if you look: the slight sag in energy when you announce something new. The polite nodding that doesn’t translate into action. People going through the motions in the first few weeks, doing just enough to not look disengaged, but not enough to actually move things forward. You might see that as a “them problem”. Maybe it is, but it’s worth asking whether the pattern starts with you.

I’ve done this myself

I often write these articles wondering what my old team must think when I put them out there. The lessons I have learned have definitely come as much from what I got wrong as right. That was me for a number of years. 

I’ve always been good with ideas. Full of enthusiasm I would start things with genuine conviction and then let them drift when something else demanded my attention or the inevitable obstacles cropped up. At the time I told myself I was being responsive and adaptive. In hindsight, I was often just being inconsistent. Inevitably my team started responding accordingly; with a polite “wait-and-see” that I mistook for a lack of initiative or motivation.

Why this keeps happening

The reason this pattern keeps repeating isn’t usually that founders are flaky or easily bored. It’s that they don’t have a clear enough plan. When you don’t know where you’re going, every new idea feels like it could be the right move. You start things reactively because starting feels like progress. And without a destination to measure against, there’s no framework for deciding what to commit to and what to leave alone.

When you do have a clear picture of what you’re trying to achieve and what needs to happen to get there it becomes much easier to say no to the things that don’t fit. More importantly, it becomes much easier to properly commit to the things you say yes to. Your team sees fewer initiatives, but the ones they see actually go somewhere. Over time that changes what they expect when you start something new.

What to do about it

There’s no five-step framework for fixing this. But there are a few things worth dedicating some thought to.

First, be honest about the pattern. Look back over the last year or two and count the things you started and never properly finished. Not the things that failed –  the things that just faded.  

Second, understand that every new initiative spends credibility. You have a finite amount of it with your team. Each time you launch something and let it die, the balance goes down. Each time you see something through, it goes back up. Start thinking about new ideas in those terms and you’ll naturally become more selective.

Third, fewer things, properly committed to, will almost always beat a long list of half-started projects. This is what I mean when I talk about “Velocity not speed”: It’s not about doing less, it’s about making sure what you do actually goes somewhere. That requires a plan, a destination, and the discipline to stay on the road even when a more interesting turning appears.

Finally, if you do decide to stop something, stop it properly. Tell the team why. Acknowledge the work that went into it. Make it a decision, not a disappearance. Even killing an initiative well builds more trust than letting it fade into nothing.

Your team wants to get behind your ideas. But they need to believe those ideas are going somewhere first. That’s not their job to fix. It’s yours.

Discuss this in the LinkedIn thread →