There's a version of product management that's taught in books: find the need, build the thing, ship it fast, iterate. It's real — and it's almost useless in a regulated industry.
In payments, "ship fast" comes with a legal review that can outlive the development cycle. "Iterate" comes with an audit trail. "Find the need" comes with a compliance team that needs to understand why you're asking about it.
The two cultures
Most of the tension in regulated product work isn't between product and engineering. It's between product and everyone else: legal, compliance, risk, security, privacy. And the honest truth is, they're often right to slow things down — because when a payment product fails, it's not a bug report, it's a regulatory filing.
The mistake is treating that as a conflict. It's not. It's the product's architecture.
What actually works
- Bring the guardrails in at the start. The PM who hands a design to compliance at the end will get it back with red ink and a schedule slip. The PM who brings compliance in at the whiteboard stage gets a design that can't violate the rules, because the rules shaped it.
- Learn to read the "no." A compliance rejection is almost always a spec, badly translated. "No" usually means "the requirement is poorly worded, and if you solve the underlying constraint, this is actually a yes."
- Make risk visible on the roadmap. Risk work that's invisible gets deprioritized; risk work that's on the roadmap gets resourced. This is a program-leadership skill more than a product skill.
- Don't romanticize speed. In a regulated industry, the moat is often the ability to not break things. "Boring" reliability is a feature users pay for, even if they never say so.
Why it matters now
AI is about to stress-test every regulated industry at once. The products that win won't be the ones that move fastest — they'll be the ones that move fast inside the guardrails, with leaders who can translate between what's possible and what's permitted.
That translation is the whole job. And it's why the best product leaders in payments are hybrids: people who can sit with the engineers on delivery risk and with legal on what "done" means — and make both feel heard.
— Rukuma