Craft can run fast: daily practices, quick iterations, skills refined from session to session. Systems run slow, structure doesn’t change often and it shouldn’t. Each vantage has a native tempo of its own. If you don’t observe and understand them, then forcing a vantage to operate at a tempo that isn’t its own might present these boundaries as failure, resistance or non-compliance.
Clockspeed
Charles Fine coined the term industry clockspeed in a 1998 book of the same name. He observed that different industries, and even different parts within an organization, change at different natural rates. Anticipating that rate to be uniform is a strategic error.
Fine’s framework breaks clockspeed into three distinct dimensions: product clockspeed, the rate of new offerings; process clockspeed, the rate at which methods and equipment turn over; and organizational clockspeed, the rate at which structure itself changes. That three-way split maps to Craft (product speed), Contextual (process speed), and Systems and Networks (encompassed by organizational speed). The 3 Dimensions model would argue that systems have a natural speed, separate from the networks, silos, and learning communities that navigate, obstruct, and problem solve beyond what a system can manage or predict (the very reason these networks, communities, and politics exist!). Within an organization or even an individual team, each has a legitimately different natural rhythm rather than one uniform pace that can be imposed across all of them.
Fine’s research connects clockspeed to decision-making: industries and functions running at a fast clockspeed are too busy to deliberate before acting, while slow-clockspeed contexts have the time, and the obligation, to think and debate before committing. Native tempo describes how fast something changes, but also how slowly it can afford to move.
Clockspeed in the world
Fine’s research offered several examples: Intel’s semiconductor fabrication facilities became technologically obsolete in roughly four years, a fast process clockspeed. A General Motors manufacturing plant can run for twenty years or more before facing the same obsolescence. Boeing introduced a new aircraft platform less than twice a decade, a slow product clockspeed befitting an industry where getting it wrong can be catastrophic, and getting it right takes patient, deliberate engineering. A major entertainment studio can release dozens of products in a single year, a fast product clockspeed matched to an industry built on rapid iterations, fast failures, and volatile customer tastes. These organizations are running at their natural pace. The failure would be forcing Boeing’s deliberation onto a decision that actually moves at entertainment-industry speed, or rushing aircraft-grade decisions through a timeline built for a much faster industry.
The same logic predicts real, internal mismatches: a Systems-level restructuring pushed through on a product-team’s native sprint cadence, or a Craft-level skill-development effort starved by being routed through review cycles built for organizational-level change.
Finding your native clockspeed
- Establish what native clockspeed looks like. Look at comparable teams in your industry and your organization. You can use these as a guide, but your team’s creativity, productiveness, Craft, and even cohesion, will be the most important gauges. Don’t judge it against a single organization-wide pace.
- Try tracking all three of the clockspeeds Fine identifies, product, process, and organizational (mindful of differences that might exist between networks and systems in your organization). Look at major functions and frictions. A single vantage can run fast loops and slow loops simultaneously, collapsing them into one may obscure the natural rhythms that are most worth discovering.
- Check if the timeline of a Systems level initiative matches other Systems’ natural (typically slower) clockspeed, or whether it’s inheriting the pace of whichever vantage is driving the proposal.
- Check whether a Craft level initiative has been routed through a cadence (like review) from an external vantage, starving it of the natural tempo it desires.
Pitfalls to watch for
Holding a team to a speed that no longer sustains it. Pushing a team beyond a speed that it can sustain. Native tempo is a proven pattern, but it’s not a fixed law. Fine documents cases where an entire industry’s clockspeed shifted over time, meaning a vantage’s natural pace today isn’t a permanent property to defer to indefinitely.
Accepting “this is how we’ve always done things” as an excuse to never question the pace. It risks calcifying rigidity. The discipline is checking for a native tempo before assuming a mismatch, not using it as a permanent shield against accelerating or slowing a given team or vantage.
References and further reading
- Fine, Charles H. Clockspeed: Winning Industry Control in the Age of Temporary Advantage, 1998, Perseus Books.
- Fine, Charles H. “Clockspeed-based Strategies for Supply Chain Design,” Production and Operations Management, 2000, extending clockspeed analysis inside a single firm’s internal organization.