Root at 06:01, 20 October 2025

2025-10-20T06:01:18Z

← Older revision		Revision as of 07:01, 20 October 2025
Line 92:		Line 92:
	* '''Status''': [Pending/Completed/Effective/Ineffective]		* '''Status''': [Pending/Completed/Effective/Ineffective]
	* '''Notes''': [Any observations or further recommendations]		* '''Notes''': [Any observations or further recommendations]
	~~<!-- From bodyContent 1543012.mraw -->~~

	[[Category:documentation templates]]		[[Category:documentation templates]]

Maintenance script: Added category documentation templates

2025-10-19T17:51:57Z

Added category documentation templates

← Older revision		Revision as of 18:51, 19 October 2025
Line 94:		Line 94:
	<!-- From bodyContent 1543012.mraw -->		<!-- From bodyContent 1543012.mraw -->

			[[Category:documentation templates]]

Maintenance script: Maintenance script moved page UserDocumentation:Templates/documentation templates/5 whys to 5 whys: Cleaned title and categorized

2025-10-19T17:51:57Z

Maintenance script moved page UserDocumentation:Templates/documentation templates/5 whys to 5 whys: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 09:18, 19 April 2025

2025-04-19T09:18:55Z

← Older revision		Revision as of 10:18, 19 April 2025
Line 1:		Line 1:
			The "5 Whys" is a problem-solving methodology that focuses on identifying the root cause of an issue by asking "Why?" repeatedly until the underlying problem is identified. It is a straightforward technique developed by Sakichi Toyoda and was later integrated into the Toyota Production System. Although it's called the "5 Whys," it's not strictly limited to five questions; you keep asking "Why?" until you reach the root cause.

			<span id="procedure"></span>
			= Procedure =

			* State the problem clearly.
			* Ask "Why did this problem occur?"
			* Based on the answer to the first "Why?", ask "Why?" again.
			* Continue the process until you identify the root cause of the problem.
			* Once the root cause is identified, implement corrective actions to prevent the problem from recurring.

			<span id="example-of-an-organizations-server-unexpectedly-shuts-down"></span>
			== Example of an organization's server unexpectedly shuts down ==

			'''Problem''': The server shut down unexpectedly.

			* '''Why?''' The server overheated.
			* '''Why did the server overheat?''' The cooling system failed.
			* '''Why did the cooling system fail?''' The air filters were clogged with dust.
			* '''Why were the air filters clogged with dust?''' They hadn't been cleaned or replaced in over a year.
			* '''Why hadn't they been cleaned or replaced?''' There was no scheduled maintenance or reminder system in place.

			'''Root Cause''': The absence of a scheduled maintenance or reminder system for server upkeep led to the server's unexpected shutdown. '''Corrective Action''': Implement a scheduled maintenance plan and set reminders for regular checks and replacements of crucial components.

			<span id="example-of-low-response-time-on-a-companys-e-commerce-website"></span>
			== Example of low response time on a company's e-commerce website ==

			'''Problem''': The e-commerce website is responding slowly.

			* '''Why?''' The server is experiencing high CPU usage.
			* '''Why is the server experiencing high CPU usage?''' There's a spike in traffic.
			* '''Why is there a spike in traffic?''' A promotional campaign was launched today.
			* '''Why was the server not prepared for this spike given the promotional campaign?''' The marketing team didn't notify the IT department about the expected increase in traffic.
			* '''Why didn't the marketing team notify the IT department?''' There's no established communication protocol for such events.

			'''Root Cause''': Lack of communication protocol between the marketing and IT departments led to the server not being prepared for a spike in traffic. '''Corrective Action''': Establish a communication protocol between departments for events or campaigns that can lead to significant changes in website traffic.

			By following the 5 Whys methodology in these examples, the organizations were able to pinpoint the underlying issues and take corrective action to prevent future problems.

			<span id="guideline-document"></span>
			= Guideline document =

			* '''Department''': [Department Name]
			* '''Date''': [Date]
			* '''Facilitator''': [Facilitator's Name]
			* '''Team Members''': [Names of those involved in the analysis]

			<span id="problem-statement"></span>
			== 1. Problem statement ==

			Clearly define and describe the problem.

			[Description of the observed problem]

			<span id="the-5-whys"></span>
			== 2. The 5 whys ==

			Start with the problem statement, and then proceed to ask "Why?" until the root cause is identified.

			<span id="why-1"></span>
			=== Why 1 ===

			'''Question''': Why did [problem or outcome from the previous answer] happen?

			'''Answer''': [Answer to the first "Why?"]

			<span id="why-2"></span>
			=== Why 2 ===

			'''Question''': Why did [outcome from the previous answer] happen?

			'''Answer''': [Answer to the second "Why?"]

			(Continue the process as needed...)

			<span id="root-cause-identification"></span>
			== 3. Root cause identification ==

			[Identified root cause after asking the series of "Why?" questions]

			<span id="corrective-actions"></span>
			== 4. Corrective actions ==

			* '''Proposed Action''': [Suggested action to address the root cause]
			* '''Responsible Person/Team''': [Name/Team assigned to execute the action]
			* '''Deadline''': [Date by which the action should be implemented]

			<span id="follow-up"></span>
			== 5. follow-up ==

			* '''Review Date''': [Date when the team will review if corrective actions have been effective]
			* '''Status''': [Pending/Completed/Effective/Ineffective]
			* '''Notes''': [Any observations or further recommendations]
	<!-- From bodyContent 1543012.mraw -->		<!-- From bodyContent 1543012.mraw -->

imported>Unknown user at 09:18, 19 April 2025

2025-04-19T09:18:55Z

← Older revision	Revision as of 10:18, 19 April 2025
(No difference)

imported>Unknown user at 09:18, 19 April 2025

2025-04-19T09:18:55Z

New page

5 whys - Revision history

Root at 06:01, 20 October 2025

Maintenance script: Added category documentation templates

Maintenance script: Maintenance script moved page UserDocumentation:Templates/documentation templates/5 whys to 5 whys: Cleaned title and categorized

imported>Unknown user at 09:18, 19 April 2025

imported>Unknown user at 09:18, 19 April 2025

imported>Unknown user at 09:18, 19 April 2025