Stop Being the Expensive Courier

Welcome to the show. Daniel, I want to start with a scene I see constantly: a newly promoted director opens Monday by approving copy, fixing a spreadsheet, calming an escalation, rewriting a slide deck, and answering six Slack threads that should never have reached them in the first place. By 6 p. m.

they feel useful... and they have done almost nothing that looked like leadership. That 6 p. m.

feeling is the trap, right? Because the word you used there - useful - is exactly what hooks people. Not strategic. Not directional.

Useful. And if you're good at cleanup, the organization will keep handing you cleanup forever. Precisely. The uncomfortable truth is that many new directors are still living as senior managers with a better title.

They are doing approvals, rescues, and quality control because those tasks produce quick gratitude. Someone says, "thank goodness you jumped in." Nobody says that when you quietly improve decision quality three levels away. Let me sharpen that.

When you say "manager-level cleanup," what are we really talking about? Because some listener's gonna say, well, I'm just being a strong leader. Fair question. I mean the work that preserves motion without increasing capability.

You rescue a deadline, but the team still cannot rescue itself next time. You approve every detail, but nobody's judgment improves. You sit in the middle of every thread, and the system becomes more dependent on you, not less. Ownership is what people actually associate with leadership, but dependency often masquerades as ownership."

Preserves motion without increasing capability." That's sticky. Because I coach a lot of brand-new VPs, and before that threshold - director, senior director - they got promoted for exactly this behavior. They were the firefighter.

They were the adult in the room. They were the person who could carry five shaky people across the finish line. Then they get promoted, and the same instinct starts costing them leverage. Yes, and the more competent you are, the more dangerous this becomes.

Competence attracts stray work. If you're articulate, you get asked to rewrite. If you're organized, you get asked to coordinate. If you're calm, you get escalations.

If you're politically trusted, you become the place where ambiguity goes to hide.Ambiguity goes to hide - that's exactly it. It shows up wearing a calendar invite.Usually a recurring one.

So here's the test I like: shadow task identification. Find the work you do that no one would miss if you stopped doing it for one week. Not forever. One week.

If the work disappears and nothing meaningful breaks, that task may be feeding your identity more than your function. Wait - one week is the key there. Not some dramatic three-month sabbatical. Just five business days.

Because five days is enough for the truth to show itself. Either people adapt, or they reveal the thing actually needed your role. That's a very clean diagnostic. It is.

And it is mildly brutal. Because many highly capable directors discover that a surprising amount of their calendar exists to soothe the organization's anxiety, not to improve the organization's outcomes.Okay, but I wanna push a little. Some anxiety-soothing is leadership.

If a cross-functional group is tense and you can settle it, that matters. I agree - but only if your presence changes the quality of the decision. If you're there merely to reassure everyone that a competent adult has entered the chat, you're acting as emotional middleware. Helpful in the moment, perhaps, but not a scalable use of a director.

Emotional middleware. That's one people are gonna remember. And maybe wince at a little.So let's put numbers on this, because abstractions let people wriggle away.

Say you're a director in a high-growth tech company. In your orbit you've got 8 direct and skip-level reports that roll up through you, maybe 6 peers across product, design, data, finance, and go-to-market, 3 or 4 senior stakeholders, a handful of partner managers, program people, maybe a vendor lead or two. Add all the dotted-line relationships and decision threads, and suddenly you've got 47 people' worth of accountability in your world. Forty-seven is the right kind of uncomfortable number.

Not 200, which sounds absurd. Forty-seven sounds plausible... and exhausting. Exactly.

And here's the catch: you do NOT have 47 people you can influence directly. You probably have 12. Maybe 10 on a bad week, 15 if you've been in role a while. Twelve people who will actually change behavior because you said something, framed something, coached something, or made a call.

So the math becomes quite clarifying. Forty-seven people create consequence around you. Twelve people absorb your influence. If you spend your week acting as though all 47 are equally steerable, you will fragment yourself into administrative vapor.

Administrative vapor is good. Because that is what it feels like. You're in 19 meetings, 40 Slack threads, two escalations, three status docs - and at the end of the week you touched everything and shifted almost nothing. This is where directors confuse proximity with control.

You're near the problem, therefore you imagine you can manage the problem. But proximity is not leverage. Being copied on a thread is not influence. Attending the meeting is not changing the outcome.

