The Year I Spent Saying No to Good Ideas

Cox sent me to a retreat in Atlanta. The theme was hyper-competition — the idea, popular since Richard D'Aveni's book a decade earlier, that competitive advantage had become temporary and companies had to keep maneuvering to hold position.

The framing in the room was that this was a condition to get through. A storm. Batten down, adapt, come out the other side.

I put my hand up and said I didn't think there was another side.

My argument was simple: this wasn't weather, it was climate. New technology and new players were going to keep arriving, and each wave would be faster than the last. There was no after. This was just what business looked like now, permanently.

I'd like to report that the room was persuaded. It was not, particularly.

Look at what happened to cable. The internet and software didn't disrupt that industry once and let it settle — they rewrote it, and then kept rewriting it. Nobody in that industry has had a quiet decade since. I don't say that to take a victory lap twenty years late. I say it because the point has a practical consequence that shaped everything I did afterward.

If competition never lets up, capital gets more expensive to justify. Every dollar has more claims on it and a higher bar to clear. Which brings me to the actual job.

What an 18% hurdle rate does to a company

At Cox I was Director of Finance, and for about six months I also carried the VP of Operations role. A lot of that work came down to one question: does this project clear the bar?

The bar was a hurdle rate above 18%. In plain terms: if a project couldn't demonstrate a return north of eighteen percent, the company didn't spend the money. Not because anyone was being stingy. Because capital was finite, the competitive environment was tightening, and a dollar tied up in a project returning twelve percent was a dollar not available for one returning twenty-two.

I worked with our local teams to build and present the cases. Build-outs across the Las Vegas area, including the large properties — MGM Grand, The Wynn. Cell tower projects with Verizon, T-Mobile and the others. Real capital, real construction, real timelines.

Some cleared. Plenty didn't.

What that seat actually teaches you

Here's the thing nobody warns you about: you don't spend your days rejecting bad ideas. Bad ideas are easy and they're rare at that level. You spend your days saying no to good ideas.

Ideas from people who knew their market, who could describe the opportunity vividly, who were right that something was there. They just couldn't show a return that cleared the bar — or, more often, they hadn't been given the help to try.

And the projects that survived weren't the most exciting ones in the pile. They were the ones where somebody had done the arithmetic properly. Where the assumptions were visible and defensible. Where you could push on a number and it held.

That is an uncomfortable thing to learn, because it means the quality of an idea and the quality of its case are two different variables, and only one of them gets you funded.

Why I won't hand you a recommendation without the numbers

This is the seat I was sitting in when consultants brought us recommendations.

I've written elsewhere about a six-week engagement that came back with a capital recommendation and no cost-benefit analysis I ever saw. I don't think those people were careless. I think they genuinely believed the case was self-evident from the story they told — and the story was convincing.

But convincing isn't the currency. The currency is a number that survives being poked at in a room where six other projects want the same money.

So when I hand someone a recommendation now, the arithmetic comes with it. What it costs. What it returns. Over what period. What happens if the assumptions are twenty percent worse than expected. Not because it's rigorous for its own sake, but because I've been the person who has to take it into that room, and I know exactly which question kills it.

The bar didn't move. The cost of clearing it did.

Here's something I think about often now.

A lot of the projects I watched fail that hurdle test would pass it today.

Not because anyone lowered standards. Because the expensive half of those business cases was almost always technology — a system, an integration, a vendor, a year of implementation, a team to run it. That's what pushed the payback out past the point where it could clear.

A meaningful share of that work now costs a fraction of what it did and takes weeks rather than quarters. Same benefit on the other side of the equation, much smaller number underneath it, and suddenly the arithmetic works.

So part of what I do when I look at a business now is run exactly that comparison: which of the things you've already decided aren't worth doing were priced back when they were genuinely expensive? That list is usually longer than the owner expects, and nobody has re-run the numbers because the decision already felt settled.

The small-business version of the same thing

Most businesses I work with don't have a formal hurdle rate. But every owner has one, whether they've written it down or not.

It's the bar in their head. If this doesn't pay for itself in about a year, I'm not interested. Or: I'll spend that if it gets me two hours of my week back. It's real, it governs every decision they make, and almost nobody has said it out loud.

Which causes the same failure as the corporate version, just faster. Someone proposes a purchase or a project, the owner feels vaguely unenthusiastic, and it drifts. Not rejected — drifted. Everyone still agrees it's a good idea.

What to do with this

Two things, and neither needs a finance department.

Write down your bar. One sentence. What return, over what period, makes something worth doing here? Once it exists, decisions get dramatically faster, because you're comparing against a standard instead of against your mood that week.

Then make anyone recommending you spend money clear it. Including me. If someone tells you to invest in something and can't tell you what it returns and when, that isn't a recommendation yet. It's an observation with a price tag.

Good ideas fail that test all the time. That's not a reason to lower the bar. It's a reason to help the good ones pass it.