Decision speed: why waiting costs more than being wrong?
Most companies do not fail because they made the wrong decision.
They fail because they made no decision at all.
While they waited for more data, the opportunity disappeared.
Deep dive theory
Why this matters?
Two companies see the same market opportunity.
Company A spends three months analyzing. They want to be sure. They build models. They do research. They have meetings about meetings.
Company B spends two weeks deciding. They launch something small. It is not perfect. They learn from customers. They adjust.
Three months later, Company B has a real product with real users. Company A is still finalizing their PowerPoint.
By the time Company A launches, Company B owns the market. The opportunity cost of waiting was bigger than the cost of being wrong early.
This pattern repeats everywhere. Speed beats perfection. Not because perfection is bad. Because waiting too long is worse.
But speed sounds risky. How to know when moving fast is safe?
1. Most decisions can be reversed
The fear of wrong decisions comes from treating every choice like it is permanent.
Some decisions are permanent. Selling the company. Taking investment that changes ownership. Shutting down a product with loyal customers.
But most decisions are not. Changing pricing. Trying a new marketing channel. Hiring a contractor. Updating a website. These can all be reversed if they do not work.
The cost of a wrong reversible decision is usually small. The cost of waiting months to make it is usually large.
A helpful rule: if a decision is reversible, make it in 24 hours. Save the deep analysis for decisions that cannot be undone.
Most companies treat every decision like it is permanent. This is why they move slowly.
Knowing which decisions are reversible changes how to approach them. But there is another trap: waiting for certainty that never comes.
2. Certainty never arrives
The world changes too fast. By the time all the information is available, the situation has already changed.
The goal is not 100% certainty. It is enough certainty to move forward.
70% confidence is usually enough. At 70%, make the decision. Use the time saved to execute and adjust based on real results.
Real results teach faster than more analysis. A small test with actual customers beats a month of spreadsheets.
A software company spends six weeks debating which feature to build next. They survey users. They analyze data. They discuss in meetings. Finally they decide.
A competitor asked ten customers over lunch, built a prototype in a week, and launched. By the time the first company shipped, the competitor had three months of user feedback and a better product.
The companies that win are not smarter. They are faster. They make more decisions, learn from more mistakes, and correct course more often.
Analysis paralysis is not caution. It is procrastination dressed up as responsibility.
3. Push decisions down
If every decision has to go through one person, that person becomes the bottleneck.
The team waits for approval. The approver is in meetings all day. Decisions stack up. By the time decisions get made, the context has changed. People redo work. Progress stalls.
The fix is pushing decisions to the lowest level possible.
If someone is closer to the problem, they should decide. If they have the information, they should act. The job of leadership is setting the direction, not approving every step along the way.
A 50-person call center gives frontline agents authority to refund up to $100 without asking a manager. Customer complaints drop 30% in three months. The cost in refunds is far less than the cost of angry customers waiting for approvals.
This requires trust. Sometimes people will be wrong. But the speed gained from distributed decision-making is worth occasional mistakes.
A company where only the CEO decides is a company that moves at the CEO's pace. That is too slow.
4. When speed is the wrong choice
Fast decisions work in most situations. But not all.
Permanent decisions need more time. Anything with legal or financial consequences that cannot be undone. Major partnerships. Large investments. These deserve careful analysis.
High-emotion moments are dangerous. Decisions made in anger or fear are usually bad. Pausing until emotions settle is wise. Speed applies to routine decisions, not crisis reactions made in panic.
Some industries require slow. Regulated industries. Healthcare. Finance. Where mistakes have legal consequences. Caution is part of the job there.
And if the team is already overwhelmed, faster decisions just create more chaos. Sometimes the right choice is deciding less, not deciding faster.
Think
What would you do in these scenarios?
Simulator
The feature debate
Your product team has been debating between two features for three weeks. Feature A improves onboarding for new users. Feature B adds reporting for existing users. Both have strong arguments. Your head of product says: we need two more weeks of user research before deciding. Your engineering lead says: we are losing momentum — pick one now so we can start building. You estimate you are about 65% confident that Feature A is right. What do you do?
Practice
Test yourself and review key terms
Knowledge check
What is the difference between a Type 1 and a Type 2 decision?
Concepts
Click to reveal
Do
Your action steps for today
Action plan: what to do today
- Clear the backlog:Look at pending decisions. Which ones are reversible? Make those today.
- Delegate one decision:Find a decision the team is waiting on from leadership. Could they have made it themselves? If yes, let them next time.
- Set the rule:Reversible decisions get 24 hours maximum. Try it for one week and see what changes.
Some examples and details may be simplified to better convey the core idea. Every business is different — adapt these ideas to your specific context and situation.