Knowing about the issue is not the same thing as owning the decision architecture around the issue. Let me make that concrete. Picture a director spending Monday morning in a launch status review, Tuesday chasing three escalations, Wednesday rewriting a peer's update so it'll land better with the VP, Thursday joining a roadmap debate "just in case," and Friday doing cleanup because engineering, product, and support each left with different assumptions. That's a full week.

It feels responsible. But maybe only two of those hours actually changed outcomes.[questioning tone] Which two? Usually the hours where they clarified a decision, named a trade-off, or coached one of the 12 people who can carry that thinking outward.

Not the status hour. Not the update-chasing. Not the polite attendance. Yes.

Less rescue, more framing. The person who frames the conversation is perceived as more senior than the one simply answering questions. If you enter a cross-functional mess and say, "Here are the three decisions, here is the owner of each, and here is what happens if we defer them," you've influenced the system. If you merely gather everyone's updates and circulate them beautifully, you've become a very elegant courier.

A very expensive courier, by the way. Quite. And there's a psychological reason people fall into this. Status work and cleanup work offer immediate feedback.

Strategic influence is slower. You may spend 30 minutes tightening a decision rule and not feel anything that day. But two weeks later, six meetings never happen. That "six meetings never happen" result is the part newer directors under-value.

They want visible heroics. But often the highest-leverage thing you did was invisible subtraction. Momentum is the currency of career advancement. Directors create momentum by reducing drag across key nodes, not by personally pulling every cart uphill.

So let us make this practical. The shadow task audit is wonderfully unglamorous. Take one ordinary week - not your best week, not your crisis week - and list recurring tasks. Every recurring task.

The Thursday escalation check-in. The deck review. The status chase. The "quick sanity check" requests.

The meeting you attend because history says you attend it. And don't just write categories like "meetings." Write the actual thing. "Tuesday 2 p.

m. launch sync." "Rewrite QBR intro." "Chase legal for answer."

Specific names matter because vague lists let your ego hide. Exactly. Then ask three questions of each item. First: who truly owns this?

Not who is currently doing it - who should own it. Second: what happens if I do not touch this for one week? Third: is this strategically appropriate for my level, or merely politically familiar? That last phrase - politically familiar - is so real.

There are tasks people keep because they know how to win there. They know how to look competent there. It's familiar territory, even if it's below level. Yes.

Common shadow tasks appear in almost every audit. Chasing updates that should live in an operating cadence. Rewriting other people's work because you dislike ambiguity in their thinking. Attending meetings "just in case" rather than because your judgment is required.

And making decisions that should have been made elsewhere - usually because you do not trust the local judgment yet.And that last one is the painful one, because sometimes the trust issue is valid. The manager really isn't ready. The peer really is vague.

The team really does drop details. Quite so. But even then, the answer is diagnostic, not permanent absorption. If a manager cannot make a decision, your task is to improve the manager's decision-making apparatus, not to inherit every decision indefinitely.

Okay, let's do the ghost assessment because I think this is the cleanest tool in the whole episode. If you disappeared for one week - no email, no Slack, no meetings - what actually breaks?And just as important: what quietly proves it never belonged to you? That is the director's ghost assessment.

Imagine your absence as a kind of X-ray. The fractures that appear reveal true accountability. The work that keeps moving reveals borrowed chores. Grab the distinction there: true accountability versus borrowed chores.

If a hiring decision stalls because only you can align compensation, scope, and org implications, that's probably real director work. If the weekly status note still goes out because somebody else pulled updates in ten minutes, that was borrowed chore territory. Yes. If executive communication degrades because you were the only person framing trade-offs clearly, that matters.

If a recurring sync feels slightly messier but still reaches the same conclusion, you have learned something invaluable. You were serving smoothness, not substance.I can hear a listener saying, "But my organization is messy. If I let go, quality drops."

And maybe it does... briefly. Briefly is the operative word. A small, temporary drop in polish is often the admission price of building actual capacity.

Directors who cannot tolerate that dip frequently end up preserving immaturity around them. Preserving immaturity. That's a hard mirror. But it's fair.

So once you've got the audit, don't just stare at it and feel judged. Sort it. Three buckets: stop, delegate, redesign. Stop means the work adds so little value that it should simply disappear.

