Your Complexity Is Not Scale. It Is a Growth Tax.

# Your Complexity Is Not Scale. It Is a Growth Tax. **Direct answer:** More products, markets, layers, approvals, and projects do not automatically make a company more mature. They often make it slower, harder to manage, and less profitable. Founders usually add complexity for good reasons. A customer asks for a feature. A new market needs a local process. A team asks for another manager. Sales wants another pricing option. The board wants another initiative. Each decision can look small. Together, they create a company that needs more people to produce less clarity. Bain surveyed more than 900 global executives and found that nearly 70% admitted complexity was hurting profits. Bain says companies that find the right balance can cut costs by as much as 35% and increase sales by up to 40% [1]. The controversial point is simple: **your company may not need more capacity. It may need fewer exceptions.** ## Complexity hides inside success Complexity is hard to see because it often arrives wearing the clothes of growth. A new product is called innovation. A new approval is called control. A new role is called leadership. A new market is called expansion. A new project is called ambition. But customers do not pay for your internal complexity. They pay for the value they receive. If your company needs five meetings to approve a price, three teams to launch a feature, and four systems to know which customer owns what, you do not have scale. You have an operating tax. Bain describes three forms of complexity: * **Product complexity:** too many products, options, packages, SKUs, or configurations. * **Organisational complexity:** too many layers, roles, committees, and overlapping accountabilities. * **Process complexity:** too many steps, approvals, handoffs, tools, and exceptions. They reinforce one another. Product variety creates process work. Process work creates new roles. New roles create more decisions. More decisions create more meetings. More meetings reduce the time available to serve customers. ## The complexity test For every product, feature, market, approval, and project, ask five questions: 1. Do customers value this enough to pay for it? 2. What recurring cost does it create? 3. Who owns the result? 4. What other work does it delay? 5. If we removed it, what would actually break? If no one can answer these questions, the company is carrying complexity without a business case. ## Complexity-as-scale versus managed simplicity | Operating question | Complexity mistaken for scale | Managed simplicity | |---|---|---| | Product range | Add options for every request | Keep variety customers value | | New feature | Build because a loud customer asked | Test demand, margin, and strategic fit | | Organisation | Add layers to solve every problem | Give one owner clear authority | | Decision | Invite more people for safety | Match input to decision risk | | Process | Add steps after every mistake | Remove root causes and keep controls simple | | Projects | Start many initiatives | Fund a few measurable priorities | | Sales model | Add specialists and variants | Standardise the core, tailor only where paid for | | Forecasting | Model every exception | Use a small set of visible drivers | | Meetings | Discuss status across many teams | Decide, assign, and review outcomes | | Scale | Increase headcount and coordination | Increase leverage and repeatability | ## Why more projects can mean less progress Bain described a large natural-resources company with 483 process-improvement projects. Only 25 were expected to have a significant impact. The company was not short of ideas. It was short of focus. After reducing complexity and concentrating resources, operating income rose by more than 20% [2]. This is the project version of founder denial. Leaders say everything is important because stopping a project feels like admitting that the earlier decision was wrong. The result is a portfolio where teams are busy, executives are informed, and the company moves slowly. A project is not progress because it has a leader, a budget, and a launch date. It is progress only when it changes a customer or business result. ## Why more managers can mean less accountability As companies grow, leaders often add layers to reduce risk. The opposite can happen. Bain described a pharmaceuticals company with an average of two research employees per supervisor and eight layers between the front line and the CEO. Competitors averaged 4.2 employees per manager and six layers. Aligning the structure with competitors saved the company as much as $500 million a year [2]. The point is not that every company needs a wider span of control. The point is that a layer is not free. It can slow information, blur ownership, and create another place for decisions to wait. McKinsey found that product, functional, and regional complexity can cloud accountabilities and increase the number of decision makers. Its research found that 72% of senior-executive respondents said bad strategic decisions were about as frequent as good ones or were the prevailing norm in their organisation [3]. More voices do not automatically create better decisions. Sometimes they create decisions that nobody owns. ## The sales model can become a complexity machine Bain analysed the 2003–2011 income statements of roughly 200 large US companies in healthcare, technology, and financial services. More than half increased sales and marketing expense as a percentage of revenue or failed to show expected scale benefits [4]. The problem was not simply higher wages. Sales models became more complex. Companies added product variants, specialists, solution teams, market coverage, and customer-specific rules. The sales organisation became harder to operate, while customers received a less coherent experience. Bain found that 15% more high-performing companies than low-performing companies had built a differentiated capability to deploy selling resources to high-value opportunities [4]. That is the difference between useful complexity and waste. High-performing companies do not remove all specialisation. They decide where it creates enough value to justify its cost. ## The founder’s complexity ledger Create one list of the exceptions your company carries. Include products, features, pricing plans, customer promises, approval steps, management layers, internal projects, reports, tools, and meetings. For each item, record: * The customer or business value it creates. * The annual cost in people, time, systems, and error risk. * The single person accountable for the outcome. * The decision that created it. * The evidence that it still deserves to exist. * The date when it will be reviewed or removed. This changes the conversation. You stop asking, “Can we support this?” and start asking, “Is this worth the complexity it creates?” ## Five rules for reducing the growth tax ### 1. Raise the return hurdle Bain recommends requiring a higher rate of return for new products and variations. A request should compete for resources against the cost of keeping the company simple [1]. ### 2. Delay complexity Add customisation as late as possible in the value chain. Keep the core platform, process, and data model standard. Tailor only where the customer values the difference and pays for it. ### 3. Assign one decision owner Input can be broad. Accountability cannot. One person should own the decision and the result. Others advise, challenge, or execute. ### 4. Kill projects, not just costs A cost cut that leaves the same project portfolio usually creates hidden overload. Stop low-impact projects. Move the best people to the few priorities that matter. ### 5. Review complexity like cash Cash has an owner, a forecast, and a review. Complexity should have the same discipline. Track new exceptions, retired exceptions, decision speed, project completion, margin by product, and time spent in coordination.

