From manager to multiplier, delegating with confidence

Good morning. Last week we talked about the shift from manager to multiplier, and why the most capable leaders often become the ceiling on their team’s performance, not because they’re bad at their job, because they’re good at it.

This week is about the part that makes the shift practically possible: the scaffolding.

Because letting go isn’t a leap of faith. Done well, it should be a system that protects the work, develops the person, and keeps you appropriately in the loop without pulling everything back through you, every step of the way.

The leaders who get this right aren’t more trusting than others by nature. They’ve just built better conditions for their trust to be well-placed.

Here’s where a lot of well-intentioned delegation goes wrong. Leaders treat it as a binary: either I do this, or I hand it over. But that’s not how capability actually works.

Before stepping back, it’s worth asking a more precise question:

Is this a competence issue, a confidence issue, or both?

The distinction matters enormously, because the support each requires is different.

Competence is about skill and knowledge. Does this person have what they need to do this well? Have they done something like this before? Do they understand the technical requirements, the standards, the non-negotiables?

Confidence is about self-belief. Does this person think they can do it, regardless of whether they actually can? High competence with low confidence produces hesitation, over-checking, and work that never quite gets finished. Low competence with high confidence produces bold mistakes.

The goal is to find the honest overlap, and calibrate your support accordingly. Hersey and Blanchard’s Situational Leadership model, one of the most durable frameworks in applied leadership development, makes exactly this point: there is no single right way to lead someone. The right approach depends on their current level of development for that specific task. Directive support builds competence. Coaching and encouragement builds confidence. Delegating works when both are present.

A useful diagnostic before you hand something over:

And that last point is worth underlining. A great deal of delegation fails not because the person lacked capability, but because the leader hadn’t been clear about what “good” looked like, the constraints, the standards, the moments where they needed to loop back rather than push forward independently. Autonomy without clarity isn’t empowerment. It’s a setup for a mistake neither party wanted.

Try this conversation first:

"Before I hand this over, I want to make sure we’re set up for success. What parts of this feel clear to you, and where would it be helpful to talk it through first?"

"Here’s what must happen, these are the non-negotiables. And here’s where you have real room to make your own calls."

Letting people take the wheel doesn’t mean removing your hands from the dashboard entirely. Good multipliers build structured support into the handover, not as a sign of distrust, but as the architecture that makes trust possible.

Think of it as four elements, agreed before the work starts:

1. Set the rails, not the route.

Be explicit about what is fixed and what is flexible. What are the must-dos, the quality standards, the stakeholder commitments, the compliance requirements, that are non-negotiable? And within those, where does the person have genuine latitude to make their own calls? The clearer you are about the edges, the more freely someone can operate in the middle.

TRY: "Here’s what must happen, and here’s where you have full room to make your own judgment."

2. Agree on checkpoints before you start, not after things go wrong.

Check-ins feel like surveillance when they’re imposed mid-flight. Yet, they can feel like support when they’re agreed upfront. Build a simple rhythm into the work from the beginning, not to micro-manage or over-monitor, but to give the person a chance to surface questions, flag emerging issues, and know that help is close if they need it.

Drawing on Hackman and Oldham's foundational work on job design, which identified feedback as a core driver of motivation, suggests that people perform better when they have regular, low-stakes opportunities to check their own progress rather than waiting for a high-stakes review. The checkpoint isn’t a control mechanism. It’s a rhythm that replaces anxiety with structure.

TRY: "Let’s agree to touch base at [point A] and [point B], to make sure you’ve got what you need and nothing unexpected has come up."

3. Name the moments to come back.

Not everything can be anticipated, but some triggers can. Help the person understand when they should bring you in rather than push through: when the scope changes, when a key stakeholder is unhappy, when something feels materially different from what was expected. This isn’t about limiting their authority, it’s about giving them a clear signal for when the situation has moved beyond what was originally delegated.

This is particularly important for people who are high confidence but still building competence, they’re the ones most likely to push through when they should pause. Naming the triggers in advance gives them permission to stop without it feeling like failure.

TRY: "If X happens, come straight to me before doing anything. Everything else, back yourself."

4. Create a genuine soft landing for early mistakes.

If someone knows that getting it wrong will result in it being taken away from them, they’ll either not try or they’ll hide problems. Both outcomes are worse than the mistake itself. The leaders who build the most capable teams are explicit that early errors are expected and recoverable, and that the way someone handles a mistake is more important than the fact that it happened.

Carol Dweck’s foundational research on growth mindset shows that people who believe their abilities can be developed through effort and feedback consistently outperform those who view capability as fixed, particularly in the face of setbacks. As a leader, you’re either reinforcing one of those beliefs or the other, every time something goes wrong.

TRY: "I’m not expecting perfect the first time. I am expecting you to tell me early if something isn’t on track."

The check-in isn’t a status update. It’s a brief, structured conversation that serves three purposes: it surfaces problems early, it reinforces the person’s thinking rather than replacing it, and it gives you the visibility you need without reclaiming ownership.

A simple check-in structure that works:

Three questions. Ten minutes. The first creates a moment of recognition. The second invites honest disclosure without making the person feel like they’re reporting a failure. The third returns agency to them, they define what support looks like, rather than having it imposed.

Notice what you’re not asking: “How is it going?” That question is too broad to surface anything useful. “Is everything okay?” invites a yes when the honest answer might be no. Precision in the question shapes the quality of what comes back.

If you’re managing someone who is high competence but low confidence, the check-in serves a different primary function: it’s a moment to name what’s working, not just to scan for problems. Confidence is built through evidence. Your job in that room is partly to reflect the evidence back.

This shift isn’t always comfortable. Letting go of the answer feels slower, at first. Watching someone work through something you could solve in two minutes requires patience that doesn’t come naturally under pressure. And the stakes are real, your reputation, your team’s results, the trust of those above you are all part of what’s on the line.

That’s not a reason not to do it. It’s a reason to do it with structure.

The safety net isn’t a compromise on the multiplier mindset, it’s what makes the multiplier mindset sustainable. It lets you extend trust without abandoning accountability. It gives people room to grow without leaving them exposed. And it gives you the confidence to step back, knowing you’ve built the conditions for things to go well, and a clear path to recovery if they don’t.

The leaders who do this well aren’t less decisive. They’re more intentional about which decisions warrant their direct involvement, which ones are better made by the people closest to the work, and what scaffolding needs to be in place to make that handover real rather than nominal.

Over time, the return compounds. The team that develops the habit of thinking without waiting for you becomes your greatest strategic asset, particularly when things get uncertain, which they always will.