Why a method

Guessing is expensive. A method finds the cause first.

"My PC is slow."GUESSINGReinstall Windowsa day goneBuy more memorymoney spentReplace the PCmore money spent✗still slow, and nobody knows whyWORKING TO A METHODAsk: what is slow, and since when?Look: which part is at its limit?Test one cause at a time✓the cause found, and the cheapest fix that removes itA guess can cost a day or a new machine and still miss. A method finds the cause before anything is spent.The complaints never change: it is slow, it will not print, it will not start. The method does not change either.The next page gives its six steps, and the pages after it take them one at a time.

Faced with "it is slow", guessing spends time and money. A method finds the cause before the fix.

The method

Six steps, always in the same order

1Identifythe problem2Theoryof probable cause3Testthe theorytheory wrong: think again, or escalate4Planand fix5Verifyand prevent6Documentwhat happenedSix steps, always in this order. Skipping one is how a ten-minute fault takes a day.Identify the problem; establish a theory of probable cause; test the theory; plan and implement the fix;verify full function and prevent a repeat; document it. Before changing anything, check the organisation'srules and back up what could be lost. Escalate when the fault is beyond your rights, skills or time.

Identify, theorise, test, fix, verify, document.

Identify the problem

Who is affected tells you where to look

One program failsEverything failsOne personMany peopleThat program, or their settings in itThat computer, or its connectionThe server or service behind itThe network or system they shareWho is affected, and by how much, tells you where to look.Then ask the three questions that solve most faults: what exactly happens, when did it start, and whatchanged just before? Try to make the fault happen in front of you. A fault you can reproduce is a faultyou can test.

One person or many? One program or everything? The answer points at the fault.

Form a theory

Halve the problem with every test

A website will not load. 8 things lie between the PC and it.PCCableWall portSwitchRouterFirewallInternet linkWebsiteTest 1: the switch answers.4 suspects leftTest 2: nothing answers past the firewall.2 suspects leftTest 3: the router answers.It is the firewall.Halve the problem with every test: 8 suspects need 3 tests, not 7.Start in the middle, not at one end. Each answer clears half of what is left. The same idea finds one badmemory module among four, or the one start-up program that breaks a machine: disable half, and test.Question the obvious first, though: is it plugged in, and is it switched on?

Test in the middle. Each answer clears half of what is left.

Test the theory

One change at a time, cheapest test first

A PC will not turn onAny lights or fan noise?noDoes a lamp work in that outlet?nothe outlet or the breakeryespower cable, then the supplyyesAnything on the screen?nocable, memory or graphicsyespower is fine: see how it startsEach question splits the causes in two, and the cheapest test comes first.Change one thing at a time, and put it back if it made no difference. Make two changes at once and youwill not know which one worked, or which one made things worse.

Each question splits the causes. Change one thing at a time.

Evidence

The log has usually recorded the cause

TimeLevelSourceMessage09:12:01InformationService ControlThe Print Spooler service started09:14:40WarningdiskAn error was detected on Harddisk1 during paging09:14:55ErrordiskThe device Harddisk1 has a bad block09:15:02CriticalKernel-PowerThe system rebooted without shutting down cleanly09:16:30InformationEventLogThe Event Log service startedreadupwardsThe log has usually recorded the cause. Find the failure, then read upwards.Windows keeps its logs in Event Viewer, graded Information, Warning, Error and Critical. Linux keeps themin the journal (journalctl) and in /var/log; macOS in Console. Copy the exact wording of any error: it isthe best search term you will get.

Find the failure in the log, then read upwards to what came before it.

Evidence · Going deeper

Symptoms and first checks

What you seeCheck firstSlow at everythingTask Manager: is the processor, memory or drive at 100%?A blue screennote the stop code; which driver or update came just before?One program keeps crashingupdate it, repair it, then reinstall itShuts down under loadheat: clear the dust, check the fans and ventsClicking or grinding from a driveit is failing: back up now, then replace itThe clock is wrong at every startthe motherboard's coin cell is flatWorks only in Safe Modea third-party driver or start-up program is the causeA burning smell, or smokepower off at once and unplugMost symptoms have a usual suspect. Check it first, then follow the method.Safe Mode starts Windows with only its own essential drivers and services. If the fault disappears there,Windows itself and the hardware are sound, and something added later is to blame.

Slow: Task Manager. Blue screen: the stop code. Clicking drive: back up now.

Finish the job

Verify it, prevent it, write it down

Ticket 4821closedSymptomNobody on floor 2 can printCauseA failed job at the front of the print queueFixCancelled the job; restarted the Print SpoolerVerifiedThree users printed a test pagePreventionPrinter driver updated on the print serverVerifythe user confirms that everything worksPreventremove the cause, not only the symptomDocumentso the next person takes minutesA fix is finished when the user confirms it and the ticket says what was done.Verifying catches the fix that cured one fault and caused another. Documenting turns one technician's hourinto everyone's five minutes the next time the fault appears.

The user confirms the fix. The ticket records symptom, cause and cure.

Professional practice

The fix is half the job

THIS LESSON✓Identify the problem✓Form a theory✓Test it✓Plan and fix✓Verify, prevent, documentNEXTThe other half: people and recordsTickets, change management, plain speech,safety, privacy and licences.These are what make a fix count.Finding the fault is half the job. The other half is how you work with people, records and risk.A fix nobody recorded will be found again from nothing, and a careless one can cost more than the fault did.

After the fault come records, people, safety and privacy: the other half of the work.

Tickets

Every request becomes a ticket

