← Practice

Engagement note · Anonymised

The bottleneck wasn't where leadership was looking

Retail bank · pricing-response diagnostic · the shape generalises; the detail does not.

A tier-2 retail bank's pricing decisions were taking longer than the competitor cycle they were responding to. Leadership had a confident diagnosis and a budget allocated to fix it. The measured finding pointed somewhere else entirely — and the eventual intervention cost a re-sequence, not a programme.

§1 — The situation

Customer behaviour was outrunning the product-response window.

Customer behaviour was shifting faster than the bank's product-response window. Competitors were repricing inside a cycle the bank couldn't match: by the time a pricing decision cleared internally, the market had moved again. The symptom was visible at board level — lost volume in rate-sensitive segments — and the pressure to act was real.

§2 — The assumed bottleneck

Leadership had already named the culprit: decision authority.

The working theory inside the executive team was that credit and pricing approvals took too long — too many committees, too many sign-offs. The proposed fix followed directly: widen decision authority, compress the approval cycle, possibly restructure the pricing committee. A plausible diagnosis, with a programme-shaped price tag attached.

This is the most common executive assumption in transformation work: when responses are slow, the decision layer gets the blame. Sometimes that's right. Usually it isn't.

§3 — What measurement found

The decision layer was fine. The delay lived upstream.

Measuring the actual delay profile across the response chain told a different story. The bank acquired the customer signal cleanly — the data was there, on time. The decision-authority layer was responsive when the question reached it: once a pricing recommendation landed in front of the committee, the decision came quickly.

The delay accumulated in assimilation — the analyst layer that turns raw customer signals into a form a pricing committee can actually decide on. The work of converting data into a decidable position was under-staffed for synthesis, organised for reporting, and nobody was instrumenting it. The signal sat in that layer for most of the elapsed time, invisible to the executive team because no one had ever measured where the time went.

More authority would have been wasted budget. The committee wasn't the constraint.

§4 — The intervention

A re-sequence, not a programme.

The intervention re-sequenced the insight-to-decision workflow in the analyst layer. No change to decision authority. No new capability built. No committee restructure. The fix sat in a layer the executive team had not been looking at — and it cost a fraction of the programme that had been budgeted for the assumed problem.

The reframe was the intervention: leadership stopped asking "how do we decide faster" and started asking "where does the time actually go."

§5 — Why this generalises

The pattern, not the particulars.

Executives usually assume the bottleneck is decision speed. In measured engagements it is more often assimilation — the organisation acquired the signal but never converted it into something decidable — or reflexive learning, where the same signal keeps arriving because the last response never closed the loop. The discipline is to measure before prescribing; the diagnostic method behind this engagement is published openly at soaringwings.ai.

Anonymised under engagement confidentiality. Full engagement note available on request, subject to anonymisation review.

Related
Bring a situation like this →
© 2026 AJ Olivier Escape velocity for enterprise transformation