Rules for Troubleshooting

11-06-2021 11:10 AM
Regular Contributor III

A mechanic colleague mentioned his "3 rules for troubleshooting" the other day. I've found those rules useful for troubleshooting technical issues in general (including GIS issues).

I thought I'd share:

  1. Try the easiest thing first.
    1. Is it plugged in? (and connected to the network)
    2. Turn it off and on again.
    3. Clear the data/cache.
    4. Check privileges.
  2. "Tested" is a lie.
    1. If someone says they tested something, assume they're wrong or lying.
    2. "It should work now" often means one bug might have been fixed, but two more were created. And no, it wasn't tested properly.
  3. 90% of issues are caused by operator error.


What simple rules for troubleshooting do you use?

Tags (1)
1 Reply
Regular Contributor III


Musky's 5-Step Engineering Protocol:

1. Make The Requirements Less Dumb
“Step one: Make the requirements less dumb. The requirements are definitely dumb; it does not matter who gave them to you. It’s particularly dangerous when they come from an intelligent person, as you may not question them enough. Everyone’s wrong. No matter who you are, everyone is wrong some of the time. All designs are wrong, it’s just a matter of how wrong,” explains Musk.

2. Try And Delete Part Of The Process
“Step two: try very hard to delete the part or process. If parts are not being added back into the design at least 10% of the time, [it means that] not enough parts are being deleted. The bias tends to be very strongly toward ‘let’s add this part or process step in case we need it’. Additionally, each required part and process must come from a name, not a department, as a department cannot be asked why a requirement exists, but a person can,” says Musk.

3. Simplify Or Optimize
“Step three: simplify and optimize the design. This is the most common error of a smart engineer — to optimize something that should simply not exist,” according to Musk. He, himself, has been a victim of implementing these steps out of order. He refers to a “mental straightjacket” that happens in traditional schools where you always have to answer the question regardless of whether the premise makes any sense at all.

4. Optimize / Accelerate Cycle Time
“Step four: accelerate cycle time. You’re moving too slowly, go faster! But don’t go faster until you’ve worked on the other three things first,” explains Musk. Here he uses another example of how these steps should occur in order. During a wrongheaded process you should simply stop, not accelerate. He says, “If you’re digging your grave, don’t dig it faster.”

5. Automate
“The final step is: automate. An important part of this is to remove in-process testing after the problems have been diagnosed; if a product is reaching the end of a production line with a high acceptance rate, there is no need for in-process testing. I have personally made the mistake of going backwards on all five steps multiple times. In making Tesla’s Model 3, I literally automated, accelerated, simplified and then deleted,” says Musk.


"Elon reveals the five steps he believes are essential to engineering something wholly new. What’s important, however, is that these five steps occur in precisely the order he lays out."




0 Kudos