World Library  
Flag as Inappropriate
Email this Article

The Toyota Way

Article Id: WHEBN0009040377
Reproduction Date:

Title: The Toyota Way  
Author: World Heritage Encyclopedia
Language: English
Subject: Management, The India Way, Visual control, Organizational culture, Shahid Khan
Collection: Lean Manufacturing, Management, Organizational Culture, Organizational Theory, Quality, Toyota
Publisher: World Heritage Encyclopedia
Publication
Date:
 

The Toyota Way

The Toyota Way is a set of principles and behaviors that underlie the Toyota Motor Corporation's managerial approach and production system. Toyota first summed up its philosophy, values and manufacturing ideals in 2001, calling it "The Toyota Way 2001". It consists of principles in two key areas: continuous improvement, and respect for people.[1][2][3]

Contents

  • Overview of the principles 1
  • The 14 Principles 2
    • Section I — Long-Term Philosophy 2.1
    • Section II — The Right Process Will Produce the Right Results 2.2
    • Section III — Add Value to the Organization by Developing Your People 2.3
    • Section IV: Continuously Solving Root Problems Drives Organizational Learning 2.4
  • Research findings 3
    • Long-term philosophy 3.1
    • Right process will produce right results 3.2
    • Value to organization by developing people 3.3
    • Solving root problems drives organizational learning 3.4
  • Translating the principles 4
  • Results 5
  • See also 6
  • References 7
  • Further reading 8

Overview of the principles

The Toyota Way has been called "a system designed to provide the tools for people to continually improve their work"[4] The 14 principles of The Toyota Way are organized in four sections: I) Long-Term Philosophy, II) The Right Process Will Produce the Right Results, III) Add Value to the Organization by Developing Your People, and IV) Continuously Solving Root Problems Drives Organizational Learning. The two focal points of the principles are continuous improvement and respect for people. The principles for a continuous improvement include establishing a long-term vision, working on challenges, continual innovation, and going to the source of the issue or problem. The principles relating to respect for people include ways of building respect and teamwork.

The 14 Principles

The system can be summarized in 14 principles.[5] The principles are set out and briefly described below:

Section I — Long-Term Philosophy

Principle 1

  • Base your management decisions on a long-term philosophy, even at the expense of short-term financial goals.

People need purpose to find motivation and establish goals.

Section II — The Right Process Will Produce the Right Results

Principle 2

  • Create a continuous process flow to bring problems to the surface.

Work processes are redesigned to eliminate waste (muda) through the process of continuous improvement — kaizen. The seven types of muda are:

  1. Overproduction
  2. Waiting (time on hand)
  3. Unnecessary transport or conveyance
  4. Overprocessing or incorrect processing
  5. Excess inventory
  6. Motion
  7. Defects

Principle 3

  • Use "pull" systems to avoid overproduction.

A method where a process signals its predecessor that more material is needed. The pull system produces only the required material after the subsequent operation signals a need for it. This process is necessary to reduce overproduction.

Principle 4

  • Level out the workload (heijunka). (Work like the tortoise, not the hare).

This helps achieve the goal of minimizing waste (muda), not overburdening people or the equipment (muri), and not creating uneven production levels (mura).

Principle 5

  • Build a culture of stopping to fix problems, to get quality right the first time.

Quality takes precedence (Jidoka). Any employee in the Toyota Production System has the authority to stop the process to signal a quality issue.

Principle 6

  • Standardized tasks and processes are the foundation for continuous improvement and employee empowerment.

Although Toyota has a bureaucratic system, the way that it is implemented allows for continuous improvement (kaizen) from the people affected by that system. It empowers the employee to aid in the growth and improvement of the company.

Principle 7

  • Use visual control so no problems are hidden.

Included in this principle is the 5S Program - steps that are used to make all work spaces efficient and productive, help people share work stations, reduce time looking for needed tools and improve the work environment.

  • Sort: Sort out unneeded items
  • Straighten: Have a place for everything
  • Shine: Keep the area clean
  • Standardize: Create rules and standard operating procedures
  • Sustain: Maintain the system and continue to improve it

Principle 8

  • Use only reliable, thoroughly tested technology that serves your people and processes.

