All Night Long

Admit it. After reading the title of this story, some of you are hearing the famous Lionel Richie song in your head. This story isn’t about that, but rather it concerns a challenging Kaizen event I recently facilitated for CITY Furniture. The business problem we were trying to solve was a series of computer programs that ran after all showrooms closed each evening. There was a period of time where no revenue could be generated through their e-commerce website, until all programs completed their reconciliations. Our goal was to cut the time by 75%, so that we could free up overnight revenue generation.

I’m an early riser and am typically in bed by 10 pm each evening. My wife says I take my “pre-sleep” nap from 8 pm to 10 pm. This Kaizen event would be held overnight, as our Gemba (the work that we needed to see) happened between 9 pm and 1:30 am. I wasn’t sure how I’d be able to make it through the night.

I met with the team leader to prepare weeks before the kick-off. We agreed to start the Kaizen event at 7 pm Sunday and work through the night for four out of five days. Then, we’d take one day off to adjust our sleep schedule and rotate to day shift. Report out was scheduled for 3 pm on Friday.

I normally fly in to Ft. Lauderdale on the Sunday before the Kaizen starts. Due to starting on Sunday, I knew I couldn’t take any chances and had to figure out how to get proper sleep prior to the event. I flew in on Saturday, got some dinner, and went directly to sleep. I woke up in the middle of the night. Somehow, I was able to go back to sleep.

After Sunday breakfast, I did some work, and took a short nap. At 5 pm, I met my team leader. We set up the meeting room and discussed the Kaizen plan. She was excited to tackle this critical business problem and had assembled a diverse team of highly skilled programmers and managers. They arrived at 6:30 pm for dinner. Afterwards, we kicked off the Kaizen. Our sponsor, the chief information officer (CIO), demonstrated his leadership commitment by staying overnight with the team and participating as a full team member.

After getting to know each other and reviewing Lean topics, we walked downstairs to watch a showroom close. We saw so much waiting and paperwork being generated. We knew there was opportunity for improvement. Then, we walked back upstairs to the meeting room and proceeded to watch the computer programs do their thing. It may have been the longest four and a half hours of my life.

The team was enthralled by what they saw and wrote many ideas on Post-its™. It looked like a lot of gibberish to me. I kept telling myself all that mattered was team members seeing waste and opportunities. I had to stay awake at all costs. It would look bad for the facilitator to fall asleep during the Kaizen!

Mercifully, the Gemba walk through the computer programs ended and I stayed awake. Ninety-two minutes became our baseline for the program reconciliations that kept the e-commerce revenue from being generated. Now it was time to Value Stream map the process, identify pain points, waste, and finally, the ideas to reduce the time it took to complete the reconciliations.

The team generated many ideas and picked three they believed would drive the time down significantly and could be completed during the week. We adjourned at 4:30 am Monday morning and agreed to reconvene at 8:30 pm Monday evening.

I went back to the hotel, surprised I didn’t feel sleepy, but that was due to adrenaline. Four hours later, I woke up. I decided to exercise and work on other projects. Then, I took an afternoon nap. Returning on Monday evening, team members were excited to work on their projects. They broke out into three sub-teams and got to their work, which was all on the computer. I felt useless, but they were fully engaged. From time to time, we’d reconvene and share project status and problem solve. On Tuesday morning, the team decided they didn’t need to work through the night anymore and that we’d take a 27-hour break, reconvening at 8 am on Wednesday morning.

Now it was time to reestablish my normal sleep pattern at the hotel. I slept almost as soon as my head hit the pillow at 6 am. I woke up at 10 am. Now what was I going to do? I got up, showered, exercised, and ate lunch. Then, I worked on other things for a few hours. I decided I should stay awake until at least 9 pm. Time went by slowly, but I made it. I went to bed, and woke up around 4 am. That had to be good enough.

Everyone seemed happier to be working in the daytime. Team members felt they were making programming changes that could be implemented by the end of the day. They installed the changes to see how the system would react on Wednesday night. On Thursday morning, we learned the program ran faster than ever previously recorded. Our 92-minute process was now taking 57 minutes, a significant impact to the system. They had more changes in mind that would reduce time, but those would have to wait for the weeks following the Kaizen event.

The report out was well attended, and our sponsor remarked the initial results had saved the company considerable money. The team has implemented a follow-up process, with meetings every two weeks. The time continues to come down and our sponsor is now ready to tackle another critical business problem in his department.