Think Better

Founders do not make decisions alone, even when they are the final decision-maker. The quality of a decision depends on whether a team can surface disagreement, challenge assumptions, and distinguish a useful dissenting view from unproductive noise.

That requires a culture where someone can say, “I see the evidence differently,” without being treated as disloyal or negative. It also requires discipline from the founder. If every challenge is experienced as an attack, people learn to protect the founder's confidence instead of improving the company's judgement.

The objective is not consensus on every issue. The objective is an honest view of reality before the decision is made, followed by clear commitment after it is made.

Thinking without action becomes analysis paralysis. Action without thinking becomes activity. The useful discipline is to connect them.

When a founder can name the decision, state the evidence, expose the assumption, and choose the smallest useful test, the company moves with both pace and learning. It does not need a perfect forecast. It needs a reliable next move and a way to review what follows.

A growth mindset is often described as believing that people can improve. For founders, that is too vague to be useful. The practical version is a willingness to treat your current view as a starting point rather than an identity.

You may believe you understand the market, know what customers need, or have chosen the right strategy. Those beliefs may be well-founded. They still need to remain open to evidence. A founder with a growth mindset does not need to defend every initial judgement. They need to keep improving it.

This changes the question after a disappointing result. Instead of asking, “Who was wrong?” ask, “What did this result teach us that we could not see before?” Instead of treating a failed experiment as proof of personal inadequacy, treat it as information about the model.

Growth mindset is not optimism without standards. It is the discipline of allowing evidence to make you wiser.

First-principles thinking means reducing a problem to the facts and constraints that are actually true before rebuilding a response. It helps founders escape inherited assumptions, fashionable advice, and solutions that worked for someone else in a different context.

For example, a team may say it needs more leads. That is a proposed solution, not necessarily the underlying problem. The company may already have sufficient interest but poor qualification, weak conversion, an unclear offer, or low retention. Adding more leads would create more activity without fixing the constraint.

Return to the basic questions: What is happening? For whom? What evidence supports that conclusion? What constraint prevents the outcome we want? What would have to be true for the obvious answer to work?

First principles are especially useful when the team is using familiar language too easily. “We need enterprise features,” “we need to hire,” “we need to raise,” and “we need a new brand” may each contain a real insight. They may also conceal a more fundamental question that has not yet been faced.

The questions a founder asks determine what the team notices. A weak question creates a weak search for evidence. A useful question makes the decision visible and creates a path to learn.

Compare “How do we grow faster?” with “Which customer segment is converting, retaining, and creating enough value to justify deeper investment?” The first question invites a broad list of tactics. The second directs attention to a specific model that can be inspected.

Good questions are concrete enough to guide work but open enough to reveal an unexpected answer. They do not smuggle in a preferred conclusion. They make assumptions visible rather than defending them.

Founders often confuse responsiveness with leadership. A full inbox, a busy calendar, and a long task list can create the feeling of progress while the most consequential question remains untouched.

Attention is a strategic resource. Every interruption, meeting, new opportunity, and unresolved conflict competes for it. If the founder does not decide where attention goes, the market, the team, and the loudest person in the room will decide instead.

Focus requires a visible choice. It means naming the one decision, outcome, or constraint that deserves disproportionate attention for a defined period. It also means declining or deferring work that does not strengthen that focus.

Good decision making is not certainty. It is the ability to decide with the confidence the evidence warrants, make the assumptions visible, and create a review point before the decision becomes too expensive to change.

Some decisions are reversible. A message test, a customer interview sequence, or a small product experiment can be changed quickly. These should move fast. Other decisions are harder to reverse: a senior hire, a major market commitment, a financing structure, or a multi-year product architecture. These require more evidence, clearer ownership, and deliberate dissent.

The mistake is treating every decision as either urgent or permanent. Strong founders match the decision process to the cost of being wrong.

Choose the next decision that is justified by the evidence. This may be a full commitment, a constrained experiment, or a deliberate decision to gather more information first.

Design the smallest practical test. Define the audience, the action, the expected signal, the owner, and the time horizon. A test without a signal is simply activity.

Review what happened against what you expected. Use observable measures where possible, but include qualitative evidence such as customer language or team behaviour when it is relevant.

