Skip to main content

The 5 Principles of Lean Thinking



Value
Lean starts with a defining value precisely from the perspective of the customer in the relationship to the features and characteristics of the organization’s product (goods or services) and other critical attributes.

Value Stream
A value stream contains all of the activities required to create customer value for a service product or family of products. This would include all of the processes needed from designing the product, building, testing, releasing and deploying it into the live environment, being able to support the use of the product by your customer and finally being able to improve it to meet the customers changing requirements over the lifetime of the product. Lean organizations wisely distinguish their value streams and arrange their operations to maximize the value created for the customer and minimize the waste in these processes.

Flow and Pull
Make the remaining value–creating steps flow. Lean organizations will seek to maximize the flow of materials, resources and capabilities. These processes will be designed to maximize the flow of the product through the value stream. This is a pull system and will be initiated by the pull of customer demand. Partnering with customers and suppliers will be critical in ensuring that a smooth flow will be accomplished, providing what the customer wants only when they want it; a goal of perfection. Lean processes are designed to maximize the flow of information, knowledge, capabilities and resources. This is accomplished by using integrated tool sets, pull processes and the continual perfection of goals.

Empowerment
Empowerment comprises of a set of tools and controls that enable each employee with the appropriate information and authority to take the essential action at the time it is required so as to add value for the customer and eliminate waste from the process.

Perfection
The pursuit of perfection is fundamental to lean thinking. The goal is not to make intermittent jumps of improvement but rather for everyone in the organization to focus on making incremental improvement in their own processes day in and day out. While few of these improvements will significantly change the processes in the short term, the combined effect of these changes is continual improvement in service quality, flow, cost and customer value. The goal is nothing less than perfection. Everyone realizes that perfection is unlikely to be achieved, but that is the goal.


For more information please see the publication "Lean Thinking: The Principles of Lean Manufacturing" written by James J. Womack and Daniel T. Jones



















Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…