In this article
There is a category of startup mistake that rarely gets named, even though it is very common.
It happens when a founder conflates the decision they are facing with the action they should take next.
These are different things. Treating them as the same is one of the most reliable ways to commit resources prematurely and end up defending a position that should already have been updated.
The difference between a decision and a move
A decision is a commitment that, once made, is expensive or impossible to reverse. Raise or don't raise. Hire a head of sales. Kill the enterprise track and go full self-serve. Enter a new market.
A move is an action taken to reduce the uncertainty surrounding a decision — before the decision is made.
The key insight is that most "next step" conversations in startups are actually decision conversations wearing the disguise of action conversations. Founders ask: what should we do? But the more useful question is almost always: what do we need to know first, and what is the smallest way to learn it?
Callout
The next move is not the decision. It is the test that makes the decision safer to make.
Why this confusion is so common
Three forces push founders toward premature commitment:
Investor pressure. "What is your plan?" requires a decision, not a test. Saying "we are running a 3-week experiment to validate whether the constraint is demand or conversion" sounds weak compared to "we are going full enterprise." The first answer is usually the right one. The second is usually what gets funded.
Team morale. Uncertainty is uncomfortable. Teams move faster when there is a committed direction, even when that commitment is not yet earned. Leaders feel pressure to appear decisive rather than exploratory.
Narrative pressure. Startups build stories about themselves. Once a story exists — "we are the infrastructure play" or "we are going direct-to-consumer" — reversing it feels like failure. This pressure starts well before the decision deserves commitment.
The result is that founders make large commitments on weak evidence, then spend disproportionate energy defending those commitments rather than updating them.
What the right next move looks like
A good next move has three properties:
-
It is bounded. There is a clear end point: a time limit, a number, an event. "We will run this for 4 weeks and look at X."
-
It is specific about what it is testing. Not "let's try ads" but "we want to know whether this segment responds to a problem-first frame or a solution-first frame."
-
It has a clear update condition. Before the test runs, you state what result would strengthen or overturn the current hypothesis. If you cannot name that condition in advance, the test is not sharp enough.
If you cannot name what result would change your mind before you run the test, the test is not a test — it is motion with extra steps.
The size calibration problem
Most founders, when asked "what is your next move?" name something roughly the same size as the decision they are facing.
Considering whether to raise a Series A? The "next move" is to build out the deck and start conversations.
Considering whether to go enterprise? The "next move" is to hire a sales rep and see what happens.
These are not bad responses. But they skip a step.
Before either of those moves makes sense, there is usually a much smaller move available: a 2-week experiment, a 10-customer call, a single high-fidelity prototype test. Something that costs almost nothing compared to the commitment it informs.
The reason founders skip to the larger move is usually one of two things: the small move feels insufficiently ambitious, or the small move would require admitting that the decision is not yet ready.
Both of those are reasons to do the smaller move first, not reasons to skip it.
A practical framework
When facing a decision, work through these questions before committing to a move:
What exactly is the decision? Name it precisely. "We need to decide X by Y, and the key uncertainty is Z."
What evidence would make that decision clearly right or clearly wrong? Be specific. Not "more traction" but "4 activated orgs who found the product without sales contact in 3 weeks."
What is the smallest move that produces that evidence? This is usually an experiment, a test, a short call series, or a focused build — not a full strategy pivot.
What is the update condition? State before the test: if the result shows P, we go direction A; if it shows Q, we revisit direction B.
Running those four questions before committing to a direction does not guarantee the right decision. But it dramatically improves the quality of evidence on which the decision is made — and it slows down the rate at which a company commits to expensive wrong moves.
The decision that is not ready yet
Sometimes the output of this process is useful in a different way: it reveals that the decision is not ready.
There is not enough evidence to make it well. The update conditions are unclear. The competing explanations have not been separated.
In that case, the right next move is not to make the decision anyway. It is to acknowledge that the decision is still ahead of the evidence, and to design the move that closes that gap.
That is not a failure to be decisive. It is the most decision-quality-preserving thing a founder can do with the time and capital currently available.