Program Management & PMO
Programme management is the operating system underneath every regulated payments build. These posts cover building a PMO from scratch, PMBOK + Agile hybrids, RAID governance, SteerCo cadence, OKR design and the rituals that hold a 12-squad org together.
Field notes for this hub.
UAE E-Invoicing Turns Finance Change Into Provider Readiness Gates
The UAE e-invoicing programme is not only a tax technology change. It forces finance, tax, procurement, ERP, payments, and operations teams to prove provider readiness before the mandate becomes a production risk.
OpenAI Daybreak Makes Cyber Agents An Access-Control Product
OpenAI's Daybreak expansion is not only a model release. It is a product lesson in how to expose more powerful AI capability through eligibility, scope, safeguards, monitoring, and review gates.
The Bank of England Just Turned Payment Vendor Risk Into a Programme Gate
The Bank of England's updated third-party and incident reporting framework turns payment-system vendor risk into a programme-delivery gate, not a procurement appendix.
GitHub Copilot Agent Metrics Make AI Adoption Governable
GitHub's Copilot usage metrics update is a repo-radar signal for AI leaders: agent adoption is no longer a single bucket. Teams can now govern agents by usage, owner, rollout intent, and cost evidence.
Worldline's Digital Euro Pilot Needs Programme Gates
Worldline's selection for the Eurosystem digital euro pilot is a programme-management signal: the hard work is not announcing participation, but governing scope, merchant acceptance, offline flows, integration, evidence, and readiness across a regulated ecosystem.
OpenAI and Hugging Face Make AI Eval Containment a Product Gate
The OpenAI and Hugging Face incident is not only an AI safety headline. It shows why high-risk model evaluations need product gates for isolation, credentials, monitoring, scope, and incident response.
PwC and Label Show CARF Reporting Needs Programme Gates
PwC Middle East and Label's CARF collaboration is a programme-management signal: reporting automation only works when onboarding data, classification, controls, vendor delivery, and evidence are governed together.
DeepMind's AI Control Roadmap Is a Programme Gate
DeepMind's AI Control Roadmap is a delivery-governance signal: AI-agent programmes need gates for monitored coverage, recall, response time, authority boundaries, drills, and escalation ownership.
Kaneo Shows Minimal PM Tools Still Need Governance Boundaries
Kaneo is a useful project-management signal because it argues for less tool noise. The operator lesson is to keep execution simple while preserving decision logs, risk ownership, and delivery evidence elsewhere.
TencentDB Agent Memory Makes Recall a Governance Problem
TencentDB Agent Memory is a useful repo-radar signal because it treats memory as a shared team asset. That makes recall a governance problem, not only a context-window trick.
GitHub Copilot's Gemini Deprecation Needs a Model Fallback Contract
GitHub Copilot's Gemini model deprecation is a useful repo-radar signal because it turns model choice into an operating dependency. Teams need fallback contracts before a provider removes a model from daily workflows.
ScotPayments 2.0 Shows Migration Is a Resilience Programme
ScotPayments 2.0 is a useful programme-management case because the migration was not only a cloud upgrade. It moved live payment services and operational data while protecting public-sector payment continuity.
Alibaba's Open Code Review Shows AI Review Needs Hard Rails
Open-code-review is a useful repo-radar signal because it treats AI review as an engineered workflow. The lesson for fintech teams is to constrain file selection, context, rules, and comment placement before trusting agent output.
Mastercard's Virtual Card Controls Are a Programme-Gate Lesson
Mastercard's virtual card platform update is a delivery lesson for B2B payment programmes: controls, clearing, API access, partners, wallets, and operating evidence need their own gates before scale.
Mambu's Swift Certification Is a Connectivity Programme Lesson
Managed Swift connectivity sounds like infrastructure simplification. The real delivery lesson is sharper: programme leaders still need ownership across connectivity, compliance, sponsor banks, operations, reconciliation, and customer go-live gates.
OmniRoute Shows AI Gateways Need Routing Controls, Not Just More Providers
The repo-radar lesson is not that teams should chase every free model endpoint. It is that AI usage needs a control plane before agents, developers, and tools start routing around limits.
The iDEAL to Wero Migration Is a Delivery-Gate Problem
The iDEAL to Wero migration will be judged less by the announcement and more by whether each participant can prove readiness before traffic moves.
Microsoft Foundry Shows Production Agents Need a Control Plane
Microsoft Foundry's production-agent direction is a useful signal: the AI platform race is moving from model access to control planes for agents.
The UK Financial Services AI Plan Is a Delivery Governance Test
The UK financial-services AI plan is not just policy. For banks and fintechs, it is a programme governance test across models, vendors, skills, resilience, and agentic payments.
Checkout.com Shows AI Payment Optimization Needs Control Loops
AI payment optimization is not a magic approval-rate lift. It is a controlled learning system for authentication, tokens, routing, retries, and risk.
Baringa's UK Payments Migration Shows Why Delivery Gates Matter
Seven delivery gates, roughly 30 million monthly payments, PRA-grade exit planning. Baringa's UK payments-hub migration is a lesson in making change provable at each gate, not a cloud story.
GitHub Copilot OpenTelemetry Makes Agent Work Auditable
Telemetry is becoming the control plane for coding agents. The question is not whether agents ran, but whether teams can explain what they did.
Satispay's Mastercard Cards Turn a Wallet Into a Card Programme
Satispay is turning a closed-loop wallet into an open-loop card programme with Mastercard. The hard part is keeping the wallet's simplicity while absorbing card tiers, FX rules, disputes, and scheme discipline.
Agent Skills Turn Prompting Into an Operating Model
Treat an agent skill as a runbook, not a clever prompt. The value shows up when repeated engineering judgment becomes a versioned procedure with exit criteria a reviewer can check.
GitHub Copilot Session Streaming Makes Agent Governance Observable
Copilot agent-session streaming gives enterprises evidence about prompts, responses, and tool calls. Evidence becomes useful only when someone operates it.
UK Payments Draws the Right Boundary Between Core Rails and Products
The UK proposes one core clearing and messaging scheme with competitive product arrangements above it. Delivery depends on explicit interfaces and decision rights.
GitHub Models Is Shutting Down. Your AI Stack Needs an Exit Plan
GitHub Models' shutdown is a useful warning: an AI prototype becomes an operational dependency faster than most teams build an exit path.
Processor-Only Card Issuing Moves the Work, Not the Risk
Processor-only issuing hands you the ledger, regulatory reporting, dispute operations, fraud policy, and the sponsor-bank relationship. If you cannot name who owns each one, you are not ready for it.
GOV.UK Pay's Adyen Migration Is a 1,000-Service Programme
Moving roughly 1,000 public services to a new payment provider is a portfolio migration across identity, settlement, reconciliation, support, and release governance.
Thredd and Sutton Turn BIN Sponsorship Into an Operating Model
A BIN sponsor shortens the route to a US card launch; it does not shorten the list of decisions someone must own. Thredd and Sutton Bank make the three-party split, sponsor, processor, and programme manager, explicit.
GitHub Desktop Makes Worktrees an AI Agent Control
GitHub Desktop 3.6 makes worktrees accessible beside Copilot-assisted commits and conflict resolution, turning branch isolation into an operating control for parallel AI work.
U.S. Bank and GigSafe Show Instant Payouts Need a PMO
Instant payouts in regulated logistics are not just a rail decision. They need compliance design, worker identity, funding controls, exception handling, reconciliation, and governance.
Stripe Shows Global Checkout Is a Product System
Stripe found that even one geographically irrelevant payment method can dent conversion. That is the tell: global checkout is a system of localisation, authorisation, fraud, tax, and treasury, not a country toggle.
Thredd's Visa Cloud Connect Rollout Is a PMO Lesson
Thredd's Visa Cloud Connect go-live in APAC reads as infrastructure news, but the real lesson is sequencing: certification, resilience, data residency, and release cadence run as one governed programme through a Singapore hub.
Finastra's Core Banking Sale Is a Product Focus Lesson
Which product lines actually deserve executive focus? Finastra answered by selling Universal Banking to Pollen Street, and the move is a sharper lesson on platform sprawl than it looks.
PCI DSS and ISO 27001 as Product Programs
PCI DSS and ISO 27001 are not paperwork projects. Run as product programs, they make the platform measurably stronger.
Payment Cost Is a Product Variable: From 50% to 1% (Tapmad Migration Playbook)
Tapmad was losing roughly half its revenue to payment cost. The rail-mix, dunning, and smart-retry rebuild took it to about 1%, past 5M subscribers, and 70% higher ARPU, with no new vendors.
Payments PRD Template: The 9 Sections Every Senior PM Should Write
A payments PRD is not a SaaS feature brief with a money movement appendix. It has to explain state, risk, settlement, compliance and operational failure before engineering starts.
The Risk-Adjusted Backlog: Prioritising Payment Products When Failure Costs Real Money
A payment roadmap cannot be ranked by revenue alone. The backlog has to price the cost of failure, the cost of delay and the cost of operating complexity.
PMO Maturity Model for Fintech: Five Stages and How to Know Yours
A fintech PMO matures from reporting office to operating system. The test is whether it improves decisions, risk control and delivery throughput.
Vendor Governance in Fintech: The PMO Surface Most Teams Underestimate
Vendor governance is not procurement hygiene. In fintech programs, vendors often own critical path risk, certification evidence, uptime, support and launch readiness.
CSPO + RICE in Practice: A Real Payments Roadmap Walkthrough
RICE is a clean ranking framework that does not know payments exists. CSPO is a clean product mindset that does not know prioritisation maths. Put together, with a risk-adjusted overlay, they become a working operating system for a payments backlog. Here is the walkthrough.
Hiring Fintech PMs: Twelve Interview Questions That Actually Separate Senior From Junior
Most fintech PM interviews still draw from the same SaaS-PM rubric the candidate practiced for. The questions that actually separate senior from junior are the ones that cannot be prepared for from a YouTube series. These are twelve I have used to hire payments product managers, with what each one tests and what the answers reveal.
OKRs at $1B+ TPV: How Payment Goals Differ From SaaS Goals
SaaS OKRs measure user behaviour and revenue growth. Payments OKRs measure money behaviour and risk posture, and the two operate on opposite reflexes. Here is what a senior payments leader actually writes when the platform is clearing a billion.
Payments PM Career Ladder: IC → Lead → Director → VP: What Actually Changes At Each Step
Most career ladders treat the levels as steps on a staircase. Payments is different, each level requires unlearning what worked at the previous one. This is the operator's map of what changes between IC, Lead, Director, and VP in a payments product organisation.
SteerCo Escalation Patterns: When To Bypass Your Boss
Most programme management training treats escalation as a process, write the risk, route the escalation, watch the path. Real escalation is a craft. The senior PgM who has been through one regulator-deadline programme has internalised five patterns that the training never covered.
Where PMOs Fail: Six Patterns I've Watched in Fintech Programmes
PMOs don't fail because the PMs are bad. They fail because the function gets miscast as governance theatre instead of decision-making infrastructure. Six failure shapes, the symptoms, the fix.
Product Management for Payments Platforms: What's Different, and What's Not
A payments PM is a SaaS PM with three extra constituencies and one extra reflex. Get the reflex wrong and the other constituencies stop trusting you.
Project Management for Fintech Regulatory Programmes: PCI DSS, ISO 27001, SOC 2, AML/CFT
Six weeks before the audit, every troubled regulatory programme looks identical: forgotten Confluence pages, evidence requests rotting in inboxes, a year of work crammed into six weeks of theatre. Run it as delivery with an immovable deadline and an external grader, or pay remediation many times over.
Program Management vs Product Management in Fintech: Lane Lines That Actually Hold
Product and program management overlap because they have to. The overlap is where most fintechs break. Hold the lane lines and the overlap becomes the most productive seam in the org.
Building a PMO from Scratch in a Fintech: A 90-Day Playbook
A fintech PMO is not a governance overlay. It's the operating system that lets product, engineering, risk and compliance ship together at regulated-payments cadence.
PMBOK + Agile Hybrid Frameworks for Payments Teams
A regulator wants a stage-gated evidence trail; a product team wants two-week cycles. At Simpaisa I ran 12 squads by classifying each workstream as Agile or Capital and applying the framework that fits. This is that operating model.
Running a $3M Digital Transformation Programme: A Postmortem (TapmadTV)
What it actually took to land a $3M transformation programme on schedule across 5 technology workstreams and 8 vendors, and the three things I would do differently.
RAID Logs, SteerCo and the PMO Stack That Actually Ships at $1B+ Scale
Most PMO failure modes come from registers without owners, SteerCos without decisions, and OKRs without consequences. Fix the stack, fix the delivery.