What Changed? And One Change at a Time
Where you are: Module 2 — The Troubleshooting Mindset · Lesson 2.2 · Based on Chapter 2 (§2.2 principle 4, §2.3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.
What you'll be able to do
- Apply the question "What changed?" at the start of any new problem.
- Turn a user's "nothing changed" into at least five specific questions.
- Explain why only one variable should be changed at a time, and follow the one-change cycle.
Watch: What Changed? And One Change at a Time
The video follows a network printer that stopped working over a weekend when, according to its user, "nothing changed". One specific question solves it in twenty minutes. The second half compares two technicians who fix the same fault, one with three changes at once and one with a single change. Keep these questions in mind:
- Which specific question uncovered the change?
- What did the one-change technician learn that the other did not?
- Why should a change that did not help be undone?
The most powerful question
Before anything else, the book says, ask: "What changed?"
Systems that worked yesterday and fail today almost always fail because something changed in between. Identifying the change frequently identifies the cause. The book lists the kinds of change to think about:
| Change | How it causes faults (examples) |
|---|---|
| A software update | A new version behaves differently or conflicts with something else |
| A moved cable | Knocked loose, unplugged, or reconnected to a different socket |
| A new user | Different settings, habits or permissions |
| A power cut | Devices restart in the wrong order, or not at all |
| A new password | The old one is still saved on another device or app |
| A different location | A new desk, network or power socket |
Asking "What changed?" is also a direct defence against the mistake of not asking what changed, which you will meet in Lesson 2.3.
When users say "nothing changed"
Users are rarely being dishonest when they say nothing changed. More often they did not notice the change, or did not think it mattered: an update installed overnight, a cleaner who moved the printer, a colleague who borrowed the laptop. The book's practitioner tip is to ask specific questions instead of general ones:
- Was anything installed or updated?
- Was the device moved or cleaned?
- Did the power go off?
- Has anyone else used it?
You can add further specific questions drawn from the list of usual changes, for example: Has a password been changed recently? Have you been working somewhere different? Specific questions recover details that general ones miss.
Beyond the book (2026 note): On Windows 11, you can check the answer to "Was anything installed or updated?" yourself: Start > Settings > Windows Update > Update history lists which updates were installed and when. Microsoft advises against removing installed updates unless necessary and notes that not all updates can be removed. In an organisation, removing an update is a change that follows policy and, where it affects others, needs approval. Source: Microsoft Support — Windows Update FAQ.
Change one thing at a time
The question has a partner rule: principle 4, change one thing at a time. The book's reasoning is simple: if three things are changed and the problem disappears, it is impossible to know which one fixed it.
Consider the same printer fault handled two ways (fictional):
| Three changes at once | One change at a time | |
|---|---|---|
| Changes | New cable, restart, driver reinstall | New cable only, then test |
| Result | Printing works | Printing works |
| What you learn | Nothing: any of the three could be the cause | The cable was the cause |
| Side effects | The reinstall may have reset other settings | Nothing else was touched |
| What you record | A guess | A confirmed cause and fix |
Both technicians "fixed" the printer, but only one can document a real cause, prevent a repeat and explain the fix to a colleague. In scientific language, each thing you might change is a variable; changing one variable at a time is what lets you link cause and effect.
The one-change cycle
- Record the current state, so you can always return to it (this is principle 6, protect what matters).
- Change exactly one thing.
- Test by repeating the action that originally failed.
- If the problem is fixed, keep the change and write it down. If it is not, undo the change before trying the next one.
Undoing unhelpful changes matters. Otherwise changes pile up, the system drifts away from your notes, and a later change may only appear to work because of an earlier one you forgot.
Ask what changed, then change only one thing at a time. Finding the change often finds the cause; one change at a time proves it.
Worked example
(Fictional scenario.) On Monday at 09:10 the accounts team reports that their network printer will not print. It worked on Friday afternoon, everyone in the team is affected, and the person reporting it says, "Nothing changed. It just stopped."
| Time | Step | What happened |
|---|---|---|
| 09:15 | Identify | The user repeats that nothing changed. |
| 09:17 | Identify | Specific question: "Was the printer moved or cleaned?" Yes: the team moved desks on Saturday, and the printer moved with them. |
| 09:20 | Theory | The network socket at the new desk is not connected to the network. |
| 09:25 | Test | The link light on that wall port stays dark; plugged into a known-good port nearby, the printer's link light comes on. |
| 09:30 | Implement | The printer is cabled to the working port. |
| 09:35 | Verify | Test pages print from two different computers. |
| 09:40 | Document | The ticket records the cause, and the unpatched wall port is reported to the facilities team. |
One specific question found the change; one change confirmed the cause.
Try it
Run a "What changed?" interview with a friend, family member or classmate about a real problem they have had with any device or service.
- Ask the general question first: "Did anything change before it started?" Note their answer.
- Then ask at least five specific questions from this lesson (updates, moves or cleaning, power, other users, passwords, location).
- Record each answer, and mark any that revealed a change the general question missed.
- Write one sentence stating the most likely change and how you would test it with a single change.
Respect privacy and safety. Do not ask anyone to tell you a password, and do not change settings on someone else's device during this exercise. It is an interview, not a repair.
You have finished when you have recorded the general answer, at least five specific questions with answers, and a one-change test plan, and you can say whether the specific questions revealed anything the general one did not.
Knowledge check
A system worked yesterday and fails today. According to the book, what is the most productive first question?
A user insists that nothing changed. Which follow-up is the best example of the book's advice?
You replace a cable, restart the computer and reinstall a driver at the same time, and the fault disappears. What is the main problem?
In the one-change cycle, what should you do if a change does not fix the problem?
Answers explained
- b — The book calls "What changed?" the most powerful question because most faults follow a recent change. Blame, replacement and warranty do not gather evidence about the cause.
- c — It is a specific question from the book's practitioner tip. A just repeats the general question, B is an action rather than a question about change, and D does not gather evidence.
- a — With three simultaneous changes, cause and effect are lost. Restarting is a legitimate check (B), and cables are a very common cause (C).
- d — Undoing keeps the system matching your notes and stops changes piling up. Keeping it (A) or making several changes (C) breaks the one-variable rule; closing the ticket (B) abandons the problem.
Key takeaways
- Ask "What changed?" before anything else: updates, moved cables, new users, power cuts, new passwords and new locations are the usual suspects.
- When users say "nothing changed", ask specific questions: installed or updated? moved or cleaned? power off? anyone else used it?
- Change one thing at a time; otherwise you cannot know which change fixed the problem.
- Record the state first, test after every change, and undo changes that did not help.
Sources
- Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §2.2 (principle 4), §2.3 and practitioner tip
- Microsoft Support — Windows Update FAQ
