Analysis

Frankly, Analysis has totally won me over. Who would have thought that just by writing down a problem or a goal and then writing down everything you can think about the goal, subtasks, and context would suddenly give you specific direction about fixing the problem. Take our fictional problem - getting employees to bake focaccia bread correctly. As I was think about the learner and their previous experience, I realized that I had no idea what the bread was supposed to look like at any step and it made my baking far less than perfect. Because of that discovery, I think that pictures need to be available throughout the training and afterwards. Also, because quality is of such importance, we need to either have a veteran employee inspect the bread, or find some way to check the quality, maybe every time. While these may seem like simple things, not putting them in place could eventually result in poorly-made bread, which could lead to a loss in customers, and eventual loss of profits. So the tiniest detail can't be missed.

All of this could be done with an interactive recipe program on a touchscreen in the bakery. It could have every step (or all simultaneous steps) on the screen at the same time along with pictures. While this may be the best way to ensure speed and quality, it isn't efficient in the least. We need to be able to find the most effective way to teach someone to make great focaccia bread, which is efficient in terms of teaching it quickly and it is cost effective, and it needs to be appealing in that the employee won't get bored and lose attention, and they will be able to walk away knowing that their new employer cares about their training.