In consumer tech, your toughest stakeholder is usually the CPO with a strong opinion about the product direction. In finance and ERP product management, you're managing the CFO, the Chief Risk Officer, the Head of Tax, external auditors, regulators, legal counsel, and sometimes a board sub-committee. Simultaneously. With different information needs, different risk appetites, and different definitions of what "done" means.
The playbook is completely different. Here's what has worked for me across banking, logistics, marketplace, and energy-tech environments.
Map Influence, Not Just Interest
The standard stakeholder matrix — high interest/high influence, low interest/low influence — is a starting point, not a strategy. In regulated industries, you also need to map veto power. Who can stop this from shipping? Who can create a delay through an audit finding or a compliance escalation? These are not always the most senior people in the room, and they're often not visible on a standard org chart.
At one regulated bank, the most consequential stakeholder on a data platform project turned out to be the Head of Regulatory Reporting — a technical expert who had no formal authority over the project but whose sign-off on the output format was required before the system could go live. Identifying her early and involving her in the design phase saved us a three-month rework cycle.
Speak the Language of Risk, Not Features
Finance and compliance stakeholders do not care about feature velocity, sprint burndown, or user story completion rates. They care about risk — specifically, what risks does this programme create, what risks does it mitigate, and what is the residual risk after implementation?
Reframing your product communication in risk language is one of the highest-leverage investments a finance PM can make. Instead of "we're shipping the new reconciliation module in Q3," communicate "the current manual reconciliation process creates a material risk of reporting errors during peak periods; the Q3 delivery mitigates this risk and reduces month-end close time by approximately 40%." The second framing resonates with every finance and compliance stakeholder in the room.
Never Surprise Senior Stakeholders
The cardinal rule of senior stakeholder management in regulated environments is that bad news must never be a surprise. A CFO who learns about a project delay at a steering committee meeting — rather than in a pre-meeting conversation with the PM — will never fully trust that PM again. A CRO who discovers a compliance gap through an external audit rather than through the product team will treat it as a governance failure.
Build a communication rhythm that ensures senior stakeholders hear about problems early, in private, with a proposed mitigation before they hear about them in a formal governance forum. This requires courage — it means having uncomfortable conversations proactively rather than hoping the problem resolves itself. It's also the only approach that builds the sustained trust that makes long programmes possible.
Earn Technical Credibility
Finance and technology stakeholders both need to trust you, but for different reasons. Finance trusts you because you understand their domain deeply enough to represent their needs accurately. Technology trusts you because you understand the architecture well enough to make sensible trade-off decisions. You don't need to be a developer or an accountant. But you need to understand both disciplines well enough that neither group feels the need to work around you to get to the right answer.