I coached a manager named David who was, by every conventional metric, exceptional. Promoted twice in three years. Highest output on his floor. The kind of leader whose name shows up in board decks as proof that the talent pipeline works.
His team had a different experience.
When I asked his senior engineer why she had stopped flagging architectural risks in sprint planning, she said something I have heard in dozens of coaching conversations since: “David will catch it anyway. He always does.”
That sentence is the sound of pace-setting leadership working exactly as designed and doing exactly the wrong thing.
David’s team had not become incompetent. They had become rational. Why invest the cognitive effort in anticipating problems when your leader will outpace you, spot the issue first, and fix it before you finish your sentence? The incentive structure was clear: wait for David.
This is the paradox at the center of pace-setting leadership. The better you are at it, the more damage it does over time.
What Pace-Setting Leadership Actually Is
Daniel Goleman identified six leadership styles in his original research on emotional intelligence and leadership. Pace-setting is the one most leaders default to without naming it. The operating instruction is simple: “Do as I do, now.”
The pace-setting leader models the standard through personal output. They are the first one in the document, the fastest to respond, the one who catches the error no one else saw. They lead by demonstration, and they expect the team to match that demonstration without extensive coaching or hand-holding.
Goleman’s research flagged something important that most leadership content skips over. Of the six styles, pace-setting had the most negative impact on organizational climate when overused. Not coercive leadership. Pace-setting. The style that looks, from the outside, like high performance.
The reason is subtle. Coercive leadership is obviously unpleasant, so teams push back or leave. Pace-setting leadership feels aspirational at first. The damage accumulates silently because no one names what is happening. The team simply stops trying to lead and starts trying to keep up.
When It Works: The Sprint Window
Pace-setting leadership is not inherently destructive. It is a precision tool with a narrow use case.
It works during a crisis or turnaround, when the team needs to see someone absorb risk and model urgency. It works during a launch phase, when speed genuinely matters more than development and the window is weeks, not months. It works with a high-competence team that already knows the work and needs a temporary push, not a permanent operating model.
The common thread is a bounded time horizon. Sprint has a natural expiry. The moment sprint becomes default, the tool starts corroding the thing it was supposed to protect.
I think of it like a tourniquet. Applied in an emergency, it saves the limb. Left on permanently, it kills it. The problem is that most pace-setting leaders never consciously applied the tourniquet in the first place. They simply lead the way they have always led, and no one tells them the limb is dying because, from the leader’s vantage point, everything looks productive.
When It Destroys: The Signals You Have Stayed Too Long
By the time most leaders recognize the damage, the best people have already started planning their exits. But the signals show up earlier if you know where to look.
Your team stops bringing problems. Not because problems disappear, but because the team has learned that raising an issue means watching you solve it in real time. That is demoralizing in a way that is hard to articulate, so they stop.
Direct reports execute but do not initiate. Tasks get done. Deadlines get hit. But no one proposes a new approach, challenges a process, or takes ownership of something outside their explicit scope. The team becomes a mirror of your priorities rather than an independent operating unit.
You are the bottleneck and you compensate by moving faster. This is the most dangerous signal because it feels like the opposite of a problem. You are the constraint, so you work harder, which reinforces the dynamic that made you the constraint. It is a feedback loop that rewards the exact behavior causing the damage.
Your best people leave. Not the ones who need direction. The ones with options. High-performers with strong skills do not stay in environments where their judgment is consistently preempted. They go somewhere their initiative is valued, and they rarely tell you the real reason in the exit interview.
If you are recognizing two or more of these in your own team, the pace has already become the problem. The fix is not to slow down. It is to redirect where your energy goes.
The Sprint, Shift, Sustain Framework
Across 300+ coaching conversations, I have seen one pattern separate pace-setting leaders who grow from those who plateau: the ability to deliberately transition out of pace-setting mode. This is not intuitive. It requires a conscious framework.
Sprint: Bound the Push and Narrate It
When you enter pace-setting mode, name it. Tell your team: “For the next two weeks, I am going to be more hands-on than usual. I will be in the details. This is temporary.”
Two things change when you do this. First, the team understands the heightened intensity has an expiration date, which prevents the learned helplessness that comes from assuming this is just how things are now. Second, you create accountability for yourself. You said two weeks. Your team heard two weeks. Now you have to actually shift.
During the sprint, do not just model output. Narrate your decision-making. When you catch an error, say out loud how you caught it. When you prioritize one task over another, explain the criteria. The goal is to make your pace-setting educational, not just performative. You are not just showing the standard. You are teaching the thinking behind it.
Shift: Reduce Your Output and Watch
This is the uncomfortable part. After the bounded sprint, deliberately reduce your personal output by roughly 20%. Do not delegate more. Just do less and observe what fills the gap.
Some of what fills the gap will be messy. Someone will make a decision you would have made differently. A deliverable will go out at 85% of the quality you would have produced. This is where most pace-setting leaders break. They see the gap between their standard and the team’s output, and they step back in.
Do not step back in. The 85% deliverable your team owns is worth more than the 100% deliverable you own. Because the first one builds capacity, and the second one builds dependency.
Sustain: Standards Through Systems, Not Personal Output
The long-term goal is to maintain your high standards without being the human engine that enforces them. This means converting your personal standards into organizational systems.
Write down your expectations for quality, speed, and communication. Not in a manifesto. In a shared document your team can reference without asking you. Establish a feedback cadence where you coach on the gap between current output and the standard, rather than closing the gap yourself. Build leadership development into your regular rhythm, not as an add-on when things are calm but as the mechanism that makes calm possible.
The leaders who make this transition successfully are the ones who redefine their job. The pace-setter’s job is to produce the best output. The leader’s job is to produce a team that produces the best output without you.
The Self-Diagnosis: 5 Behavioral Cues
If you are unsure whether your pace-setting has crossed from motivating to suffocating, run through these five cues honestly. They are behavioral, not emotional, because feelings lie but calendars and habits do not.
-
You rewrite work before it goes upstream. Not editing for clarity. Rewriting because it does not meet your standard. If you are spending more than 15 minutes reworking a direct report’s deliverable before it reaches your manager, you are doing their development for them instead of coaching them through it.
-
Your 1:1s are status updates, not development conversations. Pull up your last four 1:1 agendas. If every conversation was “what is the status of X” and none were “what skill are you building this quarter,” you are managing tasks, not growing people. The leadership assessment is a useful starting point for identifying where your direct reports actually need development.
-
You are the first to respond in team channels. Consistently. Not because you are the most available, but because you process and act faster than anyone else on the team. Every time you answer first, you teach the team that speed belongs to you and patience belongs to them.
-
You take tasks back instead of coaching through the struggle. Someone is stuck, and instead of asking questions that help them find the answer, you take the laptop (metaphorically or literally) and show them. This feels efficient. It is the most expensive form of efficiency because it purchases today’s deadline at the cost of tomorrow’s capability.
-
You have not delegated anything uncomfortable in the last 30 days. Not routine tasks. Something that carries real stakes. If every high-visibility deliverable still routes through you, your team is not developing judgment. They are developing dependence.
If three or more of these are true for you, pace-setting has become your operating system rather than a tool you deploy selectively. That is not a character flaw. It is a habit, and habits respond to deliberate intervention.
The Two-Week Test
I will leave you with one question that I have asked hundreds of managers in coaching and that consistently produces the most honest self-assessment I have seen.
If you took a two-week holiday tomorrow and could not check in at all, no email, no Slack, no “just a quick call,” what would your team do?
If your honest answer is “they would struggle with anything outside routine execution,” then your leadership style is producing compliance, not capability. The pace you have set is your pace, and it leaves with you.
The managers who answer “they would handle it, maybe differently than I would, but they would handle it” are the ones who have already made the transition from pace-setter to leader. The standard lives in the team, not in one person.
That transition is not easy, and it does not happen by reading a blog post. It happens through consistent, deliberate practice with someone who can reflect your blind spots back to you in real time. That is what coaching does. Across the 5,000+ managers we have worked with at Risely, the ones who shift from personal output to team capability see an average 26% improvement in assessed skills within 12 weeks. Not because they learned new theory, but because they changed daily behavior.
Your pace is not the problem. Your inability to turn it off is.