Newthe user reports itTriagedcategory, priorityAssignedone named ownerIn progressnotes as you goEscalatedwith every noteResolvedfix appliedClosedthe user confirmsA good ticket holds:who, and how to reach them · the device · the exact symptomwhat was tried · what fixed itEvery request becomes a ticket, and the ticket is the memory of the whole team.A ticket has one owner at a time, a priority that sets how fast it must be answered, and notes clear enoughfor a colleague to take it over without asking a question. Escalate with everything you have learned, sothat nobody starts again from the beginning.

A ticket has one owner, a priority and notes anyone could pick up.

Tickets · Going deeper

Setting the priority

Impact: how many are affectedOne personA teamEveryoneUrgencyWork has stoppedP3P2P1Work is slowedP4P3P2It can waitP4P4P3Priority is impact and urgency together, not who shouts loudest.A service level agreement (SLA) turns each priority into a promise: for example, a first response within15 minutes for P1 and within one working day for P4. The numbers differ in every organisation; the griddoes not.

Impact: how many people. Urgency: how much work has stopped.

Change management

A change needs a plan, an approval and a way back

Requestwhat, and whyAssessrisk and reachApprovethe change boardSchedulea quiet windowImplementtested beforehandVerifythen document✗Roll backplanned in advanceA change needs a plan, an approval and a way back before anyone touches anything.Most outages are caused by changes, not by failures. The request states the purpose, the scope, the riskand the rollback plan. The change is tried in a sandbox first, the people affected are told when it willhappen, and afterwards those who use the system confirm that it still does its job.

Request, assess, approve, schedule, implement, verify, with a rollback plan.

Communication

Say what happened, what you did and what comes next

In jargon"Your DHCP lease expired and the NICfell back to an APIPA address."true, and no use to the listenerIn plain wordsWhat happenedYour computer lost its network address.What I didI have renewed it and checked that it holds.What comes nextI will look in tomorrow to make sure it stays.Say what happened, what you did and what comes next, in the user's words.Listen without interrupting, then repeat the problem back to be sure of it. Be on time, or say that youwill be late. Do not blame the user, argue, or take calls while helping. Set an honest expectation, andfollow up afterwards.

Plain words: what happened, what I did, what comes next.

Safety

A spark too small to feel can destroy a chip

Static electricity in volts, to scaleCan damage a sensitive chip100 VYou can feel the spark3,000 VWalking on carpet in dry air35,000 V✓power off and unplug before opening✓wear a wrist strap clipped to the bare metal of the case✓hold boards by their edges✓keep spare parts in antistatic bags✗never open a power supply or wear a strap inside one: it holds a dangerous chargeYou can destroy a chip with a spark 30 times too small to feel.Static damage is invisible and often delayed: the part works today and fails next month. So theprecautions are habits, used every time, not judgments made case by case.

A chip can be damaged by 100 volts. You feel nothing below 3,000.

Safety · Going deeper

Safety and disposal

Liftingbend the knees, keep the load close; two people for a server or a large printerElectrical firecut the power; use a carbon dioxide or dry powder extinguisher, never waterBatteriesrecycle them; a swollen one goes in a fire-safe container, not a binTonerrecycle cartridges; clean spills with a toner vacuum, not a household oneOld driveswipe or physically destroy them before the machine leaves the buildingOld equipmentsend it to a certified electronics recycler and keep the certificateChemicalsread the safety data sheet (SDS) for handling and disposalCablesroute and tie them: a trailing cable is a fall waiting to happenThe equipment can hurt you. Thrown away carelessly, it can hurt others.Local law decides how batteries, toner and electronics are disposed of. Find the rule before the skip.

Lift with the knees. Never put water on an electrical fire. Wipe drives before disposal.

Privacy

You will see private data. The job is to not use it.

Kind of dataExamplesThe rules that cover itPersonal data (PII)names with ID numbers, addresses, dates of birthGDPR and national privacy lawHealth data (PHI)medical records, test results, prescriptionsHIPAA in the United StatesPayment card datacard numbers, expiry dates, security codesPCI DSS, set by the card industryCredentialspasswords, keys, recovery codespolicy: never ask for one, never write one down✓open only what the job needs✓lock the screen when you step away✗copy, photograph or discuss what you see✗take data away to work on it elsewhereYou will see private data. The job is to not use it.A technician has more access than almost anyone in the company. That access exists to do the work, andfor nothing else. What you see on a user's screen stays there.

Personal, health and payment data are protected by law. See only what the job needs.

Privacy · Going deeper · 1 of 2

If you find something you should not

1Stopdo not open, copy, delete or look further2Reportto the person your policy names, and to nobody else3Preserveleave the device as it is; do not switch it off unless told to4Record custodywho held the device, from when until when, with signatures5Write down factswhat you saw and when: no guesses and no opinionsThe first person on the scene preserves evidence. They do not investigate.This covers prohibited content, signs of a break-in, and data found where it should not be. The chain ofcustody, an unbroken record of who held the evidence, is what allows it to be used later.

Stop, report, preserve. Do not investigate.

Privacy · Going deeper · 2 of 2

Licensing: software is licensed, not owned

Copies installed50Licences owned40: 10 copies unlicensedLicence typeWho may use itExamplePersonal or OEMone person, or one machinethe Windows that came with a laptopVolume or sitean agreed number across a companyone agreement covering 500 seatsSubscriptioneach named user, while it is paid forMicrosoft 365, Adobe Creative CloudOpen sourceanyone, under the licence's termsLinux, Firefox, LibreOfficeSoftware is licensed, not owned. The installs must match the licences.The end-user licence agreement (EULA) says who may use a copy, and where. An audit that finds moreinstalls than licences ends in a bill and a penalty. Open source is free to use, but its licence canplace conditions on passing it on.

Every install needs a licence. The EULA says who may use it and where.

Lesson complete

You finished “Troubleshooting and professional practice”

Nicely done.

Open in a new tab