Gratitude: 6 step troubleshooting

This here gave me an advantage in life by learning this at the young age of 19 in the US Navy. I apply this in just in so many portions of life and it transfers to many different frame works with slight variants.

1. Identify the Problem
This initial step involves gathering information about the issue12. Technicians should:
Collect details from error messages, log files, and user reports
Ask questions to understand the symptoms
Determine if any recent changes occurred
Try to replicate the problem if possible
2. Establish a Theory of Probable Cause
Based on the information gathered, technicians should:
Consider multiple potential causes
Question obvious assumptions
Use existing knowledge bases and documentation
Consider both simple and complex possibilities2
3. Test the Theory to Determine Cause
This step involves verifying the suspected cause without making configuration changes2. Technicians may:
Check physical connections
Review settings and configurations
Run diagnostic tests
4. Establish an Action Plan and Implement It
Once the cause is determined, technicians should:
Develop a plan to resolve the issue
Consider potential impacts of the solution
Implement the fix or escalate if needed12
5. Verify Full System Functionality
After implementing the solution:
Test that the original problem is resolved
Check that no new issues were introduced
Have users verify functionality if possible2
6. Document Findings, Actions, and Outcomes
The final step involves:
Recording the problem, cause, and solution
Noting any lessons learned
Updating knowledge bases or documentation