What Over How

The kickoff is the best meeting of the quarter. The boss says it's time to modernize the platform, and every head in the room nods. The deck says so, the budget is approved, and the meeting ends early because there's nothing left to argue about.

The infrastructure lead is nodding because modernize obviously means stability: fewer moving parts, boring technology, nothing that pages anyone at 2am. The product lead is nodding because modernize obviously means speed: more integrations, faster releases, yes to the roadmap. The CFO is nodding at a smaller cloud bill. One word, three projects, and nobody in the room knows it yet.

Month four is when the projects finally collide. Nobody has failed on the how. Everyone's been executing well, and that's the problem. Every week of good execution carried them further apart, and the word "modernize" covered the distance until it couldn't.

This isn't a software problem. Swap the platform for a rebrand, a second location, or a hiring push, and the scene plays out the same way: the word changes, the collision doesn't. The failure happened back in that first meeting, at the moment everyone agreed on a sentence and stopped checking what it meant.

Competence doesn't correct a misaligned what. It scales it.

Why the what gets skipped

A how can be assigned, estimated, and demoed by Friday. A what is a conversation with nothing to show at the end, and it carries a risk the how never does: it can surface that two people in the room want different outcomes, and one of them is going to lose that argument. So the room stays agreeable, the hard conversation gets postponed, and the bill arrives in month four with interest.

There's an honest exception. Sometimes you find the what by building, because a rough version you can react to beats a spec you can't. I prototype constantly. That's fine as long as you know which one you're doing. The trap is committing to a how while believing you have a shared what.

Why this matters more right now

None of this is new, and none of it is about AI. I put a name on this principle back in 2018, after years of chewing on it. The principle hasn't changed. The stakes have.

I wrote in Wielding the New Fire that AI is the first new primitive on the scale of fire. Everything I said there was about the how. AI collapses the loop between having an idea and finding out whether it holds. It hands back the attention you were spending on mechanics. That makes it a multiplier, and a multiplier pointed at an unaligned what doesn't buy you a smaller failure sooner. It buys you a bigger one.

Picture two hikers leaving the same trailhead together, each quietly bound for a different peak. For the first several hours the trail is the same trail, so nothing looks wrong.

Now hand them each a helicopter.

Every team I talk to is getting faster right now. Very few of them have gotten more aligned. The distance between those two rates is where the next several years of expensive mistakes are going to come from.

What this looks like in a room

"Develop a what over how mentality" is the kind of advice that sounds good and changes nothing. So here's the actual practice.

Make people write it down separately. Before anyone estimates anything, have two or three people describe what success looks like, on their own, in specifics, in a paragraph. Then read them out loud. They almost never match. The half hour that costs you is the cheapest half hour in the project.

Ask what you're willing to give up for it. A goal that costs nothing isn't a what, it's a preference. The tradeoff is where the real objective is hiding, and people who claim the same goal will often refuse very different prices for it.

Name what's explicitly out of scope. Disagreement about exclusions is much easier to detect than disagreement about goals, because exclusions are concrete and goals are aspirational. Nobody argues with "make it great." Plenty of people will argue with "so we're not doing that."

That last one is the entire reason we could turn down auto-apply on Exec Foundry. We knew what we were protecting, so a feature everyone asks for and that demos beautifully was an easy no. Without the what, that's an agonizing decision. With it, it took about five minutes. I wrote about that one here.

None of this is a process, and I'd be suspicious of anyone who tried to sell it to you as one. It's a habit of insisting on the destination before arguing about the route, and being willing to stay in an uncomfortable conversation long enough to discover that you didn't actually agree.

Catalyst Forge is named after this. The forging is real work and it's the part I enjoy most. But the word carrying the argument was never "forge."

Find what matters. Then forge it.