NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 3 — The Universal Seven-Step MethodologyLesson 1 of 4
Video lesson

The Seven Steps at a Glance

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 3 — The Universal Seven-Step Methodology · Lesson 3.1 · Based on Chapter 3 (introduction, Figure 3.1 and §3.8) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Name the seven steps of the troubleshooting methodology in the correct order.
  • State the key question and the output of each step.
  • Explain the loop between Step 2 and Step 3, and what ends it.
  • Trace a single fault through all seven steps, from the first symptom to the written record.

Watch: The Seven Steps at a Glance

The video presents the whole method in one view, using the book's Figure 3.1, and then follows one fictional fault — a payroll workbook that crashes a spreadsheet program — from the moment the ticket is raised to the moment the record is closed. As you watch, keep these questions in mind:

  • At what point does the technician first think about a fix, and why not earlier?
  • Where in the incident is the user's data protected?
  • What makes the final record useful to someone who never saw the fault?

One method for every problem

Every problem in this course is solved with the same seven steps. Dr Al Doori notes that the methodology is widely used across the IT industry and forms the basis of most professional support training. Its strength is that it works for any system: the steps never change; only the likely causes do. A laptop that will not charge, a network that will not connect and a business process that keeps failing are all approached in the same order.

IdentifyTheoryTestPlanImplementVerifyDocument

The seven steps, in the author's words, are:

  1. Identify the problem.
  2. Establish a theory of probable cause.
  3. Test the theory to determine the cause.
  4. Establish a plan of action.
  5. Implement the solution or escalate.
  6. Verify full system functionality.
  7. Document findings, actions and outcomes.

Learn them in this order and in these words. Later modules add techniques to each step, but they never change the steps themselves.

Reading Figure 3.1

The book draws the method as a flow with one decision in it. Steps 1, 2 and 3 run left to right along the top. After Step 3 comes a question: is the theory confirmed?

  • No: go back to Step 2, establish a new theory and test it — or escalate.
  • Yes: go down to Step 4 and plan the fix, then continue through Steps 5, 6 and 7.

The figure carries a short caption worth remembering: Steps 1–3 diagnose the fault; Steps 4–7 resolve it and capture what was learned.

The Step 2 ↔ Step 3 loop

The loop between establishing and testing a theory is the engine of diagnosis. You propose the most likely cause, run one small test, and either confirm it or reject it. A rejected theory is not a failure: it removes one possibility and sends you back to Step 2 with a shorter list. The loop ends in only two ways:

  • a theory is confirmed, and you move to Step 4; or
  • the problem is escalated, because all theories are exhausted or the problem is beyond your skill, access or authority (escalation is covered fully in Module 13).

The book's key rule follows directly: no fix is applied until a cause is confirmed. Skipping from a theory straight to a fix is the "jumping to a fix" mistake from Module 2.

In one line: identify, theorise, test, plan, implement, verify, document. Keep looping between Steps 2 and 3 until a cause is confirmed, apply nothing before that, and do not call the job done until the result has been verified and written down.

The method at a glance

The book summarises each step as a question you are trying to answer and an output you should hold when the step is finished. If you cannot point to the output, the step is not finished.

StepKey questionOutput
1. IdentifyWhat exactly is wrong?A clear problem statement
2. TheoryWhat could cause this?A ranked list of probable causes
3. TestIs this theory correct?Confirmed or rejected cause
4. PlanHow will it be fixed safely?Steps, backup and rollback plan
5. ImplementWas the plan applied carefully?The change, or an escalation
6. VerifyDoes everything work now?User confirmation; preventive measures
7. DocumentWhat was learned?A written record

Three outputs deserve special attention because beginners often skip them:

  • A ranked list (Step 2). Not one favourite idea, but several causes in order of likelihood and simplicity.
  • A backup and rollback plan (Step 4). A rollback means undoing a change to return to the previous working state. You plan it before you change anything.
  • User confirmation (Step 6). The problem is not solved until the person who reported it agrees that it is.

Protect data at every stage. The method asks you to back up data in Step 1 if there is any risk to it, and to confirm the backup and record current settings in Step 4. Never begin a change on a system holding important data until you know a usable copy exists.

Worked example

(Fictional scenario.) This is the incident animated in the video.

StepWhat happened
1. IdentifyTuesday, 08:40. Maya, a payroll officer, reports that her spreadsheet program closes whenever she opens the payroll workbook. It started on Monday afternoon. Only her laptop is affected — colleagues open the same file normally. A new PDF add-in was installed on Monday at 14:00. Because payroll data is involved, the technician first confirms that the workbook is stored on the server and that last night's backup exists.
2. TheoryRanked list: (1) the workbook is corrupt; (2) the new add-in crashes the program.
3. TestTheory 1: a colleague opens the same file — it opens normally, so the theory is rejected. Back to Step 2. Theory 2: start the program with add-ins switched off — the workbook opens, so the theory is confirmed.
4. PlanBackup confirmed; the current list of add-ins recorded; the only change will be to disable the new add-in; rollback is to re-enable it from the recorded list; Maya is told she will lose the PDF feature for now; the team lead approves, because the add-in was installed for the whole team.
5. ImplementThe add-in is disabled — one change, nothing else touched.
6. VerifyThe workbook opens; saving, printing and the program's own export still work; Maya confirms it works for her. Prevention: new add-ins will be tested on one machine before wider installation.
7. DocumentThe ticket records the symptom, the confirmed cause, the action and its rollback, the checks made, who verified it and the preventive measure.

Notice that the technician spent most of the time on Steps 1–4 and only seconds on the change itself. That balance is typical of good troubleshooting.

Try it

Choose a simple, harmless fault you have seen recently — for example a phone that would not join Wi-Fi, or a document that would not print. Working on paper (do not change any device for this activity):

  1. Copy the seven step names in order down the left of a page.
  2. Beside each step, write the key question from the table above.
  3. Fill in what happened (or what you think should have happened) at each step, including at least one rejected theory.
  4. Mark where data was, or should have been, protected.

Completion criteria: all seven steps are present in the correct order; Step 2 contains at least two ranked theories; Step 3 shows at least one rejected theory and how you returned to Step 2; Step 4 names a rollback; Step 6 includes the user's confirmation.

Knowledge check

Which list gives the seven steps in the correct order?

A test disproves your theory. According to Figure 3.1, what happens next?

What is the output of Step 4, Establish a plan of action?

In the payroll example, why was a colleague asked to open the same workbook?

Answers explained

  1. C — this is the author's order. A and D swap steps, and B places planning before testing, which would mean planning a fix for an unconfirmed cause.
  2. A — the "No" path in Figure 3.1 returns to Step 2 or leads to escalation. B and C apply fixes without a confirmed cause; D abandons the problem.
  3. D — Step 4 produces the steps, backup and rollback plan. A is Step 2's output, B is Step 6's, and C is Step 1's.
  4. B — it is a small, safe Step 3 test of Theory 1; the file opened, so the theory was rejected. It was not verification (no fix had been made), workload sharing or approval.

Key takeaways

  • The seven steps never change; only the likely causes do.
  • Steps 1–3 diagnose the fault; Steps 4–7 resolve it and capture what was learned.
  • Steps 2 and 3 loop until a theory is confirmed or the problem is escalated — no fix before then.
  • Every step has an output; a plan always includes a backup and a rollback.
  • A problem is closed only when the user has confirmed the fix and the outcome is recorded.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), Chapter 3 introduction, Figure 3.1, §3.8 and Key Takeaway.