Learning to See Is a Leadership Skill
Learning to See Is a Leadership Skill
Some knowledge is easy to document. You can write down a checklist, create a standard operating procedure, record a training video, or build a step-by-step process that explains exactly what someone should do.
Other knowledge is much harder to transfer.
Experience, judgment, timing, intuition, and the ability to notice what matters often live inside people rather than manuals. They are developed through observation, repetition, mistakes, and years of paying attention. That creates a significant challenge for organizations because when too much knowledge lives inside too few people, the business becomes fragile.
On The Bliss Business Podcast, we sat down with Kaz Matsune, sushi chef, founder of Breakthrough Sushi, bestselling author, mentor, and keynote speaker. Kaz has spent decades practicing and teaching the craft of sushi, and his work today brings lessons from the sushi counter into leadership, organizational learning, and team development. His framework, “Steal With Your Eyes,” explores how people learn through observation, practice, humility, and the intentional transfer of knowledge. Sushi Lessons for Stronger Team…
His perspective reveals something business leaders often overlook: teaching people more information is not necessarily the same as helping them learn. Sometimes the most important leadership skill is creating the conditions where people can see, understand, practice, and eventually pass knowledge forward themselves.
Before You Lead, Learn How to Observe
Kaz’s first day working as a sushi chef did not unfold the way he expected.
He arrived eager to learn how to fillet fish, make rolls, and prepare nigiri. Instead, the head chef told him to stand behind the sushi bar and watch.
For hours.
At first, Kaz found the experience boring and frustrating. He had been hired to learn, yet no one seemed to be teaching him anything. But eventually he began paying closer attention. He noticed how chefs selected different plates depending on the size of an order. He realized that because he was standing nearby, he could anticipate what they needed and hand them the correct plate before they reached for it.
That small observation changed his understanding of what was happening.
He was learning.
The lesson connected with a Japanese concept he already knew but had not fully practiced: me de nusumu, which Kaz translates as “steal with your eyes.” Everything you need to learn may already be happening in front of you, but only if you are paying enough attention to see it. Sushi Lessons for Stronger Team…
There is a powerful leadership lesson in that idea. We often associate leadership with action, instruction, decisiveness, and having the answers. But leaders who are constantly talking may miss what their teams are showing them.
Observation is not inactivity. It is information gathering.
Sometimes the most intelligent first step is to watch.
Leadership Begins With Being a Good Learner
Our conversation naturally moved toward a broader question: can someone become a strong leader without first becoming a strong learner?
Kaz does not think so.
Great teachers have to remain students. Great leaders also have to understand what it means to support, observe, listen, and follow something larger than themselves. That does not necessarily mean following another person. It can mean following a framework, a set of principles, a proven system, or values that create consistency when circumstances change.
This matters because leadership can easily become distorted by ego.
People get promoted and suddenly believe they are expected to know everything. They feel pressure to speak first, solve every problem, and demonstrate certainty. Over time, that expectation can reduce curiosity precisely when curiosity becomes more important.
Kaz offered a different picture of leadership. Sometimes the leader stands at the top, providing direction and setting expectations. At other times, the leader belongs underneath the team, supporting everyone else so they have what they need to perform.
Those roles are not contradictory.
They are different expressions of leadership.
Knowing Something Is Not the Same as Understanding It
One of the most interesting distinctions Kaz made was between knowledge and understanding.
Knowledge is information. You can explain how to slice tuna. You can describe how rice should be shaped for nigiri. You can write down the correct sequence of movements and create a detailed instructional guide.
Understanding goes deeper.
At some point, the learner has to physically do the work.
They need to feel the knife moving through the fish. They need to understand how much pressure should be applied to rice. They need to recognize the difference between the correct movement and one that looks similar but produces an inferior result.
Those things are difficult to communicate entirely through language.
Kaz describes understanding as something closer to feeling. After enough practice, knowledge begins to move beyond conscious instruction and into physical awareness, judgment, and eventually muscle memory. Sushi Lessons for Stronger Team…
Businesses experience the same challenge.
You can teach someone the customer service process, but that does not automatically give them judgment about when to deviate from the script. You can teach a manager how to conduct a difficult conversation, but that does not mean they know how to recognize fear, resistance, or defensiveness while the conversation is happening.
Some capabilities have to be experienced before they are fully understood.
That means organizations need more than documentation. They need observation, practice, feedback, repetition, and opportunities for people to work beside those who already possess the judgment they are trying to develop.
Expertise Should Make You More Curious, Not Less
Experience can create confidence, but it can also create blind spots.
The more successful someone becomes, the easier it is to assume they already understand what is happening. That is why Kaz believes strongly in maintaining a beginner’s mind, an idea connected to his own study of Zen and his experience living at the San Francisco Zen Center.
The paradox of mastery is that the more deeply Kaz studies sushi, the more aware he becomes of how much he still does not know.
That is a very different form of confidence.
Early in our careers, confidence often means proving that we know the answer. As we mature, real confidence can become the ability to say, “I don’t know,” without feeling threatened by it.
That is where humility becomes powerful.
Humility is not the absence of expertise. It is the recognition that expertise is never complete.
Leaders who can remain curious are more likely to notice changes in their environment, listen to people who see things differently, and recognize when an assumption that once served them has become outdated.
Vulnerability Can Strengthen Leadership
Kaz also talked openly about nervousness.
Even after hundreds of workshops and years of speaking, he can still feel nervous before getting in front of a room. Rather than interpreting that feeling as evidence that something is wrong, he has learned to reframe it.
Physiologically, nervousness and excitement can feel very similar. The heart rate changes. Energy rises. The body prepares for something important.
Changing the language from “I’m nervous” to “I’m excited” can change the way someone interprets the same physical experience.
That may seem like a small distinction, but language shapes how we experience ourselves.
It also challenges another leadership myth: leaders always have to appear completely confident.
They do not.
A leader can admit uncertainty and still provide direction. They can feel nervous and still step forward. They can acknowledge that they do not know something without losing credibility.
In many cases, that honesty builds credibility because people no longer have to pretend either.
The Bus Factor Reveals Organizational Fragility
One of the most practical ideas Kaz discussed was the “bus factor,” sometimes described more positively as the “lottery factor.”
The concept is simple: how many people would have to suddenly become unavailable before an important project or part of the business could no longer function?
If the answer is one, the organization has a serious knowledge concentration problem.
A particular employee may know how a critical system works. A founder may be the only person capable of closing certain deals. One engineer may understand a piece of software no one else has touched. A single manager may hold years of institutional knowledge about a client or process.
Those individuals may be extraordinarily valuable, but their value has also become a vulnerability.
The answer is not merely traditional succession planning, where one person transfers knowledge to one other person. That can simply move the dependency somewhere else.
The stronger solution is distributed capability.
Leaders need to create opportunities for more people to observe, learn, practice, understand, and eventually take responsibility. Knowledge should spread through the organization instead of remaining concentrated at the top or inside a handful of specialists.
Observation Has to Be Designed Into the Workplace
Kaz shared the story of a chef who had worked alongside him for years.
For a long time, Kaz did not believe the chef could teach one of his sushi classes. But the chef had spent years watching how Kaz taught. He had observed the sequence, the interactions, the rhythm, and even some of Kaz’s jokes.
Eventually, when he was given the opportunity, much of that knowledge was already there.
This is an important reminder for modern workplaces, especially distributed and remote organizations. Observation used to happen naturally. A junior employee could sit near a senior colleague, overhear how they handled a difficult call, watch how they structured a meeting, and pick up countless behaviors that were never formally taught.
Remote work has made some of that learning less automatic.
That means leaders may need to intentionally recreate it.
Invite developing employees into meetings where they can observe how senior leaders think. Allow people to shadow client conversations. Give someone an observer role where they are explicitly permitted to watch without the pressure to perform. Afterward, talk about what they noticed and why particular decisions were made.
Observation becomes much more powerful when it is treated as a legitimate form of learning rather than passive attendance.
Ask More Questions Before Giving More Instructions
One audience question focused on how managers can tell whether an employee needs more instruction or simply needs more time to practice.
Kaz’s answer highlighted something valuable about his leadership style: he asks questions before assuming he knows the problem.
He shared an example involving a chef preparing spicy tuna differently from the expected recipe. Instead of immediately correcting him, Kaz asked whether he had ever instructed the chef to do it that way.
That question served multiple purposes.
Kaz genuinely wanted to know whether he had previously given an unclear instruction. It also encouraged the employee to think about why he was doing what he was doing.
Questions help managers diagnose before prescribing.
An employee may misunderstand the instruction. They may understand perfectly but lack repetition. They may be working from an assumption no one has corrected. They may have seen someone else perform the task differently.
If leaders jump directly to correction, they may solve the wrong problem.
Curiosity creates a better diagnosis.
Focus on the Process Instead of Forcing the Outcome
One of Kaz’s most memorable sushi lessons involves something very simple: cutting a roll.
Many students press down on the knife because they think cutting requires force. The result is that they crush the sushi roll.
Kaz teaches them something different. Let the knife do the work. Move the arm back and forth rather than focusing on pressing downward.
The language matters too.
When people hear “cut,” they often instinctively imagine applying pressure. Even changing the instruction to “slice” can alter the movement. Kaz eventually became even more specific by teaching the process rather than the desired result: move your arm back and forth and allow the knife to travel through the roll.
The same principle applies to leadership.
Organizations often overemphasize outcomes. Hit the sales target. Increase retention. Improve customer satisfaction. Grow revenue.
Those are goals, not processes.
Leaders still need to identify the behaviors, systems, tools, and actions that make those outcomes possible.
A dull knife requires more pressure. The right tool, properly maintained and used with the right technique, produces a better result with less force.
Teams work the same way.
When leaders constantly push harder without examining the process or the tools, they can crush the very thing they are trying to improve.
Pause Before You Solve
Kaz has developed a simple framework he calls Pause, Ask, and Map.
The first step is to pause.
When something goes wrong, leaders often move immediately into problem-solving mode. They diagnose, prescribe, and act before fully understanding what is happening.
The pause interrupts that reflex.
It creates room to observe what is happening externally and what is happening internally. What am I feeling? What assumptions am I bringing into this situation? What might I not be seeing?
Then comes the question.
One of Kaz’s favorite questions is, “What am I not seeing right now?” An even more difficult version might be, “What am I avoiding seeing?”
Those questions require a level of self-honesty many leaders struggle to practice.
Only after observing and questioning does the mapping begin. What needs to happen next? What is the process? Who needs to learn something? What capability is missing?
The sequence matters.
Pausing before solving can prevent leaders from using yesterday’s assumptions to solve today’s problem.
Love Becomes Visible Through Intention
When we asked Kaz what role love should play in business, his answer was simple: everything.
For Kaz, love is difficult to reduce to a definition because it is ultimately something that is felt. But it can still become visible through intention and behavior.
He shared a small example from Breakthrough Sushi. Years ago, he and his wife created a sushi sign that included a heart. It began almost casually, but the symbol became part of the experience. Guests started taking photographs with it. Kaz also puts small heart symbols on equipment and containers his team uses.
None of those things alone creates a loving culture.
But they reflect an intention.
Kaz described his broader intention as wanting people and situations to become better. Even when he corrects an employee or points out a mistake, he tries to remember that the purpose is not to prove the other person wrong. It is to help everyone improve.
That distinction matters because people can often feel the difference between correction rooted in ego and coaching rooted in care.
Love in business does not eliminate standards.
It changes the intention behind how those standards are taught, reinforced, and shared.
Key Takeaways
- Observation is an active form of learning, and leaders should create environments where people can watch experienced colleagues before being expected to perform.
- Great leaders remain great learners. Curiosity, listening, and humility should increase with expertise rather than disappear.
- Knowledge is information, while understanding develops through practice, repetition, judgment, and experience.
- A beginner’s mindset helps experienced leaders challenge assumptions and continue noticing what familiarity can make invisible.
- Leaders do not need to pretend they know everything. Vulnerability and the willingness to say “I don’t know” can strengthen trust.
- The bus factor helps leaders identify where too much critical knowledge is concentrated inside too few people.
- Knowledge transfer should build distributed capability rather than simply move dependence from one individual to another.
- Asking questions before giving instructions helps leaders determine whether someone needs clarification, practice, or a different kind of support.
- Strong leadership focuses on the process that produces an outcome, not just on applying more pressure to achieve the result.
- Pausing before solving creates space to identify assumptions, notice what is being missed, and respond with greater clarity.
- Love becomes scalable when care, intention, learning, and support are reflected consistently in how people are taught and led.
Final Thoughts
Kaz Matsune’s journey from the sushi counter to leadership teaching reminds us that some of the most important knowledge in an organization cannot be captured in a manual.
People learn by watching. They learn by practicing. They learn when someone lets them try, make mistakes, reflect, and try again. Eventually, what began as information becomes understanding, and understanding becomes judgment.
That is why leadership cannot simply be about giving people answers. Leaders have to create environments where others become capable of finding answers themselves.
This also changes the way we think about scalability. A scalable organization is not one where a handful of extraordinary people keep doing more. It is one where knowledge, capability, judgment, and confidence continually spread through the team.
Sometimes that process begins with something surprisingly simple: standing still long enough to see what is already happening in front of you.
The sushi counter teaches the same lesson that strong organizations eventually learn. You do not always get better results by pressing harder. Sometimes you need a sharper tool, a better process, more attention, and enough humility to let the work teach you something.
Check out our full conversation with Kaz Matsune of Breakthrough Sushi on The Bliss Business Podcast.
Originally Featured on The Bliss Business Podcast Blog





Recent Comments