Simplification

FOCUS: The Vital Few Constraints That Create Economic Value

Every leadership team has more opportunities than capacity. FOCUS is the discipline of choosing where the next unit of effort produces the highest return — and where the organization is already paying for complexity it never designed.

Steve Kopecky · 5 minute read

Before: everything looks like a priority

Most mid-market enterprises do not have a strategy problem. They have a concentration problem. The customer list is long, the product catalogue is longer, and every segment has a champion inside the building. Resources are allocated by history, by politics, and by the fear of disappointing a relationship that was built over years.

The result is a leadership team spread thin. Every function has its own initiative list. Capital, talent, and attention are divided across too many bets, and none of them receives the full weight of the organization. Growth feels harder than it should because the enterprise is trying to grow in every direction at once.

The 80/20 lens is what makes the pattern visible. A small set of customers, products, geographies, or use cases produces the majority of economic value. The rest consumes a disproportionate share of capacity and often returns little more than the comfort of keeping an old decision in place.

A business that serves every customer equally is a business that serves no customer fully.

After: the vital few carry the weight

FOCUS begins with an honest concentration curve. Which 20% of customers, products, or markets produce 80% of value? Which segments would the enterprise protect at all costs? The answer is usually uncomfortable, because it names the accounts, SKUs, and regions that have been carried for reasons other than economics.

Once the curve is named, the architecture changes. Decision rights, capital allocation, talent deployment, and management attention are redirected toward the high-leverage points. The enterprise stops subsidizing mediocrity and starts compounding capability where it matters.

This is not cost-cutting. It is value engineering. The same revenue becomes more profitable because the cost to serve, the exception load, and the organizational drag are concentrated in the places that actually justify them.

The complexity mirror

The external 80/20 curve has an internal reflection. A minority of customers, products, or contracts often generates the majority of internal complexity: custom terms, exception handling, manual workarounds, system variants, and meetings that exist only to manage the exception.

This 20% is frequently invisible on the P&L because its cost is buried in overhead, rework, and lost capacity. A customer who looks profitable on a revenue report may be consuming engineering, operations, and finance hours that never get attributed back to the account. A product that still sells may be held together by a workflow that no one would design today.

FOCUS requires both sides of the mirror. The value curve shows where to concentrate. The complexity curve shows what to simplify, standardize, or retire. Optimizing only for revenue concentration leaves the organization fragile. Optimizing only for complexity makes it timid. The discipline does both.

Exhibit

The two concentration curves — and where action belongs

Value concentrates in one small group. Complexity concentrates in another. FOCUS requires reading both, because the two groups are rarely the same.

Mirror one — outside in

Economic value concentration (80/20)

Population

The vital few
~20% of customers, products, markets
The long tail
~80% of customers, products, markets

Share of gross margin

80% of value
20% of value

A minority of customers, products and markets produces the majority of economic value. This is the curve that tells you where the next unit of capital, talent and attention should go.

Mirror two — inside out

Internal complexity concentration (20/80)

Population

The complexity few
~20% of accounts, SKUs, contracts
Standard work
~80% of accounts, SKUs, contracts

Share of internal complexity

80% of complexity
20% of complexity

A minority of customers, products and contracts generates the majority of exceptions, custom terms, manual workarounds and system variants. This cost is buried in overhead, so it never appears beside the revenue that caused it.

Where to focus action

High value · low complexity

Concentrate

Redirect capital, talent, decision rights and management attention here. Protect this capacity from everything below.

High value · high complexity

Standardize, then price

Keep the revenue, remove the variation: platform-engineer the exception into a common configuration, or price it to cover its true cost to serve.

Low value · high complexity

Simplify or retire

Move to self-service and standard terms, convert to partner-led, or exit with discipline. This is the capacity that funds the concentration above.

Reading only the value curve leaves the organization fragile. Reading only the complexity curve makes it timid. FOCUS reads both, then acts on the overlap.

What the trade-off looks like in practice

Concrete decisions make FOCUS real. Without them, the 80/20 curve remains a chart on a screen and the complexity mirror stays a conversation. Here are three typical trade-offs and how the discipline changes the decision.

Customer concentration

The account that looks like revenue and feels like overhead

A $50M industrial distributor discovers that 12 customers produce 60% of gross margin but only 20% of support tickets. The remaining 180 customers produce 25% of margin and consume 55% of support, credit, and expediting hours. The decision is not to fire the tail. The decision is to stop treating every account the same: assign dedicated account architecture and inventory priority to the 12, and move the long tail to a self-service catalog with minimum order thresholds and standard terms. The margin profile improves because capacity is reallocated, not because revenue is rejected.

Product portfolio

The SKU that still sells — and still consumes the floor

A manufacturer carries 40 SKUs. Eight of them generate 75% of gross profit and flow through common tooling. Six long-tail SKUs generate 8% of profit but 45% of engineering change orders, floor changeovers, and quality holds. The trade-off is not sentiment versus data. The trade-off is whether the enterprise is willing to platform-engineer those six into a common configuration, raise price to cover true cost, or retire them and free the floor for the eight. The right answer depends on strategy, but the wrong answer is to keep all 40 on equal footing.

Market / geography

The region that demands customization the market will not pay for

A services firm operates in five regions. Two regions produce 80% of revenue with a shorter sales cycle and standard delivery. One region produces 8% of revenue but consumes 25% of delivery capacity because every engagement requires local customization, separate contracting, and exception pricing. The FOCUS decision is to treat the two high-leverage regions as the growth core and convert the laggard into a partner-led or referral model — or exit with discipline. The alternative is to let the 8% region dilute the capacity that could compound the 80%.

What FOCUS asks of leadership

FOCUS cannot be delegated to a continuous-improvement team. It requires the executive team to make explicit choices about what the business is built to do and what it is no longer willing to carry. Those choices are structural, not administrative.

The test is whether the organization can stop doing something meaningful. If the answer is always no, the enterprise is not focused — it is preserved. Preservation feels safe in the short term and becomes expensive as the market moves past the accumulated weight.

Done well, FOCUS produces a shorter initiative list, faster decisions, more available leadership attention, and a business that can grow without adding proportionate complexity. The vital few constraints become the load-bearing design. Everything else is either standard or gone.

Where to look first

  • Revenue and margin concentration by customer, product, and channel.
  • The accounts or products that generate the most internal exception handling.
  • Initiatives that would not survive if only the top three outcomes were funded.
  • Meetings and reports that exist to manage complexity rather than create value.
  • Leadership attention spent on low-leverage decisions that should be standard.

FOCUS is the courage to let the right things carry the full weight of the organization — and to remove the rest before its complexity becomes the architecture.

Share this

Share on LinkedIn

Aligned to SIMPLIFY™

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

Continue reading

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.

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

Complexity Quietly Consumes Margin, Capacity and Leadership Attention

No one approves complexity. It accumulates one reasonable decision at a time, and it is paid for in margin, speed, and executive attention.

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.

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.