You're Not Managing a Team, You're Setting the Tone for One

Most leadership advice is just management advice with better branding: Delegate more! Communicate clearly! Stay organized! 

None of that is wrong, it's just incomplete. There's a difference between managing tasks and leading a team, and strong leaders know exactly which one they're responsible for.  One engagement in particular made this clear to me. 

When everything looks fine

A few years ago, I was leading a client effort that should have been hitting its stride. The team was smart and capable. The client was engaged and moving fast. On paper, we were up and running, but something was off in a way I couldn't immediately name. 

The team was underwater. Long hours, visible stress, the kind of exhaustion that makes you assume people are pushing hard on the right things. Deliverables kept slipping, but there was always a reasonable explanation. Meetings happened. Updates got shared. Nobody flagged a problem. 

Then the schedule broke. 

We had multiple client meetings land at the same time on the same day, and my team finally admitted what had been quietly true for weeks: they weren't prepared to lead any of them without me in the room. Not because they lacked ability, but because they didn't have a clear enough understanding of what the program was trying to solve or how it worked. Instead of raising that early and addressing an uncomfortable problem, they'd been muddling through, trying to project confidence while depending on me to carry every client interaction. 

They weren't avoiding accountability, they were drowning in ambiguity and didn't have the language to say so. That was the moment I realized the problem wasn't effort. It wasn't attitude. It was that I had never created the conditions for them to truly own the work. 

The signal I missed 

Here's what I had been measuring: hours logged, meetings attended, deliverables in progress. 

Here's what I hadn't been measuring: whether my team understood the work well enough to lead it independently. Whether they felt equipped or just busy. Whether the structure we were operating in was creating clarity or just creating motion. 

Those things don't show up in a status report. They show up in patterns: the same questions resurfacing week after week, decisions that should be straightforward taking longer than they should, a team that's working hard but not moving forward. 

Strong leaders learn to read those patterns before they become crises. I hadn't been reading them because I'd been reassured by the activity. Success leaves signals before failure does. Most of us just aren't trained to look for them 

What I did differently

Once I finally realized what was happening, I started addressing it directly. 

First, a hard conversation about ownership, accountability, and what it means to communicate early when something isn't working. Not punitive. Just honest. The team needed to hear that muddling through quietly was more damaging than raising a problem early, even if raising it felt uncomfortable. 

Then we handled the immediate fire. The client schedule got rearranged to buy us space. The meetings that couldn't move, we prepared for together. 

The more important shift came after. Once the acute pressure was off, I reset with the team in a way I hadn't done at the start of the engagement. We ran mock client meetings with other leaders playing the role of confused, skeptical clients, and my team had to respond in the moment. Real questions, real pressure, but in a room where it was safe to stumble. 

What that practice gave them wasn't just knowledge. It was language. Confidence. A shared understanding of what we were there to do and what it looked like to execute it well. The kind of clarity that should have existed from the beginning, and that I had assumed into existence rather than built. 

The next round of client meetings went differently, not because the team had changed, because the conditions had. 

What this means for leadership

That experience reframed something for me that I haven't gone back on since. 

When you're the one holding all the context, making all the calls, and showing up to every critical moment, it feels like leadership. I've found that it's really a structural problem wearing the costume of leadership. The team pays for it in burnout, stunted development, and an inability to operate without you present. 
 
The shift that matters isn't working less, it's designing better. Clarity around what the work is trying to accomplish. Shared language for how it runs. Structure that makes it visible when something is drifting before it becomes a significant problem. 

Most of the time, that starts with an honest look at what you've really built versus what you've assumed. 

A question worth sitting with

If you stepped out of your team's next three client meetings, what would happen? 

Not because you should, because the answer tells you something important about the conditions you've created. Whether your team has the clarity, the language, and the ownership to lead without you in the room is one of the clearest signals of where you are as a leader. 

In the next post, I'll get into what it looks like to stop being the system your team depends on and start building one that works without you.