Every founder I have ever worked with, including myself, is currently postponing one specific decision they know needs to be made. The decision varies; the postponement is universal. It is the conversation with the cofounder whose contribution has slipped, but whose departure would be uncomfortable. The product line that should be killed but currently produces revenue. The price increase that is overdue but feels risky. The hire that is needed but seems expensive. The investor relationship that needs to be exited but feels awkward. The geographic market that is not working but represents a sunk cost too painful to write off.
The postponement is not because the founder does not know the right answer. The postponement is because the right answer is uncomfortable, and the founder has been telling themselves they are waiting for more information, more clarity, a better moment. The waiting is the problem. The information will not arrive. The clarity is already there. The better moment is not coming.
I want to argue in this piece that the single most consequential thing most founders could do this quarter is to identify the decision they are currently postponing and make it within seven days. Not to find a better strategy. Not to raise more capital. Not to redesign the product. To make the decision they have been deferring, accept the discomfort that follows, and operate from the new position rather than the limbo of the old one.
Why postponement is the structural failure mode
Postponement is the most common operational failure in founder-led ventures because it is invisible. A founder who has not made a decision has not, on any visible record, done anything wrong. There is no failed launch, no botched hire, no missed quarter directly attributable to the postponement. The cost of the postponement shows up indirectly, in opportunity cost, in compounding small problems that should have been addressed early, in the slow erosion of clarity within the team that always knows when the founder is avoiding something.
This invisibility is dangerous because it lets postponement persist. A founder who made a wrong decision and produced a visible failure has feedback to learn from. A founder who has avoided a decision for six months has nothing to learn from, because nothing has happened. The avoidance produces the same kind of accumulated cost as the wrong decision, except that the cost is paid silently, over a longer period, in ways the founder cannot easily attribute to the avoidance.
The team feels the postponement before the founder admits it. Senior team members can almost always name the decision the founder is avoiding, because the consequences of the avoidance show up in their work. The conversation about the cofounder whose contribution has slipped is being had by everyone except the cofounder and the founder. The product line that should be killed is consuming team time that everyone knows is wasted. The price increase that has not happened is being absorbed by every account manager who has to defend prices that have not kept up with the market.
This is one of the most consistent patterns I have observed across founder-led ventures: the team usually knows what decision the founder is avoiding, often before the founder does. The team also, usually, has the decency not to bring it up directly, because they understand it is the founder’s call. The decision sits in the gap between the founder’s awareness and their willingness, while the venture absorbs the cumulative cost.
The two flavours of postponement
There are two distinct kinds of decision-postponement, and they require different interventions.
The first is the decision waiting for information that does not exist. The founder has framed the decision as one they cannot make until they have more data, more analysis, more confidence in the answer. The framing is honest in form and false in content; the data they say they need does not actually exist, will not arrive, or would not change the decision if it did. The decision is not actually a research question. It is a values question dressed up as a research question, and the research framing is letting the founder defer the values choice.
The fix for this kind of postponement is to honestly name the values question. Is this a hire we will make if I cannot prove the unit economics, or am I waiting for proof that will never come because the proof can only follow the hire. Is this a product line we will kill if I cannot find an alternative use for the team, or am I waiting for the alternative to materialise as an excuse not to make the call. Once the values question is named, the answer is usually accessible within an hour, because the founder already knows what they think; they were just not ready to acknowledge it.
The second is the decision waiting for the right moment. The founder accepts the decision needs to be made, but is waiting for a moment when making it will be easier. After this quarter ends. After the conference. After the holidays. After the funding round. The right moment, in this framing, is whenever the conditions for making the decision feel less stressful than they do now.
The fix here is to recognise that the conditions for making uncomfortable decisions never feel less stressful. The next quarter will have its own pressures. The conference will be replaced by the next one. The holidays will be followed by the year-end push. There is no moment ahead in which making the decision will feel easier than it feels today, and waiting for one is waiting for something that will not arrive. The decision made in the imperfect present produces a venture that operates from the new position; the decision deferred to the perfect future produces a venture that operates indefinitely from the limbo of the old one.
The week that ends the postponement
If you are a founder reading this, the most useful exercise to do this week is to spend ten minutes naming the decision you are currently postponing. Not generally. Specifically. Write it down in a single sentence. The sentence will probably embarrass you a little, because the postponement, once named, is almost always small enough to make this week.
Then write down what is making the decision uncomfortable. The honesty of this writing matters more than the elegance. The discomfort might be that you will hurt someone. It might be that you will look foolish. It might be that you will admit you were wrong about something. It might be that the decision has financial consequences you have been avoiding pricing into your projections. Whatever it is, write it down so you cannot pretend, later, that the postponement was about something more dignified than what it actually was.
Then write down the cost of continuing to postpone for the next ninety days. Specifically. What is the team cost. The customer cost. The financial cost. The opportunity cost. The cost of the cumulative small problems that will continue to compound while the decision is unmade. This is the part most founders skip, and it is the part that, in my experience, breaks the postponement faster than anything else. Once the cost is named in concrete terms, the discomfort of making the decision usually looks smaller than the cost of continuing to avoid it.
Then make the decision. Not next week. This week. The making is rarely as dramatic as the postponement made it feel. The team usually receives the decision with relief because they have been waiting for it. The customer or counterparty usually accepts it with less resistance than expected because they have been preparing for it. The financial consequence is usually smaller than the projected one because the decision unlocks possibilities that were closed while the postponement persisted.
The discipline that distinguishes Stay-Up phase founders
Founders who build Stay-Up phase ventures, the ventures that survive their founders and outlast the cycles, all share a particular relationship with postponement. They have learned, often through the painful early years, that postponement is more expensive than discomfort, and they have built personal disciplines that prevent the deferral pattern from setting in.
The disciplines are usually some version of weekly self-audit. What decision is currently sitting in my queue that I have not yet made. What is the cost of continuing to defer it. What is the smallest version of the decision I could make this week to begin moving on it. These questions, asked weekly, prevent the slow accumulation of postponements that, over a year, would otherwise produce a venture full of unaddressed problems and a founder full of low-grade dread.
The dread is, in my experience, the cost of postponement that founders never admit to but always carry. Every unmade decision is a quiet weight, and the weights compound. A founder with five outstanding postponements is operating under five weights they could remove in five weeks of decisive action. They will not remove them, in most cases, because the discomfort of removing them feels larger than the discomfort of continuing to carry them. The calculus is wrong, but the calculus persists, because the costs of carrying are invisible and the costs of removing are immediate.
If this piece has named the postponement you have been carrying, the move is this week. Not later. The decision will not get easier. The cost will continue compounding. The team is waiting. The discomfort of making it will be over by next week. The discomfort of continuing to defer it will be present every quarter for as long as you continue to defer.
That is the move. The week. The decision. The new position from which the venture operates. Most founders never make it because they are waiting for the moment that does not arrive. The Stay-Up phase founders made it five years ago, and they made it the week they realised the moment was never going to feel ready, and they have been operating from cleaner positions ever since.
For the related discipline of why caution is the riskiest strategy, see Why Playing It Safe Is the Riskiest Strategy. For the posture that complements decisive action, see Be the Disruption Before It Reaches You. For why setting specific outcomes outperforms vague ambition, see Stop Thinking Big.
