Leadership Styles Series
A founder who never stopped being the best engineer in the room. He still ships the hardest features himself, still works past midnight before a big launch, still expects the team to match a pace he set five years ago as a two-person startup.
The team is exhausted. Not all at once. One at a time. The strongest performers hit the wall first, because they're the ones actually trying to keep pace, and pacing yourself against someone who doesn't sleep is not a strategy. It's a countdown.
By the time the founder notices the slowdown, he reads it as the team getting soft. What actually happened is the team learned that keeping up was impossible, so they started looking busy instead.
That is the pacesetting leadership style, run as a permanent identity instead of the short, sharp tool it was designed to be.
Goleman's pacesetting style is built around one phrase: "Do as I do, now." The leader sets a blistering standard and models it personally, expecting the team to keep pace without being told how. In a short, bounded sprint with a small, highly skilled team, it works. Run as a default, it is the most corrosive of the six styles.
Goleman's research found pacesetting has one of the most negative effects on team climate of any style when overused, worse in most cases than commanding, because the damage is quiet. Nobody announces they've given up. They just start managing appearances instead of raising their hand.
The three failure modes are burnout (the people actually trying to match the pace hit the wall first), the founder becoming the bottleneck (delegation collapses because doing it yourself feels faster in the moment), and standard-setting without teaching (the founder models the bar but never explains it, so people who don't intuit it fast enough get quietly written off).
The hidden cost is not turnover. It is that the team gets slower, not faster, because the people still trying to keep pace burn out and everyone else learns to look busy instead of asking for help.
The fix is not abandoning the pace. It's containing it. Pacesetting works in short, defined bursts, paired with coaching that turns the demonstrated standard into something the team can sustain without the founder in the room.
Goleman's phrase for this style is "Do as I do, now." The pacesetting leader sets an extremely high bar and shows the team what it looks like by hitting it personally, rather than describing it. They move fast, work hard, and expect the team to watch and match, with little patience for anyone who can't keep up.
The strength is real, in the right window. There's no ambiguity about what "good" looks like when the founder is doing it in front of you. A small team of highly skilled, self-motivated people can absorb that pace for a defined stretch and come out with the sharpest version of the standard they've ever produced.
The catch is that pacesetting assumes everyone on the team has the same skill level and internal drive the founder has, and it rarely stops to check. It communicates the standard by demonstration, not explanation, which works for people who can reverse-engineer the why from watching and fails everyone else.
Three moments call for the pacesetting style specifically. The first is a short, defined sprint: a launch week, a fundraising close, a critical bug that must ship before the team can move on to anything else. With a small, already-skilled, self-driven team, a burst of pacesetting can produce the sharpest work the team has done all year.
The second is early in a new team's life, before habits have set. Showing a new hire what "fast" and "excellent" actually look like, once, in the room, calibrates the standard faster than a written guideline ever will. The key word is once. It's a demonstration, not a lifestyle.
The third is correcting a standard that has slipped. When quality has drifted and the team has quietly recalibrated what "good enough" means, the founder stepping back in to model the old bar resets the baseline. Then the founder steps back out. Pacesetting is a flare, not a floor.
The first failure is burnout, and it does not hit evenly. The people who burn out first are usually the ones trying hardest to match the founder's pace, which means pacesetting run as a default quietly selects against the most committed people on the team.
The second is the founder becoming the bottleneck. "I'll just do it myself" is faster in the moment and catastrophic over a year. Every task the founder pulls back to do personally is a task that never gets delegated, which means nothing in the company can scale past what one person can physically do.
The third is standard-setting without teaching. Pacesetting communicates the bar by modeling it, not by explaining it. People who can watch the founder work and reverse-engineer the underlying judgment keep up. Everyone else gets quietly filed as underperforming, when what actually happened is they were shown the answer and never taught the method.
This is the part that catches founders off guard, because pacesetting is supposed to produce speed. Used as a default, it produces the opposite.
The team's actual pace, the one measured over a year instead of a sprint, gets slower. The strongest performers, the ones with options, either burn out and coast or leave for somewhere the pace is sustainable. The people who stay are often the ones who have learned to manage the founder's perception of their speed instead of their actual output. Busy looks like fast. It isn't the same thing.
Because a pacesetting founder has little patience for what looks like underperformance, the team stops flagging problems early and starts hiding them until they can't be hidden anymore. A team that would have raised a concern in week two under a different style waits until week six under a pacesetting one, because week two felt too early to admit they were behind. The founder gets the bad news later and in worse shape than it needed to be, which is the opposite of what pacesetting was supposed to buy them.
The pacesetting founder's hiring filter is speed. They read energy, quick answers, and confidence in the interview as evidence someone can match their pace, because that's the only signal that's ever mattered to them personally.
What that filter misses is durability. Interview energy tells you how someone performs for forty-five minutes with everything to prove. It does not tell you whether they have the internal drive to sustain a demanding pace without the founder standing over them modeling it, or whether they're going to look fast in month one and quietly slow down by month four once the adrenaline of a new job wears off.
The TA-12 measures the behavioral and cognitive traits, drive, self-management, ambiguity tolerance, that predict whether someone can operate at pace on their own. It's the difference between a candidate who performs well under a founder's direct gaze and one who can hold the standard when nobody's watching, which is the only version of "fast" that actually scales.
Pacesetting and coaching are not in conflict. They're sequential, and the sequence is what makes pacesetting sustainable instead of corrosive.
Model the standard once, in a defined window with a start date and an end date. Explain the why while you're doing it, not just the what, so the team is learning the judgment behind the bar, not just watching someone hit it. Then step out of pacesetting mode and into coaching. Ask the questions that help the team build the muscle themselves, rather than staying dependent on watching you do it every time the standard needs to be reset.
The founders who use pacesetting well treat it like a tool they pick up for a sprint and put back down, not a personality. The ones who get in trouble forget to put it down.
You don't have an underperformance problem. You have a translation problem. You showed the team what fast looks like. You never turned it into something they could build without you standing there.
Look at who's left the team in the last year, and be honest about whether the strongest performers left first. Look at your last quarter and count how many problems got flagged early versus how many showed up already on fire. Both are pacesetting signals if the pattern is there.
If your team's actual output has been getting slower even though everyone looks busier, the fix isn't more pressure. It's turning the pace you've been modeling into a standard the team can hold on their own. Schedule a call. We'll show you what your hiring has been optimizing for, and whether it's speed or the appearance of it.
Quick answers to the questions founders ask most about the pacesetting style.
The pacesetting leadership style, as defined by Daniel Goleman in his 2000 Harvard Business Review research, is the approach where a leader sets an extremely high standard and models it personally, expecting the team to keep pace. The phrase that captures it is "Do as I do, now." Goleman found it most effective in short bursts with a small, highly skilled, self-motivated team, and one of the most damaging styles to team climate when used as a default leadership identity.
Pacesetting leaders set the bar by hitting it themselves rather than describing it, move at high speed, and have little patience for what they perceive as underperformance. They lead by demonstration, not explanation. The characteristic that becomes a liability is the assumption that everyone on the team shares the founder's skill level and internal drive, which is rarely true and is never checked before the pace is set.
The strengths are real in a narrow window: pacesetting can produce the sharpest version of a team's work during a defined sprint, and it removes ambiguity about what "good" looks like because the standard is being demonstrated in real time. The weaknesses are significant when the style becomes a default. It burns out the most committed performers first, turns the founder into a bottleneck by discouraging delegation, and teaches the team to hide problems instead of raising them early. Goleman's research found it had one of the most negative effects on team climate of the six styles when overused.
Use it for a short, defined sprint with a small team that already has the skill and self-motivation to absorb the pace, such as a launch week or a fundraising close. Use it once, early in a new team's life, to calibrate what "fast" and "excellent" actually mean. Don't use it as a default operating style, with a team whose skill level varies widely, or as a substitute for delegating and developing the people underneath you.
A founder who works alongside the team through a launch week, personally hitting the standard they expect everyone else to hit, then steps back once the launch is over, is running pacesetting well. A founder who pulls work back to do it themselves because it's faster than explaining it, month after month, is running pacesetting as a permanent bottleneck instead of a tool. The difference is whether the pace has a start date and an end date.
In Daniel Goleman's framework, published in the Harvard Business Review in 2000, the pacesetting style is one of six leadership styles drawn from research across thousands of executives. Goleman summarized it as "do as I do, now." It is effective in narrow circumstances, namely a highly competent and motivated team facing a time-sensitive goal, and Goleman found it was frequently overused and among the most damaging styles to organizational climate when applied broadly.
The primary disadvantage is that it burns out the team's strongest performers first, since they're the ones actually trying to match the founder's pace. The second is that it discourages delegation, since doing the work personally always feels faster in the moment, which quietly caps how much the company can scale. The third is that it teaches the team to hide problems rather than surface them early, since a pacesetting leader has little visible patience for anything that looks like falling behind.
Commanding leadership tells people exactly what to do and demands compliance. Pacesetting leadership shows people what to do by doing it and expects them to match the standard without being told how. Both demand a lot in a short window and both damage team climate when used as a default. The distinction is method: commanding operates through direct instruction, pacesetting operates through demonstration, and neither one develops the team's independent judgment the way coaching does.
Reference: Daniel Goleman, "Leadership That Gets Results," Harvard Business Review, March-April 2000.
Related reading
The 6 Leadership Styles Every Founder Should Know
Visionary Leadership Style: When To Use It And When To Stop
