Simplification

Complexity Quietly Consumes Margin, Capacity and Leadership Attention

Complexity is rarely a strategy. It is the residue of years of individually sensible exceptions that were never removed.

Written by Steve Kopecky · 6 minute read

Founder & Principal, Compass Performance, Inc.

01

Complexity is added by good decisions

A customer asks for a variant, and the answer is yes. A region needs a slightly different process. An acquisition arrives with its own system, and integrating it fully never reaches the top of the list. A product is kept alive because a long-standing account still orders it twice a year.

Each decision is defensible in isolation. Cumulatively they produce a business carrying more SKUs, more processes, more systems, more meetings, and more exceptions than the value it generates justifies.

Complexity is never approved as a whole. It is approved one reasonable exception at a time.

02

Where the cost actually lands

The cost rarely shows up as a line item. It shows up as a longer quote-to-cash cycle, inventory that will not turn, engineering time absorbed by legacy variants, a finance team producing reports nobody uses, and an executive calendar with no unclaimed hours in it.

The most expensive consumption is attention. Leadership capacity is the scarcest asset in a mid-market business, and complexity spends it on maintenance rather than on the small number of decisions that would actually move the enterprise.

Applied honestly, the 80/20 read is uncomfortable and clarifying: a minority of customers, products, and activities produce the overwhelming majority of value, and a surprising portion of the remainder is consuming more than it returns.

03

Simplification is a decision, not an efficiency program

Cost-cutting trims what already exists. Simplification decides what should exist at all — which customers the business is genuinely built to serve, which products earn their place, which processes are standard and which are legitimately exceptions, and which meetings produce decisions.

That is why simplification has to be led by the executive team rather than delegated. Only the people who approved the exceptions have the authority to remove them.

The result is not a smaller business. It is a business with the same revenue, more margin, faster decisions, and leadership attention pointed at the future rather than at the accumulated past.

Where to look first

  • Revenue and margin concentration by customer, product, and channel.
  • Products or variants kept alive for a single account.
  • Processes with more exceptions than standard cases.
  • Reports produced monthly that no decision depends on.
  • Recurring meetings that generate discussion but no owner, date, or evidence.

Complexity will not remove itself. Left alone, it compounds — and it is paid for in exactly the resources the next stage of the business requires.

Share this

LinkedInX

Interactive exercise

Which complexity is earning its keep?

Click each item, then place it. Complexity is not the enemy — unpriced complexity is.

