Remember when the news was about what happened, not how to feel about it? 1440's Daily Digest is bringing that back. Every morning, they sift through 100+ sources to deliver a concise, unbiased briefing — no pundits, no paywalls, no politics. Just the facts, all in five minutes. For free.

Read the newsletter trusted by 4.5 million fact-seekers.

When it rains it pours, and lately it's been pouring — but in the best way. I've been in a number of conversations with leaders who are genuinely investing in building their teams — not just filling seats or putting out fires, but thinking seriously about what it actually takes to lead well, especially right now. It makes my heart happy. Now if it could actually feel like spring, we’d be set….

I'm also mindful that a lot of orgs are working with tighter budgets. They want to invest in their people but can't bring someone in for deeper support — or they have one or two leaders they really want to develop and need a focused way to do it. If that's you, or someone you know, my workshop Build Your Leadership Operating System is on May 28th. Sending a new leader — or a leader stepping into a new team — somewhere to think, strategize, and get grounded pays real dividends. General subscribers get a discount. Just use this link.

Also — big news — the paid tier launches today. Here's the honest reason I'm doing this: cost is a real constraint for a lot of people, and a paid tier lets me give those leaders real tools — scripts, templates, things you can actually use. Paid subscribers get more content in every issue, additional content between issues, and discount codes on workshops. Let's be honest, writing takes time too. More on that below.

Okay. Let’s get into it.

In volleyball, there's a play that happens at every level — recreational leagues, high school gyms, professional courts. The ball goes up, and one of two things happens.

Nobody calls it. Everyone assumes someone else has it. The ball hits the floor.

Or everyone calls it at once. Three people converge, crash into each other, and the ball hits the floor anyway.

Two different problems, both having the same result.

I use this example a lot in my consulting work because it captures something that org charts and job descriptions almost never do: clarity isn't just about knowing your role. It's about knowing your position relative to everyone else on the court — who moves when the ball goes left, who holds when it goes right, who covers when someone else is out of position. When that's clear, you have a team. When it isn't, you have a group of people working very hard in the same direction (mostly) and still dropping balls (or bumping heads).

When roles are genuinely clear, people know what they own — and I don't mean their job title. I mean the actual decisions and deliverables they're responsible for, the ones where if it doesn't happen, it's on them. They also know where that ownership ends— which in my experience is the harder part. And they have enough shared understanding of everyone else's position that when something ambiguous lands, they're not guessing or stepping on each other — they know who calls it.

That last piece is what most org charts completely miss. A chart tells you the hierarchy. It doesn't tell you who moves when the ball goes left.

I want to be careful here, because I've heard the advice — delegate more, trust your team, let go — and I know how hollow it sounds when you're in the thick of it.

A few years ago, I was working with a founding Executive Director I'd known for over a decade. I noticed he was carrying more than any one person should carry, and I said something — as a friend, not as a consultant. It was the only time in ten years he got sharp with me.

"How am I supposed to do that," he said, "when every time I lean on someone, they either mess it up or quit? How do I even decide what to hand off?"

I felt that in my chest, because I had lived it. When I was starting out as a leader, I didn't feel like I could truly lean on anyone either. It wasn't about my team's capabilities. The landscape around us felt like it was constantly changing and I was managing chaos faster than I could name it. And if I'm being honest, I hadn't yet done the work we're talking about — being clear with my team about what I needed from them and how we should work together. So in a bid to protect them, and to protect the real progress we were making, I held it together myself. Misguided as that was. Delegation felt like a binary.

Here's the thing about delegation advice: it skips a step. Usually several steps. It starts with understanding what actually needs to happen — not the title, not the function, but the real work. Then it requires being honest about where your judgment is genuinely irreplaceable versus where you're holding on out of habit or habit dressed up as standards. Then it's about defining what "done well" looks like so you're not setting someone up to fail a standard they couldn't see.

The RACI, the MOCHA, the delegation matrix — all useful tools. But they only work after you've done the introspective work they assume you've already done. That's why the frameworks so often feel incomplete. You fill them out and still feel stuck, because the framework can't do the thinking for you.

The 20-minute audit below won't solve everything. But it'll show you where the confusion lives.

Pull up a blank doc. Don't look at your org chart yet.

Step 1 — List the five most important outcomes your team needs to produce in the next 90 days. Not tasks. Outcomes. "Launch the new onboarding program," not "update the slides."

Step 2 — For each outcome, write one name. One person who is ultimately accountable for whether it happens. Not a committee. Not "we." One name. If you can't write a name — or if you wrote your own name for more than two of them — that's information.

Step 3 — Now ask: does that person know they own it? Not "do they know it's on their plate" — does the person know they are accountable for the outcome, not just a contributor to the effort? Have you actually said that out loud?

Step 4 — Identify one outcome where the ownership is genuinely unclear on your team. Where two people think they're the lead, or nobody thinks they are. That's your starting point.

That's it. It won't take 20 minutes if you already know your answers. It'll take longer if the exercise makes you realize you don't.

Want to go deeper?
Paid subscribers can scroll down to see the Role Clarity Conversation script that I use and have my clients use to surface misalignment- without sounding like an HR exercise. There's also some advice on how to use this with peers. Scroll down for more…..

Alright, back to our usual programming.