Skip to content

Instantly share code, notes, and snippets.

@sakurai-youhei

sakurai-youhei/problem-solving.md

Last active March 22, 2022 14:50
Show Gist options
  • Save sakurai-youhei/68716a245d43ab47cac1154a987416dd to your computer and use it in GitHub Desktop.
Save sakurai-youhei/68716a245d43ab47cac1154a987416dd to your computer and use it in GitHub Desktop.
Download ZIP
My principles in problem-solving
Raw
problem-solving.md

My principles in problem-solving

  • 50+% is done when understanding the problem well.
  • Every problem-solving SHOULD be a one-way journey.

Application to troubleshooting

  • 50+% is done when understanding the trouble well.
  • Every troubleshooting SHOULD be a one-way journey to identify what to be corrected.
  • Our expectations could sometimes have to be corrected, too; we may be younger than we were!

troubleshooting-flow.png

!! Never ever underestimate the Understanding phase as Garbage in, garbage out is truth.

Where to start troubleshooting

Write down these carefully.

  1. Trouble - What trouble is annoying us?
  2. Issue - What issue should be addressed?
  3. Expectation - What expectation do we have?
  4. Result - What result do we observe?
  5. Title - What do we call it in a sentence?
  6. (optional) Steps - How can we reproduce it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment