Setting the Tempo - and Designing for It

A reflection on Nitin Nohria’s “How CEOs Set the Tempo”

Nitin Nohria’s article in Harvard Business Review, “How CEOs Set the Tempo”, brings an underappreciated leadership responsibility into focus. Choosing a strategy carries an accompanying judgement about time: when to act, how quickly to proceed, and how much change the organisation can absorb.

His five tempos, from experimental speed to patient compounding, give leaders a useful vocabulary. Each has circumstances in which it helps and a failure mode when pushed too far. The best leaders develop the range to move between them, attending both to the demands of the environment and to the organisation’s capacity to respond.

The article connects closely with work I have been developing around Requisite Pace: the ability to create value at appropriate speeds, coordinate across different speeds, and change that arrangement as circumstances require.

Nohria’s argument opens up a further question. How does a leader’s judgement about tempo become a dependable capability of the organisation?

Several legitimate tempos, at once

One implication of Nohria’s argument is that an organisation may need to operate at several different tempos simultaneously.

A business might experiment rapidly with a new proposition, operate with disciplined urgency in fulfilment, deliberate carefully before a major investment, and compound skills and trust over years. Fast is not always the answer. Some activities should move intentionally more slowly, allowing time to gather evidence, challenge assumptions, build commitment or protect quality. The distinction is between time that serves a purpose and delay that has accumulated through habit or poor design.

Even within one activity, the appropriate tempo can change as uncertainty resolves and commitments become harder to reverse.

Nohria already illustrates this in founders who protect time for hiring and architecture while moving quickly elsewhere; the organisational challenge is to make those choices work together.

The leadership task therefore includes designing how those tempos interact.

Consider a product team learning weekly, an investment process allocating money quarterly, and a core platform evolving over several years. Each timescale may have a legitimate purpose. The difficulty appears when a promising discovery needs funding or a platform change before its opportunity disappears.

That is where pace becomes an operating-model question. Who can authorise the next step? What resources are already available? What evidence is required? Which decisions can proceed within agreed boundaries, and which need wider judgement?

A protected funding envelope might allow weekly learning to continue within quarterly oversight. Embedded assurance might allow risks to be addressed as work develops. An agreed exception route might bring the right people together when an event demands action.

These arrangements make a leader’s intention executable.

Which clocks deserve to set the pace?

Nohria rightly places tempo in context: the business challenge, organisational readiness and external pressures all matter.

I would add that leaders must choose which external rhythms deserve to shape the organisation. Customer needs, technological change, regulation, capital markets and physical infrastructure do not move together. Trying to match every signal can consume the attention needed to interpret the important ones.

AI makes these choices more pressing by changing rhythms both inside and outside the organisation. It can accelerate analysis, experimentation and production while reshaping customer expectations and competitive possibilities. Decision-making, assurance and capability building may move on different timescales. Leaders therefore need to judge which external changes demand a response, where internal acceleration creates new dependencies, and what must remain deliberate.

The choice starts with value. Which changes affect what customers need, how we fulfil our promises, and our ability to remain viable? Where does delay destroy an opportunity? Where does taking time protect quality, trust or future capability?

This is the first discipline of Requisite Pace: choosing the clocks the organisation needs to attend to.

The CEO’s own behaviour becomes part of that environment. A leader’s urgency can focus attention on an important external change. It can also become the dominant signal itself, drawing teams towards the executive inbox and away from the customers or risks they need to understand.

A leader’s signal also passes through inherited arrangements: budget cycles, governance calendars, contracts and technology platforms. These shape whether urgency becomes useful action, waiting or overload.

A useful leadership question is therefore: what is the organisation actually keeping time to - and is that what matters most?

Making leadership judgement repeatable

Nohria’s examples show how leadership behaviour and organisational design reinforce one another.

Alan Mulally’s disciplined weekly reviews at Ford provided a recurring opportunity to make problems visible and coordinate a response. Jensen Huang’s consistent operating cadence at Nvidia illustrates how stable internal routines can support progress in a rapidly changing environment.

I read these examples as leadership judgement becoming organisational practice. The cadence creates a dependable opportunity to notice, discuss and act. The leader’s behaviour influences whether people use that opportunity honestly and effectively.

That relationship matters when the pace changes.

More frequent reviews can shorten feedback loops. They can also increase the volume of preparation, escalation and coordination without changing the organisation’s ability to decide or deliver. If funding, assurance and operational capacity cannot respond, people must reconcile the mismatch. The mismatch does not disappear; it moves to wherever nothing has been designed to absorb it.

Often, that work falls to middle managers. They translate priorities, negotiate exceptions and repeatedly rearrange commitments. Some of this is valuable coordination. When it becomes continuous improvisation, it is a clue that the organisation needs a better mechanism.

The same pressure can reach the executive team. When leaders repeatedly intervene to resolve operational delays, their attention can become organised around the fastest demands in the business. Capability building, architecture and longer-term choices then wait. Designing the interfaces between tempos also protects leadership’s capacity to attend to the future.

The human experience of pace is therefore useful evidence. Exhaustion, repeated escalation and constant re-planning can reveal a gap between the pace leaders intend and the pace the operating model can support.

Measuring the journey - and preserving the ability to change it

Nohria notes that some CEOs watch how long decisions remain unresolved and how often issues escalate. Those observations can become a practical discipline.

For an important opportunity or threat, follow the whole journey:

• How long before we recognise that a response is needed?

• How long before we commit, with authority and resources to act?

• How long before the change is working and we have evidence that it is delivering the intended result?

Then compare that elapsed time with the window the situation allows. Where consequences are significant, ask how quickly the organisation could detect failure, contain it and recover.

These questions help distinguish useful deliberation from time lost to waiting, unclear authority or overloaded decision-makers. They also expose why faster activity in one part of the business may produce little improvement overall.

There is a longer-term question too: could we change the arrangement itself?

An organisation can work well at today’s tempos while gradually losing that ability. Workarounds become permanent. Contracts constrain options. Platforms become harder to alter. All available capacity is committed to current delivery.

I call the accumulated burden of unresolved timing mismatches pace debt. It makes each subsequent adjustment more difficult.

A sustained change of tempo may require changes to the operating model itself: who can decide, how resources move, which commitments can be revised and how work crosses boundaries. Preserving that ability requires resources that can be redirected, capabilities that can be redeployed, adaptable interfaces and enough capacity to make a transition while continuing to serve customers. Patient investment in these conditions can enable decisive action later.

Tempo as an organisational capability

Nohria makes a persuasive case for treating tempo as an explicit leadership responsibility. Requisite Pace explores the design work through which that responsibility can be fulfilled.

Leaders influence which signals receive attention, how urgency is interpreted and when the organisation pauses to learn. They also shape the decision rights, funding, assurance and working routines through which different tempos meet.

Three questions bring those responsibilities together:

1. Which rhythms matter most to the value we create?

2. Where are people compensating for timing arrangements that no longer fit?

3. And could we change those arrangements within the time our environment would allow?

Setting the tempo is a consequential act of leadership. Designing the organisation to carry it - and to change it - is how that judgement becomes a lasting capability.