I haven’t posted much lately, mostly because I’m starting to write a book on instructional design. I have developed my own theory over the past decade of as a technical writer, curriculum developer, and janitorial specialist.
My ideas have really come together over the past two years working at my current position creating training for overly complex software… particularly now that I’ve been working with students in the second half of our Technical Boot Camp, the flagship of our training offerings.
Week one is instructor led with some hands on activities leading them through an implementation of our software. It takes about five days to cover theory, practice, and troubleshoot errors in the practicals along the way. Week two we give the students the materials they need to implement a sample project on their own. This takes from three days up to five days for them to complete while I try to reinforce the concepts from week one and troubleshoot problems that arise.
Most problems are results of students not following the step by step instructions in the training manual. I painstakingly go through the manual after each release and patch to ensure that my procedures are correct. If they follow the book, they should have no problems. But they don’t. Even when the instructor AND the book are telling them exactly what steps to take.
Now I will admit that the sample implementation week is a bit harder, but I try to analogize it to an algorithmic expression. I tell them to treat each project specific item of information as a variable. If X = Y in week one, what does X = ? in week two. That’s the most challenging part, but I tell them exactly how to change the variables. Some get it, some don’t…
Inevitably mistakes are made, and that’s fine… but then there are those who don’t even crack the book open the second week and by day two are lost and their configuration is so fucked up they don’t know what’s going on. They come to me for help, and I ask them what they did and try to help them back track to find the mistake.
“What are you trying to do?”
“Run MPXDATA.”
“What’s going wrong?”
“I dunno.”
“Check the log file and let me know if you’re still stuck.”
Twenty minutes pass and the book remains untouched…
“I’m still stuck.”
“Ok, let’s track backwards. Did you set up your configuration file?”
Quizzical look.
“You need to do that before you can run MPXDATA.”
Quizzical look.
“It’s on page 120.”
I walk away wanting to scream “RTFM!” but I resist. (RTFM = Read The Fucking Manual) I don’t know how many times I tell them to make sure they follow the book… but as I heard once, you can’t fix stupid. So with these students I just make sure they come out of it with the basic concepts despite the fact that they’ve completely fucked things up.
These experiences are what lead me to know new theory of instructional design. I call it the Functional Understanding of Critical Knowledge method. The main goal of a course is to give people enough knowledge of the concepts and practical experience to give them start when they’re faced with implementing their own project.
The FUCK method concedes that we can’t teach everyone everything everytime. The learning curve on our product is extremely steep. Two years in and I’m just starting to feel comfortable with it. Add onto the complexity of the software the configurability of it and you have a big mess. There’s no way we could teach every scenario they might face, all we can do is teach them enough to be dangerous.
The goal of the FUCK method is to teach the student enough to know the high level Hows since we can’t teach the Whats. If they know how to configure the product, then they only have to figure out the details to make it all work. – As an analogy… We can teach them how to use the oven and stove top, but we can’t teach them how to cook everything that they can possibly make on a range.
Anyway, that’s why I have been posting much the past week or so. If you want to read more about the FUCK method you’ll have to wait for the book.