The trust-first turnaround that 4×’d adoption of PwC’s internal audit platform

The problem & who had it

• The platform was stuck at ~100 Fortune 500 engagements, and the assumption was that it needed more features.
• Two things held it back, and they compounded: unreliable delivery (unprepared releases, unplanned changes, slipping quality) and a product shaped without the auditor’s workflow in mind.
• The users were auditors on SOC 1 / SOC 2 engagements at Fortune 500 institutions, including global investment banks and card networks. Demanding users on regulated work.
• When the setup or the sequencing tripped them up, auditors did the rational thing: they fell back to Excel and shared documents, the levers they already trusted. Every fallback was adoption lost.
• And the work left zero tolerance for failure. These reports ship to the shareholders of Fortune 500 firms after publishing, so a product that wobbled was one teams couldn’t risk.

What I found

• I didn’t trust the “needs more features” assumption, so I went to the source.
• Troubleshooting calls: I sat on the calls where users hit real problems and watched where the workflow actually broke.
• Close partnership with the Business PM: I lined up what I heard from users with where the business needed the product to go.
• The read: trust had to come before features. A team won’t adopt a tool they’ve watched break.

The fix

Trust before features sounds clean on a slide. In practice you can’t freeze a roadmap. Stakeholders still want features, and a real org keeps shipping them. So there was no freeze. The work was winning the same argument over and over: this reliability fix goes ahead of that feature, and here’s why. The auditors had already voted with their feet. The moment the tool tripped them up they fell back to Excel, so a new feature on a shaky base wouldn’t get used anyway. The incident and release data said the same thing, that the platform couldn’t safely take on more until it stopped breaking. And the stakes settled it: these reports land in front of the shareholders of Fortune 500 firms, where a tool that wobbles is not survivable. Feature by feature, reliability kept winning the slot.

• Stabilised delivery first. Release planning, QA, testing and telemetry, and clearer prioritization, so the platform stopped breaking and teams could rely on it.
• Reframed the product around the auditor. The roadmap got rebuilt around the real workflow the research surfaced, away from the builder’s original assumptions.
• Automated the grind, once trust was restored. With the platform stable, I drove the control-sequencing engine and Smart Prefill / Guided Roll-Forward to kill the repetitive manual setup.