# What the Press Release Left Out
A colleague forwarded it to me with a congratulatory message. I read the headline — “global financial leader driving innovation and transformation” — and felt something I did not expect. Not pride. Not satisfaction. A mild, specific embarrassment, the kind you feel when someone introduces you at a party with a description that technically fits and somehow misses entirely.
I saved the email. I did not share the press release.
That gap — between the curated version of a career and the one you actually lived through — is something nobody in professional services talks about honestly. We build the public record with intent. The board appointments, the regulatory frameworks delivered, the transformation programmes that made it into case studies. What we edit out, instinctively and without discussion, is everything that made the outcome uncertain. The decisions made at 11pm with incomplete information. The quarters where the answer was not obvious and the wrong call had consequences that were not theoretical.
—
## The Nights That Did Not Make the Press Release
In 2019, I was deep in a regulatory framework build — the kind of project where the regulator has opinions but not instructions, and your job is to interpret the gap correctly. We had constructed something substantial. Weeks of work, dozens of stakeholder sessions, significant institutional commitment behind it.
Two days before the submission window, a senior compliance contact — someone I trusted, someone with years of direct regulatory experience — pulled me aside and said, quietly, that she thought we had misread a core requirement.
I will not pretend I handled that moment with equanimity. My first instinct was to defend the work. We had been thorough. We had checked. I had personally reviewed the relevant sections. My second instinct, arriving about thirty seconds later, was considerably more useful: what if she is right?
We pulled apart the relevant section that evening. She was not entirely right. But she was not entirely wrong either. We rebuilt one component overnight and submitted on time. The framework survived the review. But I remember that evening more clearly than I remember the sign-off meeting three months later. The sign-off meeting was pleasant. That evening was where the actual work happened.
No press release mentions the evenings like that one.
—
## Three Things That Experience Actually Teaches
The first is that credentials are a starting condition, not an ongoing qualification. I have seen this pattern often enough to state it with confidence: the moment someone starts leading with their title as a substitute for their reasoning, the quality of their thinking has usually already started to decline. Credentials open the room. They do not guarantee you have anything worth saying once you are inside it. The senior executives I have learned from most were the ones who held their credentials lightly and their judgment rigorously.
The second is that the problems worth solving rarely announce themselves clearly. The frameworks I have built that actually worked — the ones that held up under regulatory scrutiny and operational pressure — were almost never solutions to the obvious problem. They were solutions to the thing underneath the obvious problem. This takes time to learn because the obvious problem is always loudest, always most urgent, and always surrounded by people who want it fixed quickly. Slowing down long enough to ask whether you are solving the right problem is, counterintuitively, the fastest route to a durable outcome. Most organisations never slow down. This is why most regulatory frameworks require rebuilding.
The third thing experience teaches, and this one took me longer than it should have: the measure of professional judgment is not what you do when the answer is clear. It is what you do when the answer is not clear, the deadline is real, and the consequences of being wrong are sitting in the room with you. That is the test. Everything else is preparation for that test. Titles, credentials, track records — they are evidence that you have been in the room before. They say nothing about what you will do when the pressure is on tonight.
—
## What This Means If You Are Building Something
If you are early in a senior role, or building a team, or evaluating people for high-stakes positions, I would offer this: stop looking primarily at the polished version of someone’s career. Look for the moments they are willing to tell you about honestly — the project that nearly fell apart, the call they got wrong, the evening they rebuilt something from scratch because a trusted colleague said it was not right.
Those moments are not weaknesses in a record. They are the record. The capability that matters in a crisis is not the one developed during the projects that went smoothly. It is the one forged during the ones that did not.
The press release version of a career is useful for introductions. It is genuinely useless for knowing whether someone will hold up when the framework they built gets challenged at the worst possible moment, and they have to decide in real time whether to defend it or rebuild it.
Most organisations hire for the press release. Then they wonder why they are surprised.
—
## A Final Thought
The title “global financial leader” is, by any reasonable measure, accurate. I have operated across multiple continents, built infrastructure that regulators relied on, and led teams through complexity that was not fictional. I am not dismissing it.
But the career I am actually proud of is not the one in the press release. It is the one that includes the evening in 2019, the submission I nearly got wrong, the colleagues who told me difficult things at inconvenient moments, and the judgment — slowly, expensively developed — to listen to them.
Credentials are the door. What you did when you were scared — that is the room.
—