Attitude Before Action: The Seven Principles
Where you are: Module 2 — The Troubleshooting Mindset · Lesson 2.1 · Based on Chapter 2 (§2.1–2.2) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Explain why attitude comes before action in troubleshooting.
- Name the seven principles of effective troubleshooting in the book's order.
- Apply each principle to a real fault, and identify which principle protects the user's data.
Watch: Attitude Before Action: The Seven Principles
The video opens with a speaker who panics when a projector shows "No signal" ten minutes before a talk, and ends up creating a second problem. It then introduces the seven principles one by one and replays the same situation with the principles in place. Keep these questions in mind:
- Which of the speaker's actions broke a principle, and which one?
- Why does the replayed version need only one change?
- What did the system tell the troubleshooter before anything was touched?
Attitude before action
The book makes a striking claim: the right attitude solves half the problem before anything is touched. Two forces work against good troubleshooting:
- Panic narrows thinking and encourages shortcuts. Under pressure, people skip steps, make several changes at once and stop reading what is in front of them.
- Assumptions send the investigation in the wrong direction. If you are already sure of the answer, you stop looking for evidence.
Effective troubleshooters stay calm, curious and methodical, treating each problem as a puzzle with a logical answer. Calm keeps the mind clear; curiosity keeps you asking questions and gathering evidence; method keeps the work in order and on record.
The seven principles
The book turns that attitude into seven principles. Learn them in this order:
Stay calm
A problem is a puzzle, not a disaster. Stress causes skipped steps and careless changes.
Be curious, not certain
Treat the first idea as a theory to test, never as the answer.
Start simple
Most problems have simple causes: no power, a loose cable, a typing error, a full disk, an expired password.
Change one thing at a time
If three things are changed and the problem disappears, it is impossible to know which one fixed it.
Observe before acting
Read the error message, look at the indicator lights, listen to the noise. The system is usually reporting what is wrong.
Protect what matters
Back up data and record the original settings before making any change.
Write it down
Notes prevent repeated attempts and make the next fix faster.
What each principle looks like in practice
- Stay calm. Before doing anything, pause long enough to read the situation. A minute spent looking saves ten spent undoing.
- Be curious, not certain. Say "my theory is…" rather than "it's…". The words remind you that a theory must be tested. You will meet the biases that make first ideas feel right in Lesson 2.3.
- Start simple. Check the simple causes even when the problem seems complex. Simple causes are the most common, and checking them is quick. Module 5 turns this principle into five quick-win checks.
- Change one thing at a time. One change, then test. Lesson 2.2 explores this principle in depth.
- Observe before acting. An error message such as "Not enough disk space" often names the cause outright. Indicator lights (steady, blinking or off), beeps and sounds such as clicking or grinding are all evidence.
- Protect what matters. This is the principle that protects the user's data. Before any change, make sure important files are backed up and note the original settings, so you can always return to the starting point.
- Write it down. Record what you observed, what you tried and what happened. Notes stop you repeating attempts and let a colleague continue where you stopped.
Protect what matters, in practice. If there is any risk to data, back it up before troubleshooting, not after. If a device shows signs of a failing disk (clicking, grinding, files becoming corrupt), stop using it unnecessarily and escalate: every operation on a failing drive can make recovery harder. Practise unfamiliar tools on a training machine or virtual machine, never on your only copy of important work.
Calm, curious and methodical. Stay calm, be curious not certain, start simple, change one thing at a time, observe before acting, protect what matters, write it down.
Worked example
(Fictional scenario.) It is 09:50 in Lecture Theatre B, and a guest speaker's talk starts at 10:00. The projector shows "No signal".
What happened first. The speaker unplugs both cables, changes three display settings and restarts the laptop twice. The projector still says "No signal", and now the laptop's audio is muted too. Panic produced several changes at once (principle 4 broken), nothing was observed or recorded (principles 5 and 7 broken), and a new fault was created.
The same problem, with the principles:
| Time | Action | Principle |
|---|---|---|
| 09:50 | Pause. Read the projector's message: "No signal" means it is receiving nothing on its current input. | Stay calm; observe before acting |
| 09:51 | Simplest theory first: the projector is looking at the wrong input. | Be curious, not certain; start simple |
| 09:52 | One change: press the projector's Source button, switching from HDMI 1 to HDMI 2. | Change one thing at a time |
| 09:53 | The image appears. The audio muted earlier is unmuted and sound is checked before the talk. | Observe (confirm the result) |
| 09:55 | A note is left for the room: "Lectern cable uses HDMI 2." | Write it down |
Nothing on the laptop needed changing. Had a laptop setting needed changing, recording the original value first would have applied principle 6.
Try it
Think of a time when you (or someone you watched) tackled a problem under pressure. Write a short principle audit:
- Describe the problem and what was done, in order, in five to eight lines.
- Beside each action, write the number of any principle it followed or broke.
- Identify the single principle whose absence cost the most time, and explain why in two sentences.
- Rewrite the first three actions so that they follow principles 1, 3 and 5.
You have finished when every action is annotated, you have named and justified the most costly missing principle, and your rewritten opening follows principles 1, 3 and 5 explicitly.
Knowledge check
According to the book, what does panic do to troubleshooting?
Before updating a driver, you note the current version and back up the user's files. Which principle are you applying?
A laptop shows the message Not enough disk space when saving. Which principle tells you to treat this message as evidence before changing anything?
Why should simple causes be checked first, even when a problem seems complex?
Answers explained
- a — The book says panic narrows thinking and encourages shortcuts. Urgency does not improve diagnosis (B), experience does not make anyone immune (C), and panic affects every kind of problem (D).
- d — Backing up data and recording original settings is protecting what matters. Writing it down is about notes of what you did; start simple and observe are about where and how you look.
- b — Reading the error message is the core of observing before acting; the system is reporting the cause. The other principles matter, but they are not what tells you to read the message.
- c — Simple causes are the most common, and checking them takes minutes. Complex causes do occur (A); user expectations (B) and avoiding notes (D) are not reasons.
Key takeaways
- The right attitude solves half the problem before anything is touched; panic and assumptions are the enemies of diagnosis.
- Effective troubleshooters are calm, curious and methodical.
- The seven principles, in order: stay calm, be curious not certain, start simple, change one thing at a time, observe before acting, protect what matters, write it down.
- "Protect what matters" is the principle that safeguards the user's data: back up and record settings before any change.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §2.1–2.2; failing-storage guidance from §8.5
