Founders leading under fire: bringing the board bad news
Picture the board meeting before it happens. Revenue has stalled, a key hire has walked, or a critical development programme has slipped a quarter - and the next board meeting is three weeks away. The instinct of most founders is to wait, to use those three weeks to assemble a fuller picture, a tidier story, a problem that arrives already half-solved. It feels like the responsible thing to do.
It is almost always the wrong thing to do. The board is not primarily assessing the setback. It is assessing how you carry it. Directors expect things to go wrong, because things always go wrong, and a founder who never brings them a problem is not reassuring, they are unreadable. What the directors are gauging, in the days and weeks around bad news, is something simpler and harder to fake: whether a founder under pressure stays open and legible to them, or goes quiet and opaque exactly when they most need to see in.
This is the third and final briefing in our series on operating the early-stage board. The first two were about leading the regular meeting and reading each director in turn. This one is the hardest application of the same principle, because it asks you to lead the room at the precise moment your authority feels least secure.
The setback is forgiven. The surprise is not
Let's start with the distinction that governs everything else. There is a profound difference, in a director's mind, between bad news and a surprise. The first is expected and survivable. The second is the thing that quietly corrodes their confidence in you.
The seasoned investor Andrew Wigfall puts the founder's side of this plainly: directors are not going to be alarmed by a setback, and they would far rather hear bad news quickly than good news slowly. The SaaS investor Jason Lemkin makes the same point from the other direction, in blunter terms: run towards bad news, not away from it. What spooks investors is not the missed quarter they had all been expecting. It's the news that lands without warning.
So the question a founder should sit with is not how to soften bad news. It is how to make sure it never arrives as a surprise. Everything that follows is really about timing and venue: getting the right message to the right person at the right moment, across the life of a problem.
Promptness beats completeness
The first discipline is the hardest to accept, because it runs against a founder's protective instinct. You deliver bad news promptly, even when you do not yet have a worked-up solution. A partial picture delivered early beats a full picture delivered late, every time.
Waiting for the next scheduled meeting does not buy you credibility. It buys you anxiety, yours in the intervening weeks, and theirs when they discover the timeline. And because bad news rarely keeps to a calendar, prompt almost always means between meetings. This is where the one-on-one channel we examined last week earns its keep: the deliberate contact outside the set piece meeting is not just for reading a director's mood, it is the route by which a problem reaches them before it hardens into a crisis.
Promptness is not the same as panic. There is a difference between flagging a developing problem early and firing off a half-formed alarm at midnight. The art is to move quickly while still having thought, however briefly, about what you are seeing and how you are framing it. Early and considered, not late, and not frantic.
Take it to them one at a time, and start with the independent
How you deliver the news matters as much as when. The instinct is to save it for the group, to tell everyone at once and get it over with. Resist that. Bad news delivered cold to the assembled board is the worst of all options, because it plays out in public, in real time, with every reaction feeding the next.
Delivered one-on-one, the same news behaves entirely differently. You control the narrative rather than narrating it to a room. You absorb each director's first reaction privately, where a flash of alarm cannot infect the others and no one is tempted into a performance for the benefit of their peers. And you get to listen properly, because the investor-director and the independent will each react from their own vantage point, and you want to hear those responses one at a time, not blurred into a single anxious chorus.
There is an order to this, and it is worth getting right. Start with the non-executive director. The independent is the one member of your board who owes nothing to a fund, which makes them your most neutral sounding board and your best read on how the news will land before you face the investors. Airing the problem with them first is, in effect, a rehearsal: it surfaces the obvious questions and sharpens your framing while the stakes are still low.
Which is precisely why the choice of that person matters so much. A non-executive with genuine standing and relevant experience becomes the voice of reason when investor-directors start to pile on the pressure, a role we have touched on before in the context of the chair. The neutrality is only ever as valuable as the person carrying it.
Each director hears the same news differently
Once you are delivering one to one, you quickly discover why the group setting was never going to work: the same piece of bad news, delivered in the same words, means three different things around the table.
To the independent, bad news is a problem to be solved on the company's terms. To the investor-director, it is something more loaded. They hear it, almost reflexively, through the lens of the next round, because the next raise is the event their own performance depends on: it is where a new lead independently revalues the company and marks up the book value of their stake. A setback is not just a setback to them, it is a question about the story they will tell that next investor.
This is where a quieter difficulty surfaces, and where founders of deeply technical companies should pay particular attention. A problem that is modest in engineering terms can read as alarming to a generalist investor who cannot calibrate it, while a genuinely serious issue can be waved through because it sounds minor.
Part of delivering bad news well is translating its true magnitude, neither inflating nor deflating it, into terms each director can actually weigh. Do that individually, and you arrive at the board meeting with a room that already understands the problem to the same depth.
By the time the board meets, bring the solution
Here the thread from the first briefing comes back, advanced one turn. We argued at the start of this series that a founder should arrive at the board with a recommendation, not a blank-sheet problem. Under fire, that discipline is more than just a display of competence. It becomes the thing that prevents a controlled problem from tipping into panic.
The sequence makes this possible. Because promptness and the one-on-ones have already done their work, the news is known by the time the full board convenes. The meeting does not have to absorb the shock, so its energy can go where it is useful: coolly stress-testing and improving the path forward rather than reeling at the problem itself.
So the board meeting becomes the venue for the solution, not the venue for the problem. You bring your recommended approach, framed as something to be tested and sharpened rather than rubber-stamped, and you let the room do what a good board does best. The problem was aired privately. The answer is refined and agreed collectively.
Candour is the credit you bank in the good times
None of it is free. The calm authority you build in the routine meetings, when the stakes are low and the news is good, is exactly the credit you draw down when the news is bad and the room is tense. A board that already trusts your grip leans in to help; a board that does not starts to wonder whether the problem is the company or the person running it.
Which closes the loop this series began with. Leading the board was never about the meeting that goes well. It was always about the one that does not. Bring the bad news well, and you stop being a risk to manage. You become the asset they most want to protect.
Let's talk.
To subscribe to our Blog Articles click here