Innovation Governance: Why Early Decisions Beat Perfect Data
Smart captains don't stare at the deck — they watch the horizon.
By Tristan Kromer · · 5 min read Quick Answer: Good innovation governance means deciding early, not waiting for perfect information. Earlier pivots are dramatically cheaper because projects accumulate dependencies, sunk costs, and organizational inertia that make late course corrections expensive or even impossible. As product managers, we should act the moment data reveals a fundamental flaw — additional information beyond that point is worthless. Slow down to run more experiments when facing uncertainty, but make courageous pivot-or-kill decisions quickly rather than trading control over outcomes for data we can’t effectively use.
Decide early. Delaying decisions destroys value. It seems natural to defer a decision until you have the maximum amount of information possible, but that’s rarely the optimal path. Imagine we have an option to persevere, pivot, or kill a project after one year of development, or make the decision early after only three months. In both cases, we’re going to run a lot of experiments on customer desirability, technological feasibility, and business viability. But we only have the option to make one decision. Should we decide earlier or later? Imagine we are sailing a boat and see something in the distance. It could be a rock, it could be a turtle, it could be seaweed. It’s unclear at this point. Do you wait until the last minute to change course or do it now?
Control
Of course we could wait until the last minute. We could wait until we have the maximum amount of information and are very close to the obstacle. It could turn out to be nothing, so we can just keep sailing straight. But if the obstacle is quite large, we might have to put a lot of effort into a last-minute course correction. If we change our trajectory by making a small course correction early, it requires little effort to bypass even a very large obstacle. 
Dependencies
Part of the reason for this is that innovation projects have many dependencies. If we start optimizing a marketing channel with the wrong customer segment, then our business model will never work. If we have narrow margins and haven’t figured out our growth engine, then the business model may be unviable. If there’s data that says there is no market for a potential product, gathering additional information on how to optimize the per-unit manufacturing costs doesn’t help. We should stop. The moment we have information that tells us a business model is fundamentally flawed, we should make a quick decision to stop or pivot. Additional information is worthless. 
If we do get information that we need to pivot because the consumer needs a different set of features, then obviously that will be much cheaper to do before we build a product. By going after our critical assumptions first, we radically reduce the costs of pivots.
Inertia
There is also organizational inertia that makes pivoting not just expensive, but sometimes impossible. If our product and business model is the sailboat we are trying to pivot, the boat actually gets less agile as we sail. More and more people are boarding with supplies, additional rigging, and anchors. As we start spending CapEx, getting consultants involved, and getting stakeholders excited, it becomes harder and harder to pivot on short notice. This is the sunk-cost fallacy writ large.
Slow Down
We should probably do more than pivot if there’s something in our path. Instead of just barrelling ahead at full speed, we should slow down to assess the situation. 
In the case of a startup, this means run more tests! Yes, it slows down product development, but if it’s a risky situation with many unknown variables, you have to go slow to go fast.
Trade-offs
Delaying a decision because of analysis paralysis or because we do not have the courage to shut down a poorly performing project is a bad trade-off. Delaying a decision trades control over our destiny for information that we can’t effectively use. Fortunately, we don’t just have a single opportunity to pivot, persevere, or kill. We have many. So we can optimize our process by making these decisions as quickly as possible. Just like sailing a boat, you are the captain of your startup. Smart captains don’t just stare at the deck beneath their feet — they are always looking towards the horizon.
Lessons Learned
- Earlier pivots are cheaper pivots.
- Go slow to go fast.
- Make courageous decisions early.
Need to evaluate risks on the horizon?
Download our Risk Mapping Template
Frequently Asked Questions
Why is it better to make early decisions in innovation governance even with incomplete information?
Earlier decisions give us more control over outcomes while requiring less effort to course-correct. As product managers, we know that delaying a decision trades control for information we often can’t effectively use. When we identify a fundamental flaw early, additional data gathering becomes worthless — the moment we know a business model is broken, we should pivot or kill the project immediately.
How do dependencies make early pivots cheaper than late ones?
Innovation projects have cascading dependencies — if we’re optimizing a marketing channel for the wrong customer segment, everything downstream fails. By targeting our most critical assumptions first, we radically reduce the cost of pivots. Changing direction before we build a product is dramatically cheaper than after, because later changes ripple through manufacturing, marketing, and business model decisions that are already locked in.
What is organizational inertia and how does it affect innovation projects?
Organizational inertia is the growing resistance to change as a project progresses. As we spend CapEx, involve consultants, and get stakeholders excited, pivoting becomes harder and sometimes impossible. This is the sunk-cost fallacy at scale — our “sailboat” gets heavier with more people, supplies, and anchors on board, making it far less agile when we need to change course.
Should we slow down product development to run more experiments?
Yes — we should slow down to go fast. When we face a risky situation with many unknown variables, running more tests before charging ahead is the smart move. It may delay product development in the short term, but it prevents costly late-stage pivots or outright failures. Good innovation governance means having the discipline to assess the situation rather than barreling toward an obstacle at full speed.
How do you avoid analysis paralysis when deciding to pivot, persevere, or kill a project?
We don’t have just one opportunity to decide — we have many. So we should optimize by making each pivot-persevere-kill decision as quickly as possible rather than agonizing over any single one. Delaying because we lack courage to shut down a poorly performing project is a bad trade-off. As product managers, we need to be like smart captains: always scanning the horizon, not staring at the deck beneath our feet.
Comments
Loading comments…
Leave a comment