Praise for Lean IT - Purpose Driven Leanpurposedrivenlean.com/wp-content/uploads/2016/01/583dd3ef3f8ca… · Praise for Lean IT “A great read on ... “The authors clearly articulate

Praise for Lean IT

“A great read on how to apply Lean principles to IT. These tools really work to improve IT’s perfor-mance and credibility.”

— Niel Nickolaisen, CIO Headwaters, Inc.; co-author of Stand Back and Deliver: Accelerating Business Agility

“A groundbreaking synthesis, examining IT operations, project management, software devel-opment, and governance through a Lean lens. Taut, subtly reasoned, and laced with the kind of brilliant insights that only come from practicing masters. Required reading for IT executives, archi-tects, and project managers.”

— Charles Betz, author of Architecture and Patterns for IT Service Management, Resource Planning, and Governance, and practicing Fortune 20 enterprise architect

“A superb primer for anyone interested in learning about Lean. Their work will help business lead-ers understand the arcane machinations of IT while giving IT professionals a common language to talk to the business.”

David Almond, Administrator, Office of Transformation for the Department of Administrative Services; former CIO, Oregon Department of Revenue

“Do most IT organizations waste effort? They do. Can this book transform your thinking and jumpstart your efforts to eliminate waste and optimize the business value of IT? You bet!”

Kurt Milne, Executive Director, IT Process Institute

“Finally! A practical Lean transformation blueprint that includes information systems and the IT organization, while addressing the essential element of human engagement across the enterprise. You can easily digest their lessons and learn how to adapt and apply to your specific organization. This is the key to business alignment the IT industry has been searching for.”

Andrew Rome, Talent & Organizational Performance executive of an 80,000-person global IT Management firm

“A deft application of Lean concepts and techniques to a central challenge we all face: how to increase effectiveness of investments in IT people and systems and the value they bring to enterprise processes. Current and aspiring business and IT leaders and managers at all levels of the organiza-tion will benefit from their in-depth knowledge and broad perspective.”

John Pierce, Vice President, Information Systems, Tripwire, Inc.

“Lean IT is an idea whose time has come, especially now that applications like electronic medical records may soon revolutionize health care. Bell and Orzen blend creativity and practicality as they show how to improve both information quality and ease—all the while acknowledging that more is not always better.”

Naida Grunden, Author, The Pittsburgh Way to Efficient Healthcare: Improving Patient Care Using Toyota Based Methods

“This book is long overdue. The IT world needs tools and concepts to be structured in their language and approach so they can join the productivity push that manufacturing has already experienced. “

Bill Baker, co-author, Winning the Knowledge Transfer Race

“This book is a must read for not only IT professionals, but business executives as it aligns informa-tion and information systems throughout the enterprise and supply chain, which improves organi-zational performance and agility.”

Beth Cudney, Ph.D., Missouri University of Science and Technology; author of Using Hoshin Kanri to Improve the Value Stream

“This work integrates the Lean work over the past century and brings it to focus on the IT organiza-tion to eradicate the very drivers of IT wastes, replacing them with a value driven approach based on Lean principles. This comprehensive book should be required reading for all levels in the IT organization.”

Mark Swets and Tim Schipper, Lean Coaches, Steelcase; co-authors of Innovative Lean Development

“From software development to help desk management, business leaders, IT professionals, and improvement teams finally have clear and concise answers to the question, ‘Yes, but, how does Lean apply to IT?’ Supported by compelling case studies, this outstanding book goes far beyond theory.

Karen Martin, co-author of The Kaizen Event Planner: Achieving Rapid Improvement in Office, Service, and Technical Environments

“Lean IT takes the game to a new level, particularly in the field of Lean Healthcare, where effective information systems are vital. I suppose I will have to buy multiple copies of this book -- So many IT managers in need of Lean education; so little time.”

Tom Jackson, author of Hoshin Kanri for the Lean Enterprise: Developing Competitive Capabilities and Managing Profit, winner of the 2007 Shingo Research Prize

“Read it! Learn it! Do it! These pages are meant to be dog-eared, high-lighted, and coffee-stained. Within these pages are the keys to unlocking the value of information and information systems.”

Dennis E. Wells, Lean Evangelist, Oregon Department of Human Services

“The authors clearly articulate and demystify the overwhelming challenge of enabling IT processes and organizations to embrace rapid change demanded by Lean transformation. Lean IT represents an important body of work Lean practitioners desperately need to break through the plateau of unending point improvements into sustainable system wide improvements impacting the bottom line.”

Rajesh Solanki, Corporate Director for Continuous Improvement, RTI International Metals, Inc

“Nearly every week, IT leaders ask me to help clarify their roles in their organizations’ process improvement efforts. This book not only answers how and why, it also gives great examples showing that it can be done in your organization too!”

Steve Hoeft, Lean Six Sigma Director, Altarum Institute; Lead Instructor, Univ. of Michigan Lean Manufacturing, Lean Product Design and Lean Healthcare Certification courses; and author of Stories From My Sensei.

“The gap from the implementation of Lean in production processes to office practices now has a bridge! Orzen and Bell are visionary showing the value of a fully integrated lean enterprise.”

Elizabeth M. King, Executive Director Organizational Effectiveness, ESCO Corporation; Association for Manufacturing Excellence, Director

Lean ITEnabling and Sustaining

Your Lean Transformation

Steven C. Bell • Michael A. Orzen

Productivity PressTaylor & Francis Group270 Madison AvenueNew York, NY 10016

© 2011 by Steven C. Bell and Michael A. OrzenProductivity Press is an imprint of Taylor & Francis Group, an Informa business

No claim to original U.S. Government works

Printed in the United States of America on acid-free paper10 9 8 7 6 5 4 3 2 1

International Standard Book Number: 978-1-4398-1756-8 (Hardback)

This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the validity of all materials or the consequences of their use. The authors and publishers have attempted to trace the copyright holders of all material reproduced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint.

Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, trans-mitted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying, microfilming, and recording, or in any information storage or retrieval system, without written permission from the publishers.

