Scroll down to read a detailed summary of the session.
Most organizations manage by policies, procedures, and performance metrics. Ask any executive team whether their culture is compliance-based or commitment-based and almost everyone will say commitment. Then watch the daily behaviors — what gets rewarded, what gets tolerated, what gets enforced — and the actual answer is usually different from the stated one.
Mark Parrish has lived both sides of this gap. He's a West Point graduate and Bronze Star recipient who flew AH-64 Apache helicopters during Desert Shield and Desert Storm. He holds two master's degrees from MIT and has served as CEO, president, or board director across a range of companies — Igloo Products Corp., Stuart Dean Company, and others spanning manufacturing, consumer brands, real estate restoration, and private equity. He's also a fractional chief executive today and describes himself as having more scar tissue than skin tissue on this subject.
The session is structured as a presentation of five fundamental disciplines followed by an extended Q&A on specific challenges CI practitioners have been waiting to ask a CEO about directly. The disciplines are sequential. The Q&A is candid.
What follows is the substance of the session, organized so the page is useful whether you watched it or are landing here from search.
Mark's opening framework is a spectrum with a culture of compliance at one end and a culture of commitment at the other. Almost every organization falls somewhere in between. The question isn't which bucket you're in — it's which direction you're moving.
A culture of compliance is organized around policies and procedures. There are enough rules that on any given day, most people are technically violating at least one. The Z87 safety glasses aren't always on. The metatarsal covers aren't always in place. People know they're breaking rules. So they calculate risk. They figure out whose approval matters and work the politics accordingly. Compliance cultures produce politics, and politics — Mark's definition — is the abandonment of principle for position.
The fear underneath this is real. People have obligations. Families depending on them. Careers they've worked years to build. They can't afford to lose their jobs over a principle, so they learn to keep their heads down and ride the current carefully. The culture is rational from inside it. That's what makes it hard to change from outside it.
A culture of commitment is organized differently. Policies and procedures exist, but they're guidelines rather than scripture. They never replace the values-based and principle-centered decisions that the organization has committed to making. The difference is felt by people at every level — not because someone tells them it's different, but because they experience it daily in how problems are handled, how recognition flows, and what leaders actually do when principles are under pressure.
The path from compliance to commitment runs through five disciplines. Mark is clear they're sequential — not interchangeable.
Before the five disciplines, Mark makes an argument worth unpacking because it's the one most CI practitioners need when they're selling culture work upward.
Joyful cultures yield peak performance. That's the claim. Deming said joy and pride in work are the goal. Mark says the same thing in a different language. And the argument isn't sentimental — it's that the noble goal of making a difference and the business goal of making a dollar aren't in conflict. The more leaders invest in the conditions that make people genuinely committed, the better the traditional metrics become. Not as a correlation. As a mechanism.
Igloo's performance during Mark's tenure, Simmons mattress landing on Fortune's 100 Most Admired Companies list, Harley-Davidson's performance during his time there — all examples he points to. The point isn't to catalog achievements. It's to demonstrate that the connection between culture and business outcomes is real and measurable, not hypothetical.
The implication for CI leaders: culture building isn't a side project adjacent to performance improvement. It's the upstream condition that determines how much performance improvement is possible. Leaders who build commitment get more from their CI programs because the people running those programs are genuinely invested. Leaders who manage through compliance get project outputs at best, and rarely the sustained engagement that produces lasting change.
Mark opens the framework with what he argues is the highest-priority discipline.
Most organizations treat trust as something you earn. The logic makes sense on the surface — past betrayals create scar tissue, and scar tissue teaches people to be cautious with new relationships. The problem is the arithmetic. If you bring the costs of every prior betrayal into every new relationship, you become the bottleneck on your own capacity for joy and performance. Every new colleague, every new direct report starts in a deficit because of someone else's behavior.
Mark's alternative: trust is yours to lose, not mine to earn. You have my trust until you demonstrate you're unworthy of it. I'll be transparent. I'll share my actual thinking. When you betray that or show me the risk was miscalculated, I'll know what specifically not to trust you on. But I won't throw the baby out with the bathwater. And I will have treated you as someone deserving of trust from the first interaction, which is both more human and more likely to produce the relationship that commitment requires.
In a senior-subordinate relationship, where hierarchical power exists, Mark argues the person with power must demonstrate vulnerability first. The chief executive who says "I'm not certain exactly how to accomplish this, but I'd like to tap into your experience" — who makes the admission of incomplete knowledge rather than projecting omniscience — creates the opening that allows others to contribute their best. The old hero-model CEO who had all the answers is increasingly recognized as the constraint on what an organization can do. The sharpest servant leaders today are the questioners, not the answer-holders.
The connection to psychological safety is direct. The belief that you can speak up without punishment depends on having the trust that speaking up won't be used against you. You can't have psychological safety without trust in the people around you. The gift of trust is the operational move that creates the conditions for safety to exist.
The second discipline is to suspend the judgment that each person's experience, expertise, and values makes them naturally inclined to apply.
Mark's framing starts with how values actually work. Core values are established early — between ages two and eight, roughly. Beliefs develop later, through adolescence. Together, values and beliefs form the subconscious and conscious decision-making architecture that produces observable behaviors. Most people in most organizations share the same core values. What they have different is beliefs — the conscious principles through which those values express themselves in specific situations.
The problem with judgment is that people assess others by their visible behaviors using their own values and beliefs as the standard, then assess themselves by their own good intentions. The asymmetry is permanent. You'll never have another person's internal context for why they behaved a certain way. Judgment applied without that context almost always produces a worse outcome than inquiry would.
The discipline: observe the behavior, suspend the conclusion about what it means, and use a question rather than a verdict. This is unnatural. It takes discipline — Mark's definition of discipline throughout the session is the practice of that which is unnatural. The natural move when someone does something frustrating or counterproductive is to conclude something about who they are. The disciplined move is to stay curious about what context is producing the behavior.
The third discipline makes a distinction that most people have heard before and very few have internalized.
Mark traces the etymology. Discussion shares a root with percussion and concussion — the idea of forcibly striking your position into another person. Dialogue shares a root with locomotive commotion — two people in motion together. In a discussion, both parties enter knowing roughly what outcome they're trying to produce. In dialogue, the destination is unknown. The only commitment is to the journey together.
The distinction shows up in practice in what people do when they're not talking. In discussion, the person not speaking is preparing their rebuttal — rehearsing the response to what's being said rather than listening to what's actually being said. In dialogue, there's inner silence. The person not speaking is genuinely receiving what's being said, letting it land, not pre-positioning.
Mark notes that the words "listen" and "silent" use the same letters. The rearrangement is a signal: genuine listening requires silence, internal as well as external.
The relevance for CI leaders: most improvement conversations are discussions dressed up as dialogue. The manager already knows what the problem is before the frontline worker speaks. The CI leader already knows what tool applies before the gemba walk ends. Getting to actual dialogue — free-flowing exchange where the destination is genuinely uncertain — requires the prior disciplines. You need to have given trust, and you need to have suspended judgment, before dialogue becomes possible. They build on each other.
The fourth discipline surfaces a paradox that Mark illustrates with a story from Fort Hood in 1985.
He had two platoons. He told the first: we're going to run four eight-minute miles, and success is when all 28 of you cross the finish line. He told the second: you're going to run until I tell you to stop.
The first platoon was empowered. Clear goal, clear definition of success, clear stakes. Twenty-six men waited at the finish line while one man carried the other. They were genuinely committed because they knew the fences.
The second platoon had no fences — theoretically more freedom. Eleven men didn't finish. Looking out for themselves. No shared definition of what done looked like.
The insight Mark draws: freedom without fences is not empowerment. It's disorientation. The absence of boundaries doesn't produce commitment — it produces uncertainty about what the work is, which produces compliance at best and disengagement at worst.
For CI leaders, the application is direct. Improvement work needs clear boundaries — the scope of the problem being addressed, the authority the team has to test solutions, the resources available, the timeframe. Not so tight that the team can't move, but tight enough that everyone knows what they're inside. Vague mandates to "improve the process" with no boundaries produce the same result as telling soldiers to run until further notice.
The discipline is to name the fences explicitly and consistently — what success looks like, what's in scope, what authority the team has — and then actually respect those boundaries rather than overruling decisions from above when they're inconvenient.
The fifth discipline addresses what Mark calls the insidious cancer of organizational life: politics.
He cites Ben Franklin: politics exist, politics exist, and politics exist. The three ways to respond. First, deny they exist and become a pawn. Second, acknowledge them and decide to play them — smart in the short run, corrosive to culture in the longer run. Third, stop the process whenever you observe the abandonment of principle for position. Name what's happening. Don't attack the person. But clearly identify the principle that's being violated and re-establish the commitment.
The specific practice: if someone says one thing in a meeting and something different at the water cooler, the disciplined response isn't to judge them. It's to surface the contradiction by name, suspend judgment about the motive, and use dialogue to understand what's happening and recommit to the shared principle. "I want to suspend judgment — what principle do we agree to here, and how do we move from this point forward?"
This is the discipline that requires all four of the previous ones to be in place. You can't address politics principal-centrically if you haven't given trust, suspended judgment, and moved into genuine dialogue. The fifth discipline is the test of whether the first four are actually practiced or just professed.
One of the Q&A exchanges worth lifting in full: what's the role of a CEO specifically when it comes to operational excellence and continuous improvement?
Mark's answer draws a distinction between the three types of leadership skill. Technical skills are knowing what needs to be done. Executable skills are knowing how to get things done. Interpersonal skills are knowing how to get things done through others. At the supervisor level, you might be 60% technical, 30% executable, 10% interpersonal. At the CEO level, the ratio inverts: 60% interpersonal, 30% executable, 10% technical.
The implication: the CEO's job isn't to know how to implement Lean. It's to create the cultural conditions in which Lean can take root and spread. The CEO is the spiritual and cultural leader — the person whose behavior teaches everyone else what the organization actually values. The head of HR or operations can be delegated the implementation of programs. The CEO cannot delegate the responsibility for what those programs mean to the people experiencing them.
A specific point about responsibility vs. authority: you can delegate authority but never responsibility. The CEO who says "that's my head of operations' problem" is delegating accountability they never had the right to give away. Responsibility stays with the seat.
For CI leaders, this is both clarifying and challenging. It means the most important work they can do to advance CI at their organization isn't running more events — it's getting the CEO genuinely invested in the culture that CI requires. Every CI initiative operates in the culture the CEO's behavior creates. If the CEO's behavior signals that compliance is the actual standard, CI will be a project, not a transformation.
In the Q&A on KPIs, Mark offers a framework that CI practitioners will recognize in structure but may not have heard framed this way.
Finance is a third-order language of commerce. It reports what already happened. KPIs are a second-order language — closer to home, but still lagging. The first-order language is the key result areas: people, quality, service, and cost, in that sequence.
People is the leading indicator of everything that follows. Organizations that focus on people produce higher quality, better service, and lower cost as downstream consequences. Organizations that focus on cost first — especially organizations in trouble that cut people to manage cost — destroy the very cultural foundation that cost improvement depends on.
The connection to the five disciplines: if you're measuring behaviors at the people level — the leading indicators of engagement, trust, commitment — you have the earliest possible signal of whether your culture is moving in the right direction. Financial results will follow. But the sequence matters. Leading with cost or KPIs while ignoring the cultural leading indicators is managing from the rearview mirror while trying to navigate forward.
A question Mark addressed that applies directly to CI practitioners: what about non-compliance as a starting point? If your organization isn't just compliance-based but is actively resistant or disengaged, do the five disciplines still apply?
His answer: yes, without changing a single element or their order. The fundamental five are fundamental for the same reason in non-compliance environments as in compliance environments. The teeter-totter moves one action at a time. Every disciplined action toward commitment shifts the fulcrum, regardless of where the fulcrum is starting.
The second point he makes is worth underlining. The natural reaction to non-compliance is judgment — "why can't people just follow the system?" The Pareto reality is that about 80% of what looks like people problems is actually process, procedure, or technology problems. Blaming the person when the system is broken is both unfair and ineffective. The same inquiry discipline that applies in commitment-building applies in diagnosing non-compliance — ask what in the process, not who in the workforce.
A few specific things the platform does that connect to what Mark describes.
KaiNexus makes improvement work visible in a way that reinforces the gift of trust. When an employee submits an idea and receives a rapid, thoughtful response — when they can see their idea move through a process and understand what happened to it — that's trust made operational. The system delivers the commitment to take ideas seriously that leaders often make but organizations don't always fulfill.
The platform supports principal-centered decision making by making the impact of work visible. When improvement outcomes are tracked and shared, it becomes harder to abandon CI commitments for short-term cost convenience. The data is in front of leadership the same way financial data is, which changes the decision-making context.
For CI leaders trying to make the case to their CEO that improvement culture and business performance aren't in conflict, the platform provides the evidence. The aggregate financial impact, quality outcomes, engagement indicators — the data that connects Mark's argument about commitment producing performance to the specific results at your organization.
If your CI program is operating in a compliance-based culture — people going through the motions, leaders endorsing but not engaging — the gap isn't methodology. It's the cultural substrate. KaiNexus is infrastructure for the culture Mark describes: one where trust is visible, improvement is recognized, and commitment is reinforced by what the system does, not just what leadership says.
Mark Parrish is Managing Partner and Co-Founder of Parrish Partners LLC, a Southern California-based leadership and management consulting firm. He has served as CEO, president, and board director across public, private, private equity-backed, and family-owned companies, including Igloo Products Corp. and Stuart Dean Company. His leadership has spanned iconic consumer brands including Harley-Davidson and Simmons. A distinguished graduate of the United States Military Academy at West Point, Mark served as an AH-64 Apache pilot and Army Top Gun, earning the Bronze Star and Air Medal for valor during Operations Desert Shield and Desert Storm. He holds two master's degrees in engineering and management from MIT.
What's the difference between a culture of compliance and a culture of commitment?
In a culture of compliance, policies and procedures are the primary mechanism of control. People follow them — or navigate around them — based on fear of consequences. Politics emerge naturally because people are managing risk rather than principles. In a culture of commitment, policies exist as guidelines, but values-based and principle-centered decisions are the actual driver. People contribute more because they're genuinely aligned, not because they're afraid. Mark's five disciplines are the path from one to the other.
What are the five fundamental disciplines for building cultures of commitment?
In sequence: giving trust (extending it until proven unworthy, rather than requiring it to be earned); suspending judgment (using inquiry rather than conclusions when observing others' behavior); developing dialogue rather than discussion (free-flowing exchange rather than forcible positioning); embracing empowerment with fences (freedom within defined boundaries, not undefined freedom); and practicing principal-centered decision making (naming and stopping politics when they appear, without attacking individuals).
Why does Mark say trust must be given rather than earned?
Because requiring trust to be earned holds every new relationship hostage to the betrayals of prior relationships. The person with power must demonstrate vulnerability first — the CEO, the manager, the senior leader. When leaders withhold trust until it's earned, they become the bottleneck on their organization's capacity for commitment and, by extension, performance. Mark's argument: trust is yours to lose, not mine to earn. You start with it.
What does Mark mean when he says discipline is the practice of that which is unnatural?
Discipline in his framing doesn't mean punishment or rigid control. It means consistently doing what you wouldn't do by default. Giving trust is unnatural when you've been burned. Suspending judgment is unnatural when you have strong views. Sitting in genuine silence to listen is unnatural when you have a point to make. These disciplines require effort precisely because they run against the grain of habitual behavior. That's why they build cultures others can't replicate — they require sustained practice, not just intention.
What's the CEO's specific role in continuous improvement?
The CEO is the chief cultural officer. They can delegate the implementation of CI programs to operations or HR leaders. They cannot delegate responsibility for what those programs mean to the people experiencing them. The CEO's behavior teaches everyone else what the organization actually values. If the CEO endorses CI verbally but treats cost cutting as the actual priority when it conflicts, the organization learns the lesson the behavior teaches — not the lesson the speech makes. CI practitioners who want their programs to thrive need CEOs whose behaviors align with commitment culture.
Why does Mark say finance is a "third-order language of commerce"?
Because financial results are a lagging indicator — they report what already happened. KPIs are second-order, still lagging but closer to the work. The first-order leading indicator is people: their engagement, their behaviors, their alignment with organizational values. Organizations that focus on people first produce higher quality, better service, and lower cost as consequences. Organizations that lead with cost — especially by cutting people — undermine the cultural foundation that cost improvement depends on.
How does this framework apply when the starting point is non-compliance, not just compliance?
The same five disciplines apply in the same sequence, with no modifications. Non-compliance doesn't require a different framework — it requires recognizing that the shift from wherever the fulcrum currently sits toward commitment happens one disciplined action at a time. Mark's additional point: most of what looks like non-compliance is a process or system problem, not a people problem. The disciplined response is to investigate the system, not to judge the individuals.
.svg)
Copyright © 2026
Privacy Policy