Troubleshooting Rule #2: Is it turned on?
While troubleshooting, another embarrassing discovery is that the thing in question isn’t working because you didn’t turn it on. This rule could come first, as in some sense it’s more basic than Rule #1, but for the simple AC-powered appliance, you have to plug it in before you can turn it on, so I list it second.
Again, there are lots more useful ways to think about whether you’ve turned something on. For instance:
Electronics: You might have checked one power switch. Are there more or different parts that also need to be turned on? The monitor, the printer, the router, the speakers, the amplifier, the power strip, the ground fault interrupt, the circuit breaker? Are the batteries still good?
Software: Was the program told to go, execute, connect, activate, initiate? Did you single-click something that wanted to be double-clicked? Did you actually press Send on the e-mail? Did you post the crontab and start the cron daemon? Is the server running? Did you set the right bit - and was it normal or inverted logic? Did you write a comprehensive setup function but forget to call it? Were error codes checked, so you’d be notified if something wasn’t on?
People: Did everybody know that today was the day? Was it part of the job ticket? Did anybody call to place the order? Did you assume someone was on track, available, interested, or in the schedule without checking? Do they know you care about the results?
You want it, but did you say so?
Next rule: Is it working as designed?