The project was a new digital service for a traditional industrial company. The team had spent four months developing it. Customer validation was strong — fifteen interviews showing genuine demand, three pilot customers ready to start, and a clear path to profitability within eighteen months. By any rational measure, the project deserved to proceed.
The board meeting was scheduled for thirty minutes. It lasted twelve. In those twelve minutes, a board member — who had not been involved in the development process, had not read the customer research, and had not met any of the pilot customers — raised “concerns about brand dilution” and suggested “parking the initiative until the core business stabilizes.” Two other board members nodded. The CEO, who had been supportive privately, read the room and agreed to “revisit in Q3.”
Q3 revisiting never happened. The team disbanded. The pilot customers went to a competitor. The digital service was eventually launched two years later by a different team at three times the cost, entering a market that was now crowded instead of open.
I watched this happen from my role as external innovation advisor, and it was one of the most frustrating experiences of my career. Not because the board was wrong to be cautious — caution has its place. Because the decision wasn’t made rationally. It was made politically. And the cost of that political decision — in lost revenue, lost time, and lost team morale — was enormous.
How Good Ideas Die in Organizations
That board meeting wasn’t an anomaly. I’ve seen variations of it dozens of times across my consulting career. The pattern is consistent enough to describe systematically.
Phase 1: Grassroots enthusiasm. A team identifies an opportunity, develops a concept, and builds internal momentum. The work is genuine, the data is strong, and the team is energized.
Phase 2: Mid-level support. A manager or director sponsors the project, provides resources, and shields the team from interference. Progress is fast because the team has autonomy and clear direction.
Phase 3: Executive exposure. The project reaches a point where it needs senior-level approval — budget, strategic alignment, public commitment. This is where most good ideas die.
Phase 4: The kill. An executive who hasn’t been involved raises objections that sound strategic but are often personal (protecting turf, avoiding risk to their reputation, or simply not understanding the opportunity). The objections are vague enough to be unanswerable (“brand dilution,” “market timing,” “strategic fit”) and carry enough authority to kill or delay the project.
The structural problem is this: the people closest to the customer (the team) have the least organizational power. The people with the most organizational power (the board) are furthest from the customer. Decisions that should be based on customer insight are instead based on organizational politics.
This pattern is why I eventually developed the Subtraction Audit as an approach to innovation — it’s structured to produce data-driven decisions rather than politically-driven ones. When the decision criteria are explicit and the data is transparent, it’s harder for a single objection to override months of validated work.
What the Board Member Was Actually Worried About
After the meeting, I had a private conversation with the board member who’d raised the “brand dilution” concern. In a more honest setting, his real concerns emerged:
- He didn’t understand the digital service well enough to evaluate it, and asking questions in the board meeting would have revealed his ignorance.
- The project’s success would have validated a business direction that reduced the importance of his division.
- He had been burned by a failed innovation project five years earlier and was risk-averse about anything that looked new.
None of these were mentioned in the board meeting. Instead, they were disguised as strategic concerns that sounded reasonable. “Brand dilution” is hard to argue with because it’s hard to define. The vagueness is the weapon.
Understanding this dynamic changed how I prepare innovation projects for executive review. The explicit objections are rarely the real objections. The real objections are personal, political, and often reasonable — but they need to be addressed privately, before the formal decision meeting, not in the meeting itself.
The Pre-Meeting That Should Have Happened
If I could rewind and manage that board meeting differently, here’s what I’d do:
Two weeks before the meeting: Meet individually with every board member. Not to pitch — to listen. Ask: “What would you need to see to feel comfortable with this project proceeding?” Their answers would reveal the real concerns, which I could then address in the formal presentation.
One week before: Send a one-page summary (not a fifty-page deck) covering: the opportunity, the evidence, the risk, the investment required, and the decision being requested. Give board members time to process privately, where admitting ignorance or concern doesn’t carry social cost.
At the meeting: Present the project as answering the concerns raised in private meetings, not as a new pitch. “Board member X asked about brand risk — here’s how we’ve addressed it.” “Board member Y wanted to see customer validation data — here are the fifteen interviews.”
After the meeting: Regardless of outcome, send a follow-up documenting the decision and next steps. Verbal decisions in board rooms are easily reinterpreted later.
This pre-meeting approach has worked in every subsequent enterprise innovation project I’ve managed. The formal meeting becomes a ratification of decisions already made informally, not a debate that ambushes the team.
What This Taught Me About Enterprise Innovation
That board meeting taught me three things about innovation in large organizations:
Politics is a variable, not a constant. You can’t eliminate organizational politics, but you can manage them. Pre-meetings, stakeholder mapping, and understanding personal motivations are as important as customer research and financial modeling. Ignoring politics doesn’t make you above it — it makes you vulnerable to it.
Specificity defeats vagueness. Vague objections (“brand dilution,” “market timing”) are hard to counter because they’re unfalsifiable. Specific evidence (“fifteen customer interviews showing demand,” “three pilot customers committed to paying”) is hard to dismiss because it’s concrete. When presenting to executives, be so specific that vague objections have no room to land.
Executive buy-in must happen before the meeting. The board meeting is not where you convince people. It’s where you formalize what they’ve already been convinced of. If you walk into a board meeting needing to persuade someone, you’ve already lost.
These lessons apply beyond enterprise. Any situation where someone with authority can kill your project — an investor, a partner, a key client — benefits from the same approach: understand their real concerns privately, address those concerns proactively, and use the formal meeting to confirm rather than convince.
The 5-Conversation Sprint validates with customers. The pre-meeting approach validates with decision-makers. Both are essential. Neither is sufficient alone.
The Broader Lesson: Build Where the Walls Are Low
That experience influenced my eventual choice to build businesses outside the corporate structure. Solo ventures and small partnerships have a specific advantage over corporate innovation: no board meetings.
When Adam and I decided to launch a Vulpine product, the decision took about ten minutes. We had customer signal, we had a prototype, and we had the capacity. That’s it. No presentation. No approval chain. No vague objections from people who hadn’t been involved.
This speed advantage — the ability to make good decisions quickly — is one of the most valuable things about being a small operator. You can move at velocity because nobody’s standing between your data and your action.
If you’re inside a corporate structure and feeling frustrated by slow decision-making, know that the frustration is valid. The corporate structure exists for reasons (governance, risk management, stakeholder alignment), but those reasons often produce a side effect: killing good ideas through process rather than merit.
You can work within the system by mastering the pre-meeting approach. Or you can build outside the system where the walls are lower. Both are legitimate choices. Just make them deliberately.
Key takeaways:
- Meet individually with every decision-maker before the formal meeting — discover real concerns privately where admitting ignorance doesn’t carry social cost.
- Present specific, concrete evidence that addresses each stakeholder’s private concerns — specificity defeats the vague objections that kill good ideas.
- Use the formal meeting to ratify decisions, not to persuade — if you need to convince someone in the meeting, you’ve already lost.
- Understand that the explicit objection is rarely the real objection — “brand dilution” often means “I don’t understand this” or “this threatens my division.”
- Small businesses have a structural advantage in decision speed — the ability to move from data to action without approval chains is genuinely valuable.
