Topics
◆ Product

Product Management

Product management is the work of deciding what to build and why: understanding customer problems, choosing which to solve, defining the product and measuring whether it delivers the intended outcome; in fintech and payments it also means designing around money state, risk and regulation.

Product management in payments is product management with money state, scheme rules and a regulator in the room. These essays cover the role, the toolkit, roadmaps under regulatory risk, hiring, and the failure patterns seen from the operating side.

Payment product work connects a customer decision to money state, operations, risk and a route to resolution when the expected outcome does not happen. That changes how teams define scope, prioritise a roadmap and measure whether a release is ready.

Follow the product path from discovery through requirements, experiments, measurement and launch. Pricing and lifecycle guides cover decisions after the initial release.

PRACTICAL READING PATHS

Start with the question you need to answer.

Choose the work in front of you. Each path moves from a starting question to a practical decision, with examples you can adapt. Project experience is documented separately in the case studies.

PUT THE GUIDE TO WORK

Resources you can use.

Editable files, worked examples and instructions. Free to download, with no sign-up. All example records are synthetic.

Write a payments API PRD

A filled-in payout example with payment states, safe retries, callbacks, authority and testable acceptance criteria.

How to use this resource

Open the Markdown file in a text editor or import it into your documentation tool. Replace the illustrative contract with your provider's actual behavior and assign each open decision. The example specifies a product; it is not a working payment API.

Read the companion guide
◆ Essays

The full topic archive.

74 essays
Nov 4, 20265 min read

AI hallucinations in customer-facing products: how product teams reduce and handle them

You cannot test hallucinations away entirely. Narrow the task, ground answers in approved sources, measure failure on real cases and design a safe path for the wrong answer.

Nov 4, 20265 min read

AI in operations: how to choose the first use case and prove it works

The first AI use case in operations should be boring, frequent and measurable. Pick the workflow before the model, keep a human owner and prove it against today's baseline.

Nov 4, 20266 min read

How to become a product manager in fintech: skills, path and first 90 days

Fintech product management is ordinary product craft plus four domain skills: payment flows, regulation, risk and unit economics. Here is how to build them, prove them and use your first 90 days.

Nov 4, 20264 min read

Product manager vs product owner: what is the difference, and does it matter?

A product owner is accountable for a Scrum team's backlog and product value. A product manager owns the problem, the strategy and the outcome. Many people do both.

Nov 4, 20267 min read

Product manager vs project manager vs program manager: the three roles compared

Three similar titles, three different questions: what should we build, how do we deliver this piece of work, and how do all the pieces add up to the outcome?

Nov 4, 20267 min read

How to build a product roadmap for a payments product

A payments roadmap carries dates you do not control. Put scheme, regulatory and partner obligations on a dated track, keep discretionary bets in horizons, and label what each date means.

Oct 25, 20264 min read

Accessibility belongs in the acceptance conversation

A dialog can look clear while leaving a keyboard user behind it. Follow the complete change task and record what the tested environment actually supports.

Oct 25, 20264 min read

An API contract must explain the customer outcome

A successful response can describe work that is still unfinished. Give the consuming product a contract for the outcome it may honestly show.

Oct 25, 20265 min read

Arabic support needs more than translated labels

Arabic labels can coexist with broken reference display or copying. Follow one request through input, confirmation and the receiving support team.

Oct 25, 20264 min read

Keep the reasoning behind an architecture decision

A hosted-versus-in-house decision becomes hard to revisit when its assumptions disappear. Keep the technical reasoning and the conditions that could change it.

Oct 25, 20267 min read

An Outcome OKR Needs a Baseline Before a Target

Shipping a search filter proves delivery. An outcome goal asks whether people can find the right current document, with evidence the team can inspect.

Oct 25, 20266 min read

Test the Product Business Case Where It Is Weakest

A positive base case can depend on a small change in adoption or support cost. Show the threshold, the missing evidence and the next commitment it justifies.

Oct 25, 20265 min read

