{"version":"1.0","type":"agent_native_article","locale":"en","slug":"when-growth-stops-being-your-advantage-becomes-your-trap-mt1nyqq0","title":"When Growth Stops Being Your Advantage and Becomes Your Trap","primary_category":"leadership","author":{"name":"Ricardo Mendieta","slug":"ricardo-mendieta"},"published_at":"2026-08-20T14:03:42.726Z","total_votes":88,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/when-growth-stops-being-your-advantage-becomes-your-trap-mt1nyqq0","agent":"https://sustainabl.net/agent-native/en/articulo/when-growth-stops-being-your-advantage-becomes-your-trap-mt1nyqq0"},"summary":{"one_line":"The practices that make a leader effective at ten people become structural liabilities at fifty or ninety, and most organizations fail to redesign their decision architecture before the damage is measurable.","core_question":"At what point does a leader's proven management model stop scaling, and what must change before the deterioration becomes irreversible?","main_thesis":"Organizational growth does not simply stress existing management models — it inverts their value. Leaders who do not redesign their decision architecture, information flows, and judgment transmission chains in time create systemic inefficiencies that compound silently behind positive growth metrics until the cost becomes structural and difficult to trace."},"content_markdown":"## When Growing Stops Being Your Advantage and Becomes Your Trap\n\nThere 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.\n\nIllia 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.\n\n## The Problem Is Not Growth — It Is the Cognitive Inertia of Leadership\n\nThe 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.\n\nWhen 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.\"\n\nThis 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.\n\nThe 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.\n\nThe 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.\n\n## The Transmission Chain of Judgment Is the Most Fragile Asset of a Scaling Organization\n\nSmoliienko'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.\n\nWhen 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.\n\nWhat 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.\n\nThe 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**.\n\nThis 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.\n\nThe 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.\n\n## Collaborating Is Not Delegating the Decision to the Collective\n\nThe fourth lesson touches on a failure point that management literature frequently romanticizes: collective decision-making as a sign of organizational maturity.\n\nSmoliienko 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.\n\nMcKinsey 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.\n\nThe 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.\n\nWhat 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.\n\n## The Real Cost of Scaling Without Redesigning Who Decides What\n\nWhat 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.\n\nAn 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.\n\nMcKinsey 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.\n\nSmoliienko'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**.\n\nOrganizations 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.","article_map":{"title":"When Growth Stops Being Your Advantage and Becomes Your Trap","entities":[{"name":"Illia Smoliienko","type":"person","role_in_article":"Primary source; founder and engineering lead at Sivense whose scaling experience from 10 to 90 people structures the article's argument."},{"name":"Sivense","type":"company","role_in_article":"Organization where the scaling challenges described in the article were observed firsthand."},{"name":"Fast Company","type":"institution","role_in_article":"Publication where Smoliienko's original essay appeared, cited as the source of his four lessons."},{"name":"McKinsey","type":"institution","role_in_article":"Provides quantitative data on decision-making inefficiency costs and executive time waste."},{"name":"Warwick Business School","type":"institution","role_in_article":"Provides longitudinal institutional data on the gap between strategy definers and implementers."},{"name":"SurveyMonkey","type":"institution","role_in_article":"Source of survey data on employee willingness to share honest feedback with managers."},{"name":"Jeff Bezos","type":"person","role_in_article":"Referenced as popularizer of the 'disagree and commit' principle in his 2017 Amazon shareholder letter."},{"name":"Amazon","type":"company","role_in_article":"Cited as an organizational culture that operationalizes 'disagree and commit' as a decision architecture."},{"name":"Intel","type":"company","role_in_article":"Cited alongside Amazon as an origin of the 'disagree and commit' principle."},{"name":"Ricardo Mendieta","type":"person","role_in_article":"Author; provides editorial framing and analytical layer on top of Smoliienko's original observations."}],"tradeoffs":["Speed of execution vs. inclusiveness of deliberation: consensus improves buy-in but slows and diffuses accountability","Founder control vs. scalable decision-making: retaining context in one head is efficient at small scale but becomes a bottleneck at large scale","Celebrating heroism vs. auditing its root cause: recognition maintains morale but normalizes the structural failures that produce the need for heroism","Transmitting directives vs. transmitting reasoning: directives are faster but produce distorted execution; reasoning is slower but produces calibrated judgment","Growth metrics as signal vs. growth metrics as mask: positive surface indicators can hide progressive internal deterioration for months"],"key_claims":[{"claim":"The leader who operated well with ten people built tacit, non-transferable knowledge that stops scaling as the team grows.","confidence":"high","support_type":"reported_fact"},{"claim":"Only 39% of employees feel comfortable sharing honest feedback with their managers, per SurveyMonkey-linked survey data.","confidence":"high","support_type":"reported_fact"},{"claim":"Warwick Business School documented over three years that strategy definers and implementers prioritize differently in consistent ways.","confidence":"high","support_type":"reported_fact"},{"claim":"61% of executives acknowledge at least half their decision-making time is used inefficiently, per McKinsey.","confidence":"high","support_type":"reported_fact"},{"claim":"Decision-making inefficiency can cost large companies over 530,000 lost working days and $250 million in wasted labor per year, per McKinsey.","confidence":"high","support_type":"reported_fact"},{"claim":"Consensus-seeking is a form of leadership evasion — a mechanism to avoid accountability by hiding behind unanimity.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"Organizations that scale without redesigning decision architecture deteriorate progressively while surface growth metrics remain positive.","confidence":"medium","support_type":"inference"},{"claim":"The interval before a crisis — when signals are legible and options remain open — is the defining test of leadership quality at scale.","confidence":"medium","support_type":"editorial_judgment"}],"main_thesis":"Organizational growth does not simply stress existing management models — it inverts their value. Leaders who do not redesign their decision architecture, information flows, and judgment transmission chains in time create systemic inefficiencies that compound silently behind positive growth metrics until the cost becomes structural and difficult to trace.","core_question":"At what point does a leader's proven management model stop scaling, and what must change before the deterioration becomes irreversible?","core_tensions":["Founder identity vs. organizational need: the skills that built the company become the constraints that limit it","Visibility vs. scale: the leader cannot maintain direct context as the organization grows, but the systems to replace that visibility are rarely built proactively","Accountability vs. collaboration: clear decision ownership conflicts with the cultural expectation of collective participation","Speed vs. quality of judgment transmission: faster communication sacrifices the reasoning that makes directives executable correctly","Growth as success signal vs. growth as risk amplifier: the same metrics that indicate success can mask the accumulation of structural dysfunction"],"open_questions":["At what specific team size or management layer count does the redesign of decision architecture become urgent rather than optional?","How do organizations measure the quality of judgment transmission across management layers before the distortion becomes visible in outcomes?","What mechanisms beyond postmortems can surface the root causes of recurrent heroic effort without creating a culture of blame?","How does the 'disagree and commit' principle interact with psychological safety — does it suppress dissent or channel it productively?","Can the financial cost of decision-making inefficiency be measured at the SME level, or does the McKinsey estimate only apply to large enterprises?","What is the minimum viable information architecture that allows a founder to transition from knowing to ensuring decision-makers have what they need?"],"training_value":{"recommended_for":["Founders and CEOs of SMEs transitioning from early-stage to mid-scale operations","COOs and operations leaders responsible for decision-architecture design","Management consultants advising on organizational redesign during growth phases","Investors or board members evaluating leadership quality in portfolio companies at scale inflection points","HR and organizational development professionals designing management layer structures"],"when_this_article_is_useful":["When advising a founder or executive whose team has grown beyond 20-30 people and decision speed has slowed","When diagnosing why a scaling organization is underperforming despite positive revenue or headcount metrics","When designing or auditing information flow and decision-making processes in a growing SME","When evaluating whether a leadership team is ready to manage a significant headcount increase","When building a postmortem or audit framework for recurring operational failures or heroic-effort episodes","When a client is considering whether to implement consensus-based or accountability-based decision protocols"],"what_a_business_agent_can_learn":["How to identify cognitive inertia in leadership as a structural risk, not a personal failure","The distinction between collaboration and consensus as operationally different decision protocols with measurable consequences","How to use recurrent heroic effort as a diagnostic signal for planning and process failures","Why transmitting reasoning behind decisions matters more than transmitting the decisions themselves at scale","How to quantify the financial cost of decision-architecture misalignment using McKinsey benchmarks","The MUM effect as a predictable structural consequence of hierarchy growth without information channel redesign","The 'disagree and commit' principle as a role-clarity mechanism, not an authoritarian posture"]},"argument_outline":[{"label":"1. Cognitive inertia, not incompetence","point":"Leaders fail at scale because they apply mental models calibrated for smaller teams to fundamentally different organizational contexts, not because they lack skill.","why_it_matters":"Misdiagnosing the cause as personal failure prevents the correct intervention: architectural redesign of how decisions and information flow."},{"label":"2. Information distortion as a structural problem","point":"As hierarchy grows, bad news is filtered out (MUM effect) and the leader operates on an outdated picture of reality. Only 39% of employees feel comfortable sharing honest feedback with managers.","why_it_matters":"Leaders who do not build explicit early-signal mechanisms make decisions on stale data, compounding strategic errors over time."},{"label":"3. Judgment transmission degrades across management layers","point":"Strategy loses its reasoning as it passes through intermediate managers, converting intent into instruction and instruction into noise. Warwick Business School data confirms that strategy definers and implementers prioritize differently across three consecutive years of study.","why_it_matters":"Teams technically fulfill directives while failing the underlying objective — a gap that is invisible in output metrics but visible in competitive outcomes."},{"label":"4. Heroism is a diagnostic signal, not a cultural asset","point":"Recurrent heroic effort by employees signals structural failures: poor estimation, undocumented decisions, and processes dependent on individual willingness rather than system design.","why_it_matters":"Organizations that celebrate heroism instead of auditing its root cause normalize the conditions that produce it, making the underlying dysfunction permanent."},{"label":"5. Collaboration vs. consensus is a decision-architecture choice","point":"Collective input improves decisions; transferring the decision to collective agreement paralyzes organizations. McKinsey found 61% of executives acknowledge at least half their decision time is used inefficiently, most often due to unclear decision ownership.","why_it_matters":"The operational cost of consensus-seeking — delayed projects, reopened decisions, uncommitted teams — is measurable and compounds at scale."},{"label":"6. The financial cost of not redesigning","point":"McKinsey estimates decision-making inefficiency costs large companies over 530,000 lost working days and approximately $250 million in wasted labor annually.","why_it_matters":"This reframes the redesign of decision architecture from a leadership development exercise to a financially material operational priority."}],"one_line_summary":"The practices that make a leader effective at ten people become structural liabilities at fifty or ninety, and most organizations fail to redesign their decision architecture before the damage is measurable.","related_articles":[{"reason":"Same author, same leadership category; focuses on how leaders misuse team time — directly complementary to the bottleneck and decision-architecture themes in this article.","article_id":14681},{"reason":"Addresses the structural problem of undefined ownership and accountability in transformation initiatives — mirrors the consensus-as-evasion and unclear-decision-ownership patterns analyzed here.","article_id":14641},{"reason":"Documents the gap between AI investment and organizational capacity to absorb it — structurally parallel to the gap between growth and management model redesign described in this article.","article_id":14761}],"business_patterns":["Cognitive inertia: leaders apply early-stage mental models to fundamentally different organizational contexts","MUM effect: hierarchies that grow without redesigning information channels systematically filter out bad news","Judgment transmission decay: strategy loses its reasoning across management layers, converting intent into noise","Heroism normalization: recurrent exceptional effort is celebrated rather than diagnosed as a planning or process failure","Consensus as evasion: collective decision-making is used to avoid individual accountability rather than to improve decision quality","Silent degradation: organizations deteriorate progressively behind positive growth metrics until the damage is structural"],"business_decisions":["When to stop relying on the founder's tacit knowledge and build explicit information systems","How to redesign information channels so bad news reaches leadership early rather than filtered","Whether to invest in transmitting the reasoning behind decisions, not just the decisions themselves","How to distinguish between collaboration (input without decision transfer) and consensus (decision transfer to the group)","When to apply 'disagree and commit' as a decision protocol versus open deliberation","How to audit recurrent heroic effort as a signal of structural planning failure rather than a cultural strength","When to treat decision-architecture redesign as a financially material priority rather than a leadership development initiative"]}}