I'm no expert on presenting. (Far far far far.... from it.) I also can't view your slides without downloading Open Office (which I'm too lazy to do). So... take this with a huge grain of salt. :)
My first thought is that, you're right, these techniques are most obviously applicable when selling something. But even in the case of training, I think it might be possible to "sell" what you are trying to train if you focus on the "what I'm doing" aspect.
What I mean is that I've sat through a few lame corporate training presentations in my time and they always consist of loads of processes. Things like, "do this, then this, then this, and poof - you're done!" But what they utterly fail to actually tell you is WHAT you are doing and WHAT was accomplished! Perhaps a lame example might help...
Imagine being taught how to cook a burger like this: First you are told how and where to find the meat (perhaps in the freezer in the kitchen on the 3rd shelf). Then you are told or shown that you must place the meat into a special tray. Then this tray is inserted into the microwave oven and a very specific numerical sequence is entered. Wait for exactly 3 minutes. Now you remove the container from the microwave.... etc..
What's lost here is the end goal and the WHY. What are you really trying to make and why do these steps even exist in this order? Is there really only one single right sequence of steps?
So.. how does this help? Well, I imagine Steve would first give you the motivation for wanted to make your burger. Perhaps he lets you taste one. Touch it. Smell it. Study it. Compare with the "the competition." Now you know what your goal is. Then the process is to not follow steps, but to understand what needs to be done. You must understand that the meat must be thawed and why you can't just cook it first, then form it into a burger shape. This kind of thing.
So in your case, I imagine the presentation would first include real examples and problems that need to be solved and that you will learn how to solve with the program. Maybe work through one of them. Or study it so that it becomes clear as to what variables are involved and why. The second act, then, is where you connect the dots of the first part with the software. X is represented in the software here... (do a demo) Etc. The 3rd act is to tie ti all together. A complete example of a single event or something that you'd use the software for and how to get the results and what they mean and how to translate those results into real world meaning. (If it just spits out some pretty graphs - why do I even care? What does it MEAN?)
My first thought is that, you're right, these techniques are most obviously applicable when selling something. But even in the case of training, I think it might be possible to "sell" what you are trying to train if you focus on the "what I'm doing" aspect.
What I mean is that I've sat through a few lame corporate training presentations in my time and they always consist of loads of processes. Things like, "do this, then this, then this, and poof - you're done!" But what they utterly fail to actually tell you is WHAT you are doing and WHAT was accomplished! Perhaps a lame example might help...
Imagine being taught how to cook a burger like this: First you are told how and where to find the meat (perhaps in the freezer in the kitchen on the 3rd shelf). Then you are told or shown that you must place the meat into a special tray. Then this tray is inserted into the microwave oven and a very specific numerical sequence is entered. Wait for exactly 3 minutes. Now you remove the container from the microwave.... etc..
What's lost here is the end goal and the WHY. What are you really trying to make and why do these steps even exist in this order? Is there really only one single right sequence of steps?
So.. how does this help? Well, I imagine Steve would first give you the motivation for wanted to make your burger. Perhaps he lets you taste one. Touch it. Smell it. Study it. Compare with the "the competition." Now you know what your goal is. Then the process is to not follow steps, but to understand what needs to be done. You must understand that the meat must be thawed and why you can't just cook it first, then form it into a burger shape. This kind of thing.
So in your case, I imagine the presentation would first include real examples and problems that need to be solved and that you will learn how to solve with the program. Maybe work through one of them. Or study it so that it becomes clear as to what variables are involved and why. The second act, then, is where you connect the dots of the first part with the software. X is represented in the software here... (do a demo) Etc. The 3rd act is to tie ti all together. A complete example of a single event or something that you'd use the software for and how to get the results and what they mean and how to translate those results into real world meaning. (If it just spits out some pretty graphs - why do I even care? What does it MEAN?)
That sort of thing.
Maybe. :P
Now I'm hungry.