Delegate means the work matters but should live with someone else, with context and support. Redesign means the work keeps recurring because the system is broken, so you replace heroics with a template, a rule, a cadence, or a clear owner. And the distinction matters immensely. If you eliminate a redundant check-in, that is stop.

If you hand meeting notes to a manager and coach them on the standard, that is delegate. If you create a one-page escalation protocol so people know when to involve you and when not to, that is redesign. Systems are simply decisions made in advance.Say more on redesign, because I think a lot of directors hear "delegate" and dump tasks sloppily.

Quite right. Delegation without structure is just relocating confusion. Redesign asks, what repeatable mechanism would make this less dependent on personal rescue? A status template.

A decision memo format. A rule that no issue comes upward without options and trade-offs. An escalation lane with thresholds. You are not offloading work; you are reducing cognitive burden in the system.

I love that phrase - reducing cognitive burden. Because that's what strong directors do. They make it easier for other people to make clean decisions. And letting go is not laziness.

It is creating room for strategic judgment, talent development, and higher-leverage influence. Discipline is what earns trust, and judgment is what earns promotions. If your calendar is saturated with tasks a capable manager could eventually own, you are spending judgment time on labor that cannot return director-level value.I remember my own version of this years ago.

I had to stop being the person who answered every leadership question in real time. It felt awful for a while. I was less immediately helpful. Fewer people walked away saying, "Thanks, Daniel, you saved me."

But the people reporting to me started getting stronger because they had to think before bringing something over. That discomfort is, I think, profoundly important. Early in one's career, visible helpfulness and actual value often overlap. At director level, they begin to separate.

You can feel less useful in the moment while becoming markedly more valuable over the quarter. And the emotional part is real. Some people are not clinging to shadow tasks because they're disorganized. They're clinging because those tasks confirm identity.

"I'm indispensable. I'm the fixer. I'm the safe pair of hands." Yes...

and sadly, indispensable is often another word for poorly designed. A healthy organization should not require the director's fingerprints on every moving part. Unless it's one of those genuine leverage points - talent calls, trade-offs, org design, stakeholder alignment. The work where your judgment compounds.

Precisely. The aim is not absence. It is selective presence.So what does a sharper week actually look like?

Less rescue, more framing. Less chasing, more decision architecture. Less involvement in every thread, more influence through key nodes - the 10 or 12 people and forums where your thinking genuinely changes direction. A director's week should contain protected time for talent reviews, for clarifying priorities, for identifying trade-offs, for shaping cross-functional decisions before they become cross-functional confusion.

And maybe this is the picture people need: instead of touching 47 relationships lightly, you work deeply through the 12 that transmit signal. Your managers. A couple of trusted peers. The recurring forum where priorities get set.

The handful of stakeholders whose interpretation becomes everybody else's reality. Exactly. Influence is not evenly distributed, so your attention cannot be either. The director who spends all week in reactive proximity to issues feels busy but becomes strangely non-consequential.

The director who shapes the few decisions that organize many other decisions may appear less frantically occupied... while moving far more.So if someone's listening to this on a Tuesday morning and wants to act today, where do they start? One move.

Cancel or decline one recurring meeting you attend "just in case," and replace your presence with a rule: what outcomes should emerge, what decisions should escalate, what format should come back to you. If the meeting collapses, you've discovered a capability gap. If it runs fine, you've discovered a shadow task. That's good.

Mine would be: look at your last ten Slack interventions. Not messages - interventions. The moments where you jumped in to unblock, edit, soothe, or decide. How many of those ten changed an outcome, and how many just made things feel tidier for an hour?

Tidier for an hour is the danger. It can feel so satisfying. Like pruning the top leaves while roots remain confused underneath. There is the analog mind coming out.

But it's right. And this is where the bigger question lands for me: are you managing the organization you currently have, with all its habits and dependencies and little rituals... or are you leading the organization you're supposed to build? Because shadow task identification is not merely time management.

It is identity work. It is choosing what you wish to be known for. The chores you absorb, or the decisions you shape. The rescues you perform, or the capability you leave behind.

And if letting go makes you feel a little less like the hero this week... maybe that's not a warning sign. Maybe that's the first honest signal that you're finally operating at the level where heroics stop scaling.Which leaves one rather uncomfortable thought, Daniel: if you removed all the shadow tasks tomorrow, would your calendar reveal your real job...

or expose that you've been hiding from it?