HSBC: Designing the target operating model for 500 teams and a $450M portfolio

James co-led operating-model design and pilots inside HSBC Global Payment Solutions, for an intended 500-team scope and $450M portfolio. His work is complete. Global rollout is in progress; the results here cover the design and pilot work.
Delivery
Rung
Delivery Lead co-designing, piloting and refining a target operating model.
Duration
6 months
Engagement shape
Delivery Lead co-designing, piloting and refining a target operating model.
Stage reachedDesign and pilots completed; global rollout in progress
500teams in the intended operating-model scope
$450Mportfolio scope of the model James co-designed
In progressglobal rollout; James's design and pilot work is complete
On this page

The challenge

HSBC's Global Payment Solutions division had no consistent operating model across 500 teams and a $450M budget. Every region had its own processes, creating fragmented delivery, unclear ownership, and unpredictable outcomes with little leadership visibility.

What we did

Brought in as Delivery Lead, James co-led the design, piloting, and refinement of a new target operating model with select GPS teams: standardised roles, governance and reporting; agile practices tailored for product delivery at scale; and metrics and dashboards for progress, dependencies, and value. The model was tested against real-world feedback with executive alignment throughout.

// run against The Tenhaw Way, published in full and free to adopt without engaging us

The outcome

The pilots validated the model with improved predictability, clear ownership and faster decisions. Blockers and dependencies surfaced earlier. James's design and pilot work is complete, and the wider global rollout is in progress. The case does not claim a completed rollout across all 500 teams.

Limits, and what is withheld

What transfers, and what does not

The relevant practice is operating-model design: defining roles, governance, reporting and value metrics with the teams that will use them. James co-led design, pilots and refinement inside HSBC. His work is complete, while the wider global rollout remains in progress.

book a call

Want the same thing, in your organisation?

A 30-minute call with James Rooney. We will tell you which parts of this we have done before and which we would be doing for the first time, and you will leave with a rough scope either way.

most start with a fixed-price AI Readiness Audit · £44,000 · 4 weeks · working prototypes

// pick a slot · cal.com/tenhaw/professional-servicesLIVE CALENDAR

No time that suits? Email hello@tenhaw.com. Calendar not loading? Open it on cal.com.

Describe the work

Describe the work in a paragraph. James replies with a rough scope and budget range within two working days.

Send James a paragraph about the work

We use these details to respond to your enquiry. Read our privacy notice.

Questions about this engagement

Was the HSBC payments operating model a Tenhaw engagement?

No. James Rooney, Tenhaw's founder, was brought into HSBC's Global Payment Solutions division as Delivery Lead and co-led the design, piloting and refinement of the target operating model over six months. It sits on the site as founder track record, alongside his other delivery and transformation roles at HSBC, rather than as work delivered under the Tenhaw banner. The discipline it demonstrates is the one Tenhaw sells today. Designing an operating model at bank scale and then piloting it is a different job from drawing one on a slide.

How do you design one operating model for 500 teams?

You start with a handful of the 500. At HSBC's Global Payment Solutions division, a $450M portfolio, James co-led the design with select GPS teams first: standardised roles, governance and reporting, agile practices tailored for product delivery at scale, and metrics and dashboards covering progress, dependencies and value. The model was then piloted and refined against real-world feedback, with executive alignment maintained throughout. Pilots validated it, and the framework is fully designed and tested ahead of its global rollout now in progress. Get the model right with a few teams before you ask hundreds to adopt it.

Why pilot an operating model before rolling it out?

Because an operating model that has only lived on a slide has never met a real team. At HSBC Global Payment Solutions, the target operating model was piloted with select teams and refined against real-world feedback before any global commitment. The pilots did two jobs. They validated the model, showing improved predictability, clear ownership and faster decisions, and they surfaced blockers and dependencies earlier. That evidence is what turns a 2026 rollout across 500 teams into a controlled step. Without it you are asking 500 teams to take a leap of faith.

Has the HSBC payments operating model rolled out yet?

Global rollout is in progress. James's design and pilot work is complete. The evidence in this case comes from selected teams testing and refining the model, including clearer ownership, improved predictability and faster decisions. The 500 teams and $450M describe the intended programme scope, not a completed global rollout.

What goes wrong when every region runs its own delivery processes?

HSBC's Global Payment Solutions division is a concrete example. Across 500 teams and a $450M budget there was no consistent operating model. Every region ran its own processes, which produced fragmented delivery, unclear ownership and unpredictable outcomes, and leadership had little visibility into any of it. The cost is not only inefficiency. It is that nobody can say who owns a decision or when work will land. The fix was one target operating model with standardised roles, governance and reporting, piloted with select teams and refined on real feedback before a global rollout.

What did six months of operating model work at HSBC cover?

