Isolation, and delivering bad news

Founding is structurally lonely, and telling people bad news early is a skill that protects the company as much as it protects you.

What is it?

Two related problems.

Isolation — there are things you cannot say to your team (doubt about runway), to investors (doubt about the plan), or to friends (they do not have the context).

Delivering bad news — the instinct is to delay until you have a solution, which is precisely backwards.

Why does a founder care?

Because isolation degrades judgement. Founders who talk to nobody make worse decisions, hold problems longer, and normalise things an outside perspective would flag immediately.

And because delayed bad news compounds. A problem shared at month one has options; the same problem at month four has fewer, and the delay itself becomes part of what people react to.

Example

Bad news, handled badly: runway is shorter than expected. The founder waits, hoping a deal closes. Two months later they tell investors, with six weeks left. The investors are now dealing with an emergency and wondering what else has been withheld. The delay damaged trust more than the runway did.

Handled well: 'Our runway is 7 months, not 11 — the enterprise deal slipped and two costs came in higher. Here is the plan: cut $6k/month from these lines, and start the raise in March instead of June. I wanted you to know now rather than later. What I need from you is two introductions to seed funds in this sector.'

Situation, cause, plan, ask. It takes four sentences and it is the single most trust-building thing a founder does.

On isolation: the specific fix is other founders at a similar stage. Not your team, who need you steady. Not your investors, who are evaluating you. Not friends outside startups, who cannot calibrate. Someone six months ahead of you who has had the same week.

The common mistake

First-time founders often wait to deliver bad news until they have a solution. Investors and boards are far more troubled by surprise than by problems — problems are expected, concealment is not.

The second mistake: treating the co-founder as the entire support system. You are both inside the same anxiety and cannot give each other perspective on it.

The third: telling the team nothing to protect them. People sense difficulty and fill silence with something worse than the truth. Age-appropriate honesty — 'runway is tighter than planned, here is the plan, your job is safe / here is the risk' — is almost always better than a confident vagueness nobody believes.

How it works

Step 1: Deliver bad news early, with a plan

Situation, cause, plan, ask. Four sentences. Do not wait until it is solved.

Step 2: Say the number plainly

'Seven months, not eleven.' Softening it means people discover the real figure later, and then they doubt everything.

Step 3: Always include a specific ask

It turns an announcement into a request for help, which is what most investors would prefer to give.

Step 4: Find founders at a similar stage

The only people who can calibrate. Two or three you speak to monthly is enough.

Step 5: Do not use your co-founder as your only outlet

You are inside the same problem. Neither of you can offer the other perspective on it.

Step 6: Tell your team something true

Silence gets filled with worse assumptions. Honest and calm beats vague and confident.

When to use this

The moment you know something material has changed for the worse.

When not to use it

Do not share every fluctuation. Bad news means something material that changes the picture, not an ordinary bad week.

Do this now

Apply this to your own startup in My Full Journey (free account).