Technology is pulled by manufacturing, not pushed to manufacturing.

Section III — Add Value to the Organization by Developing Your People

Principle 9

  • Grow leaders who thoroughly understand the work, live the philosophy, and teach it to others.

Without constant attention, the principles will fade. The principles have to be ingrained, it must be the way one thinks. Employees must be educated and trained: they have to maintain a learning organization.

Principle 10

  • Develop exceptional people and teams who follow your company's philosophy.

Teams should consist of 4-5 people and numerous management tiers. Success is based on the team, not the individual.

Principle 11

  • Respect your extended network of partners and suppliers by challenging them and helping them improve.

Toyota treats suppliers much like they treat their employees, challenging them to do better and helping them to achieve it. Toyota provides cross functional teams to help suppliers discover and fix problems so that they can become a stronger, better supplier.

Section IV: Continuously Solving Root Problems Drives Organizational Learning

Principle 12

  • Go and see for yourself to thoroughly understand the situation (Genchi Genbutsu).

Toyota managers are expected to "go-and-see" operations. Without experiencing the situation firsthand, managers will not have an understanding of how it can be improved. Furthermore, managers use Tadashi Yamashima's (President, Toyota Technical Center (TTC)) ten management principles as a guideline:

  1. Always keep the final target in mind.
  2. Clearly assign tasks to yourself and others.
  3. Think and speak on verified, proven information and data.
  4. Take full advantage of the wisdom and experiences of others to send, gather or discuss information.
  5. Share information with others in a timely fashion.
  6. Always report, inform and consult in a timely manner.
  7. Analyze and understand shortcomings in your capabilities in a measurable way.
  8. Relentlessly strive to conduct kaizen activities.
  9. Think "outside the box," or beyond common sense and standard rules.
  10. Always be mindful of protecting your safety and health.

Principle 13

  • Make decisions slowly by consensus, thoroughly considering all options; implement decisions rapidly (nemawashi).

The following are decision parameters:

  1. Find what is really going on (go-and-see) to test
  2. Determine the underlying cause
  3. Consider a broad range of alternatives
  4. Build consensus on the resolution
  5. Use efficient communication tools

Principle 14

  • Become a learning organization through relentless reflection (hansei) and continuous improvement (kaizen).

The process of becoming a learning organization involves criticizing every aspect of what one does. The general problem solving technique to determine the root cause of a problem includes:

  1. Initial problem perception
  2. Clarify the problem
  3. Locate area/point of cause
  4. Investigate root cause (5 whys)
  5. Countermeasure
  6. Evaluate
  7. Standardize

Research findings

In 2004, Dr. Jeffrey Liker, a University of Michigan professor of industrial engineering, published The Toyota Way. In his book Liker calls the Toyota Way "a system designed to provide the tools for people to continually improve their work."[4] According to Liker, the 14 principles of The Toyota Way are organized in four sections: (1) long-term philosophy, (2) the right process will produce the right results, (3) add value to the organization by developing your people, and (4) continuously solving root problems drives organizational learning.

Long-term philosophy

The first principle involves managing with a long-view rather than for short-term gain. It reflects a belief that people need purpose to find motivation and establish goals.

Right process will produce right results

The next seven principles are focused on process with an eye towards quality outcome. Following these principles, work processes are redesigned to eliminate waste (muda) through the process of continuous improvement — kaizen. The seven types of muda are (1) overproduction; (2) waiting, time on hand; (3) unnecessary transport or conveyance; (4) overprocessing or incorrect processing; (5) excess inventory; (6) motion; and (7) defects.

The principles in this section empower employees in spite of the bureaucratic processes of Toyota, as any employee in the Toyota Production System has the authority to stop production to signal a quality issue, emphasizing that quality takes precedence (Jidoka). The way the Toyota bureaucratic system is implemented to allow for continuous improvement (kaizen) from the people affected by that system so that any employee may aid in the growth and improvement of the company.

Recognition of the value of employees is also part of the principle of measured production rate (heijunka), as a level workload helps avoid overburdening people and equipment (muri), but this is also intended to minimize waste (muda) and avoid uneven production levels (mura).

