The CEO / Owner Lens
The Chief Executive Is Not Supposed to Be the Integration Mechanism
In most mid-market enterprises the chief executive is the last remaining integration layer. That arrangement is invisible while it works and expensive the moment the business grows.
Written by Steve Kopecky · 6 minute read
Founder & Principal, Compass Performance, Inc.
01
The tell is where integration happens
Ask a leadership team where the functions actually come together and the honest answer is often a person rather than a mechanism. Commercial commitments meet operational capacity in the chief executive's inbox. Trade-offs between margin and service are settled in a hallway. Priorities are reconciled because one person holds the whole picture in their head.
This is not a failure of leadership. It is the residue of an earlier design that worked extremely well at a smaller scale. One integrating mind was faster than any process. What changes is arithmetic: every additional product, site, channel and executive multiplies the number of integrations, and only one of them can be resolved at a time.
The symptom set is consistent. Decisions travel upward instead of outward. The executive calendar fills with items that carry no decision rights below it. Good managers wait rather than act, because waiting is rational when authority is ambiguous.
Growth does not break a company. It applies volume to whatever the design has left unresolved.
02
Three design decisions, not three initiatives
First, direction has to be translated into decisions. A strategy that cannot be stated as a small set of trade-offs — what we will do less of, which customers we will disappoint, what we will not fund — is a communication artefact, not a governing instrument.
Second, accountability has to be singular. Every outcome the enterprise manages against needs one name, and that name needs the authority to spend, staff and stop. Shared ownership is the polite form of no ownership.
Third, the leadership cadence has to hold without the chief executive in the room. If the weekly and monthly reviews only produce decisions when the CEO attends, the cadence is theatre and the CEO is the operating system.
03
What a load-bearing design feels like
Within a quarter of the redesign, three things move. Decisions that used to stall at the top get made two or three levels down, because the decision rights are written and known. The executive meeting shortens, because it is reviewing exceptions rather than reconstructing context. And initiatives that were quietly consuming capacity without an owner stop being funded.
The chief executive's role changes shape: from resolving the enterprise every week to governing the design that resolves it. That is the difference between a business that can be scaled and a business that can only be worked harder.
Exhibit
Exhibit — The one-page decision rights test
Take the six decisions that most often reach the chief executive. Fill this in from memory, in one sitting, with the leadership team present. Any row that cannot be completed in under a minute is the design defect.
| Decision | Decided by | Consulted | Escalates when | Evidence used |
|---|---|---|---|---|
| Pricing exception above threshold | One name | Finance, Sales | Margin below floor | Deal margin sheet |
| Capital spend under $250k | One name | Operations | Outside plan | Business case |
| Hiring outside approved plan | One name | People | Adds fixed cost | Capacity model |
| Stopping an initiative | One name | Sponsor | Benefit lapses | Charter and benefit |
| Accepting an out-of-standard order | One name | Operations | Schedule risk | Capacity board |
| Changing a committed date | One name | Customer lead | Contract impact | Delivery review |
Blank cells are not an administrative gap. They are the reason the decision arrives at the chief executive.
How this shows up in the business
- Cross-functional trade-offs are settled by the chief executive rather than by a mechanism.
- More than one name appears against the outcomes the enterprise is managed on.
- The leadership meeting loses its decision quality when the CEO is traveling.
- Managers describe themselves as waiting for direction rather than exercising authority.
- Growth in revenue has produced a more than proportional growth in executive workload.
The question a chief executive should be able to answer is not whether the team is working hard enough. It is whether the enterprise is designed to carry what is about to be asked of it.
Interactive exercise
The integration mechanism
Click the move that removes the dependence rather than relocating it.
Nothing cross-functional resolves without the chief executive in the room.
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 FOUNDATION™
Who are we, and what business are we actually trying to build?
Present reality, leadership capability, purpose and organizational health.
Article
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.
11 minute read
Article
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.
9 minute read
Assessment
FOUNDATION™ Diagnostic
A structured read on leadership capability, clarity of purpose, trust and organizational health.
Maturity read on screen, a print sheet, and an emailed copy.
Assessment
Lifecycle Stage Diagnostic
Fifteen statements that locate the business on the curve — Honeymoon through Reinvention — and name the binding constraint.
Stage placement, constraint, and the first move for that stage.
Instrument
30 / 60 / 90 Day Action Plan
Turns the lifecycle result into sequenced work: the stage supplies the architectural move, the lowest-scoring domain supplies what removes the constraint. Owners, dates and check-off included.
A checkable plan on screen and a board-quality PDF of the three horizons.
Instrument
Lifecycle Before & After Sheet
Holds the diagnostic result as the before, the stage and domain targets being architected as the after, the operating measures the change is judged against, and the reinvention actions carried from the ninety-day plan.
A one-page board-quality before-and-after PDF, plus an emailed copy.
Podcast
Kristina George — How an office manager became an owner leading a team of eighteen.
Kristina George describes the move from operator to owner and the decisions that made it hold. The conversation examines anchoring the agency on explicit values, investing in employee engagement, and simplifying the operating model so growth did not dilute the culture.
Podcast
Mike Domitrz — How a mission born from tragedy became a leadership standard.
Mike Domitrz shares the origin of The Center for Respect after his sister's assault in college, and how the work grew into a program trained across universities, high schools, the military, and businesses. The conversation examines how respect becomes an observable leadership behavior rather than a value on a wall.
Guide
Read the Curve Before You Build the Next One
The second curve is a timing decision before it is a strategy decision. Most companies read the curve years late, at the point where the options are cheapest to see and most expensive to take.
7 minute read
Engagement
Compass Executive Forums
A confidential peer table of owners and executives working the same architecture, month after month.
Monthly, by invitation
Engagement
The Compass Enterprise Architecture™
The core architecture Compass designs and installs with a leadership team.
The authoritative source
Continue reading
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 DesignClean 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 ArchitectureThe 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 ManagementThe 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/20Chasing 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 FitnessThe 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 FitnessThe 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 ManagementPrograms 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 EffectivenessA 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 ArchitectureDon'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 ValueThe 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 ArchitectureThe 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 ArchitectureMicromanufacturing: 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 ArchitectureThe 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 ArchitectureThe 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 CreationThe 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.
SimplificationComplexity 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.
SimplificationFOCUS: 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 ArchitectureWhat 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 ArchitectureThe 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 & ExecutionArchitecture 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 ArchitectureEvery 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 ArchitectureEffort 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 ArchitectureArchitecture 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 CHRO / People LensTurnover 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 LensPerformance 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 LensAn 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 LensA 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 LensA 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 LensPilots 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 LensExhaustion 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 LensBecoming 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 LensThe 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 GrowthYour 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 GrowthThe 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 EffectivenessBecoming 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 CreationWhen 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.
SimplificationThe 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.