In the previous lesson, you learned how to operate in the two "high direction" styles—Directing and Coaching—where you carry most of the cognitive load for someone who still needs your expertise. Now we shift to the opposite side of the matrix: the two styles where the person already has the skill, and your job is to get out of their way in the right manner. These styles—Supporting and Delegating—look deceptively easy, but they are where many well-intentioned leaders stumble. They either over-manage capable people and kill their motivation, or they under-support them and leave a hesitant expert stranded. Throughout this unit, you will learn to tell the difference and respond with precision.
The Supporting style is designed for the Capable but Cautious performer (S3)—someone who has the technical skills to do the job but hesitates because of variable confidence, perfectionism, fear of making the wrong call, or simply being new to owning a decision at this level. Their competence is high; their commitment, on any given day, is shaky.
In this style, you provide low direction and high support. You are no longer the expert handing down the method, because the person in front of you already knows how to do the work. What they need from you is a sounding board, encouragement, and the occasional reminder that their judgment is trustworthy. Your core job is to ask questions, listen, reflect back what you hear, and validate their thinking—not to hand them the answer. A Supporting conversation might sound like this: "You've done three of these before and they all landed well. What's making this one feel different? Walk me through your options and I'll listen." Notice how different that is from Coaching. You are not explaining the "why" or teaching a new rule; you are holding space for them to find the answer they already have.
To see this in action, consider how a manager handles a capable team member who is wavering on a decision she's fully equipped to make:
- Natalie: I've been going back and forth on whether to restructure the vendor contract or just extend the current one. I keep second-guessing myself.
- Ryan: You know this vendor better than anyone on the team. What's pulling you toward each option?
- Natalie: Restructuring gives us better terms long-term, but it's more work now and there's some risk if they push back.
- Ryan: And if you had to decide today, with what you already know, which one would you pick?
- Natalie: Honestly? Restructuring. The long-term gain is worth the short-term friction.
- Ryan: That matches what I would have guessed from watching you handle the last two negotiations. Trust that instinct—it's been right before.
Notice what Ryan did not do. He didn't tell Natalie which option to pick, didn't explain the tradeoffs for her, and didn't rescue her from the discomfort of deciding. Instead, he asked questions that surfaced her own reasoning, then reinforced her confidence with a concrete, evidence-based reminder of past success. That is Supporting at its best.
The Delegating style is reserved for the Self-Reliant Achiever (S4)—someone whose competence and commitment are both high. They know how to do the work, they're motivated to do it, and they are often better positioned than you are to determine the best path forward. With this person, your best leadership move is to define the outcome, transfer ownership, and step back.
In Delegating, you provide low direction and low support, but this does not mean abandonment. It means you are matching the person's appetite for autonomy rather than inserting yourself where you're not needed. A Delegating handoff centers on the Definition of Done (DoD): a clear, objective statement of what the finished result looks like without prescribing the steps to get there.
A Delegating handoff might sound like this: "I need this client problem solved by the end of the quarter. Our Definition of Done is a signed contract amendment that satisfies the new compliance standards and remains within the original budget. You own the approach, the team coordination, and the final recommendation. Update me monthly, and pull me in when you hit something where my authority unlocks a door."
Notice what's happening in that handoff:
- The outcome is crystal clear: The "Definition of Done" ensures the person knows exactly what success looks like without being told how to do it.
- The method is theirs: You are not prescribing "how," which respects their expertise.
- The check-in cadence is defined and light: They don't have to guess when to surface updates, and you've explicitly invited escalation only where you add unique value.
The biggest trap in Delegating is confusing "low support" with "no relationship." Self-Reliant Achievers still need to feel seen and valued—they just don't need you hovering or praising every deliverable. Recognition for this group is most powerful when it's specific and strategic, as in "The way you restructured the onboarding flow saved us a week of rework downstream. That's exactly the kind of call I trust you to make."
The other trap is withdrawing direction too late or too early. Delegating a project to someone who is actually an S3 in disguise will backfire—they'll feel dropped, second-guess themselves, and either stall or produce rushed work. This is precisely why the accurate diagnosis you practiced in the previous course is the prerequisite for this style.
The through-line of both Supporting and Delegating is a single discipline: knowing the difference between facilitating and interfering. Facilitating means you are adding something the person genuinely needs but cannot easily get on their own—a question that unlocks their thinking, a piece of context they don't have, a decision only you can authorize, or a word of confidence at a pivotal moment. Interfering, by contrast, means you are injecting your presence, your preferences, or your opinions into work that was already on track without you.
A quick test before you speak, email, or schedule a check-in is to ask yourself, "Am I about to give this person something they need, or something I need?" If what you're about to offer is a course correction they didn't ask for, a preference about method, or a reassurance that's more for your comfort than theirs, you're interfering. If it's a question that helps them think, a resource they couldn't access on their own, or a clearly requested input, you're facilitating.
Interference is especially dangerous with S3 and S4 performers because it erodes trust silently. Capable people rarely tell you they feel micromanaged; they just quietly stop bringing you their best thinking. Over time, an S4 who is consistently interfered with can regress into an S3 by losing confidence, or disengage from the work entirely. Remember that with capable people, restraint is an active leadership skill, not a passive one. Staying out of the way on purpose is just as deliberate an act as stepping in.
A useful mental reframe is to think of yourself less as the driver and more as the conditions-setter. In S3, you're setting emotional conditions—safety, confidence, and space to think. In S4, you're setting structural conditions—clarity of outcome (the Definition of Done), authority to act, and access to resources. In neither case are you doing the work or prescribing the method.
In the upcoming practice, you'll put these concepts into action by facilitating a problem-solving session with a capable but hesitant team member. You'll also draft a "Definition of Done" for a delegation handoff, focusing on the outcomes that matter rather than the methods you'd personally use. Get ready to practice the hardest part of adaptive leadership: leading powerfully by doing less.