4 cards left to place.

      The other side of the argument

      Send a question or an insight

      Nothing here is published. Your note goes directly to Steve Kopecky, who reads every one — reader questions decide what gets written next.

      What kind of note is this?

      0 of 4000 characters. Please leave out client names and confidential detail.

      Or email directly

      Aligned to SIMPLIFY™

      Complexity, the vital few, and the removal of what consumes margin.

      Continue reading

      Simplification

      Choose the 80 Before You Design the Enterprise: Building a Front-to-Back Strategy on the Vital Few

      80/20 is not a cost exercise. It is the first strategic design decision — naming the vital few markets, customers, products and channels the enterprise intends to win, and then connecting that choice front to back.

      Organization Design

      Clean Sheet Organization Design: Building the Structure the Strategy Requires

      A clean sheet design starts from the strategy and the vital few opportunities, not from the current org chart. This is the process, the ownership and the SIPOC that governs it.

      Organizational Architecture

      The Eight Culture Types Are Not Types. They Are Eight Reinforcement Patterns Your Design Is Already Running

      The eight culture descriptors in circulation describe what an organization rewards, tolerates and discourages. Read that way they stop being labels to pick and become findings to trace back to the mechanism producing them.

      Program & Project Management

      The Next Phase Is Delivered Across Boundaries — Which Is Why Program Management Becomes a Capability, Not a Role

      The functional strength that carried an organization to its current size is the same boundary its next phase has to cross. Program and project management is how work becomes deliverable across those boundaries.

      Front-to-Back 80/20

      Chasing Revenue, Paying for Complexity — Global Growth Dynamics and the Twenty Percent That Actually Earns the Growth

      Growth pursued as revenue funds the vital few and the trivial many on the same terms. Here is the cascade that follows, the quartile and quad decision that answers it, and the mental strength a leadership team needs to change a design that earned its respect.

      Mental Fitness

      The Brain Under Pressure: Regions, Roles and What Training Actually Changes

      The regions involved when pressure hits, what each one is known for, and why mental fitness exercise is physical development of neural pathways rather than positive thinking.

      Mental Fitness

      The Team Under Pressure: Saboteurs, the Five Dysfunctions, and the Trust a Growth Decision Requires

      The five dysfunctions are not five separate problems. They are what a room full of untrained pressure responses reliably produces — and they are trainable.

      Program & Project Management

      Programs Rarely Slip on Schedule. They Slip at the Hand-Off Nobody Owns.

      By the time a program date moves, the real failure is weeks old. It happened at a hand-off between two functions, where the work left one owner and arrived at nobody.

      Program & Project Management

      “Herding Cats” Is Not a People Problem. It Is Undeclared Authority.

      You are accountable for an outcome and you manage nobody who produces it. The advice is to influence without authority. The honest read is that authority was never declared.

      Personal Effectiveness

      A Message on Personal Habits: The Private Architecture Behind Every Executive Result

      Architecture determines performance — and that is as true of a person as it is of an enterprise. A long-form message on habit design, 80/20 daily management, and the self-talk that governs behavior.

      Organizational Architecture

      Don't Replace What Works: Architect the Constraint

      An execution system can surface a constraint, focus attention on it and force the conversation. Some constraints still require redesigning the system that keeps producing the condition.

      Private Equity & Enterprise Value

      The Next Acquisition Is Not the Growth Strategy: Talent Architecture as the Missing Operating System in Private Equity–Backed Industrial Growth

      Acquisitions buy revenue, customers, capabilities, geography and capacity. They do not create an enterprise capable of repeatedly absorbing growth. The talent architecture decides that.

      Enterprise Architecture

      The Vital Few: 80/20 Talent Strategy and What a Small-Market Ballclub Keeps Teaching

      Most talent strategies are spread evenly across every open requisition and every development program. The organizations that outperform their resources do the opposite: they find the vital few capabilities that carry the strategy, and they architect everything around them.

      Enterprise Architecture

      Micromanufacturing: The Conditions Under Which the Small Footprint Becomes the Stronger Design

      For thirty years the cost curve rewarded the biggest possible plant in the cheapest possible place. The reordering of global supply chains has changed what that curve measures — and made the small, near-demand plant a defensible strategy rather than a compromise.

      Organizational Architecture

      The Architecture That Created Today's Success Rarely Produces Tomorrow's Results

      The structure that carried a business to its current size is usually the constraint on its next stage. That is a design problem, not a people problem.

      Organizational Architecture

      The Engagement Layer: Why Slack Sits at the Center of Every Compass Partnership

      Most advisory relationships depend on quarterly meetings and email chains. Compass designs the engagement as an operating layer — and Slack is where it lives.

      Growth & Value Creation

      The Second Curve Begins Before the First One Ends

      The right moment to build what comes next is while the current business is still strong — which is precisely when no one feels the need to.

      Simplification

      FOCUS: The Vital Few Constraints That Create Economic Value

      FOCUS is not doing less. It is concentrating effort on the customers, products, and markets that produce disproportionate value — and removing the complexity mirror they cast inside the organization.

      Organizational Architecture

      What Is Enterprise Business Architecture — and Why Does It Determine Performance?

      Enterprise business architecture is the deliberate design of how an organization decides, aligns, and executes. It sets the ceiling on performance long before effort does.

      Organizational Architecture

      The Ten Elements of an Enterprise Architecture — and Why They Only Hold Together

      Strategic intent, simplification, leadership, governance, planning, cadence, decision rights, performance, enabling systems, and renewal. Designed together, or not designed at all.

      Strategy & Execution

      Architecture vs. Improvement: Why Better Execution Cannot Fix a Flawed Design

      Improvement makes the current system perform closer to its limit. Architecture changes the limit. Confusing the two is the most expensive mistake in the mid-market.

      Organizational Architecture

      Every Organization Is Producing Exactly What Its Design Allows

      Decision rights, cadence, reporting lines, incentives and leadership habits are not background. Together they are the machine producing the number on the books.

      Organizational Architecture

      Effort Cannot Solve a Design Problem

      Pressure produces a short improvement, then the system pulls the result back to where the architecture says it belongs.

      Organizational Architecture

      Architecture Is Designed, Not Discovered

      The work is concrete: name the few outcomes that matter, place each decision where it is properly made, remove the complexity consuming margin, and rebuild the cadence so commitments close.

      The CEO / Owner Lens

      The Chief Executive Is Not Supposed to Be the Integration Mechanism

      When strategy only reaches the work through the chief executive, growth adds volume to an unresolved design. The fix is structural, not personal.

      The CHRO / People Lens

      Turnover Is Usually a Structural Reading, Not a Hiring Result

      When roles, capability, managers and recognition point in different directions, capable people leave — and the organization reads it as a recruiting problem.

      The Operations Lens

      Performance That Depends on Who Is on Shift Is Not Performance

      Where the process is undefined, capable people carry it. The result looks like variable performance and is read as a discipline problem.

      The ERP / Systems Lens

      An ERP Program Is a Process Decision Wearing a Technology Budget

      Systems enable the management system; they never replace it. Configuring before the process is designed automates the current mess at scale.

      The Exit / Succession Lens

      A Buyer Discounts Precisely What the Owner Cannot Hand Over

      Transferable value is documented processes, governed data, named successors and results that hold when the founder is not in the room.

      The Leadership Team Lens

      A Team That Meets Often and Decides Rarely Is Compensating for a System

      When reviews end in discussion rather than dated commitments, the same root cause is rediscovered every quarter.

      The AI & Data Lens

      Pilots Demonstrate Capability. Designed Processes Produce Results.

      AI moves a measure inside a process. Where the process is undesigned and the data ungoverned, there is nothing for it to move.

      The Transformation Lens

      Exhaustion Is Routinely Misread as Resistance

      Change fails at the point of absorption far more often than at the point of design. Capacity, honesty about recent change, and reinforcement decide the outcome.

      The Strategic Program Lens

      Becoming Efficient at Work You Never Chose

      Portfolios fail at intake far more often than in delivery. Unranked work consumes the capacity that strategy was supposed to direct.

      The Next-Curve Lens

      The Next Curve Is Absorbed by the People Already at Capacity

      A next curve is designed on paper and delivered by an organization that must also run the current one. Readiness is whether the system can carry both.

      Entrepreneurial Growth

      Your Expertise Built the Business. What Will Help It Scale?

      The knowledge that built the business is not automatically the operating system that will scale it. What the owner with traction actually needs next.

      Entrepreneurial Growth

      The Founder Under Pressure: Mental Fitness as an Entrepreneurial Operating Advantage

      The hardest owner decisions arrive under pressure. Mental fitness is not therapy and not a Compass pillar — it is the human operating layer that decides the quality of the choice.

      Personal Effectiveness

      Becoming Who the Future Requires

      Why aspiration without affirmation rarely becomes transformation — and how to build the identity, choices and evidence that turn intention into capability.

      Growth & Value Creation

      When Growth Outruns the Operating Model

      A step-change opportunity is not a hiring problem. It is a scale discontinuity — and it is won or lost in the sequence that turns a demand signal into committed capacity.

      Simplification

      The Gardener's Choice

      Two gardeners begin the same spring with the same plot, the same water and the same hours. One treats every seed equally. One chooses. A short fable about where enterprise value actually comes from.

      The next step

      See this in your own organization.

      Reading about the operating system is one thing. Seeing yours clearly is another. Start with where you actually are.

      Not sure where to start?

      Three questions, and we point you to the right instrument.

      Under a minute. From this page, most leaders begin with The organization.