Watch the recording of the webinar:
View and download the slides:
Listen to the recording via our podcast:
Imagine it's your first job out of college. You're assigned to a paint shop in a car manufacturing plant. Your task is simple: pour paint and solvent into a vat every few hours as the levels drop. A few weeks in, a manager runs in and stops the line. One hundred cars will have to be repainted. The paint isn't sticking.
You made the mistake.
What happens next?
In most organizations, you know exactly what would happen. Frustration. Blame. Maybe consequences. But this isn't what happened to Isao Yoshino in his first weeks at Toyota Motor Corporation in the 1960s. Instead, the managers came over and asked him to walk them through his process. He picked up the cans. They paused. They looked at the labeling. It was immediately obvious that the cans of paint and solvent looked nearly identical and had no clear visual differentiator. They said: this is not your problem. This is our problem. A small team was convened. The cans were relabeled. It would never happen again.
And then they thanked him. Not just for not hiding the mistake. They thanked him because it revealed a condition they had failed to create -- a condition that made it clear to a new employee exactly which can was which. The mistake was their fault, and they owned it.
That story is not an anecdote about corporate generosity. It's a description of a functioning continuous improvement culture. And it opens this session because it contains everything Katie Anderson wants leaders to understand: that culture is not made by tools or policies but by the behaviors of leaders in everyday moments.
Katie Anderson is an internationally recognized leadership and learning coach, consultant, and professional speaker. She spent time in Japan in 2015 and 2016 getting to know Isao Yoshino, the former Toyota leader whose four decades of experience became the foundation for her international bestselling book Learning to Lead, Leading to Learn. She has worked with organizations across healthcare, biotech, manufacturing, and government -- and what she finds in all of them is the same set of gaps, and the same behaviors that close them.
Organizations that struggle to sustain CI rarely fail because their tools are wrong. They fail because the leadership behaviors required to create a learning culture are absent or inconsistent. People are going from meeting to meeting, from crisis to crisis. There's no time to develop people. There's no time to pause. There's no time to study what actually happened. Band-Aid tools get applied to problems without understanding the underlying conditions.
Katie's framing: most leaders have the right intention in their heart. They want to create a culture of improvement and engagement. The gap is between that intention and their daily actions. Intention, in her framework, equals heart plus direction. The heart -- who you want to be and what impact you want to have -- is usually already there. The direction -- the specific daily actions that align with it -- is what's missing.
The GAPS framework is the answer to that question: what specific behaviors do leaders need to practice to create the conditions for continuous improvement?
Going to see the work is one of the foundational practices of lean. But Katie's point in the session goes beyond the mechanics. Go see with purpose. There's a meaningful difference between being physically present in the work area and actually going to see with the intention of understanding the people and the process.
She distinguishes two purposes for go see: checking in with people (showing that you care about how they are, what barriers they're facing, how they're experiencing the work) and checking on the process (is it running the way you expected? what's working? what needs adjustment?). Both matter. Neither is optional.
A story from her time at Stanford Children's Hospital illustrates what happens when go see finally occurs. A pediatric outpatient cancer clinic had been struggling with a serious problem for years: children receiving infusions were sometimes waiting five or six hours, unpredictably. Multiple project teams had tried to solve it. Nothing had held. When Katie was assigned to help, one of the first things she did was bring the cross-functional team -- the scheduler, the nurse practitioner, the physician -- out to actually walk the process together.
A physician named Dr. Marina had an aha moment. She was part of the process every day, but she had never seen how her piece connected to the pieces around it. She had no idea how the scheduler's decisions were creating backups downstream. The nurse practitioner understood her own piece but not the physician's. Walking the process together made the whole visible in a way no report or meeting ever had. Within six months, the team had reduced that variation dramatically. Children were being seen within an hour rather than after a multi-hour wait.
The insight that carries across settings: when we don't go see, we can't solve the actual problem. We solve the problem as we imagine it from a distance, which is rarely the same thing. Go see makes the invisible visible.
Of the four GAPS behaviors, asking is the one Katie spends the most time on -- because it's the one where leaders most often think they're doing something they're not.
The gap she names directly: we are in a habit of thinking we're asking questions when we're actually telling people our ideas with a question mark attached. "Have you tried X?" "What if you did Y?" "Wouldn't it make more sense to Z?" These aren't questions. They're advocacy in disguise. They transfer ownership of the problem from the person doing the work to the leader offering solutions. And they teach people, over time, that their own thinking doesn't matter much -- the leader will tell them what to do eventually.
The cost isn't just interpersonal. It's operational. When the leader holds the problems, the leader has to solve the problems. That's not scalable, and it's not a culture of continuous improvement.
Katie's test for genuine questions: a genuine question doesn't contain an embedded answer. It creates space for the other person to think. It expresses real curiosity about what they believe, what they see, and what they would do. When leaders start genuinely asking rather than telling, something notable happens: people answer their own questions at least half the time when given enough space to think.
She names her own telling habit openly -- "I'm Katie Anderson and I have a telling habit" -- which models the kind of self-awareness the framework requires. Breaking the telling habit is daily practice, not a one-time decision. And it's worth noting that telling isn't always wrong. There are times when direction is genuinely needed. The problem is that telling has become the default even when asking would produce better results.
Katie introduced a 10-second pause in the middle of the session without explaining it. She let the silence sit. Most people found it uncomfortable.
That discomfort is the point. Leaders who are chronically rushed, chronically reactive, and chronically jumping from Zoom to Zoom have lost the capacity for the pause -- and with it, the capacity to create the space that real learning requires. When we ask a question and immediately follow up because the silence is uncomfortable, we've answered the question ourselves.
The pause has two distinct applications.
The first is after a question. Counting to ten (internally) after asking gives the other person the space to actually think. Ten seconds feels much longer than it is. Most people respond before the count is even finished. The rare cases where the silence holds longer usually produce the most substantive answers.
The second is what Katie calls the intention pause: before entering a meeting, a conversation, or a coaching moment, pausing to ask yourself: what is my purpose here? What role am I in? What kind of impact do I want to have? Am I here to give direction, to coach, to listen, to give feedback? Different situations call for different leadership postures, and the pause is how you match posture to situation rather than defaulting to whatever mode you were in five minutes ago.
The crisis mode that most organizations live in is, in part, a pause problem. People move from one urgent thing to the next without the moments of reflection that would allow them to step back and ask whether what they're responding to is actually urgent or just familiar. Learning to pause is a countermeasure to that pattern.
If there is one element of the GAPS framework that Western organizations are most likely to skip, it's this one. Study and reflection get cut because they feel unproductive. You're not doing anything. The work is piling up. Being good at acting feels more valuable than being good at understanding what just happened.
Isao Yoshino's observation about American organizations: we don't schedule the study part. We do PDSA but we often skip the S. We plan and we do and we maybe check if the numbers changed, but we rarely create deliberate time to ask what actually happened versus what we expected to happen, and what we should understand differently as a result.
Katie reframes PDSA as SAPD -- Study, Adjust, Plan, Do -- partly to illustrate how much we front-load action and back-load learning. The learning is in the gap between what we expected and what actually happened. If we don't create time to study that gap, we lose most of the value of having run the experiment.
The personal application matters as well as the organizational one. Leaders who want to build CI cultures need to apply the same scientific thinking to their own practice. What did I intend when I went to that meeting? What actually happened? What's the gap? What will I try differently next time? This is the habit of reflective practice that distinguishes leaders who get better over time from those who accumulate years of experience without accumulating learning.
Katie also introduces SAPD cycles for personal leadership development: study your current state honestly, adjust based on what you find, plan specific experiments (count to ten, pay attention to the quality of your questions, notice when old habits resurface), do the practice, and reflect on how it went. This isn't abstract self-improvement. It's applying the same process improvement logic to yourself that you'd apply to a clinical workflow or a manufacturing line.
A pattern runs through the entire session: knowing about these behaviors isn't the same as practicing them. Organizations have leaders who know they should go to gemba, know they should ask more questions, know they should reflect. The knowing isn't the gap. The doing is.
Katie's point about the most common barrier: we get caught in crisis mode, and crisis mode makes every behavior on the GAPS list feel like a luxury. We don't have time to go see -- we have fires. We don't have time to ask coaching questions -- we need answers. We don't have time to pause -- the next meeting is starting. We don't have time to reflect -- there are emails waiting.
The counterargument she makes, drawing on the Yoshino story and on the CEOs she's observed and interviewed: the leaders who do these things consistently aren't doing them because they have more time. They're doing them because they've recognized that these behaviors are the actual work. Managing from a distance, answering questions rather than asking them, jumping from crisis to crisis -- those behaviors feel like management, but they produce organizations that depend entirely on the manager to function. GAPS behaviors produce organizations where people develop, problems get solved, and improvement compounds.
Larry Culp, the CEO of General Electric, was on stage with Katie at the Association for Manufacturing Excellence conference in 2022. She asked him about the key behaviors he'd had to learn and practice to create CI cultures in his organizations. His answer mapped almost exactly to the GAPS framework: genuinely going out to see the work (not staying in his office), learning to ask more effective questions, really listening (which is the auditory form of the pause), and reflecting on and improving his own leadership practice continuously.
Katie closes with a frame for what happens when leaders practice GAPS consistently over time: they create a chain of learning that extends through the people they lead.
When leaders approach their work with caring -- genuine curiosity about people and processes rather than judgment and criticism -- the people they work with feel that. When they practice curiosity by asking genuine questions rather than delivering answers, they develop people's thinking capacity rather than creating dependency. When they show courage -- the courage to admit they don't have all the answers, to give challenging feedback, to operate in ways that feel unfamiliar and sometimes uncertain -- they model the same courage they're asking of the people they lead. And when all of this happens consistently, it creates connection -- the human bond between people that is the actual substrate of an improvement culture.
A client she calls Sean in the session has been practicing the GAPS framework for months. His boss started noticing that something was different. His team was more engaged. Problems were getting solved that had been stuck. When he asked Sean what he was doing, Sean told him: I make sure I go see my team regularly. I ask them what problems they think are most important. I don't jump in with solutions. I help us create time to study and reflect. Simple things, he said. But people think he has a superpower.
The superpower is just daily practice of behaviors that most leaders know about and most leaders don't do consistently.
The session ends where it began: not with tools, but with behavior. The paint shop story illustrates a culture. That culture was built by thousands of individual moments -- managers who paused before reacting, asked questions before concluding, went to see before judging, and studied what happened before moving on.
Katie's challenge to the audience: pick one gap to close. Not all four. One. Where is the gap between your intention and your daily behavior? What would better look like -- not perfect, but better? What will you practice this week?
The GAPS framework is a loop. Go see what's happening. Ask questions that develop thinking. Pause to create space for learning. Study and reflect to extract what the experience actually taught. And then start again.
Fall down seven times. Get up eight.
A few specific things the platform does that connect to this framework.
Go see requires that what's happening is visible. KaiNexus makes improvement work -- ideas submitted, projects in progress, completed improvements, impact data -- visible across the organization. Leaders who go to the platform are going to see. They're not managing from a distance based on what they remember or what someone summarized for them. They're seeing the actual state of the work.
Ask becomes more powerful when leaders have specific things to ask about. When a leader can see that a team member's improvement idea has been sitting unanswered, they have something to ask about. When they can see a pattern of problems being reported from one area, they have something to explore. The platform creates the specificity that distinguishes genuine inquiry from generic check-ins.
The futility factor that kills participation -- the belief that speaking up doesn't lead to anything -- is directly addressed by what happens in KaiNexus when someone submits an idea. It gets acknowledged, routed, responded to. That response is the reward that keeps people speaking up, which is the behavior that keeps the GAPS loop running.
If your CI culture is stalled despite good tools and good intentions, the gap is usually the leadership behaviors this session describes. KaiNexus is the infrastructure that makes those behaviors visible, consistent, and connected to results.
Katie Anderson is an internationally recognized leadership and learning coach, consultant, and professional speaker. She is best known for inspiring individuals and organizations to lead with intention and increase their personal and professional impact. Katie spent time living in Japan in 2015 and 2016, where she developed a close working relationship with Isao Yoshino, a former Toyota leader who spent 40 years at the company. That relationship became the foundation for her book Learning to Lead, Leading to Learn: Lessons from Toyota Leader Isao Yoshino on a Lifetime of Continuous Learning, an international #1 Amazon bestseller. She has worked with organizations across healthcare, biotech, manufacturing, and government and offers Japan Study Tours for leadership teams seeking firsthand exposure to Toyota thinking and culture. She can be found at katieanderson.com.
What is the GAPS framework?
GAPS is an acronym for four leadership behaviors that Katie Anderson identifies as essential to creating and sustaining a continuous improvement culture: Go See (go to where the work happens to understand people and process), Ask (ask genuine questions that develop thinking rather than delivering disguised answers), Pause (create space for thinking and reflection rather than reacting immediately), and Study (build in time to reflect on what happened versus what was expected, and apply those lessons going forward).
Why do CI cultures stall even when Lean tools are in place?
Because tools don't change behavior. Organizations can copy another organization's huddle boards, install andon cords, run kaizen events, and implement improvement software -- and still see blank boards and unused systems if the leadership behaviors that create a learning culture aren't present. The gap isn't usually the tools. It's the daily behaviors of leaders that either create the conditions for improvement or undermine them.
What's the difference between asking a genuine question and advocacy in disguise?
A genuine question creates space for the other person to think and responds to their actual thinking. Advocacy in disguise puts a question mark on an embedded answer -- "have you tried my idea?" reframed as "what if you tried X?" The test: does your question contain a preferred answer? If it does, it's advocacy. Genuine questions are expressions of actual curiosity. They don't lead anywhere specific. And they tend to produce better thinking from the person being asked.
Why is the pause so important?
Two reasons. First, silence after a question gives the other person time to actually think -- and most people produce better thinking in that space than in the first milliseconds of a response. Leaders who jump in before the answer emerges inadvertently teach people that they don't need to think very hard before speaking. Second, the intention pause before a meeting or conversation helps leaders match their posture to the purpose of the interaction, rather than defaulting to whatever mode they were in five minutes ago.
What does "study and reflect" mean in the GAPS framework?
It means creating deliberate time to examine what actually happened versus what was expected, and extracting the learning from that gap. Katie reframes PDSA as SAPD -- Study, Adjust, Plan, Do -- to highlight how much organizations front-load action and skip the study step. The learning lives in the gap between prediction and result. If you don't examine that gap, you lose most of the value of having run the experiment. She applies this to both organizational process improvement and personal leadership development.
Can GAPS behaviors be practiced in a remote or hybrid environment?
Yes. Go see requires creativity remotely but doesn't disappear -- screen sharing, video check-ins, making work visible through shared platforms, and treating conversations themselves as gemba all substitute for physical presence. Ask, Pause, and Study require no physical proximity. The challenge of remote work is that the informal go see moments that happen naturally in shared physical space have to be designed deliberately. That's harder, but it's doable.
How do these behaviors connect to psychological safety?
Directly. The Yoshino paint story illustrates a leader response to a mistake that builds psychological safety: going to see (showing up rather than sending an email), asking about the process (curiosity rather than blame), pausing before reacting, and studying what went wrong in a way that focused on system conditions rather than individual fault. Each GAPS behavior, practiced consistently, teaches people that this organization treats mistakes as learning opportunities -- which is the primary condition for psychological safety in CI work.
.svg)
Copyright © 2026
Privacy Policy