When Growing Stops Being Your Advantage and Becomes Your Trap
There is a precise moment in the life of any growing organization where the practices that built its success begin to undermine it. It is not a dramatic moment. There is no meeting where someone declares that the model no longer works. It is quieter than that: decisions take longer than they should, information arrives distorted, and the founder or leader who was once the engine of the team becomes, without intending to, its bottleneck.
Illia Smoliienko, founder and engineering lead at Sivense, describes this with the kind of honesty that is usually in short supply in leadership essays. When his team had ten people, he could know exactly where each person was stuck, redistribute work in real time, and even sit down to solve a problem with his own hands. When the team grew to fifty and then to ninety people, those same skills began generating friction. In Fast Company, Smoliienko articulates four lessons learned during that transition. These are lessons that deserve a more rigorous analysis than they typically receive, because behind each one lies a fundamental strategic decision that very few organizations process correctly.
The Problem Is Not Growth — It Is the Cognitive Inertia of Leadership
The story Smoliienko tells has a recognizable mechanics for anyone who has observed organizations at different stages of scale. The leader who operated successfully with ten people built, during that period, a set of routines, reflexes, and control mechanisms that worked with precision within that context. The problem is that those mechanisms are deeply internalized. They are not written policy, they are not documented, they do not exist outside of the founder's head. They are, in practical terms, non-transferable tacit knowledge.
When the team grows, that tacit knowledge stops scaling. And here lies the fracture that few organizations diagnose correctly: the leader does not fail due to incompetence, but due to cognitive inertia. They continue applying the same mental model that worked with ten people, without perceiving that the organizational context has changed in nature, not just in size. Smoliienko names it with precision: "the problem was the mismatch between old approaches and the new reality."
This observation, though it seems obvious when read, is extraordinarily difficult to detect from the inside. The warning signal almost never arrives as an explicit crisis. It arrives as an accumulation of small inefficiencies: decisions that are revisited across multiple meetings without resolution, information that becomes distorted as it travels down the structure, tasks that get completed thanks to someone's heroic effort rather than through a process. When those signals become normalized, the organization has already entered a state of silent degradation that its own growth metrics can mask for months.
The first lesson from Smoliienko points directly to this: the leader must stop trying to retain all context in their own head. This is not conventional delegation advice. It is a demand for architectural redesign. Transitioning from a model where the leader knows to a model where the leader ensures that decision-makers have the information they need requires building visibility systems that do not depend on the memory or availability of any particular person. It requires, in operational terms, accepting that information must flow through the system rather than accumulate at the top.
The MUM effect that Smoliienko references — the documented tendency of teams to withhold bad news as leadership becomes more distant — compounds this problem in a structural way. A survey linked to SurveyMonkey data shows that only 39% of employees feel comfortable sharing honest feedback with their managers. This is not a cultural anomaly: it is an almost inevitable consequence of hierarchies that grow without redesigning their information channels. The leader who does not build explicit mechanisms to receive early signals ends up operating on a picture of the terrain that is weeks or months out of date.
The Transmission Chain of Judgment Is the Most Fragile Asset of a Scaling Organization
Smoliienko's second and third lessons operate on territory that most leadership writing tends to avoid: the mechanics of how the leader's judgment reaches the team when there are intermediate layers of management in between.
When a team has ten people, the leader can explain the reasoning behind each decision directly. They can correct misunderstandings in real time. They can ensure that the context justifying a priority reaches the person who must execute it intact. When there are nine managers between the leader and the team, that same reasoning passes through nine different filters. Each manager interprets it through their own framework, their own priorities, their own level of understanding of the business. The result, as Smoliienko notes, is not malice: it is systematic distortion.
What the Warwick Business School documented over three consecutive years supports this diagnosis with institutional data: those who define strategy and those who must implement it prioritize in consistently different ways. The gap is not explained by middle management incompetence. It is explained by the fact that leadership rarely invests the time needed to transmit not only what was decided, but why it was decided and what considerations were discarded in the process. Without that context, the transmission chain converts strategy into instruction, and instruction into noise.
The example Smoliienko uses is precise: a directive that says "we need to make decisions faster and stop getting bogged down in approvals" can reach the team as "the main thing is to close the task quickly and not ask questions." This is not a one-off communication error. It is the predictable consequence of transmitting the directive without transmitting the reasoning behind it. And the consequences of that distortion are not trivial: teams operating with poorly calibrated criteria produce work that technically fulfills the instruction but fails at the underlying objective.
This is where the third lesson gains greater analytical weight than it is usually given. Heroism — the employee who works the weekend, the manager who saves the launch at the last minute — is not simply a human cost to be managed with empathy. It is a diagnostic signal about the quality of the organization's planning and judgment systems. When heroism becomes recurrent, it ceases to be a cultural attribute and becomes evidence of structural failures: incorrect estimations, undocumented decisions, processes that rest on someone's individual willingness rather than on a clear architecture.
The question Smoliienko recommends asking after each heroic episode is exactly the right one: where did we underestimate the workload, where was a decision not recorded, where does a process rely on personal accountability instead of a clear system. These questions are not wellness postmortems. They are audits of operational viability.
Collaborating Is Not Delegating the Decision to the Collective
The fourth lesson touches on a failure point that management literature frequently romanticizes: collective decision-making as a sign of organizational maturity.
Smoliienko distinguishes with precision between two concepts that are often confused. Collaboration means involving the team to gather experience and find the best path forward, while the leader retains the final decision. Consensus means transferring the decision to general agreement. The first moves the team forward. The second paralyzes it. And he adds something that is rarely stated with such clarity: consensus is also a form of evasion, a mechanism by which the leader shields themselves behind unanimity in order to avoid taking responsibility for choosing.
McKinsey documented that 61% of executives acknowledge that at least half the time they spend making decisions is used inefficiently. The cause that emerges most frequently in that analysis is not a lack of information: it is an overabundance of deliberative process without clarity about who decides. Meetings that repeat the same debates. Approvals that stretch out over weeks. Decisions that are only made once the last skeptic has nodded. All of that has a measurable operational cost: in delayed projects, in opportunities not captured, in teams that learn not to commit because they know any decision can be reopened.
The principle of "disagree and commit" — attributed to cultures such as those of Intel and Amazon, and popularized by Jeff Bezos in his 2017 shareholder letter — offers a more honest architecture for this problem. The team contributes its knowledge, the leader decides, and everyone executes even if they are not completely in agreement. This is not authoritarianism: it is clarity of roles. The difference between a team that disagrees and commits and one that seeks unanimity is not philosophical. It is operational, and it is measured in execution speed and decision quality over the long term.
What makes Smoliienko's analysis useful is that he does not propose this principle as a universal formula, but rather as the response to a specific problem of scale. With ten people in a room, open debate and the pursuit of consensus can be efficient. With ninety people distributed across layers of management, that same process becomes a source of systemic ambiguity. The structure that works at a certain scale does not merely stop working at another: it actively deteriorates the organization's capacity for decision-making.
The Real Cost of Scaling Without Redesigning Who Decides What
What Smoliienko's essay allows us to see, beyond its four specific lessons, is a pattern of organizational degradation that has concrete financial and competitive consequences. Not abstract ones — concrete ones.
An organization that scales without redesigning its decision architecture accumulates inefficiencies that rarely appear in financial statements under that name, but that manifest in indicators that are observable: product launch speed, capacity to respond to market changes, talent turnover in middle management, and the quality of work delivered under pressure. All of those indicators depend, ultimately, on whether the people doing the executing have the right judgment to make the day-to-day decisions that leadership cannot make for them.
McKinsey estimates that for a large company, inefficiency in decision-making can represent more than 530,000 lost working days per year and around 250 million dollars in wasted labor costs. That number does not measure individual incompetence. It measures the systemic cost of a decision architecture that was not redesigned for the scale at which it operates.
Smoliienko's underlying argument — that many leaders burn out not because they cannot handle the workload, but because they continue applying early-stage tools to an organization of a fundamentally different nature — is not an observation about the personal character of founders. It is a diagnosis of coherence between management model and organizational reality. And that diagnosis has a direct implication that few organizations process before they need to: scaling is not adding people to a model that works; it is redesigning the model so that it works with more people.
Organizations that do not make that distinction in time do not collapse all at once. They deteriorate progressively, while their superficial growth metrics continue to indicate that everything is going well. And when the deterioration becomes visible, it is usually too late to trace it back to its original cause. The moment when that cause needed to be addressed was not the crisis itself, but the period that preceded it — when the signals were legible and the organization still had room to choose how to respond. That is the interval that defines the quality of leadership at scale, and also the one that is most frequently wasted.
