You may always make that recommendation; I don't.
What's your reasoning?
Narrowing the scope of the problem of course
After trying "quick fixes", generally the second step is to gather information about a problem. One good thing to know is the general scope of the problem. Knowing if a problem affects just a single user or affects all users generally divides the root of the problem down to user account files (cache etc) or system problems. In most cases, a fix for one does not work for the other, so you can cut your problem solving roughly in half without any additional information.
And it's
always a good idea to have a second "emergency" admin account available in case your main account develops a problem that prevents you from logging in.
Of course there is a third group of problem space, hardware vs software, but that is most easily tested by booting the suspect machine's hard drive off another mac, but not everyone has another mac they can use for this. "Hardware, System, User" make up the three primary problem spaces.
And for the record of course, that fourth problem space lovingly referred to as "pebkac". Failing to consider that one can waste a lot of your time.