Reuse product decisions where backlog work begins

A team can repeat an old debate because the earlier product choice is invisible during refinement. Connect the current task to the relevant decision and its limits.

Oct 25, 20265 min read

A product handoff is ready when the receiving team can use it

A folder of designs is not enough when the receiving team cannot find the current rule. Walk through one case and expose the decisions that still affect it.

Oct 25, 20267 min read

Choose a Product Metric That Survives an Easy Shortcut

More messages can make a decision workspace look active while decisions become harder to find. Test what the metric rewards before setting the target.

Oct 25, 20267 min read

The Pricing Unit Changes How Customers Use the Product

A billable report, seat or task changes the decisions customers make. Define the unit before asking whether the price is right.

Oct 25, 20266 min read

When the Priority Score Hides the Decision

A precise score can conceal incompatible estimates. Work through the units and the ranking threshold before assigning a team.

Oct 25, 20266 min read

Why a Roadmap Date Needs a Confidence Label

A forecast can become a customer promise as it moves between teams. Give each roadmap item an evidence state and a clear communication boundary.

Oct 25, 20267 min read

Product Strategy: Make the Choice Behind the Roadmap

A team can justify every feature and still have no agreed direction. Make the choice, its cost and its test visible before assigning delivery dates.

Oct 25, 20266 min read

Product Vision Needs Boundaries: Write Non-Goals That Help Decisions

A vision that accepts every plausible request cannot guide a team. Set boundaries around the user's problem and state when evidence should change them.

Oct 25, 20267 min read

User Research Synthesis: Keep Conflicting Evidence Visible

A shorter form, more context and a clearer waiting status can describe different needs. Preserve the disagreement before choosing what to build.

Oct 25, 20265 min read

Design the state that appears when the normal journey stops

An empty form after a lost response cannot tell the user whether a booking exists. Map evidence, interface wording and the next permitted action together.

Oct 24, 20269 min read

Journey Mapping: Find the Waiting Between Screens

A submitted form can leave the customer waiting on a colleague or an internal queue. Build a journey map that follows the work through to a useful outcome.

Oct 23, 20266 min read

B2B Payments Positioning and Launch: Make the Promise Operable

A B2B payments launch is ready to test when the target customer, commercial promise, integration path and operating limits say the same thing.

Oct 23, 20264 min read

Merchant Activation and Retention Metrics: Define the Lifecycle Before the Dashboard

A merchant is not activated when an account exists; define the first repeatable value event, then measure cohorts and payment-quality guardrails around it.

Oct 23, 20267 min read

Payment Product Lifecycle Decisions: Build, Scale, Migrate or Retire With Evidence

A payment product lifecycle is a sequence of evidence decisions: prove the problem, prove the flow, scale safely, migrate transparently and retire without stranding money or customers.

Oct 23, 20267 min read

Experimenting on Payment Products Without Breaking the Money Flow

Run a payment experiment only when the treatment can be reversed safely and its success is measured alongside payment correctness, risk and support guardrails.

Oct 23, 20265 min read

Payments Product Pricing and Packaging: Price the Service You Can Operate

A payment price is a product promise: it must cover the rail, operations, risk and support model the customer is actually buying.

Oct 23, 20265 min read

Product Discovery Research in Payments: Turn Interviews Into a Decision

Payment discovery is useful when interviews, operational records and transaction evidence answer a specific decision, rather than producing a generic list of requests.

Oct 22, 20269 min read

Agentic Commerce: Payment Product Readiness

An agent purchase needs an enforceable spending instruction, a reliable order and payment lifecycle, and someone who owns the exceptions. Start with a bounded buying task and test the failure paths.

Oct 22, 202610 min read

AI Product Management: From Evaluation to Release

An enterprise AI rollout is ready when its owner can state the workflow, failure boundary, evaluation set, release threshold, monitoring signal and rollback path.

Oct 22, 20268 min read

Enterprise AI: Ownership, Access and Operating Handover

