This is the information that I gathered after doing a research on internet. It helps me alot in my troubleshooting work as an engineer.

#1 Indicators of attainment
How will I know the problem is solved?
What will I accept as evidence?
What does the solved state looked like?

#2 Putting equal attention on the problem state as well as solved state
Most of time, we channeled most of our energy into the problem state and got too engrossed in it and forgot about the solved state. Soon we realised that we lost our objectives.
First, we do some defining and self thought on the problem
Fill Up the problem matrix below and get an overview of it.

#3 Defining Problem
Establish boundary ( Locate)
Give distinguishing characteristics; Differentiate (Isolate)
To state the nature of; describe precisely (articulate)
state the meaning, definition (expliate)
It is good to revisit this on a regular basis and revise them as necessary.

#4 Plans
Although it is difficult to stick to plans, plans are required to ensure that we cover all that that needs to be covered. I called it ‘cover the bases’.
1. define the problem state
2. specifying solved state
3. Modeling the structure of the problem
4. Finding and fixing the ’cause’ of the problem
5. Engineering a solution
6. Settling on a course of action
7. Reconciling restraints & constraints
8. Obtaining support and consensus.
9. Preparing plans and schedules
10. taking actions
11. Accessing its effects & consequences
12. Adjustin further actions as required
-Step 4 and 5 are mutually exclusive. Do either one of them.

#5 Draw pictures of the structure of the problem
From input to output, draw out a flow chart of how the entire system works. Check for every small details for a possiblity of error to occur.

#6 Take concept of cause with a grain of salt
Finding cause is time consuming and may not help in solving the problem
Therefore at the start, decide if the concept of cause is /isn’t relevant before spending time/energy looking for something that doesn’t exist.

#7 Beware of vertical and hortizontal disconnects.
Vertical disconnects refers to the management team from your boss all the way down to operators. Communication and instructions may go wayward as it is being down.
Horizontal disconnects refer to people who are at the same level as you and help you in your work. A techician may find implementation difficult which analyst does not see.

#8 Be aware of own blinders
for example labeling a problem as attidual problem, system problem , psychological problem may miss out any other causes. Different labels require different actions taken. Therefore, it is always useful to check whether a change of labeling is required at times.