There's a phrase that Greg Jacobson, CEO of KaiNexus, uses that sounds like a minor word choice but functions as a completely different operating system for continuous improvement. He draws the contrast with a personal example: after tearing his ACL, he didn't set a goal of completing his physical therapy. He told himself,

"I'm the kind of person who does all the rehab my physical therapist assigns."

The goal version gives you permission to quit when motivation dips. The identity version makes quitting a contradiction of who you are.

Applied to organizations, the difference sounds like this:

"We're trying to huddle every morning" vs. "We're the kind of organization that huddles."

"We're working toward a culture of continuous improvement" vs. "We're an organization where everyone improves their work."

"We're trying to increase improvement participation by 20%" vs. "We improve. That's what we do here."

The first version in each pair is a goal. Goals have endpoints. They require sustained motivation. They can be deprioritized when the quarter gets tough or leadership changes. The second version is an identity. Identities persist. They guide hundreds of micro-decisions without requiring anyone to consciously choose each time. You don't debate whether to huddle any more than you debate whether to answer the phone. It's who you are.

This distinction, drawn from James Clear's Atomic Habits, turns out to explain something that puzzles a lot of CI leaders: why organizations with identical training, identical tools, and identical executive sponsorship produce wildly different long-term results.

The Electrolux Discovery

Sandro Casagrande has spent 20 years building and evolving the Electrolux Manufacturing System across 34 factories on multiple continents. When he describes the turning point in Electrolux's Lean journey, the language he uses is revealing. After nine years of deploying tools, training change agents, and running kaizen events -- all the right activities -- only a handful of sites had advanced to gold or platinum certification. The rest were stuck.

What Sandro and his team concluded wasn't that they needed more training or better tools. They concluded they needed to create "organizational habits" -- to make EMS something the organization is rather than something it does. That shift -- from program to identity -- led to what Electrolux calls EMS Way: a framework focused on leadership processes and leadership behaviors designed to be practiced daily until they become automatic.

The mechanism Sandro chose was Toyota Kata, a coaching approach built on daily repetition of structured questions. Not weekly. Not when there's a problem. Daily. The repetition isn't busywork. It's the neuroplasticity principle at work -- the brain physically rewires through repeated practice, building new neural pathways that eventually become the default. Sandro showed his leadership teams a video on neuroplasticity to explain why daily practice matters: you're not just following a routine. You're changing the wiring.

That framing is an identity play, even if Electrolux wouldn't use that term. They stopped asking leaders to "do Kata" (a goal that can be skipped) and started building an organization where coaching is how leadership works (an identity that persists).

What Identity Does That Goals Can't

Goals create a success/failure binary. You hit the number, or you don't. If you hit it, the energy dissipates -- mission accomplished. If you don't, discouragement sets in. Either way, the goal is a temporary motivational structure that must be replaced once it expires.

Identity operates differently. It works at the level of micro-decisions -- the small, unglamorous choices that happen dozens of times a day and collectively determine whether improvement sticks.

A manager walking through a work area notices a process deviation. The goal-oriented version: "Is correcting this deviation part of my current objectives?" Often, the answer is no, and the manager walks past. The identity-oriented version: "We're the kind of organization where leaders stop and address what they see." The manager stops, not because of a KPI, but because walking past would contradict who they are.

A frontline worker has an idea for a small improvement. The goal version: "Is there a campaign running right now? Will this count toward the participation target?" The identity version: "I see problems. I say something. That's my job." The idea gets submitted regardless of whether there's an active initiative, because participation isn't a response to a campaign -- it's a characteristic of the person.

An executive has a conflict during the time they normally review improvements in the system. The goal version: "I'll catch up next week." The identity version: "I'm the kind of leader who stays connected to improvement work." They find 10 minutes later that day, because the identity creates a pull that rescheduling doesn't eliminate.

These micro-decisions are invisible individually. Compounded across an organization of thousands of people over months and years, they're the difference between a CI program that plateaus and one that compounds.

