The Leaders Who Get the Most Done Aren't the Busiest Ones in the Room

My team started laughing when I got to my part of the daily stand-up. This wasn't a heavy stretch in our workload, it was probably just an average Wednesday and I was a delivery Manager. 

They laughed because the scene was a bit absurd. I was managing a portfolio of about 30 consultants across 8 projects under one large client organization, and every morning I would recite my action items and my meeting count for the day. It was often at least thirteen meetings. Sometimes more. All 30 minutes. All back to back. 

They laughed, and I laughed too, because what else do you do when you've built something that unsustainable and called it leadership?

I covered what strong leaders understand about not being needed in every room in the first post in this series, and what that revealed about the conditions I'd built for my team. This is the part where I turn that same lens on myself. 

What I had built

The heavy meeting volume was the culture. Managers stayed plugged in through working sessions and 1:1s, on repeat all day. Being present was how you demonstrated you were on top of things. So I was present. Constantly. 

The problem was that thirteen meetings a day left almost no time for actual management work. No time to think about where the portfolio was heading. No time to notice what might be drifting before it became a problem. No time to do anything except show up, contribute what I could in 30-minute windows, and move to the next one. 

I had built a schedule that made real leadership nearly impossible, not a leadership system. 

The stand-up laughter was the moment I stopped being able to ignore that. The shift I needed to make involved designing something that didn't require my presence in every room to hold together. 

Solving or designing 

There's a question that separates leaders who scale from leaders who become the bottleneck: am I solving this problem, or am I designing so this problem doesn't come back? 

Most leaders default to solving because it's immediate. It produces visible results and creates the feeling of forward motion. Designing is slower and doesn't reward you until something doesn't happen - a decision that got made without you, a new team member who oriented without needing six weeks of shadowing, a risk that surfaced early enough to address before it reached fire-drill status. 

The shift from solver to designer is one of the more underrated transitions in leadership. It doesn't mean being less involved. It means being involved differently. 

What the design included

For my portfolio, it came down to a few specific changes. 

• Decision rights and role clarity. People defaulted to me because it wasn't always clear who else to go to. Once we mapped out who owned what and who had authority to decide at each level, a meaningful chunk of what was landing in my lap stopped coming to me. 

• Priority clarity. Not a list of everything that mattered - every team has that. A clear answer to what gets resourced when everything can't happen at once. When that's explicit and visible, teams stop waiting for a manager to arbitrate and start making calls themselves. 

• A different stand-up format. We stopped reciting action items and meeting counts. Instead, the stand-up became a place to flag risks and areas that truly needed manager awareness or involvement. The difference sounds small. It wasn't. It changed what information I was getting and when, and it made the meeting worth having. 

None of this was complicated. Most of it just required me to do something counterintuitive: step back from the volume of contact I'd been using as a proxy for being useful, and trust that the structure would hold. 

When it did, escalations dropped because the team had enough context to resolve them. When something did get stuck, it pointed to a gap in the structure rather than a gap in someone's commitment. New people got up to speed faster. Growth didn't immediately require re-coordinating everything from scratch. I spent more time on work that required my judgment and less on work that just required my presence. 

What I lost, and what got better

The team appreciated it almost immediately. Less time in meetings meant more time for actual work - creative collaboration, big-thinking, business development. The internal operations ran differently, and better. 

What I gave up was granularity. When you're in every room, you hear everything. When you're not, you don't, so I found it differently. The restructured stand-up made risks visible in a way the old format never had. And with some of the time I'd gotten back, I started reading more closely into individual and team trackers - not to monitor, but to notice. To see what people were working on, where I had questions, where something looked like it might need attention before anyone flagged it. 

It was a different kind of awareness. And for the leadership role I was responsible for, it was more useful. 

Where Asana enters

The system I built was largely manual at first - restructured meetings, documented decision rights, clearer role definitions. It worked, but it required ongoing maintenance in a way that a shared platform removes. 

This is where Asana earns its place, not as a task tracker, but as the structure itself. When priorities, ownership, dependencies, and status live in one visible system, the design becomes durable. Leaders don't have to re-inject context into every conversation because the context is already there. New team members can orient without reconstruction. Risks surface in the work, not just when someone decides to raise them. 

For a portfolio the size of what I was running, that kind of shared visibility would have changed what my mornings looked like before I ever got to the stand-up. The stand-up itself becomes a different conversation when everyone has already seen where things are in real time. 

The leaders I've seen use Asana most effectively aren't using it to watch their teams work. They're using it to build something that holds when they're not in the room. 

If you pulled up your calendar right now and counted your meetings for tomorrow, what would that number tell you? 

Not about how hard you're working. About what you've built, and whether it can run without you in every conversation. 

Keep an eye out for the next blog in the series: leaders of the strongest teams know when to bring in backup. Who to partner with, when, and why getting that call right matters.