Why Incumbents Lose Speed: The Three Clocks Problem

Executive summary

The solution is not to push harder. It is to align your product, risk, and finance clocks with four critical fixes:

1. Continuous assurance instead of manual gating.
2. Outcome-based tranche funding instead of quarterly project budgets.
3. Explicit decision rights.
4. A pragmatically designed cadence map.

Measure queue time and decision latency, not just effort. If most lead time is waiting, “move faster” will not help.

Start with one value stream, build reusable patterns such as pre-approvals, policy checks, and funding templates, then scale.

The Three Clocks problem

If you are an incumbent executive, your competitive disadvantage is rarely talent. It is timing.

Picture a capable product team. Their backlog is clear, the platform is stable, and they are ready to release value. They can deliver meaningful increments on a steady cadence until the system intervenes.

Release approval waits for a monthly forum.

Security checks happen manually at the end, surfacing risks when they are most expensive to fix.

Funding is locked in an annual budget, making it impossible to pivot resources to a winning idea until the next fiscal year.

This is why digital transformation often feels like grinding gears. Work stops. Queues form. Leaders conclude that agile is not delivering speed. But the team is not slow. The operating system is mistimed.

You have a product clock trying to spin weekly, while your risk clock ticks monthly and your finance clock ticks annually.

Clock misalignment creates four predictable problems:

1. Queues and waiting: work piles up at the slowest clock, and waiting becomes the dominant component of cycle time.
2. Bigger batches: teams bundle changes to make the gate worth it, increasing blast radius and making rollbacks harder.
3. Late risk discovery: controls that could have been automated show up near release, when fixes are expensive and political.
4. Rework and mistrust: late surprises trigger escalation, escalation triggers more gating, and gating triggers more batching.

Why “move faster” does not work

Is it fair to say incumbents are slow? The data suggests it is not just fair. It is a mathematical certainty.

When we measure flow efficiency, the ratio of time work is active versus time work is waiting, high-performing digital natives often achieve 40% or more. In typical large enterprises, flow efficiency is often below 5%.

This means that for every 100 days a feature takes to reach the market, it may only be worked on for 5 days. For the other 95 days, it is sitting in a queue, waiting for a signature, waiting for a committee, or waiting for a budget code.

Move faster mandates fail because they squeeze the product clock without changing the risk and finance clocks that govern flow. They focus on the 5% of effort without touching the 95% of waiting.

To fix this, you must redesign the interfaces between your three clocks.

First define the three clocks

1. The Product Clock, the delivery loop

The Product Clock is the cadence at which teams build and deploy increments, measure adoption, quality, and cost to serve, and reprioritize based on evidence.

The goal is fast value realization.

Healthy delivery reduces uncertainty quickly: smaller releases, faster feedback, and fewer surprises.

2. The Risk Clock, the assurance loop

The Risk Clock manages critical risks such as regulatory obligations, privacy, security, safety, model risk, and reputational exposure.

The goal is safety, compliance, and regulatory adherence.

If assurance is mostly manual, late, and approval-centric, it cannot keep up with modern delivery. It becomes a queue.

3. The Finance Clock, the allocation loop

The Finance Clock allocates scarce resources.

The goal is efficient and timely allocation of scarce capital.

But many incumbents still allocate through annual planning, quarterly gates, and headcount locks. You cannot run a weekly delivery system on an annual budget cycle.

By the time you realize a project is failing, the money is already committed for the year.

Then define the alignment metrics that matter

The most important metrics are:

1. End-to-end lead time versus queue time, meaning how long work waits at gates.
2. Approval lead time by gate, for example security review, release forum, or steering committee.
3. Share of changes that are standard, meaning pre-approved with automated checks, versus exceptions.
4. Exception cycle time, meaning time from flag to decision to remediation.
5. Funding decision frequency, meaning how often capacity can be reallocated.

A 10-minute diagnostic

If you see these symptoms, you have a Three Clocks problem:

1. Projects are done but stuck in approval limbo.
2. Quarterly funding governs weekly delivery.
3. Risk is discovered late and triggers rollback, escalation, and anxiety.
4. Agile rituals exist, but waterfall governance sits underneath.
5. Teams optimize for passing gates, not for learning and outcomes.

Ask for these numbers. They are usually easy to extract:

1. Queue time share. This reveals whether waiting dominates lead time. Action: make queues visible and cut the biggest queue first.
2. Approval lead time by gate. This shows which clock sets the pace. Action: single-digit days for standard changes.
3. Percentage of standard changes versus exceptions. This reveals how much change can flow without manual review. Action: grow standards month by month.
4. Exception cycle time. This shows how fast the organization resolves true risk. Action: create a clear SLA and escalation path.
5. Funding decision frequency. This shows how quickly capital can move. Action: create monthly reallocation and quarterly strategy refresh.