How Identity Spreads (and Why It Can't Be Mandated)

You can mandate a goal. You cannot mandate an identity. This is the hard part.

Colleen Soppelsa, a continuous improvement leader who has worked at Toyota, GE Aviation, and L3 Harris Technologies, describes a method she encountered that illustrates how identity actually propagates. A peer support network program at GE -- small circles of four to six people meeting one hour a week over 12 weeks -- produced a 94% satisfaction score in a pilot of 25 people. More telling: 80% of participants were so changed by the experience that they started their own peer circles spontaneously. The program spread organically through the organization without a formal rollout.

Colleen calls this "immune therapy" -- it changes organizations at the cellular level. The participants didn't adopt a new program. They became different kinds of colleagues. The identity shift preceded the behavioral change, and the behavioral change spread through the network without requiring a campaign to push it.

The implication for CI leaders is uncomfortable: you can't create identity through a launch event, a training class, or an email from the CEO. Identity is built through repeated experiences that are consistent enough to become a belief. Every time an idea gets a fast response, the person learns "this organization actually listens." Every time a leader shows up at a huddle, the team learns "this matters to the people in charge." Every time a mistake is met with curiosity instead of blame, someone learns "it's safe to be honest here."

And the reverse is equally true. Every vanished idea, every canceled huddle, every punitive response to an error teaches people that the stated identity is performance -- not reality. The damage from these contradictions is asymmetric. It takes dozens of consistent positive experiences to build an identity, and a single high-profile violation to shatter it. This is why leaders modeling the identity matters so disproportionately: people watch what leaders do far more carefully than they listen to what leaders say.

The Infrastructure of Identity

If identity can't be mandated but must be experienced into existence, the practical question becomes: how do you create enough consistent experiences, fast enough, across enough people, that the identity takes root before the initial enthusiasm fades?

Lynn Kelley, who led change across Textron and Union Pacific Railroad, has a partial answer: start with people who are already inclined to adopt. In any group, roughly 20% will accept change readily. Their early, visible success creates what Lynn calls "fear of missing out" in the neutral 60%. The identity spreads not through mandate but through social proof -- the people who adopted early become the evidence that this is real, and the middle group starts wanting to be part of it.

The other part of the answer is structural. An improvement system that responds to every idea quickly and visibly is manufacturing consistent positive experiences at scale. Each notification that says "your improvement moved to the next stage" is a micro-experience that reinforces the belief "this organization takes my input seriously." Each dashboard that shows a team's cumulative impact is evidence that "we're a team that makes things better." Each badge earned for a participation milestone is a small identity marker -- not a prize for hitting a target, but a signal of who you are in this organization.

This is a fundamentally different way to think about what improvement software does. It's not project management. It's not workflow automation. It's identity infrastructure. The system creates, at scale, the consistent experiences that build the beliefs that become the identity that sustains the behaviors that produce the results.

See KaiNexus in action ->

When Sandro describes Electrolux's aspiration for EMS Way, he uses language about creating organizational habits -- shared routines that define who the company is. When Greg describes the difference between a CI program and a CI culture, the dividing line is identity. A program is something you participate in. A culture is something you are. The distance between those two states isn't covered by training. It's covered by thousands of experiences that all point in the same direction.

The Test

There's a simple diagnostic for whether your organization has crossed from goal-oriented improvement to identity-oriented improvement. Ask a frontline worker -- not a CI coach, not an executive, a frontline worker -- to describe what happens at their organization when someone has an idea for making work better.

If the answer involves a process ("you submit it through the system, your manager reviews it, you get feedback within a few days, and if it works we spread it"), you're building identity.

If the answer involves a shrug ("I think there's a form somewhere") or a grimace ("last time I said something, nothing happened"), you're still in goal territory -- regardless of what the executive team believes.

The gap between those two answers is the gap between what the organization says it is and what people experience it to be. Closing that gap, consistently, across every interaction, is the actual work of building a culture of continuous improvement. Everything else is scaffolding.

Related KaiNexus webinars referenced in this post:

• How to Sustain Continuous Improvement with Habit Science (Part 3) with Greg Jacobson and Morgan Wright
• Unlock the Power of Leadership: The Electrolux Manufacturing System Way with Sandro Casagrande
• Why Trust Is the Foundation of Continuous Improvement with Colleen Soppelsa
• No More "Flavor of the Month" Change: How to Deliver Sustainable Improvement with Lynn Kelley