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.
Written by Steve Kopecky · 5 minute read
Founder & Principal, Compass Performance, Inc.
01
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 catalog 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.
02
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.
03
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.
Concentration diagram: economic value clusters in roughly 20% of customers, products and markets, while internal complexity clusters in a different ~20% of accounts, SKUs and contracts. FOCUS compares both curves to redirect capital, talent and attention to the high-value, low-complexity targets.
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.
Decision rule
If the next decision does not increase concentration on the high-value, low-complexity overlap, defer it until it does.
04
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%.
05
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.
Interactive exercise
Choosing the vital few
One click. Which list is a focus decision?
A leadership team leaves an offsite with its priorities for the year.
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.
Aligned to SIMPLIFY™
What deserves our attention?
Complexity, the vital few, and the removal of what consumes margin.
Article
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.
6 minute read
Article
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.
7 minute read
Instrument
5S Audit & Plan
Scores the current state of a work area and builds the plan, with before-and-after measures for search time, usable space and items removed.
Board-quality audit and plan sheet, print or email.
Instrument
5S Implementation Checklist
The Red Tag event and 60-minute execution roadmap, translated to your setting — shop floor, office, classroom, home.
Setting-specific checklist sheet, print or email.
Podcast
Chad Ritterbusch — How a lean marketing function earns its budget in a mid-market company.
Chad Ritterbusch traces a 30-year arc from large agencies to building TRG for Midwest small and mid-market companies. The conversation covers cash-flow discipline, sequencing the vital few go-to-market activities, using the BCG matrix to sharpen focus, and where AI actually creates leverage inside a small marketing team.
Podcast
Max Meinerz — How a support platform lets dental practitioners stay clinical.
Max Meinerz explains the founding logic of Ascendent Health Partners: a business model that separates clinical work from operational drag so practitioners can concentrate on the patients in front of them. The conversation examines the economics, the service model, and what has to be centralized versus left local.
Guide
Simplify Before You Scale
Scaling a complex system multiplies the complexity, not the result. The transition every growing company misses is subtraction before addition.
8 minute read
Engagement
The Compass Enterprise Architecture™
The core architecture Compass designs and installs with a leadership team.
The authoritative source
Related insights
Where this reading continues
- Simplification
Complexity Quietly Consumes Margin, Capacity and Leadership Attention
The cost side of the mirror: how unmanaged complexity quietly takes the margin the vital few create.
6 minute read → - Strategy & Execution
Architecture vs. Improvement: Why Better Execution Cannot Fix a Flawed Design
Why concentrating effort is a design decision, not a productivity push.
8 minute read → - Organizational Architecture
Effort Cannot Solve a Design Problem
What happens when a leadership team answers a complexity problem with more work.
6 minute read → - The Operations Lens
Performance That Depends on Who Is on Shift Is Not Performance
The operating read: flow and decision rights redesigned around the vital few.
5 minute read → - Organizational Architecture
Every Organization Is Producing Exactly What Its Design Allows
The principle underneath FOCUS — the design decides what results are available.
6 minute read →