
Why core banking programmes fail, and what the survivors did differently
The failure pattern is remarkably consistent across every abandoned core replacement we have been asked to review. It is almost never the software.
Priya Venkatesh
Written by the people doing the work. Specific, occasionally uncomfortable, never ghostwritten.

The failure pattern is remarkably consistent across every abandoned core replacement we have been asked to review. It is almost never the software.
Priya Venkatesh
5 results

Retrieval-augmented generation gets you to a convincing demo. Everything between that demo and a system a regulator will accept is the real work.
Marcus Lindqvist

Most cloud business cases are built at datacentre level and validated never. Here is the workload-level model we use instead.
Aisha Al-Mansoori

The centralised ESB deserved its reputation. The capabilities it provided did not disappear when the product went out of fashion.
Aisha Al-Mansoori

Mirroring an English layout and swapping the strings produces something that reads as foreign to every Arabic-speaking user. Here is what changes.
Aisha Al-Mansoori

Response-time service levels reward acknowledging incidents quickly. They are indifferent to whether the same incident happens again next month.
Daniel Okoye
One email a month. New articles, migration post-mortems and the occasional uncomfortable benchmark. No product marketing.
Our architects run working sessions on exactly these problems.