COMPASS INSIGHTS — LEADERSHIP & OPERATIONAL EXCELLENCE
Safety Is Not a Program. It Is How an Organization Operates.
Why shared responsibility, leadership accountability and Gemba matter more than another safety initiative
Stephen R. Kopecky | Founder & Principal, Compass Performance, Inc. · 9 minute read
01
The difference between managing safety and leading it
During a previous executive leadership engagement, I worked with an industrial manufacturer seeking to strengthen safety across a complex operating environment. The organization had established procedures, safety professionals and injury reporting. The deeper question was whether safety was being managed as a function—or led as an integral part of how the business operated.
Managing safety can become an exercise in compliance, reporting and responding after an incident. Leading safety requires a system that connects intent, work design, frontline engagement, accountability and continuous improvement.
Safety is everyone’s responsibility. Leadership is accountable for making the system work.
02
Freedom within a framework
Different facilities face different hazards, equipment, work practices and capability levels. A uniform checklist alone cannot solve those differences. The answer is a common management framework—clear standards, decision rights, measures and escalation—combined with local ownership of practical improvements. The goal is not a larger safety bureaucracy. It is stronger operating capability.
03
Everyone participates; leaders remain accountable
Employees must be able to recognize hazards, follow safe practices, report near misses and improve their work. Supervisors reinforce safe execution and remove immediate obstacles. Plant and operations leaders own the effectiveness of controls, resources and corrective action. Executives establish expectations, review leading indicators and intervene when the system is not performing. EHS professionals provide expertise, standards, coaching and independent challenge; they do not replace operating ownership.
The essential management question is not simply “Who is responsible for safety?” It is “How does every person contribute—and how do leaders know the system is working?”
04
Gemba: leadership goes to where work happens
Gemba—going to the actual place where work occurs—bridges the distance between a leadership report and the reality of production. Injury statistics show what has happened. A disciplined safety walk can reveal what might happen next: awkward reaches, incomplete guarding, rushed changeovers, weak maintenance controls or workarounds that have become normal.
The purpose is not to catch someone making a mistake. It is to observe, ask, listen and understand the conditions that shape behavior. Effective walks end with clear action ownership and a return visit to verify that the hazard has actually been controlled.
Observe the work → Engage employees → Identify risk → Correct the system → Verify effectiveness.
05
A management system, not a collection of programs
The approach drew on connected disciplines: a shared safety vision, leadership and employee engagement, safety committees, communication, training, audits and hazard identification, risk prevention, incident investigation, performance measurement and compliance. Each element matters; the connection between them matters more.
One way to operationalize those disciplines is a 20-point safety management framework: twenty governed expectations supported by process- and job-level playbooks. The framework establishes the enterprise standard; the playbooks translate it into decisions, handoffs, controls, qualifications and evidence. A plant may adapt its work methods to local risks and regulation without relaxing the underlying standard.
For the practical architecture behind this approach—including the distinction between process and job playbooks and the idea of making the person doing the work the hero—see the companion Compass Insights article, “From Strategy to Execution: Why Frameworks and Playbooks Matter.” The twenty-point model is illustrative, not a reproduction of a former employer’s proprietary system.
Cross-functional root-cause reviews bring operators, engineering, operations, quality, HR and safety expertise together. Near-miss reporting surfaces weak signals before injury. Standardized playbooks clarify expectations, while model facilities demonstrate practical methods that other teams can adapt. Integrating safety with 6S, standard work and continuous improvement makes it part of production management rather than an activity alongside it.
06
Safety is designed into the entire value stream
The safety of a production employee is shaped by decisions made long before the shift begins. Purchasing determines incoming material and equipment requirements; receiving manages docks, loads and unloading; logistics determines storage, forklift routes and pedestrian separation; engineering establishes flow, ergonomics and safeguarding; maintenance controls equipment integrity and hazardous energy; and packaging and shipping manage lifting, pallet stability and outbound loading. Each function owns the risks it can influence. Operations leadership remains accountable for the performance of the integrated system.
Consider a modernization project. A capital request may promise higher throughput, but its safety case should also address machine guarding, robotic-cell access, interlocks, lockout/tagout (LOTO), maintenance access, material presentation, ergonomics and emergency response. A formal management-of-change (MOC) review should occur before purchase, during commissioning and before release to production. Automation can eliminate exposure to hazardous work—but can also introduce new risks if design and implementation are disconnected.
The same discipline applies to receiving and shipping: a near miss at a loading dock, a damaged pallet, or repeated manual handling is not merely a local issue. It is a signal about supplier specifications, material flow, layout, packaging design or standard work. Gemba gives leaders a way to see those connections and assign corrective action to the right process owner.
07
What improved—and what the evidence means
In a regional North American manufacturing operation employing approximately 3,500 people, a comparison of equivalent five-month reporting periods showed substantial improvements in reported safety outcomes. The figures illustrate the scale of improvement that can be tracked when safety is managed as an operating discipline; they do not establish that any single practice caused the change.
Regional, period-matched observations; not global results or evidence that any single practice caused the change.
| Performance measure | Earlier period (Jan–May 2016) | Later period (Jan–May 2017) | Improvement |
|---|---|---|---|
| Medical-treatment injuries (MTIs) | 133 | 87 | 35% reduction |
| Lost-time accidents (LTAs) | 42 | 27 | 36% reduction |
| Workers’ compensation claims | 97 | 79 | 19% reduction |
| Workers’ compensation reserves | $1.00M | $443K | 56% reduction |
08
A common safety language across borders
International implementation required more than translating a playbook. Leaders needed common definitions, a consistent reporting cadence, and comparable measures—while respecting local legal requirements, languages, workforce practices, and regulatory reporting rules. A lost-time accident (LTA), medical-treatment injury (MTI), near miss, and corrective action had to mean the same thing in management reviews, even when statutory reporting differed by country.
The scorecard combined lagging measures—LTAs, MTIs, workers’ compensation claims and reserves—with leading measures such as near-miss reporting, safety observations, Gemba participation, hazard-assessment completion, overdue corrective actions, training, and verification that controls actually worked. Where exposure hours were reliable, frequency rates could normalize injury counts so a small plant and a large plant were not compared solely on raw totals.
We also needed discipline around data quality: a common reporting period, agreed definitions, ownership of each metric, timely incident entry, and clear escalation when a serious exposure was identified. More reported near misses could initially signal stronger employee trust and hazard visibility—not necessarily worsening safety. Leaders had to interpret the measures together and go to Gemba to understand the story behind the numbers.
The practical international scorecard distinguished outcomes from prevention. LTAs and MTIs described harm already experienced; near misses, hazard observations, machine-guarding assessments, root-cause analysis (RCA), corrective-action closure and Gemba reviews showed whether prevention was functioning. A common incident tracker, defined reporting windows and divisional action owners made the information actionable. One documented operating practice required incidents to be entered within two working days; another called for safety to appear on platform leadership agendas at least quarterly.
09
The Compass Operating Model: five disciplines
FOUNDATION™ Establish values, trust, clear expectations and the accountability structure that allows employees to speak up and leaders to act.
SIMPLIFY™ Design hazards and unnecessary complexity out of work; make the safe method the most reliable method.
LEAD™ Make leadership commitment observable through Gemba, coaching, resources, decisions and follow-through.
GROW™ Develop the ability of every employee, supervisor and leader to recognize risk, solve problems and share learning.
ARC™ Analyze performance and emerging risks, Refine controls and work practices, and Commit to verified corrective action.
10
A cadence that keeps prevention alive
Daily huddles surface immediate hazards. Weekly reviews close actions and remove barriers. Monthly operating reviews examine trends, repeat exposures and capability gaps. Quarterly leadership reviews test whether the overall system is improving. The objective is not more meetings; it is timely decisions supported by evidence from the workplace.
11
The broader leadership lesson
Safety is a particularly visible test of an organization’s operating model, but the same principles apply to quality, talent, customer experience and productivity. Strategic intent must connect to work design, clear accountability, capability, execution evidence and a continuous learning loop. Without that connection, programs multiply while performance remains inconsistent.
Build the foundation. Simplify the work. Lead through behavior. Grow capability. Analyze, refine and commit.
A strong safety culture is not proven by a slogan on the wall. It is demonstrated when people identify risk, leaders act before harm occurs, and the organization learns faster than problems recur. Safety is not simply a program we manage. It is a reflection of how we operate—and how we lead.
Aligned to LEAD™
How do we align the organization and manage the work daily?
Authority, decision rights, accountability and operating cadence.
Article
Freedom Within a Framework™ — Strategic Intent, Adaptive Frameworks, and Connected Playbooks in Rapid Organizational Transformation
Strategic Intent, Adaptive Frameworks and Connected Playbooks in an Era of Rapid Organizational Transformation
11 minute read
Article
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.
7 minute read
Assessment
Compass Leadership Capability Assessment™
Assesses an individual leader through the whole Compass architecture — FOUNDATION, SIMPLIFY, LEAD, GROW, ARC — rather than the enterprise.
On-screen executive profile: five-axis radar, strongest capability, primary constraint, next priority.
Assessment
Governance Readiness Diagnostic
Scores governance maturity across the authority stack, with saved history, score editing and comparison across runs.
Executive report as branded PDF or PNG, plus a saved run history.
Instrument
Clean Sheet Organization Design
Designs the structure from the strategy instead of the current org chart — five to seven load-bearing roles, three accountabilities each, one decision owned, and the white space assigned.
Board-quality organization design PDF, emailed or downloaded.
Instrument
Decision Rights Grid
Settles who decides, who is consulted and who is informed for the decisions that actually stall the enterprise.
Printable decision rights grid.
Podcast
Ken Vandervest — How a solutions-first culture differentiates a technical integrator.
Ken Vandervest tells the Lisbon Creek story since 2016: a non-proprietary product philosophy, staying close to the customer, and how video analytics, license-plate recognition, and mass notification are reshaping the protective-systems industry. He closes with practical advice for founders on starting small and mastering the core.
Podcast
Dwayne Marks — How to turn analysis into decisions leaders will actually make.
Dwayne Marks pairs data science with narrative to tackle complex organizational and global problems. The conversation examines why the analysis is only half the work, and how storytelling converts a model into a decision an executive team can commit to.
Guide
Rebuild the Leadership Architecture the Second Curve Requires
The second curve almost always fails on leadership capacity, not strategy. The transition is from a business that runs through the owner to one that runs through a designed leadership system.
8 minute read
Engagement
Engagement pathways
How the work is structured — architecture reviews, design engagements, forums and advisory.
Where the work begins
Engagement
Compass Executive Forums
A confidential peer table of owners and executives working the same architecture, month after month.
Monthly, by invitation
Explore more Insights
Don't Scale the Old Factory
The factory that created today's success may not be the factory capable of producing tomorrow's growth. The Model Factory is a future-work design project.
COMPASS INSIGHTS — STRATEGY & OPERATING ARCHITECTUREFreedom Within a Framework™ — Strategic Intent, Adaptive Frameworks, and Connected Playbooks in Rapid Organizational Transformation
Strategic Intent, Adaptive Frameworks and Connected Playbooks in an Era of Rapid Organizational Transformation
SimplificationChoose 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.
Editorial Review Draft · The Capability Advantage™ Series | Part 1The Constraint Isn’t Cyclical
Two 2026 studies reach the same conclusion from different directions: the trades shortage is structural, not cyclical. It shows up not as a headline risk but as a quiet drag on execution.
The Capability Advantage™ Series | Part 2Stop Measuring Time to Fill. Measure Time to Productive Capability.
Time to fill reports vacancy activity. Time to productive capability shows whether the enterprise can turn a strategic requirement into usable operating capacity.
Editorial Review Draft · The Capability Advantage™ Series | Part 2Recruiting Must Build the Supply Market
In a constrained labor market, Recruiting cannot operate primarily as a requisition-processing function. It must develop and manage the organization's talent supply market.
Editorial Review Draft · White PaperFrom Frameworks to Playbooks — Mapping the Human Resources Architecture
Global HR organizations often have policies, process maps, centers of expertise, systems and playbooks — as separate artifacts. A value-stream architecture makes the function easier to operate.
Editorial Review Draft · Summary White PaperFrom Frameworks to Playbooks — Integrated HR Architecture Summary
A modern HR architecture should create a line of sight from enterprise strategy to the value HR must create, the work required, who owns it, how performance is measured, and how people execute consistently.
Editorial Review Draft · Enterprise ArchitectureOne Operating System. One Core Architecture.
When priorities, process designs, decision rights and measures describe different versions of the business, capable leaders spend their time reconciling the differences. Growth exposes those differences faster.
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 CEO / Owner LensThe 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 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.