Design, piloting and refinement of one target operating model. Brought in as Delivery Lead, James co-led the work for HSBC's Global Payment Solutions division: standardised roles, governance and reporting, agile practices tailored for product delivery at scale, and metrics and dashboards for progress, dependencies and value. The model was then tested with select GPS teams against real-world feedback, with executive alignment maintained throughout. By the end, pilots had validated it and the framework was fully designed and tested, ready for global rollout now in progress.

How do you keep executives aligned during an operating model redesign?

Keep the alignment continuous. At HSBC Global Payment Solutions, executive alignment was maintained right through the design, piloting and refinement of the target operating model, so leaders watched it evolve against real-world feedback instead of being handed a finished document to approve. Then the pilots gave them results to look at, with improved predictability, clear ownership, faster decisions, and blockers and dependencies surfacing earlier. An executive who has seen a model survive contact with real teams needs far less persuading than one reading about it for the first time.

What should an operating model's dashboards actually measure?

Three things: progress, dependencies and value. That was the metrics layer built into HSBC Global Payment Solutions' target operating model, alongside standardised roles, governance and reporting, in a division of 500 teams and a $450M budget that previously gave leadership little visibility. In pilots, that visibility showed up as improved predictability, clear ownership and faster decisions, with blockers and dependencies surfacing earlier. A dashboard that tracks activity tells you people are busy; one that tracks progress, dependencies and value tells you whether the portfolio is actually moving.

What does payments operating model work have to do with agentic AI?

The transferable part is the operating model discipline itself. You define roles, governance, reporting and value metrics once, so the fifty-first team to adopt a capability is cheap instead of a fresh negotiation. That is the problem an AI programme hits at scale, where every new team otherwise renegotiates ownership, oversight and measurement from scratch. The study is honest about its limit. The model was piloted and validated against real feedback, and nothing in it has been through a global rollout yet, let alone an agentic one. Tenhaw's agentic design work applies the same discipline to organisations putting agents into real workflows.

Does agile actually work across hundreds of teams in a bank?

It works when it is tailored, and it fails when it is transplanted. In HSBC's Global Payment Solutions division, agile practices were adapted for product delivery at scale and embedded in a wider target operating model with standardised roles, governance and reporting. Nobody rolled out an off-the-shelf framework. Piloted with select teams and refined on real-world feedback, the result was improved predictability, clear ownership and faster decisions, with blockers and dependencies surfacing earlier. The scale is the notable part. That model is designed for 500 teams and a $450M operating budget, with global rollout in progress.

Is a banking AI target operating model worth it for a smaller bank?

Yes, because scale is not what makes one work. A banking AI target operating model is mostly a set of decisions you want to make once: roles, governance and reporting, and metrics for progress, dependencies and value. At HSBC's Global Payment Solutions division those decisions were co-designed with select teams, piloted and refined against real-world feedback before anything global was committed, so the working unit was a handful of teams even though the scope was 500 teams and a $450M budget. The HSBC model covered payments delivery. Agents were not in its scope. The components travel down to twenty teams without much trouble.

How do you get teams to give up processes they built themselves?

Design the replacement with some of them, not for all of them. At HSBC Global Payment Solutions, James was brought in as Delivery Lead and co-led the target operating model with select GPS teams, piloting it and refining it against real-world feedback, so the version now due for global rollout now in progress has already been changed by the people who used it. The pilots gave teams a reason to move as well, with improved predictability, clear ownership, faster decisions, and blockers and dependencies surfacing earlier. People give up a process they built when the replacement visibly makes their week easier. That is a different argument from a mandate.

What should you standardise first when every team delivers differently?

Roles and ownership, before process. Across HSBC's Global Payment Solutions division the deeper problem was not that 500 teams worked differently; it was that nobody could say who owned a decision, so outcomes were unpredictable and leadership had little visibility across a $450M budget. The target operating model addressed that directly: standardised roles, governance and reporting, with agile practices tailored for product delivery at scale and metrics and dashboards for progress, dependencies and value alongside. In the pilots, clear ownership showed up next to improved predictability and faster decisions. Standardise a process before its owner and you get compliance without accountability.

What should we ask a firm proposing an operating model redesign?

Ask which teams will pilot it and what the pilot changed. A model that has never met a real team is a document. At HSBC's Global Payment Solutions division the target operating model was co-designed with select GPS teams, piloted, and refined against real-world feedback, and the pilots reported improved predictability, clear ownership, faster decisions and earlier sight of blockers. Then ask what the firm is not claiming yet. This study separates completed design and pilots from the global rollout now in progress. A firm that is careful about where its evidence stops is usually careful about the rest of its numbers too.

Should we just roll out our best region's way of working?

Rarely. A region's process carries the context that produced it, meaning its people, its products and the history behind every exception. HSBC's Global Payment Solutions division had all of that, with every region running its own processes across 500 teams and a $450M budget. What was designed instead was one target operating model for the division: standardised roles, governance and reporting, agile practices tailored for product delivery at scale, and metrics and dashboards for progress, dependencies and value, then piloted with select GPS teams and refined on real feedback. Your strongest region is a valuable input to that design rather than the design itself.