These principles are also designed to ensure that only essential materials are employed (to avoid overproduction), that the work environment is maintained efficiently (the 5S Program) to help people share work stations and to reduce time looking for needed tools, and that the technology used is reliable and thoroughly tested.

Value to organization by developing people

Human development is the focus of principles 9 through 11. Principle 9 emphasizes the need to ensure that leaders embrace and promote the corporate philosophy. This reflects, according to Liker, a belief that the principles have to be ingrained in employees to survive. The 10th principle emphasizes the need of individuals and work teams to embrace the company's philosophy, with teams of 4-5 people who are judged in success by their team achievements, rather than their individual efforts. Principle 11 looks to business partners, who are treated by Toyota much like they treat their employees. Toyota challenges them to do better and helps them to achieve it, providing cross functional teams to help suppliers discover and fix problems so that they can become a stronger, better supplier.

Solving root problems drives organizational learning

The final principles embrace a philosophy of problem solving that emphasizes thorough understanding,

Translating the principles

There is a question of uptake of the principles now that Toyota has production operations in many different countries around the world. As a New York Times article notes, while the corporate culture may have been easily disseminated by word of mouth when Toyota manufacturing was only in Japan, with worldwide production, many different cultures must be taken into account. Concepts such as "mutual ownership of problems", or "genchi genbutsu", (solving problems at the source instead of behind desks), and the "kaizen mind", (an unending sense of crisis behind the company’s constant drive to improve), may be unfamiliar to North Americans and people of other cultures. A recent increase in vehicle recalls may be due, in part, to "a failure by Toyota to spread its obsession for craftsmanship among its growing ranks of overseas factory workers and managers." Toyota is attempting to address these needs by establishing training institutes in the United States and in Thailand.[6]

Results

Toyota Way has been driven so deeply into the psyche of employees at all levels that it has morphed from a strategy into an important element of the company's culture.[7] According to Masaki Saruta, author of several books on Toyota, "the real Toyota Way is a culture of control."[8][9] The Toyota Way rewards intense company loyalty that at the same time invariably reduces the voice of those who challenge authority.[10][11] "The Toyota Way of constructive criticism to reach a better way of doing things 'is not always received in good spirit at home.'"[12] The Toyota Way management approach at the automaker "worked until it didn't."[7]

One consequence was when Toyota was given reports of sudden acceleration in its vehicles and the company faced a potential recall situation. There were questions if Toyota's crisis was caused by the company losing sight of its own principles.[13] The Toyota Way in this case did not address the problem and provide direction on what the automaker would be doing, but managers instead protected the company and issued flat-out denials and placed the blame at others.[14] The consequence of the automaker's actions led to the 2009–11 Toyota vehicle recalls. Although one of the Toyota Way principles is to "build a culture of stopping to fix problems to get quality right the first time," Akio Toyoda, President and CEO, stated during Congressional hearings that the reason for the problems was that his "company grew too fast."[15] Toyota management had determined its goal was to become the world's largest automotive manufacturer.[16] According to some management consultants, when the pursuit of growth took priority, the automaker "lost sight of the key values that gave it its reputation in the first place."[17]

See also

References


-- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno

local p = {}


-- Helper functions


local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end

function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end

function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '
%s
', table.concat(classes, ' '), s )

end

return p-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno

local p = {}


-- Helper functions


local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end

function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end

function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '
%s
', table.concat(classes, ' '), s )

end

return p
  1. ^
  2. ^ Toyota Motor Corporation Annual Report, 2003, page 19. "The Toyota Way, which has been passed down since the Companyʼs founding, is a unique set of values and manufacturing ideals. Clearly, our operations are going to become more and more globalized. With this in mind, we compiled a booklet, The Toyota Way 2001, in order to transcend the diverse languages and cultures of our employees and to communicate our philosophy to them." (Mr. Fujio Cho, President, Toyota Motor Corporation)
  3. ^
  4. ^ a b
  5. ^
  6. ^
  7. ^ a b
  8. ^
  9. ^
  10. ^
  11. ^
  12. ^
  13. ^
  14. ^
  15. ^
  16. ^
  17. ^
  18. ^

Further reading

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 



Copyright © World Library Foundation. All rights reserved. eBooks from World Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.