Clock alignment: four practical fixes

The fix is not faster teams. It is redesigning the interfaces so speed is safe and capital is agile.

Fix 1: Move risk from approval to continuous assurance

Stop treating risk as a ticket queue. Treat it as a continuously monitored system that is designed for two flows:

1. Standards: routine changes, such as content updates or standard API integrations, that use pre-approved patterns and pass automated policy checks.
2. Exceptions: changes that fall outside standards and get triaged with an explicit cadence and SLA.

Continuous assurance typically combines a pre-approval library, policy checks in the delivery pipeline, and an exception triage forum.

This speeds delivery and improves risk posture because controls are applied consistently and early. By automating the governance for the 80% of standard work, your risk teams have the capacity to deeply inspect the 20% of work that actually poses a threat.

Fix 2: Replace quarterly funding with outcome-based tranche funding

Product teams cannot operate on a two-week delivery cadence if money only moves quarterly. Tranche funding is the practical middle ground between rigid project budgets and uncontrolled spend.

Fund persistent teams and value streams against outcomes such as adoption, cycle time, revenue impact, and customer satisfaction, not fixed project plans.

Release funding in smaller tranches tied to evidence and learning, for example four to eight week increments.

Create explicit kill, pivot, or scale moments based on what you now know.

Use guardrails to keep control: spend caps, transparency dashboards, and clear policy constraints.

It is often helpful to frame the change in a CFO-friendly way. You are managing an investment portfolio, not enforcing rigid compliance to a plan. This gives the CFO more control, not less, allowing capital to move from failing initiatives to winning ones without waiting for the next fiscal planning cycle.

Fix 3: Make decision rights explicit and keep governance lightweight

Governance slows organizations when it tries to inspect and approve every change.

A better model separates responsibilities:

1. Product teams ship and operate on short cadences within defined standards.
2. Risk teams define policies, monitor adherence, and manage exceptions, not repeat approvals.
3. Finance steers the portfolio cadence and reallocates capacity without resetting teams to zero each quarter.

One operating rule matters most: delegated decision rights must be unambiguous.

Ambiguity is where delay hides.

Fix 4: Design the cadence map

Do not debate culture until you have designed cadence.

Your calendar is your operating system.

A pragmatic cadence map can vary by organization. The principle cannot: finance must move often enough to respond to learning, and risk must run early enough to prevent late surprises.

Common failure modes and what to do instead

1. Automating checks without updating policy: start with standards and conditions, then encode checks.
2. Exceptions becoming the new queue: set an SLA, keep the forum short, and continuously expand standards.
3. Monthly forums that only review: require decisions, such as reallocate, kill, or scale.
4. Measuring effort instead of waiting: publish queue time by gate and treat it as waste.
5. Asking teams to go faster while holding headcount rigid: decouple delivery cadence from quarterly staffing cycles.

Implementation: start small, scale by patterns

Do not attempt to realign clocks across the entire enterprise in one initiative. Pick one value stream and treat it as a pilot.

Step 1: Choose a value stream

Choose a value stream with real customer impact and real risk constraints.

Step 2: Map the clocks

For that stream, document the current product cadence, risk gates, and funding cadence. Identify where work queues and why.

Step 3: Implement the three interfaces

1. Risk to product: a pre-approval library and automated checks.
2. Finance to product: tranche funding and a monthly steering forum.
3. Risk to finance: exception governance and reporting.

Step 4: Measure queue time, not just effort

If you only measure how hard people work, you will miss the real constraint.

Step 5: Scale by reusing patterns

Reuse policy templates, funding templates, and cadence templates.

Monday morning actions

If you do nothing else this week, do these five things:

1. Identify your slowest clock and name the mechanism. “Risk is slow” is not a mechanism. “Security review is monthly and manual” is.
2. Create a risk pre-approval library v1. Start with 10 to 20 patterns that represent most change volume.
3. Pilot a monthly portfolio review instead of quarterly. Keep it short and decision-oriented.
4. Publish decision rights for one value stream. Reduce the hidden tax of “who needs to sign off?”
5. Make queue time visible. Track how long work waits at gates and treat waiting time as waste.

A closing challenge

If you are an incumbent executive, your competitive disadvantage is rarely talent. It is timing.

Digital-native competitors are not magically faster. They run a system where assurance and allocation operate at a compatible cadence with delivery. They align clocks by default.

The question is not, “How do we push teams harder?”

It is: “Which clock is governing us, and how do we redesign the interfaces so speed is safe and capital is agile?”

A practical starting point: run a 60-minute Three Clocks diagnostic with your leadership team. Walk out with a scorecard, a one-page cadence map, a first set of pre-approval patterns, and a pilot charter for one value stream.