REALITY
BEFORE THEORY

I watched eighteen stakeholders across eight functional domains walk into a three-day e-commerce summit, every one of them correct about their own constraints and none of them seeing anyone else's.

Operations knew the distribution center couldn't handle the volume. Finance had no SKU-level margin visibility. Marketing knew their attribution data was incomplete. Technology knew the ERP migration had no clear scope. All true simultaneously. None of it had ever been placed next to the others in a single conversation.

Every previous attempt at a roadmap had failed because it started with theory. What do we want to build? Where do we want to be in three years? Those are fine questions if you already have a shared understanding of what's actually possible. They didn't. Asking people to dream before they've agreed on reality produces roadmaps that collapse the moment someone names a constraint the room wasn't ready to hear.

So I started upstream. Not with vision. With limits. What can't you do right now? What breaks if we try? Who owns this, and does everyone agree? I needed every function to stop presenting their preferred version of reality and start disclosing the version they were actually living with.

The summit worked because the first day was dedicated entirely to pressure testing. Not solving. Not planning. Just surfacing where things would break. It was explicitly acceptable to let initiatives die if the stakeholders couldn't defend them against the constraints in the room.

I didn't invent this instinct. I grew up in Clarence, Missouri, a town where honesty mattered more than polish and people worked with what they had. The newsroom reinforced it daily. You report what happened, not what you wanted to happen. You go to the scene. You talk to the people who were there. You don't write the story before you've done the reporting.

The corporate world has a strange tolerance for skipping that step. Roadmaps built on what leadership wants to be true rather than what the teams on the ground can actually execute. The map gets drawn first, then everyone is surprised when the terrain doesn't match.

Everything I've built that held up started with the terrain. Everything I've watched collapse skipped it.