State what became more or less likely as a result. Record the lesson in plain language. This prevents the next conversation from starting again at opinion.

Use the learning to improve the next question, decision, or experiment. The loop compounds when it becomes part of the company’s normal rhythm rather than an exceptional event after something goes wrong.

Activity bias is the belief that more motion must create more progress. It leads to additional meetings, features, campaigns, and hiring before the company has identified the actual constraint.

Before adding work, ask what outcome the activity is expected to change and what evidence will tell you it worked. If there is no answer, the work may be avoiding the harder decision.

Analysis paralysis occurs when the desire for more certainty becomes a reason not to decide. More information is not always better information. Sometimes the next useful learning only arrives after a small commitment is made.

The response is not recklessness. It is to reduce the size of the decision. Replace a major bet with an experiment that can generate the missing evidence.

Every founder will encounter new markets, channels, technologies, partnerships, and customer requests. Some deserve attention. Many are simply more interesting than the current work.

Use the focus test: does this opportunity strengthen the decision we have already chosen to learn about, or does it fragment the evidence we are trying to gather? A good opportunity at the wrong time can still be a distraction.

The latest customer comment, impressive win, or painful failure can dominate thinking more than the full pattern deserves. A successful tactic can also become a story the company keeps repeating after the context has changed.

Look for a relevant sample, not the most memorable example. Ask whether the event represents a pattern, an exception, or a signal that needs more observation.

Useful dissent is not opposition for its own sake. It is the strongest good-faith challenge to the current interpretation. It asks whether there is another explanation for the evidence, an important consequence that has been overlooked, or a less expensive way to learn.

Founders can make this easier by asking directly: “What would someone who disagrees with us say?” or “What evidence are we missing that could make this a bad decision?” The question should be asked before the decision is announced, while the answer can still improve it.

The team also needs to know what will happen with dissent. If a person raises a concern and the founder chooses a different direction, the concern should be acknowledged and the review signal should be clear. That shows people their perspective was considered even when it did not determine the outcome.

An unresolved decision often remains unresolved because no one knows who owns the final call, who must provide input, and who is responsible for acting after the decision. This creates polite ambiguity. Work continues, but in several directions at once.

For a consequential decision, state the owner plainly. The owner does not need to do all the work or possess all the expertise. Their job is to make the call, explain the reasoning, and ensure the review happens.

Others may be contributors, executors, or people who need to be informed. The distinction matters. It prevents the company from treating every stakeholder as a veto holder while still giving relevant expertise a route into the decision.

The best decisions under uncertainty are often shared experiments. The company agrees on the working assumption, the next move, the expected signal, and the review date. If the evidence supports the assumption, it can invest further. If it weakens the assumption, the company can adjust before the commitment grows.

This approach reduces two unhelpful behaviours. It stops people from treating a decision as permanent simply because it has been made, and it stops people from quietly resisting it because they believe the discussion was never truly finished.

When the review date arrives, return to the evidence rather than the politics of the original meeting. Ask what the company learned and what the next decision should be. That is how a team becomes both decisive and adaptable.

Once a month, step back from individual outcomes. Which decisions keep returning? Where does the company repeatedly make an assumption without testing it? Which meetings create clarity, and which ones recycle the same uncertainty?

Patterns reveal system problems. If the same issue recurs, the company may not need another answer. It may need a better decision process, clearer ownership, or a different source of evidence.

After a launch, major deal, key hire, difficult customer loss, or substantial operational incident, run a short retrospective. Include the people closest to the work. Capture what was expected, what happened, what surprised the team, and what will change.

The value is not the meeting itself. The value is preserving the lesson while the evidence is still clear.

Name the assumption that would make the decision dangerous if false. Record the strongest alternative explanation or dissenting view. A decision becomes more robust when the concern is visible rather than privately held.

Define what happens next. If the decision is reversible, state the smallest experiment. If it is a commitment, state the owner, boundary, and resources allocated.

Specify what outcome will strengthen, weaken, or invalidate the assumption, and when the decision will be reviewed. Without this, the company will tend to interpret every result through the original belief.

The page is not bureaucracy. It is a tool for making the thinking behind a decision visible enough to improve.