Your problem (other than unreasonably dumb users) is step 5, where your other staff restarts the computer without doing even the most basic troubleshooting.

I assume you're referring to IT staff, who should damn well know better, and not make the problem worse, which is what they do when they just reboot the computer without doing even basic troubleshooting. Rectify this problem first (whipping them with old CAT5 cables or flogging them with old keyboards or laptops is very motivating, in my experience), and the user problem will get better. Your staff needs to show the users why this is happening, while this is happening if there's any hope of having it stick. Not unlike housebreaking a puppy. If you smack it on the nose when it urinates on your carpet, it will learn not to urinate on your carpet. If you wait until 10 minutes after the fact, it won't know why it's being punished, and will never learn. Users, much like puppies, need this immediacy if there's any hope of having them learn anything, and that's why telling them what the problem was after the computer's been bounced isn't working.

Of course, you'll still have infuriatingly dense users who just don't (or won't) get it, but that's out of your control, and frankly a management problem. My advice on that situation is (assuming you are a manager) to talk the managers of your worst offending users, and point out how much productivity (in their department, as well as yours) is being wasted because their users are too #$&^ing stupid to check for a save dialogue. By pointing out how their employees refusal or inability to learn simple tasks is hurting them and their departments, those managers will be much more open to solving the problem with the tools at their disposal. When presented with the problem this way, I've seen managers in other departments take it on themselves to "train"/"educate" their users on this type of simple thing, and even discipline or terminate employees who just wouldn't or couldn't get it. (As in: "Sorry that you forget your password every 3 hours and can't log in, but it means you're not a productive employee, and we can't afford to employ you anymore. Get out.")

And let me tell you, it's hella satisfying to hear a sales manager scream "It's not IT's fault you're too @$*^ing stupid to click a a button!!!"

Your problem is step 5, where your other staff restarts the computer without doing even the most basic troubleshooting.

I assume you're referring to IT staff, who should frankly know better, and not make the problem worse, which is what they do when they just reboot the computer without doing even basic troubleshooting. Rectify this problem first, and the user problem will get better.

Your staff needs to show the users why this is happening, while this is happening if there's any hope of having it stick. Not unlike housebreaking a puppy: If you smack it on the nose when it urinates on your carpet, it will learn not to urinate on your carpet. If you wait until 10 minutes after the fact, it won't know why it's being punished, and will never learn. Users, much like puppies, need this immediacy if there's any hope of having them learn anything, and that's why telling them what the problem was after the computer's been bounced isn't working.

Of course, you'll still have infuriatingly dense users who just don't (or won't) get it, but that's out of your control, and frankly a management problem. My advice on that situation is (assuming you are a manager) to talk the managers of your worst offending users, and point out how much productivity (in their department, as well as yours) is being wasted because their users not checking for a simple save dialogue.
By pointing out how their employees refusal or inability to learn simple tasks is hurting them and their departments, those managers will be much more open to solving the problem with the tools at their disposal. When presented with the problem this way I've seen managers in other departments take it on themselves to "train"/"educate" their users on this type of simple thing, and even discipline or terminate employees who just wouldn't or couldn't get it. (As in: "Sorry that you forget your password every 3 hours and can't log in, but it means you're not a productive employee, and we can't afford to employ you anymore. Get out.")

And on a personal note let me tell you: it's quite satisfying to hear a sales manager scream "It's not IT's fault you're too stupid to click a a button!!!"

Your problem (other than unreasonably dumb users) is step 5, where your other staff restarts the computer without doing even the most basic troubleshooting.

I assume you're referring to IT staff, who should damn well know better, and not make the problem worse, which is what they do when they just reboot the computer without doing even basic troubleshooting. Rectify this problem first (whipping them with old CAT5 cables or flogging them with old keyboards or laptops is very motivating, in my experience), and the user problem will get better. Your staff needs to show the users why this is happening, while this is happening if there's any hope of having it stick. Not unlike housebreaking a puppy. If you smack it on the nose when it urinates on your carpet, it will learn not to urinate on your carpet. If you wait until 10 minutes after the fact, it won't know why it's being punished, and will never learn. Users, much like puppies, need this immediacy if there's any hope of having them learn anything, and that's why telling them what the problem was after the computer's been bounced isn't working.

Of course, you'll still have infuriatingly dense users who just don't (or won't) get it, but that's out of your control, and frankly a management problem. My advice on that situation is (assuming you are a manager) to talk the managers of your worst offending users, and point out how much productivity (in their department, as well as yours) is being wasted because their users are too ****ing stupid to check for a save dialogue. By pointing out how their employees refusal or inability to learn simple tasks is hurting them and their departments, those managers will be much more open to solving the problem with the tools at their disposal. When presented with the problem this way, I've seen managers in other departments take it on themselves to "train"/"educate" their users on this type of simple thing, and even discipline or terminate employees who just wouldn't or couldn't get it. (As in: "Sorry that you forget your password every 3 hours and can't log in, but it means you're not a productive employee, and we can't afford to employ you anymore. Get out.")

And let me tell you, it's hella satisfying to hear a sales manager scream "It's not IT's fault you're too ****ing stupid to click a a button!!!"

Your problem (other than unreasonably dumb users) is step 5, where your other staff restarts the computer without doing even the most basic troubleshooting.

I assume you're referring to IT staff, who should damn well know better, and not make the problem worse, which is what they do when they just reboot the computer without doing even basic troubleshooting. Rectify this problem first (whipping them with old CAT5 cables or flogging them with old keyboards or laptops is very motivating, in my experience), and the user problem will get better. Your staff needs to show the users why this is happening, while this is happening if there's any hope of having it stick. Not unlike housebreaking a puppy. If you smack it on the nose when it urinates on your carpet, it will learn not to urinate on your carpet. If you wait until 10 minutes after the fact, it won't know why it's being punished, and will never learn. Users, much like puppies, need this immediacy if there's any hope of having them learn anything, and that's why telling them what the problem was after the computer's been bounced isn't working.

Of course, you'll still have infuriatingly dense users who just don't (or won't) get it, but that's out of your control, and frankly a management problem. My advice on that situation is (assuming you are a manager) to talk the managers of your worst offending users, and point out how much productivity (in their department, as well as yours) is being wasted because their users are too #$&^ing stupid to check for a save dialogue. By pointing out how their employees refusal or inability to learn simple tasks is hurting them and their departments, those managers will be much more open to solving the problem with the tools at their disposal. When presented with the problem this way, I've seen managers in other departments take it on themselves to "train"/"educate" their users on this type of simple thing, and even discipline or terminate employees who just wouldn't or couldn't get it. (As in: "Sorry that you forget your password every 3 hours and can't log in, but it means you're not a productive employee, and we can't afford to employ you anymore. Get out.")

And let me tell you, it's hella satisfying to hear a sales manager scream "It's not IT's fault you're too @$*^ing stupid to click a a button!!!"