Why Compass Exists

The Compass Enterprise Architecture was not designed in a classroom. It was assembled from what held under pressure.

Steve Kopecky spent twenty-five years operating at the intersection of leadership, organizational development, operational transformation and business performance — Navy officer, then senior operating and executive roles across industrial, manufacturing, privately held and private-equity-backed companies. Every discipline in the framework exists because a real organization proved it was missing. This page is the origin of that architecture, not a career journey.

Begin a Confidential Conversation

The origin

Five conditions. One architecture.

Read down the column. Each environment taught one thing that organizations were missing; each of those became a discipline of the Compass Enterprise Architecture.

  1. U.S. Navy

    Active duty · leadership under consequence

    What it proved

    Readiness is a standard, not an intention. Preparation, accountability and calm judgment are architected before the pressure arrives — or they are absent when it does.

    What it became

    FOUNDATION™

    Truth, trust, standards and readiness established before anything is optimized.

  2. Human behavior & organizational development

    Executive assessment · succession · development architecture

    What it proved

    Capability was almost never the missing ingredient. What was missing was a system that equipped leaders to keep pace with the strategy they had signed up to execute.

    What it became

    LEAD™

    Leadership capability built to operate the system, with decision rights made explicit.

  3. ITW and front-to-back 80/20

    Simplification · Lean Six Sigma capability

    What it proved

    Complexity consumes margin quietly. Inside an organization that already believed in simplification, disciplined focus produced growth from the right customers and EBITDA that held.

    What it became

    SIMPLIFY™

    Remove what does not create value — product, customer and process, front to back.

  4. PE-backed and global enterprise leadership

    $100M+ P&L · four continents · transformation office

    What it proved

    When stated values and daily behavior diverge, the enterprise pays in years, not quarters — and growth that depends on heroics cannot be transferred to anyone.

    What it became

    GROW™

    Scale what works and transfer ownership, so results survive the people who built them.

  5. Enterprise transformation

    Announcement to sustained adoption

    What it proved

    Initiatives were announced, resourced and celebrated while the daily work never changed. Nothing holds without a renewal loop that re-reads reality on a cadence.

    What it became

    ARC™

    Assess, Refine, Commit — the renewal engine running across the whole system.

Compass is the integrated architecture built from those five conditions — one operating system, not a collection of the lessons that produced it.

See the Compass Enterprise Architecture

The record

The enterprises where this architecture was proven

Compass architects how organizations operate — and equips leaders to sustain that architecture.

Illinois Tool Works (ITW)Global diversified industrial manufacturer
Front-to-back 80/20 simplification and global transformation — product, customer and process portfolios rebuilt around what actually earns its keep.
SchneiderLarge-scale North American transportation and logistics
Enterprise operating discipline and leadership capability inside a high-volume, execution-driven business where the daily cadence is the strategy.
ManitowocGlobal capital-equipment manufacturer
Organizational redesign, leadership readiness and transformation-office leadership across multi-site, multi-country operations.
United States NavyActive-duty officer
Readiness, preparation and accountability under real consequence — the standard the Compass Enterprise Architecture is still built to.

  • 25+ years

    Operating and executive leadership

  • 4 continents

    Europe, Asia, North and South America

  • $100M+

    Enterprise P&L accountability

  • ERP

    Enterprise system deployment and adoption

  • 1,000+

    Leaders assessed, developed and readied

  • 80/20 · Lean Six Sigma

    Front-to-back deployment

Steve Kopecky, Founder and Strategy and Performance Architect at Compass Performance, at his desk with enterprise operating architecture drawings

Steve Kopecky

Founder & Strategy and Performance Architect

Why the architect matters

Four reasons the framework holds — none of them a methodology.

  1. 01

    He has run the system, not studied it.

    Active-duty Navy officer, then senior operating and executive roles in industrial, manufacturing, privately held and PE-backed companies — accountable for the numbers, not adjacent to them.

  2. 02

    He works on the architecture, not the symptoms.

    Decision rights, structure, cadence, leadership capability and execution are treated as one system — which is why the results hold after the engagement ends.

  3. 03

    He is credible in the boardroom and on the floor.

    Four continents, five years in France, two in Bahrain, and enough time in blue-collar environments to know respect there is earned, not assumed.

  4. 04

    He leaves business architects, not dependency.

    The capability transfers to your leaders. Success is measured by what the team can architect without an adviser in the room.

The record

The conditions this architecture was built and tested under.

25+years
Operating and executive leadership
4continents
Global operating experience
1,000+leaders
Assessed, developed and readied
$100M+P&L
Enterprise scope led
80/20and Lean Six Sigma
Front-to-back deployment
5disciplines
One integrated architecture

Rearchitecting, in practice

