How to Use Conditioning to Your Advantage
Grab a bag of candy. It should be your favorite candy (might as well be something in this for you too). It should be one type of candy, maybe even one brand. A grab bag of miscellaneous Halloween candy may work, but not as quickly nor as well. Your candy can be Smarties, Snickers, Skittles, pretzels, whatever. But pick one. We want our people to associate a behavior with this candy. I used Snickers bite-sized candies (my favorite).
When I most recently presented PostRestore (a number of years ago actually) I wanted to use Pavlovian and operant conditioning to get the DBAs to use this immediately. There were too many non-prod envs that weren't properly setup, causing delays and hard-to-dissect bugs. I passed around a Snickers to every participant every time I executed the proc during my demo. Now, really, how hard is it to execute a stored proc after you restore a database? It didn't take long before the subjects, er DBAs, were getting antsy. They clearly felt I was wasting their time. No matter, the goal is not training, rather behavior modification. I then had a handful of the DBAs each try executing the proc for the group by coming up to my laptop and pressing F5 while I projected the image to the group and providing positive reinforcement...and I gave each subject a Snickers for being a good assistant. As people were leaving I gave them another Snickers as I reminded them to, "remember to always run PostRestore." By now I was getting strange looks from the DBAs...why so much candy?
This is a bit Pavlovian and a bit operant. But I was just getting started. I knew that invariably I would still have to deal with support issues for a few weeks because Service Broker was disabled (which was the hardest to diagnose due to its asynchronous, non-GUI nature). The cause was always, of course, PostRestore not being run. This meant I still had some behavior to modify. I would then walk over to the DBA and tell him he didn't earn his Snickers today. The first few times I did this I got a blank stare, followed quickly by that unmistakable lightbulb going off over his head...indicating he just remembered he forgot to run PostRestore. This was followed by perfuse apologies and guarantees that this would never happen again. As I would leave I would toss a piece of candy at him. This is obviously operant conditioning.
So I had operant conditioning covered, but why not got a little Pavlovian too? Right after my first training session I arrived at the office a bit early and place a bowl of Snickers right in the middle of the DBA bullpen. No note attached. My hope was the visual image of Snickers sitting in the middle of the room would subconsciously help at least one DBA to run PostRestore. I would pop over every morning for a few weeks and top off the bowl.
Within a month, using the Pavlovian and operant conditioning steps I mentioned above, I never had to troubleshoot a problem due to a disabled broker on a restored db. NEVER.
That's behavior modification. It didn't require and hootin' and hollerin'. It didn't require a line item on an annual review. It didn't require nasty emails. It only required a little effort on my part and a sawbuck's-worth of Snickers.
You may find this story funny, you may find it degrading...but you will find that a little conditioning will affect behavior modification.
Here's a few reasons I know conditioning works.
Dave Wentzel CONTENT