Bias to Action: Decide With the Real World, Not Your Head
Most early questions cannot be answered by thinking harder. Will people pay for this? Which headline converts? Is this feature worth building? You can argue both sides forever in your own head, and you will, because thinking feels safe. The entrepreneurial move is to convert the question into a small action that produces real data, then let reality settle the argument.
Bias to action does not mean acting recklessly. It means defaulting to the smallest experiment that moves you from opinion to evidence. Instead of debating whether a market exists, post in the forum where that market hangs out and watch the response. Instead of guessing at pricing, put a number on a page and see who clicks buy. The point is to spend an hour learning what a month of meetings would only guess at.
The cost of inaction is invisible, which is why it is so dangerous. Every week spent deliberating is a week of runway burned and a week of feedback not received. When you are stuck, ask one question: what is the cheapest thing I could do this week that would tell me whether I am right?
- If two people could argue it forever, it is an empirical question. Go get data.
- Default to the smallest test that turns an opinion into evidence.
- Deliberation has a cost too. It is just invisible until the runway is gone.
Cheap Tests: Buy the Most Learning per Dollar
Every decision you face has a learning cost and a being-wrong cost. The skill is to keep both low. A cheap test is any experiment that gives you a real answer for a fraction of the price of building the full thing. A landing page that takes a morning can tell you whether an idea has pull. A few customer conversations can tell you whether a problem is real. You do not need the product to learn most of what matters.
Sequence your tests from cheapest to most expensive, and only advance when the current test passes. Talk to people before you design. Design before you build. Build a manual version before you automate. At each gate, a no costs you almost nothing and saves you everything downstream. This is the whole logic of a build-or-kill approach: you are trying to fail at the cheapest possible stage.
The trap is confusing motion with learning. Building a beautiful product is motion. Discovering that customers will pay is learning. Always ask what a given week of work will actually teach you, and prefer the option that teaches the most for the least.
- A cheap test buys a real answer at a fraction of the build cost.
- Run tests in order of price and only advance when one passes.
- Motion is not learning. Optimise for learning per dollar, not features per week.
Kill Your Darlings: Hold Ideas Loosely
Founders fall in love with their ideas, and love makes you a bad judge. The same conviction that gets you started will, left unchecked, keep you building something the market has quietly rejected. The mature version of the mindset is to commit hard to the problem and hold the solution loosely. You are married to the customer, not to your first guess about how to serve them.
Practically, this means deciding in advance what evidence would make you stop. Write down the result that would kill the idea before you run the test, so the answer cannot be rationalised away afterward. If the smoke test gets no signups, if nobody will pre-order, if every customer conversation is polite but uninterested, that is the market talking. Listen the first time.
Killing a darling is not failure, it is information you bought cheaply. The founders who win are not the ones who never have bad ideas. They are the ones who kill bad ideas fast and redirect that energy into the next test. Sunk cost is a feeling, not a reason.
- Commit to the problem, stay loose on the solution.
- Write down the kill condition before the test, so you cannot argue your way out later.
- Killing an idea is bought information, not personal failure. Sunk cost is not a reason.
Default-Alive Thinking: Always Know the Math
Default-alive means that on your current revenue, growth, and costs, you reach profitability before you run out of money. Default-dead means you do not. The mindset shift is making this calculation a reflex rather than a fear you avoid. Most founders never do the math, which is exactly why running out of money seems to surprise them.
Translate every decision into its effect on runway. A new hire, a tool subscription, a month of building before charging: each one shortens the time you have to find traction. That is not a reason to never spend. It is a reason to know what each choice buys you and how much survival it costs. Time is the resource that lets every other experiment happen, so protect it deliberately.
Default-alive thinking also reframes revenue. For an early founder, getting one customer to pay is not just income, it is the cleanest signal you exist and the thing that extends your runway at the same time. Chase paid validation early, keep costs embarrassingly low, and you turn time from an enemy into an ally.
- Know whether you are default-alive or default-dead, and recheck it monthly.
- Translate every spend into runway. Know what each decision buys and what it costs.
- Early revenue is signal and survival at once. Chase it sooner than feels comfortable.