Work Redesign and Experience Redesign Must Happen Together

The Global Signal

In April 2018, the British bank TSB attempted to migrate 5.4 million customers to a new in-house digital banking platform over an 18-month project window. The migration failed publicly and immediately: online and mobile banking went down, and branches were unable to serve customers who could no longer access their own accounts. Case-study analyses of the failure describe root causes including fragmented testing that never simulated realistic full customer load, too many uncoordinated technology suppliers working on interdependent pieces, and no functioning rollback plan once problems began (Henrico Dolfing case study; Panorama Consulting). TSB ultimately paid more than £330 million in recovery costs and regulatory penalties tied to risk governance failures in how the migration was managed.

The lesson is not that ambitious technology change is inherently risky, since most large organizations undertake it successfully. It is that TSB's failure was specifically a readiness failure: the bank moved customers onto a fundamentally new system before the operational capability to support that system at scale actually existed, and customers discovered the gap in real time, alongside the bank itself.

The Hidden Signal

TSB's case is a large, public, expensive version of a pattern that plays out at smaller scale constantly, usually without headlines. Consider a hypothetical scenario that illustrates the same mechanism at a more modest scope: a financial services company redesigns its customer portal, a cleaner interface, faster forms, clearer status indicators, and customer satisfaction with the new interface improves measurably after launch. Behind that interface, the underlying process it connects to, loan approval, claims processing, account servicing, has not changed at all, and still takes the same amount of time it always did. Customers get a genuinely better experience submitting a request and the same experience waiting for a decision. The interface investment shows up in satisfaction scores. It does not show up in the outcome that actually determines whether customers stay.

Why the Visible Metric Misleads

Interface satisfaction and adoption metrics measure the moment of interaction: was the form easy to fill out, was the new app pleasant to use. They do not measure the outcome that follows the interaction, which is usually what customers actually care about. TSB's case shows the extreme version of this gap, a genuinely ambitious redesign that failed not because customers rejected the new interface conceptually, but because the operational and technical foundation underneath it was not ready to bear the load the redesign promised.

The more revealing measure is end-to-end cycle time, from the moment a customer initiates a request to the moment it is actually resolved, compared against interface-level satisfaction. When satisfaction rises while cycle time stays flat, the redesign has improved the customer's first impression without improving the thing that determines whether that impression survives contact with the rest of the process.

Implication for Operators

TSB's case is instructive precisely because the consequences were severe enough to be fully documented and publicly analyzed. Most organizations will never experience a failure at that scale, but the underlying pattern, customer-facing ambition outpacing operational readiness, is common at smaller scale and mostly invisible until it shows up quietly in retention rather than in headlines. The practical shift is treating operational readiness as inseparable from the redesign decision itself, not as a separate workstream that can lag behind.