I’m Still Dreaming About My Meal at Sukiyabashi Jiro’s Sushi in Tokyo

11
0

Before Katie Anderson's Japan Study Trip in November, I was able to spend six days in Kyoto and Tokyo with two friends (one of whom is cropped out of the photo below for privacy, and the other has an emoji that approximates his general expression, LOL).

Through our hotel concierge, we were able to snag lunchtime seats at the famed Sukiyabashi Jiro restaurant, which was made famous by the film “Jiro Dreams of Sushi” (as I blogged about years ago).

You're not allowed to take photos in the restaurant, but they'll take a photo afterward outside. I'm in the photo, of course, and to the far left is Yoshikazu Ono, the son of the main subject of the film and the founder of the restaurant, Jiro Ono.

Jiro was at one point a 3-star Michelin selection, the first-ever sushi restaurant to receive that honor. But they lost the stars in 2019 because they're technically no longer open to the public. You can only book through hotel concierges (and probably other insider connections).

Jiro Ono is now 99 years old and it's said that you can't be guaranteed to see him, but he will make appearances at the restaurant. But his son, Yoshikazu, carries on with the traditions and excellence. Ono's other son, Takashi, started his own restaurant in Tokyo.

I write this post not to brag but to share some observable details about their operations. The price of the meal was actually on par with a high-end omakase sushi meal in Dallas or other cities. But, the price is a bit lower because no alcohol is served (Jiro believes green tea is what complements the sushi best).

So I'm not saying it was “affordable,” but it wasn't the most expensive meal I've had.

What a Fast Cycle Time!

We arrived early and were greeted promptly when the restaurant opened. There are just ten seats, and I was surprised that five were empty for the meal. It was just the three of us and two other diners who were together.

The one thing that surprised me most was the pacing of the meal.

The menu is omakase (chef's choice) and they offer 20 pieces of nigiri sushi (fish on sushi rice, with some other flavors added, like yuzu citrus).

Here was the day's menu, which is said to be based on what's fresh and good at the fish market that morning:

Rice is prepared in advance (that morning, I'm sure), cooked in a batch, and stored in a round bamboo container to Yoshikazu's left.

There were two (sometimes three) assistant prep chefs working around him. One was generally slicing fish and seafood in the precise sushi manner, cutting a batch of five pieces for the five customers. The slices were put on a tray that was generally moved to Yoshikazu's right, and a course or two was generally queued up for him to do the assembly work.

Here's my rough diagram:

I'm not here to critique the layout or their flow. It seems to work for them. It's a fine-tuned sushi-making machine.

And I guess that's my only criticism. The pacing of the courses was FAST.

I didn't have a stopwatch out, but it took about 20 minutes to serve the 20 courses. It was definitely a push system where Yoshikazu's was handing the next piece to you… so you'd better be ready.

I didn't exactly feel rushed… but it was a little quicker than I would have preferred. Everything seemed driven by Yoshikazu's (and team's) “cycle time” (how long it took to produce pieces) than by the customer's “takt time” (the rate at which we wanted sushi).

It might have taken Yoshikazu's 12 seconds to assemble each piece, as he handed to them to customers one by one (no batching). It was make-serve-make-serve-make-serve, etc., rotating around the five of us. It was almost like he was dealing blackjack cards around a table in Vegas.

The meal might have been served at a slower pace had all ten seats been filled.

The flow of components going to Yoshikazu's ensured he had no “waste of waiting.” It seemed optimized around the chef's efficiency, not the customer's needs.

Don't get me wrong. Everything was delicious. The menu had some of my favorites (like uni) and some fish or seafood that was new to me.

But it was quick.

President Barack Obama dined there in 2014, served by Jiro-san it was said to be a 20-minute sushi meal.

Now, when the sushi is over, things become a bit more leisurely. My friends and I were moved to a booth-style table where we were served the most amazing piece of cantaloupe-style melon that I've ever had. It was so fresh and naturally sweet — and I don't normally like cantaloupe. We were allowed to linger over that and eat at our pace.

Different Dimensions of Quality

So the whole process makes me think of the dimensions of quality. There are multiple dimensions of quality in a hospital (the quality of care and the quality of the experience, for example).

When I worked for Dell Computer, the quality of the computer products mattered, but Dell was also selling the quality of the corporate buying and delivery process (not just avoiding being late, but also not arriving early when a company loading dock and IT team might not be there and ready).

The restaurant lived up to the food quality component by far. But “service quality” is very subjective. Was the meal too fast? Would it have been better if the chef had interacted with us at all? I don't know how good his English is, but he didn't interact with the two Japanese customers to my left, either.

Should the chef be on a bit of a customer “pull” system where he adjusts his pacing to the diners' pace, slowing down as necessary?

When I took a sushi-making class with a chef in Japan years ago, pre-Covid, he told us that each piece of sushi should be bite-sized. And that means customers with smaller mouths (he said “women”) would get smaller pieces than those with bigger mouths. In the U.S., you might get sued for not giving the same amount of sushi to each customer who is paying the same price.

My visit to Sukiyabashi Jiro was a fascinating experience–not just for the exceptional sushi but also for the insights into craftsmanship, efficiency, and customer experience. The precision and speed of service were remarkable, though it raised questions about the balance between efficiency and hospitality. It reminded me that quality isn't just about the end product–it's also about the experience of receiving it.

Questions for You

  • Would you prefer a sushi experience that's hyper-efficient or one that allows more time for conversation and savoring each piece?
  • How do you define great service–by the speed and precision of delivery or by the level of engagement with the chef?
  • Have you ever had an experience where efficiency came at the cost of comfort or enjoyment? How did that impact your perception of quality?
  • If Jiro's sushi-making process was a Lean system, would you see the speed as waste reduction or as an area for customer-driven improvement?
  • What lessons from this experience could be applied in other industries–like healthcare, manufacturing, or hospitality?


What do you think? Please scroll down (or click) to post a comment. Or please share the post with your thoughts on LinkedIn – and follow me or connect with me there.

Did you like this post? Make sure you don't miss a post or podcast — Subscribe to get notified about posts via email daily or weekly.


Check out my latest book, The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation:

Get New Posts Sent To You

Select list(s):
Previous articleJoin Me at HSPI 2025: Red Beads, Lean Leadership, and Smarter Process Improvement
Mark Graban
Mark Graban is an internationally-recognized consultant, author, and professional speaker, and podcaster with experience in healthcare, manufacturing, and startups. Mark's new book is The Mistakes That Make Us: Cultivating a Culture of Learning and Innovation. He is also the author of Measures of Success: React Less, Lead Better, Improve More, the Shingo Award-winning books Lean Hospitals and Healthcare Kaizen, and the anthology Practicing Lean. Mark is also a Senior Advisor to the technology company KaiNexus.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.