Enterprise AI scales when teams share a usable operating model for ownership, risk, evaluation, data, vendors and recovery, rather than a collection of unconnected pilots.

Sep 27, 20267 min read

AI for Product Managers in Regulated Payments: Skills, Roles and How to Learn

AI product management in payments is not prompt engineering. It is deciding which bounded workflow gets a model, what it is allowed to do, who owns it, and how you prove it behaved.

Sep 27, 20266 min read

The Biggest Mistakes Product Managers Make in Payments

The mistakes that hurt in payments are not the ones in product management books. They are the ones where the feature worked and the money did not.

Sep 27, 20266 min read

Why Fintech Products Fail: Seven Causes Seen from the Operating Side

Fintech products rarely fail because the technology did not work. They fail because a partner exited, the losses arrived after the growth, or the money could not be found.

Sep 25, 20266 min read

Fintech vs Traditional Banks: How Product Management Differs on Each Side

The difference between a fintech and a bank is not technology. It is who holds the licence, how decisions are made, and what a product manager is allowed to own.

Sep 25, 20269 min read

The Product Management Toolkit for Payments: Frameworks That Survive Regulators and Settlement

Most product frameworks assume features are independent and the only cost is engineering time. In payments, one feature can change reconciliation load, fraud exposure and licence obligations at once.

Sep 23, 20268 min read

Product Management Roles, Responsibilities and Skills in a Payments Company

Every product management job description lists the same ten responsibilities. What differs is which ones the company actually holds you to. In payments, it is the ones about money state.

Sep 21, 20267 min read

What Is Product Management? A Payments Operator's Definition

Product management is the job of deciding what gets built and being accountable for whether it worked. In payments, that accountability includes money state.

Aug 8, 20266 min read

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.

Aug 8, 20266 min read

UK Open Banking Has a Product Scale Scorecard Now

UK Open Banking's one billion payments and 100 billion API calls should push product teams from adoption storytelling into a harder scale scorecard: reliability, consent completion, VRP quality, fraud, disputes, and cash-flow outcomes.

Aug 6, 20266 min read

Adyen Personalize Turns Checkout Into a Product Control

Adyen Personalize is not only AI checkout optimization. It forces product leaders to decide how shopper data, cost, conversion, experiments, and fraud controls change together.

Aug 5, 20265 min read

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.

Aug 5, 20265 min read

LoopX Shows Agent Teams Need a State Kernel

LoopX is a repo-radar signal because it treats long-running agent work as state management: durable goals, typed todos, human gates, evidence logs, quota-aware continuation, and verifiable handoffs.

Aug 5, 20266 min read

OpenAI Presence Turns Agent Products Into Change Management

OpenAI Presence is a product-management signal because it moves agents from prompt demos into managed service design: channel consistency, evaluations, guardrails, human approval, and change control.

Aug 4, 20266 min read

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.

Aug 4, 20265 min read

Which? and MoneySuperMarket Make Comparison a Trust Loop

The useful product lesson in Which? and MoneySuperMarket's insurance comparison partnership is not more quotes. It is the attempt to combine price discovery with trusted evaluation inside the buying journey.

Aug 1, 20266 min read

NatWest and Uinsure Turn Insurance Into a Product Loop

The NatWest and Uinsure partnership is a product-management lesson: the useful surface is not a faster quote alone. It is a loop that remembers the policy, monitors renewal timing, compares cover, and gives the customer a reason to trust the bank again.

Jul 27, 20266 min read

Ecommpay Shows SMB Payments Need a Product Ladder

The product lesson in Ecommpay for Small Businesses is not cheaper card processing. It is how an enterprise payment stack becomes a staged product ladder for merchants with limited time, volume, and technical capacity.

Jul 22, 20266 min read

Klarna Shows BNPL Product Strategy Has Moved Past Checkout

BNPL is no longer won by adding a pay-later button. The product problem has moved to repeat engagement, transaction margin, credit discipline, merchant distribution, and a scorecard that proves the product is worth default placement.

Jul 21, 20266 min read