## Frequently asked questions ### Is complexity always bad for a growing company? No. Some complexity creates customer value or helps a company serve a market. The problem is unmanaged complexity: cost that customers do not value and leaders do not measure. ### How can a founder tell if the company is too complex? Look for slow decisions, repeated meetings, unclear ownership, custom work, too many projects, low product margins, rising support load, and employees who cannot explain the standard way to do the work. ### Should a startup remove product options? Remove options that few customers value or that create more cost than revenue. Keep options that attract valuable customers and can be delivered through a standard platform. ### How many projects should a leadership team run? There is no universal number. The test is whether the team can name the expected result, owner, decision date, and resource trade-off for every project. If not, the portfolio is too large. ### Does simplification mean reducing ambition? No. Simplification concentrates ambition. It gives the company fewer priorities, faster decisions, and more resources for the work that can create durable value. ### Who owns organisational complexity? The CEO and executive team own the system. Every leader owns the complexity created by their products, processes, people, and exceptions. No function can outsource the cost to everyone else. ### What is the fastest complexity to remove? Start with work that nobody can connect to customer value: duplicate reports, inactive projects, unused tools, unnecessary approvals, low-volume product variants, and meetings without decisions. ## Final verdict Scale should increase leverage, not the number of exceptions. **If customers are not paying for your complexity, your margin is.** ## References [1] [Bain — Cutting through complexity](https://www.bain.com/insights/cutting-through-complexity/) [2] [Bain — The power of managing complexity](https://www.bain.com/insights/the-power-of-managing-complexity/) [3] [McKinsey — Untangling your organization’s decision making](https://www.mckinsey.com/capabilities/people-and-organization/our-insights/untangling-your-organizations-decision-making) [4] [Bain — Is complexity killing your sales model?](https://www.bain.com/insights/is-complexity-killing-your-sales-model/)