Read a sample: 1. A Technician's Approach to Laptop Symptoms
A user sets a laptop on your desk and says, “The screen is broken.” The laptop may have a cracked panel, but that is only one possibility. The screen might be dim, the image might be directed to an external monitor, or the computer might not have started as expected. At this point, “broken” describes the user’s experience, not a confirmed cause.
A good technician does not need an immediate answer. A good technician needs a reliable way to move from a report to useful evidence.
This chapter introduces a workflow you can use throughout the book: listen, observe, test, document, decide, and verify. The steps are simple enough for a beginner, but they help prevent a common mistake at every experience level—changing several things at once and then guessing which change mattered.
The user is often your best source of information about when a problem began and how it affects daily work. Start with open questions, and let the person describe the issue in ordinary language.
For a display complaint, you might ask:
- What do you see when the problem occurs?
- Does it happen as soon as the laptop starts, or later?
- Is the screen completely dark, dim, flickering, or showing an unusual image?
- Does it happen on the laptop screen, an external monitor, or both?
- Was anything changed or connected shortly before you noticed it?
For a keyboard or touchpad complaint, ask which actions fail and whether the problem appears in every application. A user who says “the keyboard types the wrong things” may mean that particular keys produce unexpected characters, shortcuts activate instead of letters appearing, or typed text repeats.
Ask about relevant events without assigning blame. A recent move, a connected dock, a software change, or contact with liquid may be important. The purpose is to understand the situation, not to make the user defend it.
Also ask what the user has already tried. If they restarted the laptop, disconnected a monitor, or changed a setting, record the result. You may still need to repeat a check, but knowing the history helps you choose the next step.
Finally, clarify the impact. A touchpad gesture that stopped working is inconvenient; a keyboard that cannot enter a password may prevent the user from working at all. Impact helps determine priority, even before the cause is known.
A symptom is something you can observe or have reliably reported: the pointer does not move, the screen flickers, or pressing a key produces an unexpected character. A cause is the reason the symptom occurs. Until the evidence supports it, keep those ideas separate.
Compare these notes:
> The display cable is bad.
> The laptop screen flickers intermittently. The user reports that it began after the laptop was moved between desks. An external monitor has not yet been tested.
The second note is more useful because it preserves what is known and identifies a useful gap. A display cable may eventually be worth investigating, but the first note treats a possibility as a conclusion.
When practical, observe the problem with the user. Ask them to demonstrate the normal steps that lead to it. Watch what happens, including what happens immediately before the symptom. If the issue occurs only in a particular application, note that detail. If it appears before the user opens any application, note that too.
Do not force a symptom to appear. For example, if a screen flickers when the lid moves during normal use, record that observation rather than repeatedly bending or twisting the lid. If you notice a raised touchpad, a distorted case, liquid, smoke, an unusual odor, or excessive heat, stop normal troubleshooting and follow the appropriate safety and escalation procedure.
Before changing anything, learn what the laptop is doing now. This starting point is your baseline. It gives you something to compare with later results.
The baseline depends on the complaint. For a screen problem, you might note whether:
- The laptop appears to start and show an image.
- The image is present but too dim, distorted, or intermittent.
- An external display is connected.
- The symptom is visible before and after signing in, if you can safely and normally reach both states.
For an input problem, you might note whether the issue affects one key, several keys, the entire keyboard, the touchpad, or more than one input device. Record whether the problem occurs in one application or in a simple text field as well.
You do not need to perform every possible check at the beginning. The baseline should be focused enough to guide your next decision. If a laptop screen is visibly cracked, detailed display-setting experiments are unlikely to explain the physical damage. If the user reports that a keyboard problem appears only in one program, application behavior deserves attention before you assume the keyboard needs replacement.
Work within the access you have been given. Do not browse personal files or enter credentials on a user’s behalf without appropriate authorization. If a test requires an account, ask the user to sign in or follow your organization’s approved process.
A controlled test asks a specific question. You make one relevant change, observe the result, and compare it with the baseline.
Suppose a user says the laptop screen is too dark. After confirming that an image is present, you can ask: “Does increasing the display brightness make the…