Why Your Best HR Business Case Still Gets a No (and the Framework That Fixes It)

A CEO once told me, flat out, “We don’t need that kind of thing.” I had asked for bonuses for a delivery team that had never had any upside. Not a soft no. A door-closed no.

I could have told myself the CEO just didn’t get it. A lot of executives tell themselves exactly that when a project gets shot down: the pitch was the problem, or the decision-maker was never going to be won over, and they walk away a little more cynical about the whole exercise. That’s not what happened here. What happened is I hadn’t done my due diligence, not on the business case, on the person deciding it.

Why does a well-researched HR proposal still get rejected?

Usually because the case was built in HR’s language instead of the decision-maker’s, and nobody stopped to find out what that language actually was.

It’s easy to take it for granted that because you work inside the company, you already understand how decisions there actually get made. Often you don’t. You know the org chart. You don’t necessarily know the person’s real decision criteria, what they think is unique about your ask, why timing matters to them, what they think you’re competing against, how they expect it to get funded, who really has to say yes, or how badly they actually feel the need.

Skip any one of those and you can have the best-built proposal in the company and still walk out with nothing.

This isn’t rare. SHRM has found that up to two years after rollout, 42% of HR staff said their initiative had either failed or hadn’t been fully successful, and lack of senior leadership buy-in is one of the most cited reasons why. A great idea and a rejected idea can be the exact same idea. The difference is usually whether someone worked out what the decision-maker was actually deciding on.

What is the DUTCHMAN framework for getting a project approved?

DUTCHMAN is an eight-question checklist for figuring out whether you’re actually ready to pitch, before you walk into the room. I learned it years ago in professional services and executive search, and I still use it today, for internal proposals as much as external ones.

D - Decision criteria. 

What factors actually drive the final call? If you can’t answer that with confidence, go back and ask before you pitch.

U - Unique value.

Can the decision-maker articulate why this is genuinely different from doing nothing, or from handling it themselves without your function?

T - Timing.

Is there real urgency tied to this, a promotion, a deadline, a board date, or can it comfortably wait?

H - How.

How will this actually get delivered? That’s part of your solution, not an afterthought.

M - Money.

Whose budget is this coming from? Does it need a new line, or can it be funded from something that already exists?

A - Authority.

Who actually has to sign off? It isn’t always the name at the top of the org chart.

N - Need.

How desperately does the decision-maker feel this, versus how desperately you feel it?

I’m intentionally listing Competition separately below, because it’s the one people misjudge most inside a company.

C - Competition.

Internally, competition is rarely another vendor. It’s usually the status quo, doing nothing, or another initiative already fighting for the same budget or attention.

If you can answer all eight with real confidence, you already know your odds before you ever present.

How do you find out what actually drives a CEO’s decision before you pitch? You go looking for it directly, and you build the case in their terms, not yours.

Here’s how that played out with the delivery team bonus. This CEO had come up as a CFO before running the company, so every real decision in their head ran through the P&L. My first pitch made the people case: fairness, retention risk, market competitiveness. All true. None of it in their language. I was answering a test they weren’t grading.

The second time, I ran the ask through DUTCHMAN properly.

Decision criteria was financial, full stop, because of their background. Unique value wasn’t about whether a delivery bonus was rare in the market. It wasn’t. Plenty of firms have one. But this person had never worked anywhere that offered it, so in their mind, it was a genuinely differentiated thing we could offer as an employer. What’s unique in the market and what’s unique to the person deciding are two different questions, and I only needed to win the second one.

On timing, we were already deep into Q4. I wasn’t asking them to touch that year’s numbers. I told them we’d build it into next year’s plan, which took “not now” off the table before they could reach for it.

Competition was the real blocker. In their head, this wasn’t competing against doing nothing, it was competing against the sales team. They believed upside belonged to salespeople, full stop, and giving the delivery team a bonus meant taking something away from the people who “actually brought in the revenue.” Until I broke that zero-sum read, nothing else I said was going to land.

How is where it turned. I named the real cost problem: we were overpaying base salary because we had no bonus lever, and that was inflating the cost of delivery. What if we funded the bonus by tying it to hitting or beating our gross margin target?

That answered money on its own. No new budget line, no pulling from another team’s pool. If we hit 40% gross margin, or beat it, there were dollars to divide. If we didn’t, there weren’t. Somewhere in that conversation I asked directly: if we hit the number, do you really care how we divvy up the money?

For authority, this person was the only signature that mattered, so the sharpest thing I said wasn’t a numbers argument at all. We call ourselves a meritocracy, and yet we don’t pay our delivery team for performance. How does that work? I wasn’t asking them to adopt a new value. I was asking them to be consistent with the one they already claimed.

And need. Going in, they didn’t feel one. I did. We had real turnover on the delivery side, and I made that visible instead of assuming they’d connect the dots on their own.

Same ask, same person, same company. Completely different outcome, because the second time I wasn’t more persuasive. I’d just finally answered the eight questions I hadn’t answered the first time.

What do you do when a CEO already said no?

Don’t rewrite the pitch. Rerun the diligence, then rewrite the pitch.

A first no is information, not a verdict. It tells you which of the eight DUTCHMAN questions you skipped. Go back through them one at a time and be honest about which ones you actually have real answers to, not the ones you assumed. In the story above, the miss wasn’t the idea. It was that the case was built around fairness and retention when the actual decision criteria was financial, and around fixing a people problem when the actual objection was a competition problem with the sales team. Once both of those were corrected, the rest of the pitch barely had to change.

This is also why the same idea, pitched twice to the same person, can get a no and then a yes. Nothing about the merit of the idea changed. What changed was whether the case matched how that specific person actually decides.

Is this a tactical problem or a strategic one?

 Neither, mostly. It’s a discovery problem.

HR often gets read as tactical instead of strategic, but that’s usually the wrong diagnosis. It’s rarely the thinking that holds a proposal back. It’s that the case gets built in HR’s language instead of the decision-maker’s, because nobody stopped to discover what that language actually is. The CHROs who get funded aren’t the ones with the best slides. They’re the ones who did the homework on how their specific executive actually decides, before they ever asked for the yes.

A few quick answers

Is DUTCHMAN only useful for big proposals?

No. It works for a leadership development program, a comp change, a headcount ask, or a candidate offer. Anywhere you need someone else to say yes, the same eight questions apply.

What if I genuinely don’t know the answer to one of the eight questions?

That’s the point of running the checklist before you pitch, not after you get rejected. If you can’t answer one with confidence, go find out. Ask the decision-maker directly, or someone close to them, rather than guessing.

Does this only work on financially minded executives?

No. The specific lever changes person to person, financial for a former CFO, risk for a former operator, market position for a former salesperson, but the method is the same: find their actual decision criteria before you build the case.

Run your own project through it!

 Before your next pitch, whether it’s a leadership development program, a talent management initiative, or a comp structure nobody wants to touch, run it through the same eight questions. What actually drives their yes. What makes this genuinely different from doing nothing. Why now instead of later. What are you really competing against in their head. How will it get delivered. Whose budget, and does it need a new one. Who really signs off, even when it’s not the obvious name on the org chart. And how badly do they feel the need, versus how badly you feel it.

If you can’t answer one of those with confidence, you don’t have a pitch problem. You have a diligence problem, and no amount of polish on the deck fixes that.

This is exactly the kind of thing we work through at The Big CHRO Event, our flagship gathering of 100+ sitting CHROs in Dallas each September, and in the CHRO Mastermind Groups that run year-round. If you’re a sitting CHRO and want a room of peers to pressure-test your next pitch before you take it upstairs, reach out and I’ll get you the details.