Organizations Steve has worked alongside.

Client identities are withheld by agreement. Each example is labeled by evidence tier; named references are provided during a confidential conversation.

Anonymous client story

Global industrial · growth strategy

Present reality
A new strategy, a new code of conduct and a world-class leadership development system were each strong on their own — and the leaders running them were not elevating their thinking at the pace of the strategy.
What was re-architected
Leadership capability, executive assessment and development were rebuilt as one architecture tied directly to the strategy the team had signed up to execute.
Outcome
The engagement made the real constraint visible: capability was never the missing ingredient — the system equipping leaders was.

Anonymous client story

Manufacturing · 80/20 front to back

Present reality
Acquisition pressure was pulling the leadership team away from the operating model that had built the enterprise, while complexity in the customer and product portfolio quietly consumed margin.
What was re-architected
The team held its disciplined price ceiling, walked from the deal, and redeployed front-to-back 80/20 across customers, products and processes.
Outcome
Top-line growth came from the right customers, and EBITDA expanded because complexity was no longer paid for out of margin.

Anonymous client story

PE-backed portfolio company · leadership architecture

Present reality
The sponsor's thesis and stated values were sound. One senior leader ran the business with little care for people and a loose relationship to the strategy.
What was re-architected
Values and behavior were architected into how the business was led — decision rights, accountability standards and executive readiness made explicit rather than assumed.
Outcome
The lesson priced into that business: the hardest number to reset is not a P&L line, it is the years lost regaining trust with the people who deliver the value-creation plan.

In their words

What the leaders say.

Compass publishes only client-approved, attributable quotes — never composed praise. Executive and owner references, including leaders from the engagements above, are made available directly on request under confidentiality.

Request Client References

Relevance

Where this experience becomes relevant.

  • Founder and successor transitions

    The company has outgrown the way it has always been led, and the next generation of leadership is not yet ready to carry it.

  • Executive development and readiness

    A leader is capable in the current role and unproven in the one the business will need them to hold next.

  • Leadership-team trust and performance

    The team is competent individually and cannot make a hard decision together without the owner in the room.

  • Strategy and operating-model alignment

    The strategy is sound on paper and the organization is structured to produce something else entirely.

  • Organizational simplification and 80/20

    Growth has added complexity faster than value, and no one can say which customers and products actually earn their keep.

  • Transformation, adoption, and execution

    The initiative was announced, resourced, and celebrated — and the daily work never changed.

The evidence behind the framework

The record beneath the architecture, for those who want it.

The record reads in five parts: the platforms the framework was tested on, the three engagements that shaped it, how the work engages and where it has held, the forum standard and the convictions beneath it, and the personal ground it stands on.

  • Four operating platforms the framework was tested on

    Navy command, global enterprises, leadership capability, and transformation discipline.

  • Three engagements that shaped the framework

    What each one proved, and the line it left behind.

  • Engagement types and industries served

    How the work engages, and the sectors it has held in.

  • The forum standard and the convictions behind the work

    How a room is held, and the five convictions beneath the architecture.

  • Personally

    Wisconsin, the Navy, five years in France, and rooms where respect is earned.

See the full record
  • Active-duty U.S. Navy leadership
  • Experience across four continents
  • Five years as an expatriate in France, two years in Manama, Bahrain
  • Industrial, manufacturing, private and PE-backed
  • Regional Vice President, HR and Transformation
  • Front-to-back 80/20 and Lean Six Sigma
  • Executive assessment and succession architecture
  • Award-recognized global leadership development
  • Transformation and change leadership

The doctrine

What the record taught, stated plainly.

Five beliefs

  • Every organization is perfectly designed to produce the results it is currently getting. Different outcomes require redesigning the architecture—not asking people to work harder.
  • Organizations rarely fail because people do not care. They fail because the architecture no longer supports the mission.
  • Leadership is architecture. Leaders design clarity, alignment, decision rights, culture, trust, accountability, learning, and execution.
  • Execution is never accidental. Execution is engineered.
  • The greatest legacy of leadership is creating leaders who no longer depend on you.

Eight laws of organizational architecture

  1. 01Reality is the foundation. Face reality with faith.
  2. 02Complexity always wins until simplified.
  3. 03People support what they architect.
  4. 04Leadership determines the limits of performance.
  5. 05Every organization has an architecture—intentional or accidental.
  6. 06Capability compounds. Dependency does not.
  7. 07The bridge is never finished.
  8. 08Organizations become what leaders repeatedly architect.

The next step

Begin a confidential conversation.

No sales theater. No premature prescription. A focused dialogue about what you are architecting next.

Begin a ConversationExplore Executive Forums

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 leadership.

Not sure? Answer three questions Or browse every instrument