4. excess of what the customer requires. Customers in one restaurant were sometimes served
water with three lemon slices. Most customers were satisfied with a single lemon slice. As
Hirsch explained, “Customers write us all the time to tell us what they love about our
casinos in Tunica, but occasionally getting additional lemons in their ice water is not a cause
for customer delight.” Producing three times as many lemon slices as necessary was waste
because it consumed money and time without creating additional value for the customer. –
Waiting: Waiting-time waste occurs when employees are idle or when customers must wait
for service. Time spent waiting adds no value to the product or service. If a gaming table
runs out of a particular dollar-value betting chip, the table-games supervisor signals for a
chip replenishment. Chip replenishment is a time-consuming process that, because of
regulatory standards and asset protection protocols, requires supervisor verification, travel
to and from the cashier cage where money and chips are held, and engaging a security
guard to oversee the transport. During portions of the process, patrons and employees
sometimes must wait to resume gaming activity, which affects profitability of gaming
operations. Similarly, if a hotel-room attendant cannot finish cleaning a room because
sheets or towels from the laundry aren’t delivered on time, the attendant may be forced to
wait. This yields non-value-creating payroll expense and a delay in room readiness for
customers.– Not Engaging People: Organizations incur waste when they don’t routinely ask
employees, “What would you change that would make your job easier to do and allow you
to better serve customers?” Prior to the introduction of LEAN methods, the majority of
tactical process changes occurred as a result of a top-down approach. Although some of
these top-down solutions produced improvement, they did not always achieve their highest
potential. Without immediate feedback from the employees actually doing the work,
managers could not fully appreciate delivery-system challenges. For example, employees in
one area struggled to transport food carts across deep-pile carpeting in corridors, resulting
in relatively long transport times and employee fatigue. During a kaizen event, the
employees who had experienced this performance obstacle greatly appreciated having their
voices heard.– Transportation: This is the waste of resources, time, and effort involved in
moving items and tracking their locations. Damage and non-value-added payroll expense
are always a risk when items are transported, and transportation adds to process
throughput time. Moving food, for example, does not add to its value. One kaizen team
tracked the life of a beer and discovered that a beer could be put into storage in up to five
different locations before being acquired by the beverage server for delivery to customers.
Limiting transportation frees employees for higher-value work, and, in the hospitality
industry, can also help protect product quality. – Inventory: Inventory waste is incurred
when material on hand exceeds current demand. Excess inventory costs money, takes up
space, can create a safety hazard, and becomes obsolete when customer requirements
change. Inventory is, in essence, dead money—money has been spent on something that is
doing nothing to create customer value. An examination of one of the Tunica warehouses
revealed multiple pallets of boxes of paper used to print vouchers for customers cashing out
from slot machines. Each month, a team ordered approximately $10,000 worth of slot
paper, regardless of current inventory levels. This order level had historically enabled the
property to have the right quantity of slot paper on site. However, as business levels
10. million. After witnessing these positive results and seeing evidence of support from the top,
departments began asking for kaizen events and employees requested opportunities to
participate on kaizen teams. Managers and employees alike viewed the effort as an effective
way of instilling a continuous improve-ment mindset in the organization. An IT manager
observed, “Having done a few kaizen events, I continue to see that this is a true employee
engagement tool.” An accounting clerk who participated in a kaizen event noted, “It was
great to be considered an equal participant and to have input on big decisions that affect our
work and department.” One of the team’s cooks commented, “LEAN ought to be a way of life
here.” And a table games supervisor said, “I wish these kaizens had been implemented a
long time ago. It would have made our jobs easier.” A janitorial team member offered this
perspective: The LEAN program is a fantastic idea. It made my job a whole lot easier and
less stressful. The LEAN two-bin system eliminated the time I had to spend unnecessarily
counting inventory each day. I also feel more valuable to the property because I now play a
role in ensuring my co-workers get what they need to keep our property clean. I still can’t
believe our CEO took the time to call me on my cell phone to ask me about LEAN and
congratulate me on our success.Reflections on the Tunica ExperienceReflecting on the
successful effort at Tunica, Hirsch was cognizant of several important lessons. One was the
vital role of senior leaders. Without their support, Hirsch knew the effort would have
faltered. Their engage-ment—from participating in kaizen events, to routinely leading
gemba walks—was key in demonstrating to the organization that LEAN was real and here
to stay. Still, he observed, there were some leaders, primarily at the middle-management
level, who were at times slower to adopt new operating practices or embrace the LEAN
cultural shift. In many cases, these managers were fearful of departing from long-standing
operational practices they personally designed, and thus were more inclined to defend.
Furthermore, some managers could tend to feel that a decision to abandon an existing
process was a sign that senior leaders lacked confidence in their tech-nical expertise. Hirsch
and the other members of the Regional LEAN Team recognized, early on, the challenge
resistance to change could present and how it must be addressed to move the organization
forward. Another challenge within the organization was obtaining the financial support to
make physical changes (e.g., moving equipment) to implement kaizen recommendations.
Physical changes sometimes required the kaizen event leader to seek higher-level approval
for the release of funds above a department’s current repair and maintenance budget.
Initially, obtaining additional financial support was a challenge because the senior leader-
ship team sought to maintain expense discipline throughout the business. However, once
the kaizens began to yield tangible benefits, much of the hesitation to fund infrastructure
changes diminished. The Tunica experience also convinced Hirsch that the shock-and-awe
implementation philosophy Caesars casinos embraced had been effective. The team
designed the kaizen events to be lightning fast and generate im-mediate results that would
convince the rest of the organization that the initiative had merit. Hirsch observed: “Our
regional leadership team wanted to make it so big that our team members could feel the
earth tremble with operational improvements. This occurred as a direct result of how the
Tunica team began to embrace the intense kaizen spirit and the support we received in
areas from the senior leadership team to Facilities to IT and everyone in between. Everyone
15. problem preventing the company from meeting its goals? How does the problem affect the
company’s stakeholders? C. Resources: Analyze the company’s resource management. In
other words, is the company managing its resources effectively? How is the effectiveness of
the resource management related to the problem youidentified? II. Data: Interpret the
initial data provided in the case study. How does the data relate to the problem the
company is trying to solve? How does the data show you that the company is not meeting
itsgoals? III. Graphical Representation A. Creation: Create a graphical representation of the
initial data provided in the case study. For example, you could create a Pareto chart, an X-
bar and R chart, or a histogram. Make sure your graphical representation is clearlylabeled.
B. Explanation: Explain the graphical representation. What does it show? How will it help
the stakeholders make informeddecisions? IV. Continuous Improvement Cycle: Use the
PDCA cycle to address the problem in the case study. A. Plan 1. Solution: Identify a solution
in the case study that addresses the problem and supports the sustainable operations of the
company. Which continuous improvement best practices can you apply to the solution
youidentified? 2. Plan: Develop a plan to implement the solution. Explain how the plan
supports organizationaleffectiveness. B. Do: How can the company in the case study test the
solution? Describe the changes that the company could implement to test the solution. What
data could be collected to show the effectiveness of the changes the company implements to
test the solution? C. Check 1. Analysis: Analyze the data produced after the company
implements changes to test the solution (the data collected could be qualitative or
quantitative). Does the data support the proposed solution to the problem? Why or why
not? 2. Graphical Representation: Create a graphical representation of the data collected
after changes were implemented to test the solution. For example, if your data is qualitative,
you could create a pie chart. If your data is quantitative, you could create an X-bar and R
chart or a p-chart. Make sure your graphical representation is clearly labeled. D. Act 1.
Evaluation: Evaluate the solution. Did the solution address the problem you identified? Why
or whynot? 2. Adjustments: What adjustments could the company make to the solution
based on the data collected after changes were implemented to test the solution? If the
solution was not completely successful, what new solution could beproposed?
3. Reflection: Reflect on the company’s choices in applying
continuous improvement tools and techniques. What decision(s) would you have made that
differ from the decisions the company made? How can the company continue to apply
continuous improvement tools and techniques to promote organizational effectiveness?
Provide examples to support yourreflection. Rubric Guidelines for Submission: The report
should be submitted as a Word document and should follow standard APA guidelines.
Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not
Evident (0%) Value Introduction: Company Meets “Proficient” criteria, and description is
exceptionally clear and detailed Comprehensively describes company, goals, and
stakeholders Describes company, goals, and stakeholders, but description is cursory or
inaccurate Does not describe company, goals, and stakeholders 7 Introduction: Problem
Meets “Proficient” criteria, and description shows keen insight into effect of problem on
company’s goals and stakeholders Clearly describes problem and its effect on the
company’s goals and stakeholders Describes problem, but does not describe effect of
16. problem on the company’s goals and stakeholders, or description lacks clarity Does not
describe problem 7 Introduction: Resources Meets “Proficient” criteria and draws clear
connection between effectiveness of resource management and identified problem
Accurately analyzes the company’s resource management and relates effectiveness to
identified problem Analyzes the company’s resource management, but does not relate
effectiveness to identified problem, or analysis is inaccurate Does not analyze the
company’s resource management 7 Data Meets “Proficient” criteria, and interpretation is
exceptionally logical and detailed Accurately interprets data and relates data to problem
and goals of company Interprets data, but does not relate data to problem and goals of
company, or interpretation is inaccurate Does not interpret data 7 Graphical
Representation: Creation Meets “Proficient” criteria, and graphical representation is
exceptionally clear and contextualized Creates clearly labeled graphical representation of
data Creates graphical representation of data, but graphical representation is not clearly
labeled Does not create graphical representation of data 7 Graphical Representation:
Explanation Meets “Proficient” criteria, and explanation is exceptionally clear and detailed
Clearly explains graphical representation and how it will help stakeholders make informed
decisions Explains graphical representation, but does not explain how it will help
stakeholders make informed decisions Does not explain graphical representation 7
Continuous Improvement Cycle: Plan: Solution Meets “Proficient” criteria, and application of
continuous improvement best practices shows nuanced insight into relationship between
proposed solution and identified problem Proposes a solution that addresses the problem
and supports the sustainable operations of the company by applying continuous
improvement best practices Proposes a solution that addresses the problem, but solution
does not support the sustainable operations of the company by applying continuous
improvement best practices Does not propose a solution that addresses the problem 7
Continuous Improvement Cycle: Plan: Plan Meets “Proficient” criteria, and plan and
explanation are exceptionally logical and detailed Develops a plan to implement the
proposed solution andclearly explains how the plan supports organizational effectiveness
Develops a plan to implement the proposed solution, but does not explain how the plan
supports organizational effectiveness, or explanation lacks clarity or detail Does not
develop a plan to implement the proposed solution 7 Continuous Improvement Cycle: Do
Meets “Proficient” criteria, and description includes specific examples that connect the
changes that could be implemented to test the solution to the data that could be collected
Clearly describes changes that could be implemented to test the solution and data that could
be collected to show the effectiveness of the changes Describes changes that could be
implemented to test the solution, but does not describe data that could be collected to show
the effectiveness of the changes, or the description lacks clarity or detail Does not describe
changes that could be implemented to test the solution 7 Continuous Improvement Cycle:
Check: Analysis Meets “Proficient” criteria and draws clear connections between the data
and the proposed solution Accurately analyzes the data produced after company
implements changes and explains how the data supports the proposed solution to the
problem Analyzes the data produced after the company implements changes, but does not
17. explain how the data supports the proposed solution to the problem, or analysis is cursory
or inaccurate Does not analyze the results of the small-scale study 7 Continuous
Improvement Cycle: Check: Graphical Representation Meets “Proficient” criteria, and
graphical representation is exceptionally clear and contextualized Creates a clearly labeled
graphical representation of the data collected after changes were implemented to test the
solution Creates graphical representation of data collected after changes were implemented
to test the solution, but graphical representation is not clearly labeled Does not create
graphical representation of the data collected after changes were implemented to test the
solution 7 Continuous Improvement Cycle: Act: Evaluation Meets “Proficient” criteria, and
evaluation is qualified with specific details and examples Accurately evaluates the solution
and explains how it addresses the identified problem Evaluates the solution, but does not
explain how it addresses the identified problem, or evaluation is cursory or inaccurate Does
not evaluate the solution 7 Continuous Improvement Cycle: Act: Adjustments Meets
“Proficient” criteria, and adjustments are qualified with insightful examples Identifies
appropriate adjustments the company could make to the solution based on data Identifies
adjustments the company could make to the solution, but the adjustments are not based on
data or are not appropriate Does not identify adjustments the company could make to the
solution based on data 7
Continuous Improvement Cycle: Act: Reflection Meets “Proficient” criteria, and
supporting examples show insight and understanding of company and continuous
improvement tools and techniques Discusses company’s choices in applying continuous
improvement tools and techniques and provides supporting examples Discusses
company’s choices in applying continuous improvement tools and techniques, but does
not provide supporting examples Does not discuss company’s choices in applying
continuous improvement tools and techniques 7 Articulation of Response Submission is
free of errors related to citations, grammar, spelling, syntax, and organization and is
presented in a professional and easy-to-read format Submission has no major errors
related to citations, grammar, spelling, syntax, or organization Submission has major
errors related to citations, grammar, spelling, syntax, or organization that negatively
impact readability and articulation of main ideas Submission has critical errors related to
citations, grammar, spelling, syntax, or organization that prevent understanding of ideas 2
Earned Total 100%