🎧 Listen to this article

An AI-generated podcast companion to this article, produced with Google NotebookLM.

The Leader's Hidden Job Requirement

Most high performers arrive at leadership the same way: they were exceptional at getting things done. They hit their numbers, solved the hard problems, and built a reputation for reliability. So they were promoted. And then, almost immediately, the skills that carried them to that point began to work against them.

The trap is easy to fall into. When you are wired to produce results and you can see exactly how something should be done, it feels faster and safer to just do it yourself. Delegation starts to feel like a gamble: will they do it the way it needs to be done? Will the quality hold? Will the deadline stick? For people who have built their identity around being the one who delivers, handing work off can feel like surrendering control.

But here is the problem with that logic: a leader's output is not their individual contribution. It is the collective output of their team. And a team that depends on the leader to carry the weight will never develop the capability to carry it themselves. What feels like efficiency in the short run compounds into a bottleneck over time. The leader stays indispensable. The team stays underdeveloped. And the organization's capacity stays flat.

Building capability and capacity on your team is not a nice-to-have that happens when you have extra time. It is the job. It is what separates a manager who produces results from a leader who multiplies them.

Two Very Different Kinds of Delegation

Most managers who delegate are practicing what might be called delegation for doing. The logic is simple: there is work to be done, this person has the bandwidth to do it, so assign the task and monitor for delivery. The goal is completion. The measure of success is whether the work got done on time and to standard.

Delegation for development operates from a different premise. The work still needs to get done, but that is not the only goal. The assignment is also an opportunity to stretch the person's capability, build their confidence in new territory, and expand what the team can handle without the leader in the room. The measure of success includes not just whether the deliverable landed, but whether the person grew in the process.

The distinction matters because the two approaches require fundamentally different conversations. Delegation for doing is transactional: here is the task, here is the deadline, here is what I need. Delegation for development is relational and developmental. It requires a leader to understand where the person currently is, where they need to grow, what support they need to succeed, and how to create accountability without undermining ownership.

That is a harder conversation to have well. And it is the conversation that most leaders skip.

The difference between a team that maxes out at your capacity and one that grows beyond it is almost always traceable to this: whether the leader learned to delegate for development instead of just for doing.

A Framework for the Conversation That Matters

The ACCORD framework was built for exactly this kind of work. Whether you are assigning a stretch assignment to a capable team member, navigating reluctance from someone who is uncomfortable with new responsibility, or trying to turn a pattern of dropped commitments into a culture of reliable follow-through, ACCORD gives you both the mindset and the mechanics to have the conversation well.

It is worth noting that alignment and clarity are not luxuries you pursue when people are cooperative. They are especially important when people are not. Resistance, hesitation, and passive agreement are almost always symptoms of something that was skipped earlier in the conversation: a shared purpose that was never established, an expectation that was never truly confirmed, a commitment that was assumed rather than secured. ACCORD is designed to catch those gaps before they become breakdowns.

The ACCORD Model

Even the most capable leaders encounter moments when a team member hesitates or resists taking action. Whether it is a task they are uncomfortable with, a change they disagree with, or simply a case of inertia, the leader's role is not to coerce — it is to create alignment, clarity, and accountability. ACCORD offers both the mindset and the mechanics for having a conversation that helps someone move from reluctance to responsible action.

A
Align Create shared purpose — move from me vs. you to me and you vs. the goal
C
Clarify Define the what and the when — eliminate ambiguity before it breeds avoidance
C
Confirm Close the loop on understanding — don't assume the message landed as intended
O
Obligate Turn understanding into ownership — secure a clear, affirmative commitment
R
Reinforce Follow through and build trust — accountability is built on consistency
D
Debrief Reflect and learn together — where delegation for development pays its most lasting dividends

A — Align: Me and You vs. the Shared Goal

Start by moving from me vs. you to me and you vs. the goal. Establish a common purpose or value that both of you care about.

How to do it

  • Connect to the "why" — describe why this matters for your collective cause.
  • Where possible, surface what's in it for them: how their work or day will become better, easier, or more meaningful by getting on board.
  • Use inclusive language: "we," "our," "together."
  • Elicit and empathize with underlying concerns.
Example
"I know this change adds extra work up front, but our goal is to reduce rework later. Let's find a way to make this smoother together."

C — Clarify: Define the What and the When

Ambiguity breeds avoidance. Be explicit about what needs to be done and by when.

How to do it

  • State the concrete action or deliverable.
  • Include clear timeframes and outcomes.
  • Translate vague goals into measurable tasks.
Example
"Please update the client presentation with the revised data by 3 p.m. tomorrow."

C — Confirm: Close the Loop on Understanding

Do not assume your message landed as intended. As George Bernard Shaw wrote, "The problem with communication is the illusion that it has taken place." To help ensure that what the other person heard is aligned with what you said, employ the tool of closed-loop communication.

How to do it

  • Ask the person to restate what they will do and by when.
  • Listen for alignment.
  • Summarize and affirm understanding.
Example
You: "I want to be sure I didn't miss any important parts of the request. Can you recap what you'll deliver and by when?"

Them: "Sure. You'd like the updated slide deck by 3 p.m. tomorrow so we can review it before sending."

O — Obligate: Turn Understanding into Ownership

Understanding alone does not equal agreement or action. At the core of any effective team lies the principle of accountability: the ability for team members to count on one another to deliver what they committed to, when and how they said they would. A leader's role is to explicitly convert understanding into ownership by obtaining a clear, affirmative commitment. This is where accountability begins — not at the deadline, but at the moment of commitment.

How to do it

  • Ask directly for commitment.
  • Frame it relationally — it is about dependability and trust.
Example
"So I can count on you to deliver that by 3 p.m. tomorrow?"

While this may feel uncomfortable at first, failing to ask — or accepting vague responses like "I'll try" or "I'll do my best" — often leads to unmet expectations. When you do not have a firm commitment, assume you do not yet have a plan you can count on.

It is also worth noting that not every "yes" means "yes." Some people have a tendency to agree automatically without fully considering what follow-through requires. If you suspect this might be the case, try shifting your question to one that surfaces potential barriers before they become breakdowns.

Example
"What do you think might get in the way of my receiving this by 3 p.m. tomorrow?"

Be ready for an honest response. If legitimate obstacles arise and cannot be navigated, you may have to accept that this individual cannot be counted on for this particular task at this particular time. Strong leaders do not just extract promises — they create conditions for reliable delivery by ensuring that commitments are realistic, explicit, and mutually understood.

R — Reinforce: Follow Through and Build Trust

Accountability is built on consistency. When people deliver on commitments, recognize it. When they do not, address it promptly and fairly.

How to do it

  • Follow up on deliverables.
  • Acknowledge follow-through publicly when appropriate.
  • Address missed commitments directly and constructively.
Example
"I appreciate that you got it done early — that helped us avoid last-minute stress."

D — Debrief: Reflect and Learn Together

After the action, take time to reflect on what worked and what could improve. This strengthens learning and team relationships — and it is where delegation for development pays its most lasting dividends.

How to do it

  • Ask reflective questions.
  • Identify obstacles and improvements.
  • Reinforce shared ownership for growth.
Example
"Thanks for getting that done on time. Was there anything that made it harder than it needed to be? Let's learn from it."

Summary: The ACCORD Model

Step Key Action Purpose
Align Create shared purpose Build connection and motivation
Clarify Define what and when Eliminate ambiguity
Confirm Close the loop Ensure mutual understanding
Obligate Secure commitment Move from agreement to ownership
Reinforce Follow through Build trust through accountability
Debrief Reflect and learn Sustain improvement