Several programmes need one target state.
An 8–12 week design-authority engagement for CIOs and heads of payments — target state across rails, Swift, open banking and cards, vendor selection, and a chaired design authority that continues monthly.
8–12 weeks, then monthly · Fixed fee quoted after a short scoping call
Who this is for
- CIOs and heads of payments running several regulator-driven programmes at once
- Institutions where rail, Swift, open banking and cards projects compete for the same stack
- Teams that need a chaired design authority, not another steering committee without teeth
One target state. I set it up and chair the authority.
Parallel programmes invent conflicting architectures
Instant rails, ISO 20022 phase two, open banking and card modernisation often land as separate sponsor decks with separate vendors. The core and hubs pay the price. This engagement produces a coherent target state, runs vendor selection with a scoring model you own, stands up a design authority, and mobilises the programme — then continues monthly as retainer design authority if you want it.
How design authority holds
- Target stateOne architecture across rails, Swift, open banking and cards — conflicts made explicit.
- Vendor selectionRFP and scoring you own, so decisions survive personnel changes.
- AuthorityDesign authority set up and chaired — then monthly cadence as retainer.
What you leave with
- Target state across rails, Swift, open banking and cardsArchitecture the programmes must share
- Vendor selection: RFP and scoringProcess and scorecards you can reuse
- Design authority set up and chairedForum with mandate, membership and decision rights
- Programme mobilizationOwners, sequencing and the handoff into build
How the engagement runs
- Weeks 1–3Inventory programmes, conflicts and current architecture. Leave with a target-state draft and authority charter.
- Weeks 4–8Deepen target state; run or coach vendor selection. Leave with scored decisions and a standing design authority.
- Weeks 9–12Mobilise the programme and lock the monthly retainer cadence if you continue.
Scope fence
This is architecture and design-authority advisory. I am not your PMO factory or a preferred vendor.
In scope
- Target-state architecture across named domains
- Vendor RFP/scoring design and facilitation
- Design authority setup and chairing
- Programme mobilization into build oversight
Out of scope
- Full programme delivery as a body shop
- Taking keys, production admin or vendor commercial agency
- Legal or regulatory filing
- Open-ended strategy without a target-state artefact
If you need another status meeting, keep your PMO. If you need one architecture that holds, start here.
What I need from you
- Executive sponsor (CIO or head of payments) with decision rights
- Access to programme packs across the colliding workstreams — under NDA
- Willingness to stand up a design authority with real mandate
8–12 weeks, then monthly · Fixed fee quoted after a short scoping call