Introduction
One of the most underrated startup decisions is deciding not to act yet.
Founders are rewarded for action. That creates a bias. Many teams build, hire, migrate or redesign simply because standing still feels uncomfortable. Sometimes waiting is the better decision.
This framework helps you decide when the right move is to act, when the right move is to wait, and how to wait deliberately rather than accidentally.
What it solves
What deliberate inaction delivers
-
Cheaper decisions later
Information arrives over time. Decisions made next month with better data are usually better than decisions made this month with assumptions.
-
Lower compounding cost
Every action creates downstream commitments, hosting, support, maintenance, hires, expectations. Waiting avoids the compound interest on a wrong move.
-
Capacity for the right move
A team busy with the wrong action cannot pick up the right one when it appears. Deliberate inaction preserves the option value of the team.
-
Clarity through observation
Sometimes the right answer reveals itself when you stop pushing. Customers stay or churn, competitors move or stall, markets shift, and the shape of the decision becomes obvious.
-
Calmer judgement
Action-bias is exhausting. Teams that act constantly tend to make worse calls than teams that act decisively but selectively. Pace is part of strategy.
What it does not solve
What waiting will not fix
-
An urgent customer problem
Some problems compound dangerously: an outage, a security incident, a regulatory deadline, a churn spike. Waiting on those is not strategy; it is denial.
-
An obvious next step
When the path is clear and the cost of waiting is high, deferring action becomes its own mistake. Waiting works when the answer is unclear, not when it is uncomfortable.
-
A team that wants to move
Telling a healthy team to wait without explanation drains energy. Deliberate inaction works only when the reason is understood and shared.
-
Investor or board pressure
External pressure is real and sometimes useful, but it should not produce action for its own sake. Waiting against pressure is harder than waiting in silence, and often the right call.
-
Founder anxiety
Waiting because action is scary is not the same as waiting because action is wrong. Recognising the difference is most of the discipline.
Decision tree
Six questions before you act
Run the proposed action through these questions. The 'yes' answers will tell you whether to move now or hold.
- Question 01
What changes if we wait 30 days?
No → If nothing material changes, the action is not urgent. Use the 30 days to sharpen the move.Yes → Name what changes specifically, pricing, a customer, a regulatory date, competitor movement. Vague urgency is not urgency. - Question 02
What new information will become available?
No → If no new information will arrive, waiting buys nothing. Either act or change the question.Yes → Confirm the information will arrive on a known timeline. Open-ended waiting is drift in a disguise. - Question 03
What is the cost of waiting?
No → Quantify it. 'Probably costs us something' is not a cost, it is a feeling.Yes → Confirm the cost is concrete and recurring. One-time costs of waiting are usually smaller than they feel. - Question 04
What is the cost of acting?
No → Quantify it the same way. Most actions cost more than they appear to once downstream commitments are included.Yes → Compare the two costs honestly. Acting is only correct when the cost of waiting is meaningfully higher. - Question 05
Can customer feedback answer this?
No → Treat it as an internal call. Some decisions cannot be customer-validated and must be made on judgment.Yes → Wait for the feedback. A decision answered by customers is cheaper and more durable than one answered by debate. - Question 06
Are we solving a real problem or reducing anxiety?
No → If the action exists primarily to reduce founder anxiety, the cost is paid by the company. Wait, write down the anxiety, and revisit when calmer.Yes → Confirm the problem is named, owned and durable. Real problems persist across weeks; anxiety problems often dissolve.
Common mistakes
Five common mistakes founders make
- 01
Acting too early
Many founder regrets come from acting on incomplete information. The cost of an early wrong move usually exceeds the cost of a slightly delayed right one. Bias toward more information unless the cost of waiting is genuinely high.
- 02
Building before learning
Build cycles are slow; learning cycles are fast. Building before learning fixes assumptions into code. Learn, through customer conversations, prototypes, or just waiting and watching, before committing engineering time to the answer.
- 03
Hiring before clarity
Hiring is one of the hardest commitments to reverse. Hiring under unclear scope produces unclear results. Sharpen the scope first; the right hire becomes obvious once the work is.
- 04
Rebuilding before evidence
Rebuilds proposed without evidence of business impact are almost always emotional. Wait until the evidence is real, and the rebuild scope will narrow naturally.
- 05
Optimising before demand
Optimisation work assumes the thing being optimised will exist at scale. Without demand, the optimisation is decoration. Build the demand first; optimise what survives.
Alternatives
Patterns for deliberate inaction
Four patterns that make 'wait' an active choice rather than a passive one.
-
The 30-day hold
Write down the decision, set a date 30 days out, and revisit. Most decisions either resolve themselves, sharpen meaningfully, or reveal themselves as smaller than they felt. Cheap, fast, and often saves a quarter of misdirected work.
-
The decision journal
Record the decision, the options considered and the reasoning at the moment of choice. When the situation returns, the journal beats memory by a wide margin, and quickly shows whether the team is repeating decisions or learning from them.
-
Observation phase
Some decisions need data the team does not yet have. A formal observation phase, three to six weeks of watching usage, talking to customers, monitoring competitors, usually produces a sharper answer than three to six weeks of action.
-
The reversible default
When in doubt, choose the action that can be undone in a week. Reversible defaults let you start moving without committing the company. Action without optionality is the trap; reversible action is not.
Ronald's rule of thumb
Doing nothing is a decision. Make sure it is a deliberate one.
There is a difference between waiting because the situation rewards it and waiting because action feels uncomfortable. The first is strategy; the second is drift. Write down which one you are doing, and revisit on a date. Inaction without intent is the most expensive form of work a startup can do.
, Ronald · YourStartup.Expert
Summary
Summary
Action-bias is wired into startups. It is also the source of many of their most expensive mistakes. The six questions above turn 'should we act?' into a decision the team can examine: what changes, what arrives, what it costs, what acting costs, whether customers can answer, and whether the action is real or anxious.
Sometimes the right answer is to move. Sometimes it is to wait, deliberately, on a timeline, with a name and a date. Both choices are work. Doing the second well is one of the most underrated startup skills, and one of the cheapest sources of leverage when practised honestly.
Common questions
Choosing not to act, answered.
The questions founders ask when waiting feels uncomfortable.
- When is doing nothing the right decision?
- When new information will arrive soon, when the cost of waiting is lower than the cost of acting, when customers can answer the question for you, or when the action being considered exists primarily to reduce founder anxiety rather than to solve a real problem. Doing nothing is a deliberate choice, not the same as procrastination, and works best when paired with a written decision, a revisit date and an honest reason.
- How do I know if I am procrastinating or waiting strategically?
- Strategic waiting has a name, a reason and a deadline. Procrastination has none of the three. If you cannot write down what you are waiting for, when you will revisit, and what would trigger an earlier decision, you are probably procrastinating. The fix is not to act; it is to write down those three pieces and turn the wait into a decision.
- Is doing nothing always cheaper than acting?
- No. Some actions compound dangerously when deferred: outages, security incidents, regulatory deadlines, churn signals. The framework is to compare the cost of waiting against the cost of acting honestly. When the cost of waiting is concrete and recurring, action is the answer. When the cost is vague or feelings-based, waiting is usually cheaper than it seems.
- How do I justify waiting to investors or my team?
- Write the decision down: the question, the options, the reason for waiting, the information you expect to arrive, and the date you will revisit. Strategic waiting that is written and shared lands as discipline; unspoken waiting lands as drift. The difference is whether the team can see the shape of the decision, and the act of writing it tightens the thinking on your side as well.
- What is the most underrated startup skill?
- The discipline to not act when not acting is the right move. Founders are trained to ship, hire, build and move; almost nobody is trained to wait deliberately. Yet the teams that survive longest tend to be the ones that act decisively when the path is clear and wait carefully when it is not. Both halves are skill; the second half is the one most teams underdevelop.