Leadership Coaching for Team Leads

Stop Delegating
Your Job

Get called out before you hand off what’s actually yours, then leave with a delegation brief, management cadence, or conversation script built for your situation.

Delegation keeps coming back wrong, and the harder parts of leading (hard conversations, managing people, meetings) keep getting skipped.

The external problem

You handed off a task and it came back wrong, or you keep avoiding the hard conversation with someone on your team.

The internal problem

You call it trust, or not wanting to micromanage. Underneath, it’s easier to look away than to actually manage them.

What's at stake

Small problems stay small until they don’t. The team watching you avoid the hard stuff learns that avoiding it is fine too.

Six areas. Each one ends with something you can use.

Describe what you’re facing and the coach routes you to the right one, or name it directly if you already know.

01

Delegation Brief

Runs the intake, a Task-Relevant Maturity read, and an enrollment conversation, then builds a brief (what, why, success looks like, constraints, authority level) with a monitoring cadence calibrated to it.

02

Developing the Team

Finds the lowest broken layer (trust, conflict, or peer accountability) and builds a plan where you carry the uncomfortable part yourself instead of handing it to HR or an offsite.

03

Managing Subordinates

Builds a management cadence (direction, progress visibility, behavioral coaching) for the report you’ve been under-managing, plus a check that your own managers are doing the same for their people.

04

Difficult Conversations

Turns a vague complaint into an observable behavior, then scripts the opening, the affirmation, and the choice you put on the other person, with a plan for how they might react.

05

Running Meetings

Redesigns one specific meeting: a real purpose, a cut list, a way to force disagreement into the room, and a named decision and owner on every key item.

06

Repetitive Communication

Narrows a rollout to one message, then builds a repetition plan across channels and real occasions so it’s heard past the seven times people need before they take it seriously.

The books this coach argues from.

The Motive supplies the spine: the two motives, the five omissions, and the definition of management the whole coach runs on. High Output Management’s Task-Relevant Maturity sets how much monitoring a handoff needs. Who Not How and the 1974 HBR piece on monkey management shape how the brief gets built and how work stops crawling back onto your desk.

Reference

The Motive

Contents

  • Overview
  • Why this is in the vault
  • Synthesis — core principles (the two motives; the management definition; the five omissions; imperfection & vigilance; the danger of fun)
  • The two load-bearing lines for this skill
  • Verbatim extracts
  • Where this is used in the skill
  • Sources

Overview

