Speed Is a Skill: How High-Performing PE Leadership Teams Design Their Cadence

Some leadership teams move fast and others move slowly, and the easy explanation is that fast teams have faster people. Duke CE's research dismantles that assumption. Speed is a learned capability, not a trait. High-performing teams build speed by driving alignment, removing friction, and intentionally designing their cadence of decisions. Velocity is engineered, which means any team can build it — and any team can lose it through neglect.

The reframe matters because it changes what a slow team should do. If speed were a trait, the only fix would be to replace people. Because speed is a designed capability, the fix is to redesign — to build the clarity, remove the friction, and choose the cadence that produces velocity. The same people who moved slowly under a bad design move fast under a good one.

EX · 01The velocity equation

Duke CE reduces velocity to a simple relationship: it equals clarity plus alignment plus pace. It's not about going fast for its own sake — it's about making better decisions faster, with less rework. The 'less rework' qualifier is essential. A team that moves fast but constantly revisits decisions isn't fast; it's churning. Real velocity is forward motion that sticks, which is why clarity and alignment are prerequisites for pace rather than alternatives to it.

The single thing high-velocity teams share is clarity — clarity of strategy, clarity of roles, and clarity of communication. Each removes a source of the hesitation and rework that slow teams down. Strategic clarity means people know what they're optimizing for. Role clarity means they know who decides. Communication clarity means decisions propagate without distortion. Together they let a team move fast without breaking, which is the only speed that compounds.

EX · 02Friction is cultural, not structural

One of Duke CE's sharpest findings is that friction is cultural, not structural. The instinct when a team is slow is to reorganize — change the structure, redraw the boxes. But the friction usually lives in the culture: in the unstated norms about how decisions get made, who needs to be consulted, how much consensus is required before action. Restructuring leaves that culture intact and the friction with it.

This is why removing friction is leadership work rather than org-design work. It means changing the norms — making it culturally acceptable to decide with good-enough information, to act without universal consensus, to move before everyone is comfortable. A team that builds a culture tolerant of fast, adjustable decisions removes friction in a way no reorganization can, because it addresses where the friction actually lives.

EX · 03Weekly beats annual

The cadence design itself carries a clear lesson: weekly cadences outperform annual planning. A team that reviews, decides, and adjusts weekly operates on a fundamentally faster clock than one that plans annually and reacts in between. The weekly rhythm forces continuous small corrections rather than infrequent large ones, keeping the organization aligned to a thesis that itself evolves as the market shifts.

Leadership time signals strategy clarity — how a team spends its time reveals what it actually prioritizes, regardless of what the strategy deck says. A team whose cadence concentrates leadership attention on the few things that move enterprise value is demonstrating clarity; a team whose calendar is consumed by everything is revealing the absence of it. Designing the cadence — what gets reviewed, how often, by whom — is therefore one of the most consequential acts of leadership, and one of the most overlooked. Speed is the result, and it is a skill any team can choose to build.

EX · 04Speed is built, not summoned

Duke CE's central finding is that speed is a skill — a learned capability that high-performing teams build deliberately, not a trait that fast people happen to have. They build it by driving alignment, removing friction, and intentionally designing their cadence of decisions. The reframe matters because it makes velocity actionable: a slow team is not stuck being slow, it is running a design that produces slowness, and the design can be changed.

The companies with high velocity share one underlying trait: clarity. Clarity of strategy, clarity of roles, and clarity of communication. This is why speed and alignment are inseparable — a team aligned on priorities and clear on who owns what makes decisions quickly because there is nothing to litigate first. The fastest teams aren't rushing; they have removed the ambiguity that makes everyone else slow.

EX · 05Weekly cadence beats annual planning

The cadence finding is specific and practical: weekly cadences outperform annual planning. A business that plans annually and reviews quarterly is making decisions on a rhythm far slower than the market moves, accumulating variance between checkpoints that turns into surprises. A business running a disciplined weekly rhythm catches drift early, adjusts continuously, and compounds small corrections instead of absorbing large ones. The rhythm itself is a performance asset.

This connects cadence to leadership time, another signal the research highlights: how leaders spend their time signals strategy clarity. Leaders who design their cadence deliberately spend their time on the few decisions that matter and delegate the rest, while leaders without a designed rhythm get pulled into whatever is loudest. Rhythm discipline is what lets a leadership team make better decisions faster, with less rework — the practical definition of the velocity that separates high-performing organizations from busy ones.

EX · 06Speed as a learned skill

Duke Corporate Education's central finding is that speed is a skill, not a temperament — something a leadership team builds deliberately rather than something fast people happen to have. High-velocity teams drive alignment, remove friction, and design their cadence of decisions intentionally. The result is not recklessness but the opposite: better decisions made faster, with less rework, because clarity upstream prevents the churn that slow teams generate downstream.

The practical implication is that any team can get faster by working on the inputs to speed rather than exhorting people to hurry. Clarify the strategy so people know what they're optimizing for. Clarify roles so decisions have obvious owners. Design a weekly cadence that surfaces blockers while they're still small. Friction, the research notes, is cultural rather than structural — which means it can be removed by leaders who decide to remove it, and who treat decision rhythm as a performance asset worth engineering.

None of this requires extraordinary people. It requires ordinary people working inside a system deliberately designed for flow rather than friction. That is the genuinely liberating implication of treating speed as a learned skill: it puts real velocity within reach of any team willing to do the unglamorous, repeatable work of clarifying its strategy, defining its roles, and engineering its decision cadence — and then to keep doing all of it consistently as the business and its market continue to evolve.