The Bias Toward Action: The Founder’s Guide to Execution over Strategy

The three-question test

Before another week goes into the plan, answer three questions honestly. They take about ten minutes, and they get harder in roughly the order they are written.

1. What decision does this unlock?

   If the plan finishes and nothing changes about what you do on Monday, it was not a plan. It was a delay with footnotes.

2. What would I learn faster by selling?

   A persona document is a guess about a person. An invoice is a fact about one. If the cheapest way to answer the question is to ask somebody for money, the research is the expensive option.

3. What am I afraid this will tell me?

   This is the one that stings, and it is the one that gives you the answer. Name the verdict you are avoiding and you will usually find you have been circling it for months.

The distinction underneath all three is the same. Genuine preparation reduces a risk you have named. Avoidance postpones a verdict you fear. The second one feels more responsible, because it never produces a result anybody can judge.

Why the answer is almost never more strategy

Strategy is cheap and fairly evenly distributed. The scarce thing is a team that finishes. That makes execution less a matter of willpower than of who is in the room — and there are two ways that room goes wrong.

Hiring for potential

Talent that does not deliver costs more than competence that does, because the whole organization reorganizes itself around waiting. The people who quietly close things out are worth more than their résumés suggest, and they are almost never the most impressive in an interview.

Unwritten alignment

A team can be individually excellent and still pull in five directions, because the goal that was obvious in the founder’s head was never made obvious anywhere else. Alignment is not a communication exercise you run once. It is maintenance.

The moving target as cover

There is always another platform, another model, another shift that makes “we need to understand this before we commit” sound like diligence rather than fear. It is genuinely harder to stay current than it was in 1982. That is true, and it is also the most respectable excuse available for not shipping.

The order that follows from this is short. Decide how big you actually want the company to be — the honest answer, not the one for investors. Set goals somebody could visibly fail to meet. Build only the infrastructure those goals require. Then hire people who finish, and get out of their way.

The arguments underneath it

Three pieces of commentary this guide rests on. Read them in this order if you are reading them for the first time.

The audit

The questions above are for a plan. This is for the team running it. Ten statements about how the company actually behaves, scored one to five, with the total read against three bands. It takes about fifteen minutes and it is more useful done with somebody who will argue with your scores.

If the audit says the problem is the team