*The Motive* (Lencioni's shortest book, 2020) argues that there are only two reasons anyone becomes a leader — to serve (responsibility-centered) or to be rewarded (reward-centered) — and that this single underlying motive predicts whether a leader does the hard, tedious, uncomfortable work that only a leader can do. Reward-centered leaders delegate, abdicate, or avoid five specific responsibilities; the book names them and shows why the avoidance is a motive problem, not a skill problem. It is written to CEOs but Lencioni states it applies to all leaders.

Why this is in the vault

This reference is the top-level spine of the leadership-coach skill. Every session is now framed by the motive question — *are you doing this because it's your responsibility, or avoiding it because it isn't rewarding?* The book supplies (1) the reward-vs-responsibility frame the coach reads every situation through, (2) the second of the skill's two load-bearing lines (the definition of management), and (3) the five omissions, which are now the coach's routable coaching territories alongside delegation. It also grounds the motive gate at intake: when a user tries to hand off one of the five omissions, that's abdication, and the coach redirects to doing the work rather than delegating it.

Synthesis — core principles

1. The two motives

Lencioni reduces all leadership motivation to two options, and insists one always becomes dominant:

  • Responsibility-centered: *"the belief that being a leader is a responsibility; therefore, the experience of leading should be difficult and challenging (though certainly not without elements of personal gratification)."*
  • Reward-centered: *"the belief that being a leader is the reward for hard work; therefore, the experience of being a leader should be pleasant and enjoyable, free to choose what they work on and avoid anything mundane, unpleasant, or uncomfortable."*

The mechanism that makes the motive matter: *"When leaders are motivated by personal reward, they will avoid the unpleasant situations and activities that leadership requires. They will calculate the personal economics of uncomfortable and tedious responsibilities... and try to avoid them."* The result is *"a painful and destructive vacuum"* where the people in their charge lose direction, guidance, and protection.

2. What management actually is

Against the idea that management is bureaucracy (objectives, reviews, comp) or that seniority exempts someone from being managed, Lencioni gives a working definition that is the second spine line of this skill (see below). He adds: *"trusting someone is not an excuse for not managing them"* and that a leader must also ensure their subordinates one level down are managing *their* people — a cascade most senior leaders skip.

3. The five omissions of reward-centered leaders

These are the situations reward-centered leaders find tedious, uncomfortable, or hard, and therefore offload. Lencioni is explicit that this is not a list of a leader's primary responsibilities — it's the list of what gets avoided:

  • Developing the leadership team. Often delegated to HR, which never works: *"If people on a leadership team don't believe that the leader sees team development as one of his or her most critical roles, they're not going to take it seriously."* Team development means improving interpersonal dynamics, facilitating honesty and conflict, enforcing peer accountability, and navigating uncomfortable conversations. It is *"the practical, tangible competitive advantage"* that enables finance, strategy, and marketing.
  • Managing subordinates (and making them manage theirs). Not writing objectives and running reviews — *"helping them set the general direction of their work, ensuring that it is aligned with and understood by their peers, and staying informed enough to identify potential obstacles and problems as early as possible,"* plus coaching them behaviorally, plus checking that they do the same one level down. The reward-centered dodge: *"I hire experienced executives and I trust them. They shouldn't need me to manage them."*
  • Having difficult and uncomfortable conversations. Confronting behavioral issues — annoying mannerisms, poisonous dynamics, politics — *"quickly and with clarity, charity, and resolve."* Lencioni's model is Alan Mulally's "joyful accountability": cheerfully tell the person it's up to them to change; if they can't, you'll still be their friend, but they can't stay. The reframe that unlocks it: avoiding the conversation is not kindness, it's selfishness — trading your discomfort for theirs and letting a small issue grow into a career-ending one.
  • Running great team meetings. *"Meetings are the setting, the arena, the moment when the most important discussions and decisions take place."* A leader who finds meetings to be drudgery is like a surgeon who feels that way about surgery. Bad meetings cause bad decisions and set the ceiling for the whole company.
  • Communicating constantly and repetitively. Leaders vastly underestimate the volume of repetition required — *"employees have to hear a message seven times before they believe executives are serious about it."* The best leaders act as Chief Reminding Officers (CROs), and *"no reasonable human being has ever left a company because management communicated too much."*

4. Imperfection and vigilance

No leader has a pure motive; everyone slips toward reward-centered under *"flattery and fatigue."* Because responsibility-centered leaders get praised for their selflessness, they can drift by comparing themselves favorably to worse leaders and lowering their standards. The antidote: *"surround themselves with people who will be honest with them,"* because *"for every morsel of constructive feedback a leader gets, there will be a dozen compliments, many of them unwarranted."*

5. The surprising danger of fun

Not all reward-centered leaders chase status or power — many just want to spend their time on what they find *enjoyable*. Lencioni flags this as especially dangerous *because it seems harmless:* *"even leaders who seek fun are doing so for themselves."* The vacuum a fun-seeking leader creates is no smaller than the one an ego-driven leader creates.

The two load-bearing lines for this skill

The skill is built on exactly two lines, embodied in every framework, phase, and artifact:

  • "Delegation without follow-through is abdication." — Andy Grove, *High Output Management* (see grove_high-output-management.md). Names *what* abdication is.
  • "Management is the act of aligning people's actions, behaviors, and attitudes with the needs of the organization and making sure that little problems don't become big ones." — Lencioni, *The Motive* (Managing Subordinates). Names what the leader is *on the hook to keep doing* after the handoff.

Grove says the follow-through is non-negotiable; Lencioni says the follow-through *is* management, and defines it. Together they draw the line between leading and abdicating that the whole coach protects.

Verbatim extracts

"First, they want to serve others, to do whatever is necessary to bring about something good for the people they lead... serving others is the only valid motivation for leadership." — The Two Motives

"The second basic reason why people choose to be a leader—the all-too-common but invalid one—is that they want to be rewarded. They see leadership as the prize for years of hard work and are drawn by its trappings: attention, status, power, money." — The Two Motives

"Management is the act of aligning people's actions, behaviors, and attitudes with the needs of the organization and making sure that little problems don't become big ones." — Managing Subordinates

"Of course, trusting someone is not an excuse for not managing them. And helping subordinates establish a direction and knowing how they are progressing is far from micromanagement." — Managing Subordinates

"One of the main responsibilities of a leader is to confront difficult, awkward issues quickly and with clarity, charity, and resolve." — Having Difficult and Uncomfortable Conversations

"Until one day I realized that holding back and avoiding those conversations was actually an act of selfishness. I wasn't avoiding those conversations for the sake of my employees' feelings, but for my own!" — Having Difficult and Uncomfortable Conversations

"A leader seeing his or her meetings as drudgery would be like a doctor viewing surgery that way." — Running Great Team Meetings

"What is tolerated at the top of a company is often the ceiling of what can be expected deeper within it." — Running Great Team Meetings

"I've read studies that say employees have to hear a message seven times before they believe executives are serious about it." — Communicating Constantly and Repetitively

"The very best leaders in the corporate world understand this and don't hesitate to repeat themselves. They see themselves as CROs—chief reminding officers." — Communicating Constantly and Repetitively

"For every morsel of constructive feedback a leader gets, there will be a dozen compliments, many of them unwarranted." — Imperfection and Vigilance

"Leadership can never be about the leader more than the led." — The End of Servant Leadership

Where this is used in the skill

  • SKILL.md — the responsibility-vs-reward spine, the two load-bearing lines, the motive gate, and the six-way router.
  • frameworks/motive-check/flow.md — the two-motives frame and the five-omissions test that decide whether a handoff is delegation or abdication.
  • frameworks/developing-team/flow.md — Omission 1.
  • frameworks/managing-subordinates/flow.md — Omission 2 and the management definition.
  • frameworks/difficult-conversations/flow.md — Omission 3, clarity/charity/resolve, joyful accountability, the selfishness reframe.
  • frameworks/running-meetings/flow.md — Omission 4, meetings-as-surgery, the ceiling principle.
  • frameworks/repetitive-communication/flow.md — Omission 5, the rule of seven, the CRO role.
  • frameworks/delegation/phases/1-intake.md — the motive check that can halt a delegation.
  • frameworks/delegation/phases/7-diagnose.md — reward-centered motive as a root cause behind structural gaps.

Sources (live-fetched on 2026-07-06)

  • [The Motive — The Table Group (official)](https://www.tablegroup.com/product/themotive/)
  • [The Motive — Amazon (ISBN 9781119600459)](https://www.amazon.com/Motive-Leaders-Abdicate-Important-Responsibilities/dp/1119600456)
  • [The Motive — Goodreads](https://www.goodreads.com/book/show/51771754-the-motive)

Primary source: the full book text (Wiley, 2020) supplied by the user this session; all quotes verbatim from it.

Use it now. It's free.

Works on all platforms. Pick yours and get set up in under a minute.

Download & upload in 60 seconds

One click downloads the zip and opens Claude.ai.

01

Click below — the zip downloads and Claude.ai opens.

02

Click the + button in the skills column on the left.

03

Select Create a skill.

04

Select Upload a skill and upload the zip.

05

Start your leadership coaching session by running /estack-leadership-coach.

Leadership Coach ships in E-Stack, a set of 20 free skills installed by one command. See the whole stack.