<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Igor Fishelev</title>
    <description>The latest articles on Forem by Igor Fishelev (@igor_fishelev).</description>
    <link>https://forem.com/igor_fishelev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3485484%2F2f2af29d-113c-4073-900b-bcca6b4fd9ef.jpg</url>
      <title>Forem: Igor Fishelev</title>
      <link>https://forem.com/igor_fishelev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/igor_fishelev"/>
    <language>en</language>
    <item>
      <title>The Difference Between a Business Plan and a Business by Igor Fishelev</title>
      <dc:creator>Igor Fishelev</dc:creator>
      <pubDate>Mon, 30 Mar 2026 14:14:05 +0000</pubDate>
      <link>https://forem.com/igor_fishelev/the-difference-between-a-business-plan-and-a-businessby-igor-fishelev-30pl</link>
      <guid>https://forem.com/igor_fishelev/the-difference-between-a-business-plan-and-a-businessby-igor-fishelev-30pl</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgvulnqgxnh1v56d4vcgg.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fgvulnqgxnh1v56d4vcgg.jpg" alt=" " width="800" height="839"&gt;&lt;/a&gt;&lt;br&gt;
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.&lt;br&gt;
&lt;strong&gt;The controlled environment problem&lt;/strong&gt;&lt;br&gt;
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.&lt;br&gt;
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.&lt;br&gt;
&lt;strong&gt;Protecting the plan instead of the business&lt;/strong&gt;&lt;br&gt;
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.&lt;br&gt;
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.&lt;br&gt;
&lt;strong&gt;What a plan cannot do&lt;/strong&gt;&lt;br&gt;
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.&lt;br&gt;
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.&lt;br&gt;
&lt;strong&gt;What planning is actually good for&lt;/strong&gt;&lt;br&gt;
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.&lt;br&gt;
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.&lt;/p&gt;

</description>
      <category>leadership</category>
      <category>management</category>
      <category>startup</category>
    </item>
    <item>
      <title>Why Growth Is Not a Universal Strategy By Igor Fishelev</title>
      <dc:creator>Igor Fishelev</dc:creator>
      <pubDate>Wed, 25 Feb 2026 13:39:30 +0000</pubDate>
      <link>https://forem.com/igor_fishelev/why-growth-is-not-a-universal-strategy-by-igor-fishelev-kho</link>
      <guid>https://forem.com/igor_fishelev/why-growth-is-not-a-universal-strategy-by-igor-fishelev-kho</guid>
      <description>&lt;p&gt;In modern business culture, growth is often treated as an unquestioned objective. Companies are encouraged to expand markets, increase headcount, diversify product lines, and pursue aggressive revenue targets. The narrative is straightforward: scale equals success. If a business is not growing rapidly, it risks being perceived as stagnant.&lt;br&gt;
However, growth in itself is not a strategy. It is an outcome – and sometimes a risky one.&lt;br&gt;
Scaling a company introduces structural complexity. As operations expand, coordination becomes more difficult. Informal communication gives way to layered management systems. Decision-making slows. Accountability must be redistributed across larger teams. What once worked through direct oversight and personal trust now requires formal procedures and institutional discipline.&lt;br&gt;
If these systems are not fully developed, rapid expansion exposes vulnerabilities. Inefficient workflows become more expensive. Quality control becomes harder to maintain. Corporate culture weakens under pressure. In industrial sectors, where reliability and precision are fundamental, these risks can undermine long-term competitiveness.&lt;br&gt;
Another common misconception is that market presence must constantly widen. In reality, depth often creates more value than breadth. A company that understands its niche, invests in expertise, and builds long-term partnerships can achieve устойчивость without aggressive territorial expansion. When businesses stretch beyond their core competencies merely to increase scale, they frequently dilute what made them effective in the first place.&lt;br&gt;
Financial stability is also a critical factor. Scaling typically requires significant capital investment – in infrastructure, personnel, technology, and marketing. If revenue growth does not keep pace with rising operational complexity, the result can be financial strain rather than progress. Growth financed by optimism rather than operational readiness often leads to instability.&lt;br&gt;
There is also a leadership dimension. Managing a compact organization is fundamentally different from leading a large one. The skills that help build a company are not always the same skills required to scale it. Expansion demands new governance structures, stronger delegation, and disciplined performance measurement. Without this evolution in leadership, growth becomes difficult to sustain.&lt;br&gt;
None of this implies that scaling should be avoided. Expansion can open access to innovation, global partnerships, and new opportunities. But growth should follow capability, not ambition alone. It must strengthen the company’s foundation rather than test its limits prematurely.&lt;br&gt;
In my experience, the most resilient enterprises are those that grow deliberately. They prioritize internal stability before external expansion. They ensure processes are efficient before increasing volume. They invest in competence before entering new markets.&lt;br&gt;
A business does not need to become larger to become stronger. Sometimes, controlled development, technological depth, and operational excellence provide greater long-term value than rapid scale.&lt;br&gt;
Sustainable success is not measured by size alone. It is measured by stability, adaptability, and the ability to deliver consistent quality over time.&lt;/p&gt;

</description>
      <category>igor</category>
      <category>fishelev</category>
    </item>
  </channel>
</rss>
