cases study – struggling to win the hearts and minds of his people, the author took lean home, learned as much as he could about it and brought it back to his business with the idea of making everybody’s lives easier.
words: kieron hales, executive chef and managing partner, zingerman’s cornman farms
i opened cornman farms in 2014. we were a small team doing a big job: we host and run up weddings and other large events that, to work, require a great conductor who knows everything that’s going on and can facilitate collaboration and the flow of information. with every day that went by, i grew increasingly frustrated with constantly being that person. i didn’t see myself ever being able to step out of that role. i must admit that the stress of all the variables for that first year was gut-wrenching.
lean thinking became very important for me from the beginning as a way of empowering staff so that i could stop feeling like the log jam of the system. it helped me to see and accept there were many things i didn’t know, that i wasn’t the expert. i wanted to get to a point where people could find the answers to their own questions.
i had been exposed to lean through tom root’s work at mail order, and immediately got very interested in it. i was particularly fascinated by the idea of being able to reduce lead-times from days to hours. so, i dived right in and started reading about lean and toyota extensively. tom and i have wondered many times why i became a convert so easily, and i think it has to do with being a classically trained bassoonist (my first career ever). musicians in an orchestra are only an expert in their field yet work together in harmony.
one of the most common challenges in a lean transformation is to get leadership to understand it and embrace it. i didn’t have that problem. my issue was that nobody else at cornman farms wanted to do it! for the system i was introducing to succeed, we needed a lot of lean elements and tools – from water spider routes to kanban – to work at the same time. the almost complete lack of buy-in on the first year, however, made that impossible. and the fact that i had no other cheerleader in the team (with the exception of tom root, who came over from mail order to support me) didn’t help.
when i realized i wasn’t getting traction at work, i took lean home and turned my house into my “lean lab”. i started to run experiments all over the place: silly things like moving the closets next to the laundry room for better flow, implementing a kanban system in our cupboards or hanging pictures to the wall of what rooms should look like after tiding them up. i got a lot of inspiration from my kids’ pre-school, where everything is simple visual management. my experiments put a bit of a strain on my marriage, i will admit, but they gave me the proof of concept i was struggling to get at the farm. i started to take cornman farms employees to my house, to show them how lean worked!
back to the farm
armed with all the knowledge i had gained at home, i brought lean back to the farm. one of the most impactful things we did in those early days was to create videos to show people how to perform certain tasks. up until them, we’d been using very long sops that were not fun to write and even less fun to read. the videos changed our interaction and got people interested. they were our way to establish standards that cornman farms employees could access at any time using their mobile devices to immediately see what good work looked like.
we don’t use them as much today, because they are hard to edit and are therefore not adequate for ever-changing standards. but there is no doubt they represented a great baseline for us: i myself used each and every one of those videos over time, which inarguably made even tasks like cleaning the sewer ejector pump less unpleasant to perform. sometimes, we still watch some of them, to prove ourselves how far we have come. our history and the evolution of our processes are now our proof of concept.
standards and visual management became part and parcel of our work. my favorite example is perhaps our system to ensure we properly lock the building: we place an animal magnet on every door, window and lock the building in the farm and collect them in the morning when we open up – a fantastic example of poke-yoke. i brought my four-year-old in one day, and he unlocked the building with the staff. that’s how simple our system is!
i believe that getting people to buy into lean thinking means making their lives easier. that is why fixing processes they perceive as boring or overly complicated and making them as painless as possible goes a long way. our health inspections are a great example of this: they entail performing the same tasks, like checking the temperatures of fridges, four times a day. each check used to take us 28 minutes, which we were able to bring down to 11 minutes by providing the team with a toolkit.
another sign that i was finally getting some traction was that our senior manager – now my business partner tabitha mason – finally bought in. she was my number-one naysayer and detractor of lean at first. she thought it was crazy and that it would never work, but today she is even more of convert than i am. what finally won her over was being able to fix the coffee ordering process: it sounds simple enough, but it took us six months to get that sop to work. food and produce ordering is typically done by the chef, using as many as 20 different factors – from the type of guest to the age blend, from the time of the year the event is taking place to what food guests are having. even a process as complex as this could be documented and successfully replicated, and that was a revelation for us. it’s not necessary to learn everything: all you need to do is carry with you a stack of cards you can refer to any time you are in doubt.
getting tabitha on board was great. over time, she introduced lean thinking to areas i wasn’t going to, from the logistics of sitting people down to marketing, from sales to the guest journey though the business. these days, we use 42 folders to track our guest experience from the moment they book an event with us.
around two years ago, tabitha and i realized we had to take our hands off the wheel and let the team drive. we’d become the log jam in the system again, because any big change now depended on us. letting go was one of the hardest things we did, because we had to let our people go through all the same mistakes we had gone through. i believe it’s the only way to learn. they couldn’t just pick up from where we left off; they had to go back a few steps and learn for themselves, even if that meant slowing down our transformation. time and time again i had to resist the urge to step in; i found that even giving advice wasn’t very helpful.
the hairiest change we implemented, but also the most effected, was adapting our schedule to the actual work and the guest timeline. we had been reluctant to do it, because it entailed mapping the whole day (we are open between 18 and 20 hours a day) and the myriad tasks we have to perform throughout it. i thought it wasn’t even doable, but tom insisted that documenting every little step in the end-to-end process was the only thing that would work. he was right. it was horrible work, but it was life-changing: it told us when the key touch points were (when the bride arrives, the cutting of the cake, etc) and when we had to complete the activities necessary for that touch point to be met without any glitches. we then laid out every type of variation we could experience, and immediately figured out how long we needed for each task in the different scenarios. we had never looked at our process like that. for the first time, we realized how many people we actually needed on each activity. it changed how staff felt they were being supported. that’s when they really realized that we were there to help them with their problems.
critically, scheduling to the work bell curves allowed us to properly allocate our resources and save $5,000 in labor every month. that’s when we started to see our financial gains. having introduced lean at the very beginning, we had nothing to compare our performance to. we also implemented a two-bin kanban system that drastically reduced the number of items we were carrying – from light bulbs to ingredients. if an item was only used once a year, we stopped having it in stock. we even adapted our menu to take out products that we almost never use but still took shelf space. these measures resulted in our food stock dropping from $86,000 to $32,000. when we first opened, inventory took us between eight and nine hours; today we can do it in 45 minutes.
in the early stages of our transformation, it was very frustrating to see how some of our people thought that, through our lean efforts, we were trying to document their jobs out of existence. we had hired great firefighters and now they we were trying to stop the fires from happening, people were afraid they’d soon become redundant. many of them could not make that leap and, a few months in, left. it was hard, because all we wanted was their brains in the game.
today things could not be more different, and our people are actively participating in cornman farms’ lean transformation. there is a common understanding that it is everyone’s responsibility to not only do the work, but also improve it. it is thanks to our people’s great commitment and their support to our lean system that today we are able to plan around 200 events per year – something that would have been unthinkable when we opened six years ago. we are currently seeing a 25%-30% increase in sales year on year, with the same number of full-time employees (16 people, to which we hire 30 to 40 seasonal hires).
the biggest lesson i have taken home after six years? that it’s much more fun to put the work with the people and learn with them than to be the expert. in fact, i have completely accepted that i am not the expert in a lot of things in my business. i love the fact that there are people who have been with us only a few months and already know more about certain parts of the company than i do. truth is, it is liberating to not be expected to have all the answers. it’s nice to be on the intellectual side solving problems, rather than the go-to firefighter.