Skip to main content

Why I write about banking systems

Decision notes on integration, content and AI governance — with dated evidence, not vendor slideware.

Updated 3 min readMarkdown
Why I write about banking systems

For most of the last decade I have been the person who has to sign the paper that says we chose this platform, and here is why. Core banking, content management, API layers, identity, collections data, programme estimates. The work is rarely about technology being new. It is about a decision that has to survive a board, an auditor and a renewal cycle three years later.

This blog is where I make those decision patterns public — anonymised, with the numbers that can be cited and the trade-offs that usually stay inside a slide deck.

Banking fails on decisions, not on ideas

I have watched a bank renew a document platform because replacing it looked riskier than keeping it, and I have watched another replace the same class of platform because the renewal price had quietly become the second-largest line in the IT budget. Both were rational. Neither was obvious.

The difference was never the product comparison. It was whether someone had written down what would have to be true for each option to be the right one — and had the evidence to check it.

What you will find here

Six lines of work, each with its own series:

  1. Integration and APIs — when an ESB is still the right answer, what ISO 20022 really costs to implement, and how payment hubs are chosen.
  2. Content services and ECM — renewal versus replacement for document platforms, and how to read a market that is consolidating.
  3. AI governance — what a regulated institution must be able to prove, not just promise, about models and agents.
  4. Identity and e-signature — the evidence chain behind a digital contract, and where implementations usually break it.
  5. Running programmes — estimates, PMOs and operating models that measure decisions instead of activity.
  6. Buying enterprise software — RFPs, scorecards and the questions that make a vendor answer honestly.

Every article follows the same shape: what changed, a decision framework, options and trade-offs, the numbers, and what I would do in the first 30, 60 and 90 days. Where I do not know, I say so.

What this blog is not

It is not a review site. I do not rank products or take vendor briefings as fact. It is not investment or legal advice. And it is not a place to find client names: every case is anonymised, every figure is either public with a source or rounded beyond recognition.

Who it is for

Architects, engineering leads, CIOs and programme sponsors who have to choose between two reasonable options and explain the choice afterwards. If you are earlier in your career, the decision frameworks should still be useful — the constraints are the interesting part.

If that sounds like your week, subscribe to get the next note. I publish on Tuesdays, and the first series starts with integration: why ESB is not dead, and why it stopped being the default.

Personal views. Client and employer details are anonymised. Market figures are linked to public sources and dated.

No comments yet. Be the first to comment.