The Difference Between a Business Plan and a Business by Igor Fishelev

A business plan is a description of a world that does not exist yet. That is not a criticism – it is simply what a plan is. The trouble begins when people forget the distinction and start managing the document instead of the reality.
The controlled environment problem
Plans are built on assumptions. Customers will behave as the research suggests. Costs will land within the projected range. The right people will be hired on schedule. Competitors will do roughly what they have always done. Each of these assumptions is defensible on its own. Together, they describe conditions that are cleaner and more cooperative than any actual market has ever been.
The real business begins the moment something the plan did not account for appears – which tends to happen earlier than expected and more often than projected. A hire falls through. A customer segment that looked promising turns out to be less interested than the interviews suggested. A cost that was treated as fixed turns out not to be. Individually, none of these things are fatal. But they create a growing distance between the version of the business on paper and the one that is actually operating, and that distance rarely closes on its own.
Protecting the plan instead of the business
When reality and the plan diverge, the temptation is to protect the plan. To treat the gap as temporary, to adjust the numbers without revisiting the assumptions behind them, to keep presenting the original story to investors and partners while managing a different situation in practice. This feels like discipline. It is usually the opposite – a way of delaying the moment when the real problem gets addressed, in favour of preserving a narrative that is becoming less accurate over time.
The organisations that handle difficulty well are almost always the ones where someone was willing to say clearly, and early enough to matter, that the situation had changed and the approach needed to change with it. That sounds straightforward. In practice, when credibility has been staked on a particular version of the story, it requires a degree of honesty that is genuinely uncomfortable.
What a plan cannot do
A detailed, well-constructed plan can give the impression of competence without requiring the thing competence actually consists of – the ability to make reasonable decisions in conditions you did not foresee, with incomplete information and real consequences attached. Following a plan when it is working is not particularly difficult. The test comes when it stops working and something has to be figured out without a template.
This is why the way a leadership team reasons through an unfamiliar problem tells you considerably more than their financial projections do. Projections can be built to support almost any conclusion. Judgment under pressure is harder to construct and harder to fake.
What planning is actually good for
A serious plan, used honestly, gives you a baseline – something to measure against as the situation develops, a record of the assumptions you were making at the start that can be revisited when reality turns out differently. It creates a shared language inside an organisation for talking about direction and priorities. It forces decisions to be made explicitly rather than left vague until they become urgent.
But it is a starting point, not a substitute for the thing itself. The business is not the plan. The business is what happens when the plan meets conditions it was not designed for – and how the people running it respond when that happens. That part cannot be written in advance. It can only be navigated, and the quality of the navigation is what ultimately determines whether the business works or not.