For permission to photocopy or use material electronically from this work, please access www.copyright.com (http://www.copyright.com/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and registration for a variety of users. For organizations that have been granted a photocopy license by the CCC, a separate system of payment has been arranged.

Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used only for identification and explanation without intent to infringe.

Library of Congress Cataloging‑in‑Publication Data

Bell, Steve, 1960 Sept. 30-Lean IT: enabling and sustaining your lean transformation / Steven C. Bell and

Michael A. Orzen.p. cm.

Includes bibliographical references and index.ISBN 978-1-4398-1756-81. Information technology--Management. 2. Information resources management.

I. Orzen, Michael A. II. Title.

HD30.2.B4573 2011004.068’4--dc22 2010010004

Visit the Taylor & Francis Web site athttp://www.taylorandfrancis.com

and the Productivity Press Web site athttp://www.productivitypress.com

This book is dedicated to Morton and Rickie Orzen, and Bob and Betty Bell, our incredible parents who molded us with their unconditional love.

We also dedicate the concepts and practices within this book to the count-less dedicated community volunteers, and aid workers with nonprofit and nongovernmental organizations around the world. We believe that Lean IT not only offers benefits to the industrialized countries, but to the billions of individuals in this world living at the bottom of the pyramid, who must do more with much less. We hope that Lean IT can help these compassionate individuals to harness the power and breadth of low-cost information tech-nologies to raise the standard and quality of living for all.

Performance: ITOperational Excellence

4. Lean IT and Business Process Improvement

7. Lean IT Operations:ITIL and Cloud Computing

10. Leading the Lean IT Transformation

3. �e Lean IT andBusiness Partnership

8. Lean Software Development

9. Applying Lean to Project Management

5. Lean IT Lessons Learned from Lean Manufacturing:

Flow and Pull

Integration: AligningLean IT and the Business

6. Lean Management Systems

2. Foundations of Lean

1. Why Does Lean IT Matter?

Introduction

Foundation:What Is Lean IT and Why Is It Important?

11. A Lean IT Roadmap

Leadership Roadmap

Barry-Wehmiller, Con-way, Group Health,Ingersoll Rand, Steelcase, Toyota, Virginia Mason Hospital

Lean IT Case Studies

vii

Contents

Acknowledgments ................................................................................ xvIntroduction ........................................................................................xvii

SECTION I Foundation What Is Lean IT and Why Is it Important?

Chapter 1 Why Does Lean IT Matter? ............................................... 3

The Business View .......................................................................3The IT View ..................................................................................5What Causes IT and Business Misalignment? ........................6How Lean IT Encourages Alignment and Creates Value ......8Moving Forward ........................................................................10Endnotes .....................................................................................11

Chapter 2 Foundations of Lean ........................................................ 13

A Brief History of Continuous Improvement .......................13The Age of Scientific Management: 1890–1940 ................13The Age of Engagement: 1940–1995 ..................................14The Age of Integration: 1996–Present ...............................15

Lean Principles ..........................................................................16Constancy of Purpose ..........................................................17Respect for People .................................................................21Continuous Improvement and the Pursuit of Perfection ...............................................................................22Proactive Behavior ................................................................24Voice of the Customer ..........................................................26Quality at the Source ............................................................27Systems Thinking .................................................................27Flow, Pull, and Just in Time ................................................29Culture .................................................................................. 30

The Central Concepts of Value and Waste ............................33

viii • Contents

Value Stream .........................................................................33Value .......................................................................................33

Value-Added Work: VA, NVA, and NNVA ................ 34The Three Ms ........................................................................ 34

Unevenness: Mura .......................................................... 34Overburden: Muri ........................................................... 34Waste: Muda .....................................................................35The Power of the Three Ms .............................................36

Lean Tools Overview ................................................................36A3 Thinking, the Scientific Method, and PDCA .............36Value Stream Mapping ........................................................37Kaizen .................................................................................... 40

System and Process Kaizen ........................................... 40Kaizen Events, Projects and Daily Improvement ........41

Kaikaku ................................................................................. 42Standardized Work .............................................................. 425S and the Visual Workplace ............................................. 43

Let’s Get Started! ...................................................................... 43Endnotes .................................................................................... 44

Chapter 3 The Lean IT and Business Partnership .......................... 45

Why Hasn’t IT Been a Focus of Lean? ................................... 46What Is IT’s Burning Platform for Transformation? .......... 48

Lean versus Traditional IT: A Natural Tension? ..............49Legacy Systems ......................................................................50What about Process Maturity Models? .............................51

What Is Information Waste? ....................................................52Excess Information Inventory Waste .................................53Information Overprocessing Waste .................................. 54Poor Data Quality Waste .....................................................55

Learning to See Information Waste ........................................55Health Care Information Quality .......................................... 56Lean and Green IT ....................................................................61The Tools of Lean IT .................................................................63How Do We Do Lean IT? .........................................................65Endnotes .................................................................................... 66

Contents • ix

SECTION II Integration Aligning Lean IT and the Business

Chapter 4 Lean IT and Business Process Improvement ................. 69

Chapter Objectives ....................................................................69The Coordinating Function of Information, IT, and the Lean Office ...........................................................................70The Intangible Nature of Information Value and Waste .....74

IT Brings Systems Perspective to Business Process Improvement .........................................................................75Enterprise Software Applications and the Ghosts of Projects Past...........................................................................77The Efficiency–Flexibility Trade-Off: Agility ...................79Process versus Practice ....................................................... 80

What Processes and Practices Are “Best”? ............................82Benchmarking: No Need to Reinvent the Wheel..................83Using Measurement Effectively ...............................................85

Compliance: A Special Form of Measurement .................87Business Process Management (BPM) .................................. 88Prioritizing Process Improvement with Strategy ................ 90

Supporting Processes .......................................................... 90Innovating Processes ............................................................92

The IT Organization’s Contribution .......................................93Endnotes .....................................................................................95

Chapter 5 Lean IT Lessons Learned from Lean Manufacturing: Flow and Pull ........................................ 97

Chapter Objectives ....................................................................97Push versus Pull: What Went Wrong with MRP? ............. 100Flow, Balance, and Agility ......................................................102Kanban Is an Information System for Pull ...........................104Creating a Level Schedule ......................................................107IT Demand Management: The Foundation for Flow .........109

Only Three Choices When Demand Exceeds Capacity 111The IT Demand Management Cycle ................................112

Demand Planning ..........................................................112

x • Contents

Flow Simplifies Demand Planning ..............................114Capacity Planning ..........................................................115Balancing.........................................................................116Executive Review ...........................................................117

Lean IT Lessons Learned from the Shop Floor ...................118Endnotes ...................................................................................119

Chapter 6 Lean Management Systems............................................ 121

Communication ...................................................................... 123Knowledge Management and Collaboration ...................... 124

Knowledge Management ...................................................125Collaborative Workspaces .................................................127

The Evolution of a Lean Intranet Site .................................. 128IT Service Desk (Help Desk) .............................................129Education and Training .....................................................130

Performance Measurement ....................................................131Lean Business Intelligence ................................................133Rapid Acquisition and Integration ...................................135

Strategy Deployment ...............................................................136The Role of Information Systems in Strategy Deployment .........................................................................139

Measuring Value: Lean Accounting .....................................140Focus on Creating Value, Not Cost Reduction ...................143The Importance of the Lean Management System .............144Endnotes ...................................................................................145

SECTION III Performance IT Operational Excellence

Chapter 7 Lean IT Operations: ITIL and Cloud Computing ....... 149

Quality Is Free ..........................................................................150Functional Silo or Value-Adding Service Center? ..............152ITIL: A Lean Approach to IT Services Management .........156

ITIL Is a Set of Integrated Processes ................................157How ITIL Emphasizes Quality at the Source ......................159

Contents • xi

How ITIL Supports Lean IT ..............................................160A3 Problem Solving .......................................................160Voice of the Customer ...................................................160

Lean Thinking Applied to Security and License Management ..................................................................161

Quality at the Source .....................................................162Standard Work ...............................................................162Measurement ..................................................................163

Lean IT in the Cloud ...............................................................164Lean Tips for Successful IT Services Adoption ...................165Endnotes ...................................................................................168

Chapter 8 Lean Software Development .......................................... 169

The Challenges of Traditional Software Development .......171Lean Software Development Basics ......................................174Lean Software Development Life Cycle ................................177

Organization and Approach .............................................177Requirements Definition ...................................................178Demand Management .......................................................181Execution and Test Iterations ...........................................183Customer Service and Support .........................................186Measurements .....................................................................187

Implementation and Integration Lessons Learned.............189Endnotes ...................................................................................191

Chapter 9 Applying Lean to Project Management..................... 193

The Value of Effective Project Management ........................193The Project Management Body of Knowledge ...............197Portfolio Management .......................................................197Program Management .......................................................198

The Project Management Office ..................................198Is Lean a Program? ..................................................................199

Project Management ......................................................... 200The Disconnect between Strategy and Execution: The Role of the PMO ...............................................................201

xii • Contents

Improving Project Management Results with Lean Thinking ............................................................................. 203

Lean Project Management .................................................... 206The Triple Constraints Model .......................................... 206Applying Lean Thinking to Project Management ........ 207

A3 Thinking................................................................... 208Value Stream Mapping ..................................................212

Plan-Do-Check-Act, DMAIC, and Project Management ........................................................................213

Initiate .............................................................................213Plan ..................................................................................215

The Five Whys ..........................................................................217The Fishbone Diagram ...........................................................217

Execute ............................................................................219Monitor and Control .................................................... 220Close.................................................................................221

Lean Project Management Enables the Lean Enterprise .. 222Endnotes .................................................................................. 223

SECTION IV Leadership Roadmap

Chapter 10 Leading the Lean IT Transformation ...................... 227

How to Launch a Lean Enterprise Transformation ........... 227Strategic Intent ........................................................................ 229Leadership Is a State of Mind ................................................232The Importance of Effective Management Systems........... 234

Strategy Deployment ..........................................................235Demand Management ...................................................... 236Business Process Management .........................................237Project, Program, and Portfolio Management .............. 238Governance ......................................................................... 238

The Three Levels of a Lean Management System .............. 240Integrating Lean IT ................................................................ 244Endnotes .................................................................................. 248

Contents • xiii

Chapter 11 A Lean IT Roadmap ................................................... 249

People Lead Lean IT Change................................................. 249How to Start the Lean IT Transformation ...........................252Lean IT Transformation Roadmap .......................................253Strategy .................................................................................... 254

Establish Leadership Vision and Consensus ................. 254Articulate Strategic Intent and Drivers .......................... 256

Planning ................................................................................... 256Define and Communicate the Transformation Plan .... 256

IT’s Stop-Doing List ................................................................257Build a Lean Leadership Team ........................................ 258Create a Basic Toolkit .........................................................259Assess Key Enterprise Value Streams ..............................259

Execution ................................................................................. 260Launch Pilot Kaizen Projects ........................................... 260Invest in Enterprise-Wide Infrastructure ...................... 260Measure Results and Assess Understanding and Buy-In .................................................................................. 260

Who Goes First? ......................................................................261Consolidate Gains and Build Momentum ..................... 262

Setting the Pace for Change ................................................. 264Endnotes .................................................................................. 266

SECTION V Lean IT Case Studies

Case Studies ........................................................................................ 269Barry-Wehmiller: Lean and ERP Work Together .............. 269Con-way: Document Management Virtual 5S ....................271Con-way: Focused Value Streams .........................................274Group Health: Lean Software Development Aligns with the Business Strategy .....................................................279Ingersoll Rand Security Technologies: Lean Six Sigma Improves Order Quality ........................................................ 284Steelcase: Product Data Management Lean Transformation ....................................................................... 288Toyota Australia: How IT Helped Implement Breakthrough Strategy Management ...................................291

xiv • Contents

Virginia Mason Medical Center: Laboratory Order Process and System Improvement ........................................301

Appendix A: A Brief History of Continuous Improvement ............ 307

Appendix B: How Lean and Six Sigma Work Together ................... 313Focus .........................................................................................315Roles ..........................................................................................315Project Size and Duration ......................................................316Project Selection ......................................................................316Complementary Coexistence .................................................317

Appendix C: Information Wastes ...................................................... 319

Appendix D: IT Service Desk A3 Example ....................................... 329

Index .................................................................................................... 333

About the Authors .............................................................................. 349

Introduction • xix

practical example of how Lean IT can enable and sustain the Lean enter-prise transformation.

An ancient proverb says that the best time to plant a tree is 20 years ago. The next best time is right now. So let’s get started.

section i

foundation

What Is Lean IT and Why Is it Important?

13

2Foundations of Lean

ChaPter oBjeCtiVes

To create a shared foundation for our discussion of Lean IT, in this chapter we will:

• Review a brief history of business process improvement, culminat-ing in Lean.

• Establish the foundational principles of a lasting transformation of culture and performance.

• Explore the concepts of value and waste in relation to Lean problem-solving tools, concepts, and terminology.

a Brief history of Continuous iMProVeMent

Since its beginnings at the turn of the twentieth century, business pro-cess improvement has focused on solving problems to improve effi-ciency, productivity, and quality. We view the evolution of process improvement as occurring in three distinct stages: scientific manage-ment, engagement, and integration.

the age of scientific Management: 1890–1940

Beginning in the late 1800s, business pioneers Frederick Taylor, Frank and Lillian Gilbreth, Henry Ford, and others ushered in an era of efficiency and

14 • Lean IT: Enabling and Sustaining Your Lean Transformation

productivity by introducing standardized manufacturing methods, simpli-fied work, and division of labor. Beginning in 1918, Walter Shewhart pio-neered the use of statistical control to improve quality. During this era, emphasis on output drove significant gains in productivity—for instance, Taylor at Midvale Steel Company (1878–1890) achieved gains greater than 300 percent—but also left workers uninspired with tedious, repetitive tasks.

During these early process improvement efforts, workers were consid-ered to be property and treated as such. Command and control was the established management system, in which workers were seen as inter-changeable resources, hired for their hands, not their minds. Those in management positions solved problems and were paid to think, while workers were expected to follow orders and meet output quotas.

the age of engagement: 1940–1995

World War II necessitated a massive shift in industrial productivity that could not be achieved using the existing system of management or the prevailing methods of process improvement. The U.S. Department of War introduced an innovative program, Training within Industry (TWI), which promoted worker participation, productivity-driven problem solving, supervisor training, work process documentation, and ongoing improvement programs that accelerated output and enhanced quality.

During this period, the ideas of W. Edwards Deming, Joseph Juran, and Armand Feigenbaum broke new ground introducing respect for work-ers, quality at the source, employee development, team problem solv-ing, and listening to customers to define value. The Quality Movement, as it became known, shifted the primary focus of process improvement from productive efficiency to delivering value to the customer. After the war, Taiichi Ohno and Shigeo Shingo at Toyota, and others in Japan, embraced the ideas of quality and continuous improvement and devel-oped the Toyota Production System—laying the groundwork for mod-ern-day Lean.

The 1980s were a time of competing methodologies as organizations experimented with various methods of continuous improvement. Six Sigma was introduced during this time and quickly became the poster child of process improvement, with successes at Motorola, Allied Signal, GE, and many other companies. Six Sigma applied statistical rigor to improvement processes and emphasized the quantification of results in

Foundations of Lean • 15

terms of dollar savings. With the publication of The Goal by Eli Goldratt in 1992,1 the Theory of Constraints also became popular, demonstrating that bottlenecks could be exploited to pace production, focus improvement efforts, and significantly boost throughput. Then in 1990, The Machine That Changed the World was published by Womack, Jones, and Roos at MIT.2 This book examined the Toyota Production System and introduced the term Lean. (For a detailed discussion of how Six Sigma and Lean can effectively work together, see Appendix B.)

Reengineering the Corporation,3 published in 1993, popularized busi-ness process reengineering (BPR) emphasizing process improvement and encouraging companies to abandon outdated systems, methods, and pro-cesses that no longer serve their purpose. While this was well intentioned, instead of engaging workers, it often was misunderstood and misapplied to justify downsizing. While the Age of Engagement experimented with the central idea of engaging people to drive continuous improvement, we still have a long way to go to achieve Deming’s vision as too many compa-nies still do not engage the hearts and minds of their people.

Note to the reader: For the remainder of this book, unless otherwise stated, we will use the term continuous improvement to embody all improvement disciplines, including Lean, Total Quality Management, Six Sigma, the Theory of Constraints, and the Toyota Production System.

the age of integration: 1996–Present

By the mid-1990s, companies around the globe were beginning to apply Lean, Six Sigma, and other improvement methods beyond the factory floor to office and administration, supply chain, accounting, and software development. Nonmanufacturing industries quickly discovered that Lean manufacturing techniques could produce significant results. Trading partners were enlisted to develop integrated processes throughout the supply chain. Advances in computing functionality, speed, and cost further supported the integration of business systems and communica-tions. In 1996, Lean Thinking4 was published, emphasizing integration of improvement across value streams, unleashing the current age of integra-tion of improvement methods across all functions of the business, and in all industries, including health care, insurance, banking, and nonprofits.

For an in-depth discussion of the history of continuous improvement, see Appendix A. For a timeline of continuous improvement, see Figure 2.1.


Lean PrinCiPLes

Many companies and individuals implementing Lean make the mistake of becoming preoccupied with specific tools. When properly applied, tools are performance enablers, but it is the principles embedded within the culture of an organization that compel long-term behavioral change. Without a clear grasp of Lean principles, focus on Lean tools is like sail-ing a ship without a rudder. Companies that fail to anchor their continu-ous improvement efforts with principles rather than tools may experience short-term localized results, but will not achieve the broad acceptance needed for sustained improvement. The Shingo Prize for Operational Excellence* emphasizes this primacy of principles over tools:

As organizations begin a Lean transformation, it is usually at the Tools & Techniques level in specific areas of the organization. Ideally, the Lean journey then proceeds to the Systems level, creating a more integrated and sustained improvement model. Eventually all employees throughout all business processes develop a deeper understanding of principles (the

* In 1988, the Shingo Prize for Operational Excellence was established to acknowledge Shigeo Shingo’s contribution to continuous improvement, promote awareness of Lean concepts, and rec-ognize companies that achieve world-class status in Lean manufacturing and business processes. The philosophy of the Shingo Prize is that world-class performance for quality, cost, and delivery can be achieved through consistent application of Lean principles and tools in all business pro-cesses. See www.shingoprize.org.

00020091

Henry FordConveyor Line/Process Flow

Taylor, GilbrethScientific Management

DemingVisits Japan

Taiichi Ohno - Birth of Toyota Production System

Shewhart atBell LabsStatistical Analysis/Process Control

TotalQualityManagement

Six SigmaMotorola, Allied Signal, GE

“�e Machine �atChanged the World”published

“Lean �inking”published

Lean Six Sigma

�eory of Constraints

TrainingWithin Industry

JuranVisits Japan

Feigenbaum publishes “Quality Control Principles” Shingo Prize

created

Age of Scientific Management Age of Integration

Lean Office, Supply Chain, Health Care, Service

Industries and beyond

“Reengineering the Corporation” published

1950

Age of Engagement

figure 2.1Timeline of continuous improvement.


‘know why’), empowering the organization to develop and deploy specific methodologies and practices unique to the organization.5

Principles are timeless, whereas tools evolve as needs change. Organizations which emphasize principles over tools significantly increase the likelihood of a successful transformation. By contrast, organizations that fall in love with certain tools (e.g., 5S and value stream mapping) may fail to establish the principles that form the bedrock of sustainable Lean performance. Eventually, the initial enthusiasm for Lean subsides, improvements become more challenging as the remaining problems get tougher, and there is nothing to fall back on to sustain long-term change.

In Principle-Centered Leadership, Dr. Stephen Covey stresses the need for organizations to embrace core principles which serve as a compass, providing constancy of purpose and alignment of organizational goals and actions. According to Covey, the most successful companies estab-lish objective, steadfast principles which reflect timeless values that guide behavior and foster a unique culture.6 When principles are borrowed from another company, they are easily discarded as soon as they become incon-venient to live up to. Companies should develop their own principles based on shared values and beliefs, and nurture them as consistent attitudes and behaviors. The following ideas are a compilation of central tenets we have seen successfully applied in support of lasting Lean transformations. Our discussion of Lean principles begins at the base of the pyramid (see Figure 2.2), laying a solid foundation. Experience has shown three ele-ments that support a strong social structure for a Lean enterprise.

Constancy of Purpose

• Theme: Leadership provides the direction and clarity we need to focus on the things that matter most—what Deming called “Constancy of Purpose,” maintaining clarity on important long-term objectives. This is the cornerstone in the principles pyramid because it provides the persistent direction needed to influence behavior. When daily behaviors change, culture also changes.*

* See Out of the crisis by W. Edwards Deming.


• The issue: In many organizations, there is a lack of clarity concern-ing what matters most. We like to ask various people at our client sites, “What are the goals of the company, and how do they influ-ence your daily work?” We typically receive a variety of answers. Two important issues often become apparent: (1) there is a wide range of understanding of company goals, and (2) goals are at best indirectly aligned with the concerns and actions of individuals and workgroups. This manifests as a lack of coordination within depart-ments and between various functional areas, accompanied by coun-terproductive or conflicting performance measures and incentives. Activity is often mistaken for productivity and is not necessarily effective in supporting the organization’s strategy or adding cus-tomer value.

• How does the principle address this challenge? Constancy of purpose focuses thinking and behavior, aligning effort and getting everyone rowing in the same direction. Effective leaders lead by example, a

Flow

Perspective

Behavior

Foundation Constancy of Purpose

Respectfor People

Pursuitof Perfection

Proactive Behavior

Voice ofthe Customer

Quality atthe Source Systems

�inking

Flow/Pull/JIT

Culture

TIM

E

QU

AL

IT

Y

CO

ST

MO

RA

LE

Capstone

figure 2.2Lean Enterprise Principles Pyramid.


responsibility that cannot be delegated. Management should adopt a visible and active role in supporting change. As people are encour-aged to challenge the way we do things around here and begin to perceive difficulties as opportunities for improvement, collabora-tive problem solving, and ownership of process quality starts to take root.

At this critical time, the way management reacts to setbacks either reinforces proactive behavior or discourages it. Effective lead-ers embrace an essential truth: poor processes—not people—are the cause of most problems. For most of his career, Deming put forth the 85/15 rule, suggesting that 85 percent of problems were inherent to process design and not controlled by the people doing the work. He later revised the estimate to 96 percent.

A clear understanding that Lean is about fixing processes, not peo-ple, creates the tone for fact-based improvement. In this atmosphere, people move out of their comfort zones, and actively seek out problems as opportunities to make things better. Every successful Lean trans-formation we have witnessed has been led by a champion who pro-vided the focus, enthusiasm, and drive that inspired others to move beyond business as usual. This role can be filled by an executive spon-sor, a program manager, or any person in your organization who pos-sesses credibility and respect. Early successes inspire others to become involved and build momentum. Gandhi said it best: “Be the change you wish to see.”

To be effective, leadership should be balanced with employee-driven participation. In a process known as strategy deployment,* leaders estab-lish objectives (top-down) and employees determine how to best accom-plish and measure them (bottom-up).

Some organizations often manage in a hierarchal, top-down manner with management at the top of the pyramid, issuing commands down-ward. Lean inverts this pyramid, as shown in Figure 2.3. At the very top are customers and business partners, since they define value and create demand pull signals that trigger work to be performed. Next are the work-ers, who most frequently interact with those customers, vendors, and

* Strategy deployment (also known as policy deployment, hoshin kanri, and hoshin planning) is a management system to align daily work with strategy. See Chapter 6.


trading partners and are, thus, in the best position to directly identify those actions that add the most value.

Management’s role is to translate and communicate purpose, strategy, and goals throughout the organization to teams and workers. Prioritization of improvements and consensus is achieved through a back-and-forth dia-logue between management and employees that aligns strategy and action at each level, reconciling action plans with available resource capacity. Rather than being told what to do, the people closest to the customer and the work develop and implement ideas for improvement based on a clear understanding of how their actions support company objectives.

Summary: Executive leadership’s responsibility is to define strate-gic goals and create a constancy of purpose. Management’s role is to eliminate barriers to success, stabilize processes, and sup-port employees to develop problem-solving skills, so they can take ownership of their work and assume responsibility for continuous improvement. When considering potential areas of improvement, the alternatives are almost endless, so an important enabler of effec-tive leadership is a formal decision-making framework. This estab-lishes clear priorities and ensures consistent choices are made when selecting improvement projects. Alignment and prioritization are consistent themes throughout this book, and we’ll revisit constancy of purpose in Chapter 10.

ImprovementIdeas

StrategicDirection

Managers

Associates

SeniorLeadership

CUSTOMERS, SUPPLIERS, AND TRADING PARTNERS

Team Leads & Supervisors

figure 2.3Lean Enterprise Inverted Managerial Pyramid.


respect for People

• Theme: The second foundation principle is respect for people. All individuals possess a unique collection of experience and insight, and can make a distinctive contribution when they participate in process improvement. Cross-functional problem solving can only occur when respect for people is consistently applied throughout all levels of the organization. Respect drives employee development, encourages participation, and improves supplier, customer, and community relations.

• The issue: When people sense that their input is disregarded or not respected, they tend to withdraw their support, concern, and active participation. Even worse, they may become cynical or even confrontational from having been left out of the dialogue. If leaders don’t engage the people doing the work with genuine respect, change for the better has little chance of succeeding. This is because those who have the knowledge and ability to create last-ing improvement have no stake in the final outcome. Worse yet, organizations lose the creativity and innovative potential each person offers.

• How does the principle address this challenge? Respect for people unlocks personal excellence and creative potential. In a collabora-tive learning environment, people know their ideas are valued and appreciated. Those individuals actually doing the work see potential improvement opportunities at a deeper level than anyone else in the organization. They hold the insight, understanding, and passion to add value and drive daily improvement. In some workers, these skills are dormant from lack of use.

Good leaders tap into this inexhaustible resource by mentoring, coaching, and collaborating with their associates, seeking their opin-ions and respecting differing points of view. Lean transformation requires the input, support, and active participation of everyone in the organization. Lean organizations cultivate collaborative problem solv-ing where people become scientific thinkers, learning from successes as well as failing forward from mistakes and setbacks. Questioning the way we’ve always done it is not only accepted, but also respected and positively acknowledged.


Humility is a very effective catalyst for a culture of continuous improve-ment, embodied in the Japanese term hansei, meaning mindfulness and self-reflection. Everyone in the organization must feel safe about sharing ideas and taking experimental risks, confident of not being ridiculed. Experimental risk is feeling comfortable enough to try new ways of doing things—approaching them as a means to validate new ideas, understand-ing, and predictions. Experiments never fail because they provide new evidence, clues to be used to develop further improvements! When we come to accept that every process can be improved, and that everyone brings a unique set of life experiences and perceptions to the table, people begin to appreciate that a good idea can come from anyone and that ideas have no rank.

Summary: Respect for people taps into an unlimited reserve of creativ-ity by treating every individual with consideration and regard. Give your people a good reputation to live up to.

Continuous improvement and the Pursuit of Perfection

• Theme: The final building block in our foundation is the continuous pursuit of perfection. Today’s solutions, while they may be adequate, are at best temporary. Change is relentless, and new ideas are needed whenever current standard work no longer produces acceptable results. In a Lean culture, workers embrace change as inescapable (and even desirable), proactively meeting challenges. Every individ-ual should see his or her job as having two inseparable components: daily work and daily improvement.

Changing social norms and daily behavior involves shifting the tone of the workplace from reactive firefighting (a deeply ingrained reflex often based on emotion) to proactive problem solving (methodical rational behavior).

• The issue: We are all creatures of habit and naturally territorial. Most people like change, but they don’t like being changed. Effective change is usually disruptive and uncomfortable. Left to our own human nature, we fall into patterns of thinking and behavior that actually avoid change and stifle creativity and innovation. When


Lean is perceived as a program or project (with a beginning and an end point), people may assume it is just another management fla-vor of the month that will blow over. They may then decide the best course of action is to keep your head down and ride low in the middle of the pack until the storm passes. Without active engagement and constant reinforcement, we naturally fall back on old habits of think-ing and behavior.

• How does the principle address this challenge? When we collectively recognize that if we are not improving we are falling behind, our understanding of daily work undergoes a radical shift. This realiza-tion breathes fresh ideas and energy into the organization, inspir-ing us to continually reinvent ourselves. With a constant focus on improvement, we avoid falling into patterns of stagnation in our daily behavior.

In The Fifth Discipline,7 Peter Senge uses the term learning organization to describe an environment where people continually develop their abilities to understand complexity and improve shared understanding. Setbacks and failures are treated as opportunities to reflect and learn. Perhaps most importantly, learning organizations encourage systems thinking—the ability to comprehend and focus on the whole while understanding the interrelationship of the parts. Each individual must begin identifying with the organization’s overall purpose and mission as well as individual department, workgroup, project, and process-level goals. The pursuit of perfection requires companies to become learning organizations where a trial-and-discovery method of process improvement is embraced without fear of reprimand or ridicule.

The pursuit of perfection is often misunderstood—it’s an aspiration, but one that is never achieved. Voltaire said, “The perfect is the enemy of the good.” With Lean, whether in the factory, the office, or the IT organiza-tion, we should avoid over-automating or striving for the hyper-efficiency of a “perfect solution”—these ultimately create waste and rigidity, and resist further cycles of improvement.

Summary: The endless quest for excellence stimulates everyone in the organization to make things better. People no longer see a difference between performing the work they do, improving the work they do, and improving themselves.


Proactive Behavior

Behavior

Foundation Constancy of Purpose

Respectfor People


Proactive Behavior

• Theme: Building on our foundation, proactive behavior means tak-ing the initiative, assuming personal responsibility for the quality of our work and work environment. Being proactive means seizing the opportunity to make a difference every day.

• The issue: Why do the vast majority of companies fail to achieve a sustaining Lean transformation? Perhaps one reason is that many people in the business world tend to be seasoned firefighters but poor police officers. Stereotypically, firefighters react to problems* by rushing into burning buildings and attacking everything that may be an issue (flames and smoke). They live on adrenaline dur-ing periods of intense focus until the crisis passes, and accept (even sometime enjoy) emergencies as part of normal operations. Police officers, by contrast, are methodical proactive problem solvers who walk the beat investigating the current situation to determine root causes of problems. Their focus is long term, systematic, preventa-tive, and disciplined. They ask lots of questions and shoot only when necessary.

• How does the principle address this challenge? In The 7 Habits of Highly Effective People, Dr. Stephen Covey introduces a model called the Time Management Matrix, dividing work into four quadrants based on importance and urgency. He points out that the highest value-added work lies in the Important but Not Urgent quadrant, where proactive planning, prevention, preparation, learning, and development occur. Unplanned work focuses on issues that are either Important and Urgent (reactive firefighting) or Not Important and Urgent (deceptive activities that seem important due to their urgency). In either case, they steal time and resources that should be used to proactively address Important but Not Urgent work.

* Our hats go off to real firefighters, some of the bravest and most proactive thinkers we know. In this example, we are talking about the common label of firefighting as a behavior.


Established culture often reinforces reactive firefighting at the cost of dis-ciplined problem solving. Because firefighting is highly rewarded, some firefighters become very good arsonists. This unconscious behavior cre-ates a never-ending cycle of interruptions and interventions which intro-duce more instability. Cultural DNA8 strongly influences organizations to revert to reactive behavior when problems arrive and the pressure is on. Ironically, reactive behavior usually introduces waste and creates more problems than it solves—actually preventing sustained progress.

As shown in Figure 2.4, Lean shifts the emphasis away from unplanned work to proactive continuous improvement. This approach is effective because it feeds itself: as more time is invested in process improvement efforts, less unplanned incidents occur, which frees additional time to work on more proactive improvements.

Summary: Deming described quality as “pride of workmanship.” Proactive behavior requires both personal and team pride combined with discipline. We then take responsibility for solving problems and strive for quality at the source.

Fire FightingCrisis Management

InterruptionsRework

Misaligned ObjectivesMisunderstood Tasks

Unproductive MeetingsExcessive Email

Interruptions

Lean �inkingAlignment

PrioritizationPlanning, Prevention,

and PreparationMeasurement

Reactive

Deceptive

Important

NotImportant

Proactive

Non-ValueAddedWork

Urgent Not Urgent

figure 2.4Lean perspective of the importance paradigm.


The next level in our pyramid addresses awareness, with three essential perspectives embraced by the Lean enterprise: voice of the customer, qual-ity at the source, and systems thinking.

Voice of the Customer

Perspective


Respectfor People


Proactive Behavior



�inking

• Theme: Lean thinkers always ask, “What does the customer value, want, and need?” By understanding how customers and information system users define value, they position themselves to begin with the end in mind.

• The issue: It is imperative that organizations develop a clear under-standing of what customers care about most. Often they assume they know what customers desire, and as a result deliver products and services that fail to address real customer needs.

• How does the principle address this challenge? Most processes have both internal customers who receive work output and external customers (trading partners and end users) who receive products, services, and information. To clearly understand the voice of the customer, you must engage with your customers, whoever they are. Use customer segmentation, interviews, focus groups, surveys, sales and service data analysis, and point-of-use observation to develop critical-to-quality requirements. Then return regularly to the cus-tomer to ensure improvements and innovations deliver what the customer values most.

Summary: Consistently listening to the voice of the customer ensures you are focusing on the right issues and making improvements that will be valued by your current and future customers. Understanding customer needs and desires more clearly than your competition will


enable you to be more responsive and agile, creating competitive advantage and market leadership.

Quality at the source

• Theme: Quality at the source means doing it right the first time, every time: imperfect work is not sent to the next operation or to the customer.

• The issue: The we’ll fix it later approach is accepted in many orga-nizations due to time pressure, inadequate training, and a lack of understanding of the entire process. The best time to solve a prob-lem is at the time it occurs because evidence is fresh, workers are engaged, and it prevents the release of additional defects until the root cause of the problem is corrected. The focus of daily work should be producing quality at the source. Solely focusing on quickly work-ing through the backlog results in the same problems reemerging time and time again. Time-consuming corrections, clarifications, and completions become necessary when quality is poor, creating interruptions and delays which increase costs and aggravation.

• How does the principle address this challenge? In a Lean environ-ment, there is an obligation to stop and fix problems, and a shared commitment to avoid passing known defects downstream toward the customer. By applying standardized work, training, and error proofing, every effort is made to ensure the problem or defect is pre-vented the next time. People assume responsibility for the quality of the work they pass on, regardless of where the problem originated. This fundamental change in attitude reduces waste and frustration. More importantly, problems become the evidence used to detect root causes and prevent their recurrence.

Summary: When quality at the source takes hold, more time is avail-able to do the work customers are paying for, which in turn improves productivity, cost, quality, and morale.

systems thinking

• Theme: The third element of awareness is systems thinking—the ability to view the interconnected processes that make up the entire


value stream while being aware of the cause-and-effect interdepen-dencies that either add value or create waste. A value stream is com-prised of all processes, tasks, and activities used to bring a product or service from concept to customer, and includes all information, work, and material flows.

• The issue: To avoid solutions that create localized optimization and silo behavior, Lean thinking requires an awareness of the simultaneously integrated and interdependent nature of all busi-ness functions and underlying information flows. This is not the way our minds and our organizations naturally work; we tend to focus on specific pieces of a puzzle rather than the entire picture. Inappropriate measures and incentives often reinforce this narrow focus.

• How does the principle address this challenge? When problem solv-ing is founded on a clear understanding of the overall value stream and the customers it serves, companies avoid the common error of making local improvements which often transfer inefficiencies and waste from one area to another. Cross-functional teams provide the breadth of understanding required for systems thinking, spanning the value stream by connecting the expertise and understanding of each team member.

The holistic perspective needed here may be unfamiliar to many pro-fessionals because they have spent their careers honing skills in a special-ized area (e.g., engineering, IT, finance, and human resources). A systems mind-set stimulates the creative potential of employees by broadening their horizons and challenging the breadth of their perception. To make improvements that impact external customers, a value stream must be viewed as a system. Value stream mapping and systems thinking are complementary, helping people to view business processes in a new con-text: flow.

Summary: Systems thinking enables us to see the whole, creating a smooth flow of value to the customer.


flow, Pull, and just in time

Flow


Respectfor People


Proactive Behavior



�inking

Flow/Pull/JIT

• Theme: The next level of the pyramid focuses on flow—the unin-terrupted progression of materials, services, and information. As Jeffrey Liker emphasizes in The Toyota Way, “Flow where you can, pull where you must.”9 Allow work to flow whenever you can; when flow is interrupted, use pull signals to initiate work.

• The issue: Poor flow of work manifests as interruptions, delays, rework, and cost. Deficient information flow causes even more irregular flow of materials, work in process, and finished work inventory where it is common to have too much (overstock) or too little (shortage). In an office environment, inventory is usually composed of paper and electronic documents, including e-mail. Work in process is all work started but not finished plus work queued up for the next process. As a general rule, the more work in process there is, the less work is able to flow, and the more slowly work is completed. Work in process inventory causes congestion, confusion, and delays; hides problems; must be managed and tracked; often becomes obsolete; and is often reworked or discarded. This in turn creates further interruptions, delays, rework, and cost.

• How does the principle address the issue? Flow is achieved through eliminating delays and interruptions throughout the entire value stream. Value stream mapping is an effective tool for identifying, quantifying, and eliminating waste. The smooth flow of informa-tion produces the transparency and visibility needed to coordinate efficient flow of work. When information is used to level demand,


balance capacity, and improve quality, flow is improved and value is delivered to the customer sooner.

When there are no interruptions in a series of tasks, work flows smoothly. Typically, work will flow until it encounters a barrier that prevents it from continuing (e.g., physical or electronic transportation to another location). When work cannot be designed to flow, it needs to be connected to the next series of tasks that do flow using a pull mechanism.

Pull removes the opportunity for overproduction* and supports flow by regulating work activity. In a pull system, all work is performed just-in-time triggered by a customer demand signal (kanban). The sequence of the pull signals establishes clear priorities, the receiver of the signal is directly accountable, and the signal itself provides visibility.

As overproduction decreases, work-in-process inventory decreases and flow is improved; work stoppages and delays happen less frequently, fur-ther reducing work in process, response time, and backlogs.

Summary: As flow improves, information and work product are received earlier by both internal and external customers. Flow releases pent-up, committed time and resources, effectively increasing an organi-zation’s capacity to respond to change with limited disruptions. This translates to better quality, response time, customer service, inven-tory turns, and ultimately cash flow.

Culture

• Theme: The capstone on our principles pyramid is culture, which represents an organization’s shared beliefs and values, manifested as attitude and behavior. Culture is an outcome of behavioral change. (See Figure 2.5) A Lean culture of continuous improvement cre-ates a shared capability which enables people to proactively seek out and solve problems, resulting in superior performance, competitive advantage, and bottom-line financial results.

• The challenge: Sustained Lean transformation is only possible when cul-ture evolves to reinforce new behaviors. The vast majority of companies

* Overproduction was considered the most harmful form of waste by Taiichi Ohno because it gener-ates other additional forms of waste (inventory, transportation, etc.).


that have embarked on a journey of continuous improvement (Lean, Six Sigma, or another discipline) have not realized long-term break-through results—having failed to transform their daily behavior and culture. The hearts and minds of their people are not engaged nor committed.

• How does the principle address the issue? We are often asked, “How do we create a Lean culture?” Our belief is that a Lean culture is developed over time by changing the way people perceive their roles and perform their daily work. In Who Says Elephants Can’t Dance? Lou Gerstner, former CEO of IBM, emphasizes the importance of culture:

I came to see, in my time at IBM, that culture isn’t just one aspect of the game—it is the game. In the end, an organization is nothing more than the collective capacity of its people to create value.10

Cornerstone


Respectfor People


Proactive Behavior



�inking

Flow/Pull/JIT

Culture

TIM

E

QU

AL

IT

Y

CO

ST

MO

RA

LE

Capstone

figure 2.5Lean Enterprise Principles Pyramid.


The evolution of a Lean culture often begins with the adoption of con-tinuous improvement tools, followed by the formation of behavior-driven systems, guided by shared values and principles. Tools provide structure and capability, systems* develop common practices and procedures, and principles provide a foundation which reinforces cultural standards and daily behaviors. (See Figure 2.6.)11

It’s one thing to create a mission statement and clever slogans articu-lating strategic objectives of the organization, and an entirely different thing to have a deeply shared vision and constancy of purpose by all employees. Shared beliefs are ref lected in self-created social systems that become the way we get things done around here. As organizations evolve, certain behaviors become the norm and are reinforced by daily actions.

When it is customary for people to take personal responsibility for the quality of their work, actively solve problems in a collaborative spirit, and give their very best, the energy and excitement of the workplace are palpable. The satisfaction of being part of an effective team accomplish-ing clear objectives is contagious. When actions are aligned with the principles we’ve discussed, they reinforce the strategic direction of the

* Systems, in this context, are collections of tools and procedures which form a standard way of doing things. Examples of Lean systems include kaizen process, A3 thinking, standard work, 5S, level loading, measurement, the visual workplace, and strategy deployment.

Embedding Principlesinto Culture

Structuring Tools into aSystems Context

Creating Point Solutions

figure 2.6Stages of Lean transformation.


organization while creating a constancy of purpose in support of unre-lenting improvement.

Summary: Aristotle said over 2,000 years ago, “We are what we repeat-edly do. Excellence, then, is not an act, but a habit.” Shared values and principles will serve as a compass throughout your Lean jour-ney. Develop a solid foundation of main beliefs that inspire respect, proactive behavior, innovation, and constant learning, and you will be well on your way toward sustainable operational excellence.

the CentraL ConCePts of VaLue and Waste

The principal focus of Lean is problem solving for the primary purpose of delivering value to the customer, achieved by the systematic elimination of waste throughout the value stream. While many people we meet feel they understand these concepts, often we discover their grasp of these terms varies greatly. Let’s begin by defining value stream, value, and waste.

Value stream

A value stream is composed of all the life cycle processes required to bring services, products, and information from concept to customer. This includes all current activities, whether or not they create value, carried out for internal and external customers. Value stream improvement requires a cross-func-tional perspective, drawing individuals, workgroups, and departments away from local optimization and silo thinking. Systems thinking enables people to see the whole process and understand value from the customer’s perspective.

Value

Value is what the customer wants and is willing to pay for. Intuitively, we all know some activities add value for the customer while others do not. Surprisingly, value stream mapping analysis reveals that, for most value streams, processes add value only 5 percent of the time it takes to deliver the product, service, or information to the customer. To put it another way, no value is created at least 95 percent of the time!


Value-added Work: Va, nVa, and nnVa

All components of work can be characterized as value-added (VA), non-value-added (NVA), or necessary but non-value-added (NNVA) work. The assessment process of whether an activity is adding value is straightforward but not always easy to answer: if they knew about it, would customers be willing to pay for it? Alternatively, would the cus-tomer judge the product or service as less valuable if the task was not performed?

NNVA work includes tasks the customer may not choose to pay for but the company is legally or ethically compelled to do (e.g., filing tax returns, Sarbanes-Oxley Act [SOX] compliance, supporting the local community, and other acts of corporate social responsibility).

the three Ms

Wasteful practices can be divided into three categories known as the three Ms: mura, muri, and muda. The differences and similarities among these terms lead to a deeper understanding of the impact of wasteful practices and the need for their methodical elimination.

Unevenness: Mura

Unevenness and variation (mura in Japanese) represent inconsistency in the flow of work, caused by changes in volume (uneven demand), mix (variation), and quality. Customers desire variety and flexibility, but these should be achieved while avoiding unnecessary complexity and chaotic behavior. It is the responsibility of management to minimize the impact of variation by encouraging standardized product and process design, level-ing demand, and introducing flow, pull, and just-in-time production con-trol and delivery systems.

Overburden: Muri

Overburden (muri in Japanese) represents placing unrealistic work-loads on people and equipment, which leads to stress, mistakes, rework, and poor morale. It is the job of management to remove overburden by


making use of work design,* training, standardized work, and demand management† to support a smooth flow of products, services, and information.

Waste: Muda

Waste (muda in Japanese) is any NVA work (defined earlier). In the mid-1950s, Taiichi Ohno introduced the concept of systematic elim-ination of waste at Toyota. This evolved into the Toyota Production System’s seven wastes found in production (see also Chapter 3 and Appendix C):

1. Overproduction: producing more or sooner than is needed by the customer (this contributes to the other wastes)

2. Inventory: having more than the minimum levels of raw materials, work in process, and finished goods required to support flow and pull (excess inventory disguises other wastes)

3. Waiting: stopping or slowing down for work to arrive 4. Transportation: movement of work product, information, and

materials 5. Overprocessing: excessive or unnecessary work 6. Motion: unnecessary physical movement 7. Correction: reworking defects and mistakes, inspection, and scrap

Often an eighth major waste is included in the list: unused human cre-ativity and potential. Recently many Lean practitioners have also begun to add environmental waste to the list. Every type of waste mentioned is found in all business environments, not exclusively manufacturing.

By learning to see those activities that consume time, materials, and effort while failing to add value, individuals and teams identify and remove muda from the value stream. While simple in theory, it requires practice to develop beginner’s mind—the ability to look at a familiar process as if for the first time and really see what is happening.

* Work design centers on creating work procedures and environments that support efficient execu-tion of tasks and smooth throughput of work by focusing on the difficulty of tasks, job stress, and employee satisfaction.

† Demand management is the practice of matching available capacity to a prioritized backlog of work to support an even flow of attainable work. See Chapter 5.


The Power of the Three Ms

The three Ms bring a comprehensive perspective to waste reduction and reinforce a cycle of continuous improvement.

Managers are responsible for addressing the systemic conditions of mura and muri. Variability (mura) reduction is achieved through selecting mar-kets, product design, and pricing, which supports level demand. Overburden (muri) reduction focuses on designing processes for workflow and consis-tent quality, standard work, cross-training, and balancing resources to cre-ate stable capacity conditions that support the smooth flow of information and work. When management reduces the systemic wastes of variability and overburden, levels demand, and frees capacity, workers then have the time, energy, and focus to continuously improve their activities to eliminate waste (muda), while simultaneously engaging in their daily work.

Lean tooLs oVerVieW

Lean offers a wide variety of problem-solving tools which provide structure and consistency to identify and quantify NVA tasks, analyze problems, discover root causes, develop countermeasures, implement improvements, and measure results. In this section, we provide a brief description of the most commonly used Lean tools.*

A tool is anything that enables us to accomplish a task more easily and effectively. We discovered long ago that, if you start out with just a handful of tools and then hone your process improvement skills, you will be in a much better position to learn and apply additional tools as you need them.

a3 thinking, the scientific Method, and PdCa

At the heart of Lean is the A3, a single piece of paper used to summarize the definition, scope, discovery process, findings, proposed countermeasures,

* For an in-depth discussion of Lean tools, see Pascal Dennis, Lean production simplified (New York: Productivity Press, 2007); John Bicheno and Matthias Holweg, The Lean toolbox, 4th rev. ed. (Johannesburg, South Africa: Picsie Books, 2008); and Chet Marchwinski and John Shook, Lean lexicon (Cambridge, MA: Lean Enterprise Institute, 2008). For an in-depth review of Six Sigma tools, see Thomas Pyzdek and Paul Keller, The Six Sigma handbook, 3rd ed. (New York: McGraw-Hill, 2009).


and results of a problem-solving exercise. A3 is an international paper size approximately 11 × 17 inches (297 × 420 millimeters), suggesting that a person or team be able to communicate the essential elements of a prob-lem-solving effort summarized on a single sheet of paper.

An A3 can also be employed as a proposal or status report. But the A3 is much more than a form; A3 thinking is a mental framework used to reinforce the scientific method of solving problems: Plan-Do-Check-Act (PDCA*). The scientific method is a structured approach to problem solving which includes observation, development of a tentative description of cause and effect (hypothesis), prediction, testing, and evaluation. More often than not, attempts at problem solving lack structure and method. People naturally jump to solutions, focusing on symptoms instead of root causes, and failing to fully understand, let alone solve, the problem at hand.

Benefits from applying A3 thinking include fact-based decision making, consensus building, clearly documented assumptions, defined targets, faster results, and follow-up to ensure that improvements are sustained.† Although there are many different formats for an A3, the specific form design is not important—but the disciplined A3 thinking process is. For an example of an A3, see Appendix D.

Value stream Mapping

Many people have experience with process mapping (as shown in Figure 2.7), which provides a detailed view of the tasks and decisions con-tained in a specific process. While process mapping is very effective at providing a detailed step-by-step view of a specific procedure, it does not attempt to capture information about flow, elapsed time, cost, or quality at the value stream level.

Value stream mapping visually depicts the flow of information, mate-rials, and work across functional silos with an emphasis on quantifying wastes, including time and quality. As shown in Figure 2.8, however, a value stream map can also illustrate a lower level of detail. Typically, the focus is at a more macro level than process mapping and does not include individual tasks and decisions.

* In healthcare this is commonly known as PDSA, Plan-Do-Study-Act.† For an in-depth example of A3 thinking and PDCA, see John Shook, Managing to learn

(Cambridge, MA: Lean Enterprise Institute, 2008).


Star

t

Serv

ice D

esk R

eceiv

esRe

ques

t

Forw

ard

to R

evie

wBo

ard

Que

ue

Cove

red

inSe

rvic

eCa

talo

g?

End

Serv

ice

Des

kIn

itial

Rou

ting

Proc

ess

Cove

red

Serv

ice?

Info

rm R

eque

stor

Clos

e Req

uest

Crea

te T

icke

t

Del

iver

yAc

cept

ance

Log

Serv

ice/

Clos

eTi

cket

Clos

e Req

uest

Info

rm R

eque

stor

/Sc

hedu

le W

ork

Yes

No

No

Yes

fig

ur

e 2.

7Pr

oces

s map

exa

mpl

e.


Cust

omer

CSC

Ente

rsIn

form

atio

nin

to S

AP

Sche

dule

d by

Disp

atch

Sche

dulin

g Pr

ogra

m

Prin

t Out

P/U

Requ

est

(loca

l)

CSC

Rece

ives

Ord

er

SAP

Pick

up

and

Driv

er M

akes

Rece

ivin

g Ta

g

Rece

ivin

g Cr

ewG

rade

s Dru

ms a

ndCo

mpl

etes

Tag

Send

Tag

sto

Adm

in.

Revi

ew T

ags

for C

ateg

ory

and

Pric

ing

Confi

rm in

Sys

tem

Upd

ate I

nven

tory

Batc

h Si

ze 5

Exce

l

Shar

ePo

int

File

a Co

pyM

ail t

o Co

rpor

ate

via

Clev

elan

d

Inte

roffi

ce 3

X w

eek

Sort

by L

ocat

ion

Proc

ess a

nd In

voic

eTa

g an

d In

voic

eto

Cus

tom

erFi

le T

ag

Cycl

e Tim

eM

ins

3Pr

oduc

tion

Lead

Tim

eM

ins

3

Qua

lity

%80

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eM

ins

60

Qua

lity

%10

0

Cycl

e Tim

eM

ins

2Pr

oduc

tion

Lead

Tim

eM

ins

120

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eM

ins

10

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eD

ays

5

Qua

lity

%10

0

Cycl

e Tim

eM

ins

60Pr

oduc

tion

Lead

Tim

eD

ays

5

Qua

lity

%95

Prod

uctio

nLe

ad T

ime

Day

s1

Cycl

e Tim

eM

ins

3Pr

oduc

tion

Lead

Tim

eM

ins

45

Qua

lity

%80

Cycl

e Tim

eM

ins

2Pr

oduc

tion

Lead

Tim

eM

ins

20

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eM

ins

20

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eM

ins

15

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eD

ays

4

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eM

ins

50

Qua

lity

%10

0

Cycl

e Tim

eM

ins

4Pr

oduc

tion

Lead

Tim

eM

ins

120

Qua

lity

%95

Cycl

e Tim

eM

ins

2Pr

oduc

tion

Lead

Tim

eH

rs4

Qua

lity

%10

0

Cycl

e Tim

eM

ins

1Pr

oduc

tion

Lead

Tim

eD

ays

2.5

Qua

lity

%10

0

11

E-M

AIL

FAX

IN

10 IN

Rece

ivin

g In

form

atio

nCu

rren

t Sta

te

Cycl

e Tim

eH

rs1.

40

Lead

Tim

eD

ays

18.9

6

NVA

%99

.7

Sum

mar

y D

ata

Qua

lity

%57

.76

10x

Day

POST

POST

One

Tag

per

Cust

omer

fig

ur

e 2.

8Va

lue

stre

am m

ap e

xam

ple.


Beyond the physical map itself, the activity of value stream mapping helps to bring a multidisciplinary team together to see the whole process from a work and information flow perspective. When a cross-functional team is assembled (ideally including a representative from IT) to map a process, a picture of the current state emerges through rounds of discussion and discovery. Once the team agrees that the current-state value stream map accurately depicts the situation, they are in a position to make data-sup-ported predictions on which improvements will yield the greatest results. Developing a current-state value stream map brings a shared understanding and consensus to the cross-functional team, representing stakeholders—including in-house resources, internal and external customers, vendors, and suppliers—from various parts of the organization that may seldom otherwise interact. As the team reaches agreement on the current state of the process and the waste it contains, they create a baseline for developing a future blueprint of the improved value stream, in order to highlight gaps between the current and target future state, prioritize activities, and estab-lish metrics.* Maintaining an updated current and future-state value stream map keeps the team focused, enabling targeted continuous improvement that delivers meaningful and quantifiable results.

Kaizen

Kaizen† (Japanese for continuous improvement) is a systematic improve-ment methodology that is central to Lean. Kaizen involves many small incremental improvements and provides structure to process improvement.

System and Process Kaizen

There are two kinds of kaizen: system (also called flow) and process (Figure 2.9). System kaizen attempts to improve the overall value stream by enhancing material and information flow, and is the focus of man-agement. Process kaizen, performed by teams and individuals, concen-trates on reducing waste in specific focus areas within the value stream. Improvement in one type of kaizen positively impacts the other.

* See Beau Keyte and Drew Locher, The complete Lean enterprise: Value stream mapping for admin-istrative and office processes (New York: Productivity Press, 2004); and Mike Rother and John Shook, Learning to see (Cambridge, MA: Lean Enterprise Institute, 1999).

† See Masaaki Imai, Kaizen: The key to Japan’s competitive success (New York: McGraw-Hill, 1986).


Kaizen events, Projects and Daily Improvement

The duration of kaizen activity ranges from a few minutes to several months. The degree of rigor and formality varies with the nature of the undertaking. Kaizen events are focused short-term improvement efforts that usually involve a cross-functional team and last from three to five days. Although the Kaizen event lasts just a few days, preparation can take place over several months prior to the activity.

Some Lean efforts require more time to plan and execute; these kaizen projects last from several weeks to up to three months. To maintain focus and deliver improvements as quickly as possible, we recommend that no kaizen activity last longer than 90 days. If the scope is larger than that, decompose the project into smaller phases (see Lean Project Management in Chapter 9).

For Lean to become a part of daily culture, every individual should be inspired to drive improvement on a daily basis. Daily kaizen (a form of process kaizen also known as a kaizen blitz) is spontaneous improve-ment performed as a need is identified. For example, when a problem is encountered, an individual or small group stops working to identify the problem, analyze it, develop potential countermeasures, select the most promising solution, make the improvement, and assess the impact. In a Lean enterprise, the highest proportion of problem solving occurs at the daily kaizen level.

SeniorMgmt

TeamMembers

System Kaizen (value stream improvement) • Improve Work & Info flow• Eliminate overburden• Eliminate variation

Process Kaizen(elimination of waste)

• People• Process

Top down Process Focus Bottom up

DailyKaizen

MidMgmt

figure 2.9Kaizen types


Kaikaku

Organizations also take on strategic breakthrough initiatives. Kaikaku, typically initiated by senior leadership, is system kaizen focused on achieving radical improvement, as contrasted with kaizen which is grad-ual and continuous. Kaikaku is strategically focused and represents a leap forward, not incremental change. Wisdom and experience suggest an organization should undertake only a few kaikaku projects at one time.

standardized Work

Standardized work defines and documents the most effective method to accomplish a task. There are usually a variety of ways to perform the same work, depending on who is doing it. Variation in work practices cre-ates variation in time, quality, and cost. First a team establishes a current standard to which they all agree to adhere. As work improvements are developed, tested, approved, and implemented (PDCA), they become the newest version of standardized work.* As variation and waste are reduced, process quality and stability are enhanced, and cost reduction is often a natural by-product.

Rather than being dictated by management, standard work is estab-lished and owned by the people performing the work, converting tribal knowledge known only by a few to a documented method consistently performed by all. Shared understanding of how work is done also sup-ports rapid learning, skills transfer, cross-training, and load balancing.

Standard work also applies to managers, supervisors, and team leaders. Using a Lean management system, leaders combine standard work, visual controls, gemba walks, daily accountability, and disci-pline to support their people and generate measurable results. Gemba is Japanese for “real or actual place” and highlights the need to leave the comfort of your office or cubicle and go where the internal or exter-nal customer is using the product or service to witness what is really occurring and verify your understanding. There is no substitute for personal observation.

For some people, the word standard implies rigidity and inflexibility—barriers to innovation. But in fact, the process stability created by standard

* For a comprehensive study, see David Mann, Creating a Lean culture: Tools to sustain Lean conver-sions (New York: Productivity Press, 2005).


work encourages innovation. Why? It is virtually impossible to improve a process that is unstable or not consistently performed. As work proce-dures are standardized, employees experience stable work processes upon which they can build.

5s and the Visual Workplace

5S is a workplace organization method. Roughly translated to English from Japanese, 5S stands for “Sort, Set in Order, Shine, Standardize, and Sustain.”* 5S provides a systematic approach for cleaning up, organizing, and maintaining an orderly workplace. Disorganized work environments encourage wasteful business practices and hide underlying problems. They also create mental clutter and chaos. Companies often begin their Lean journey with 5S, not only to establish a foundation of order, but also to raise awareness of business processes, sources of waste, and opportuni-ties for improvement (see the Con-way Virtual 5S case study).

5S also lays the groundwork for the visual workplace,† eliminating visual and mental noise—creating an environment where the status of work is so self-apparent that emerging problems call attention to themselves. By actively displaying the information that needs to be shared, the visual workplace provides people with the information they need to know with-out having to ask for it. A great deal of time is wasted on interruptions to answer questions such as “What is the status of …?” Most status inquiries are no longer necessary in a visual workplace, since the answers to such queries are constantly displayed, updated, and accessible to all.

Let’s get started!

We have established our foundation, discussing the central principles and tools of Lean. In the next chapter, we build on these ideas by describing Lean IT and its importance in creating and sustaining a Lean transformation.

* See Thomas Fabrizio and Don Tapping, 5S for the office (New York: Productivity Press, 2006).† See Gwendolyn Galsworth, Visual workplace, visual thinking (Portland, OR: Visual-Lean

Enterprise Press, 2005); and Hiroyuki Hirano, 5 Pillars of the Visual Workplace (New York: Productivity Press, 1995).


endnotes

1. Eliyahu Goldratt, The Goal, (Great Barrington: North River Press, 1984). 2. James P. Womack, Daniel T. Jones, and Daniel Roos, The machine that changed the

world (New York: HarperCollins, 1990). 3. Michael Hammer and James Champy, Reengineering the corporation (New York:

HarperCollins, 2003). 4. James P. Womack and Daniel T. Jones, Lean thinking (New York: Free Press, 1996),

16–26. 5. The Shingo Prize for Operational Excellence: Model-application guidelines, 3rd ed.

(Logan: Utah State University, Jon M. Huntsman School of Business), 3. 6. Stephen Covey, Principle-centered leadership (New York: Simon & Schuster, 1992). 7. Peter Senge, The fifth discipline, rev. ed. (New York: Random House, 2006). 8. Steven Spear and H. Kent Bowen, Decoding the DNA of the Toyota Production System

(Boston: Harvard Business Press, 2007). 9. Jeffrey K. Liker, The Toyota way (New York: McGraw-Hill, 2004), 108. 10. Lou V. Gerstner, Who says elephants can’t dance? (New York: HarperBusiness, 2002),

182. 11. Diagram supplied by The Shingo Prize for Operational Excellence (Logan: Utah State

University, Jon M. Huntsman School of Business, 2009).

Documents

Praise for Lean IT - Purpose Driven Leanpurposedrivenlean.com/wp-content/uploads/2016/01/583dd3ef3f8ca… · Praise for Lean IT “A great read on ... “The authors clearly articulate