How to Make Your Judgment Visible — And Why Waiting Is the Most Expensive Decision You Can Make

The most expensive thing a VP can do is nothing. Not a wrong call or a bad decision, just nothing. Waiting until the role feels less heavy. Waiting until you feel settled. Waiting for the right moment to start paying attention to how you're being read in senior rooms.

The problem is that perception doesn't wait. It forms in whatever direction it started, and then it builds on itself.

Why Visibility Is the Work at VP Level

Being good at the job is necessary, but it was never going to be enough on its own.

A level down, good work turned into reputation more or less automatically. You delivered, people saw the quality, and they formed their view from that. That was the arrangement.

At VP level you're still expected to deliver, but the thing being measured has changed. The senior people quietly forming a view of you, meeting by meeting, aren't really grading your analysis anymore. They're reading your judgment. How you hold a position. What you do when someone pushes back. Whether you sound like someone who has settled into the seat, or someone still trying to earn it.

Judgment only counts when people can actually see it. When you bury it inside a long explanation, it disappears. A lot of new VPs are doing excellent work and hiding the best part of it in the process.

Seventeen years inside a very demanding institution, across governance forums and regulatory reviews on three continents, taught me the same lesson over and over.

1. State the decision, not the analysis

Lead with your conclusion. The detail is there if anyone wants it, but don't make people sit through all of it to find your point. A level down, the habit was to build the case first and land the recommendation at the end. In a senior seat, the room already assumes you did the work. They're waiting to hear what you actually think.

I watched this play out with someone on my team. They were proposing a fix to an implementation, and they did almost everything right. They gave the background, framed the challenge, walked through real data that supported the fix. And then they closed with, "any questions?" They never actually said, "this is my recommendation." They left the fix to speak for itself. In a room with that many people, leaving it to speak for itself is like asking the table what they want for lunch. You get opinions, not a decision. I stepped in before the questions started, because they were on my team and it was mine to do, and I said it plainly: here's the problem, and here's the fix we're recommending. Same data, same person, same work. The only thing that changed was that the judgment was finally visible.

2. Name the risk you considered, briefly

One sentence is enough. Something like, "I weighed this against that, and here's where I landed." It shows you saw the downside without turning the downside into the headline. You signal judgment without signalling doubt.

3. Hold the position until there's a real reason to move

There's a real difference between caving under social pressure and changing your mind because new information showed up. The first one quietly costs you authority. The second one is just good thinking. So when someone pushes back, the only question worth asking yourself is whether they've actually given you something new, or whether they're simply pushing. People remember who held a position, and they remember who folded.

4. Close clearly, then stop

"That's my recommendation. Happy to walk through the detail." Then stop talking. Almost everything you add after the close chips away at it. The instinct to add one more qualifier, to head off an objection nobody has raised, to soften the landing, all of it reads as uncertainty. Say the thing, and let it sit.

The Hidden Cost of Waiting

Waiting has a price, and you can actually put a number on it. A single delayed promotion cycle in financial services is, conservatively, somewhere north of $450,000 in lost compensation, before you even count the knock-on effect on everything that comes after it.

I know the cost of waiting because I've paid it. At one point I built a data model for the way my team ran its core function. I pitched it to a senior managing director and he was on board, but the build took far longer than it should have, mostly because I was trying to do it on top of a full day job and barely had the bandwidth for it. The concept was strong. It genuinely had the bones to save the team an enormous amount of time. My mistake was waiting for the right moment to hand over a finished, polished version. What I should have done was put together a rough working version early, used it to build enough belief in the idea, and let that get me the resources to do it properly. I waited for perfect, and perfect turned out to be the expensive option.

The VPs I work with who have stalled aren't short on ability. Not even close. What they were missing was one person willing to name the pattern clearly enough that they could finally do something about it.