Adyen's Orb and Talon.One Close Shows Product Integration Is the Strategy

The product lesson is not that Adyen bought two adjacent platforms. It is that multi-product strategy only works when identity, billing, payments, incentives, and execution have a designed integration model.

Jul 20, 20265 min read

Stripe Projects Shows Agentic Products Need Cost Boundaries

The product lesson is not that agents can provision services. It is that agent-native products need explicit cost, credential, environment, and evidence boundaries.

Jul 19, 20265 min read

Spreedly's Standalone Vault Turns Credential Ownership Into Product Strategy

A payment vault is not only a security store. It is the control point that decides how much future product optionality a merchant keeps.

Jul 17, 20266 min read

CaixaBank Shows Merchant Payments Are Becoming a Product System

CaixaBank's new merchant platform is a useful product lesson: payments win when they reduce operating work, not when they add another terminal feature.

Jul 9, 20266 min read

PNC's App Overhaul Is a Product Migration, Not a Redesign

The app redesign is the visible part. The harder product work is moving millions of users to a new daily-money surface without breaking trust.

Jul 5, 20266 min read

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.

Jun 30, 20267 min read

SWIFT in 2026: ISO 20022, Instant Rails, and the Pressure on Correspondent Banking

ISO 20022 is the past-tense story by 2026. The future-tense story is interoperability with instant domestic rails.

Jun 26, 20265 min read

GoCardless and Sequence Make Billing a Product Surface

GoCardless and Sequence are a useful reminder that billing is not a back-office afterthought. Payment collection, retries, mandates, and cash timing shape activation, retention, and customer trust.

Jun 25, 20266 min read

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.

Jun 21, 20267 min read

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.

May 29, 20267 min read

Chargebacks Are a Product Problem

A rising chargeback line is product debt that finance is paying. The fix is upstream.

May 29, 20266 min read

Payment Cost Is a Product Variable: From 50% to 1% (OTT Migration Playbook)

An OTT streaming platform 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.

May 29, 20265 min read

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.

May 28, 20265 min read

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.

May 26, 20267 min read

Onboarding Conversion vs. Default Rate: The Real Tradeoff

Conversion and default rate are not enemies. They are two sides of the same product surface.

May 25, 20267 min read

Risk Tiering Merchants Is a Product Decision

Tiering is the single most leveraged product decision in a payments platform. Most teams hand it to risk and never recover.

May 20, 202612 min read

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.

May 20, 202613 min read

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.

May 20, 202611 min read

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.

May 20, 20266 min read

Payment Infrastructure Is Not Just APIs, It Is State, Trust and Failure Handling

APIs are the easy part. The hard part is what happens between the auth response and the bank statement.

May 20, 202613 min read

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.

May 16, 20269 min read

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.

May 13, 20266 min read

Program Management vs Product Management in Fintech: Lane Lines That Actually Hold

Use explicit decisions and authority to coordinate product direction, integrated delivery and the transfer into operations.

May 9, 20265 min read

Value-Modeling GenAI Use Cases in Fintech: ROI, Feasibility, Data Readiness, Regulatory Risk

Apply control gates before ranking AI use cases, then compare total cost per accepted task. Keep forecast value, pilot evidence and measured outcomes distinct.

◆ Questions

Common questions about Product Management.

What does a product manager do?

A product manager identifies the customer and business problem worth solving, sets priorities with the team, defines what success looks like and works with engineering, design and operations to ship and measure the result. They own the why and the what; the team shapes the how.

What is different about product management in fintech and payments?

Every feature changes money state, so product managers design for failures, reversals, reconciliation, fraud, scheme rules and regulatory requirements as well as the happy path. Operations, risk and compliance are part of the product.

What is the difference between a product manager and a project manager?

A product manager decides what should be built and why, and is accountable for outcomes over the product's life. A project manager plans and coordinates delivery of a defined scope to time and budget. The roles work closely together.

Need help applying this to a payment product, delivery program or AI workflow? Let’s discuss the work.