I’ve been thinking a lot lately about thinking.
More specifically, I’ve been thinking about how to think backward from a goal.
For the last three months, I’ve been working at building a new website with content from my old “You Can Teach Writing” site.
That has necessitated learning a new software program to replace my antique Dreamweaver (purchased in 2000!), learning how to create responsive sites that will display properly on mobile devices, and figuring out how to organize all the website elements—photographs, illustrations, icons, call-out boxes, text, headlines—so I can find information when I need it and format it consistently across the site.
Finding all the information I need to learn requires a lot of research. All too often something I’m sure I will need to have later is discussed at the point where it is deployed, rather than at the point at which I ought to start collecting it.
I’ve not reached any earth-shaking conclusions from these three projects, but I’ve made a few observations that I want to remember when I teach.
Goals hold emotions
Goals always have an emotional component, either actual or potential.
I’ve seen that emotional component several times in software user forums where company employees were annoyed by users’ desire for step-by-step directions.
Users felt successful when they could complete a simple task quickly with the software, while the employees felt unsuccessful if users only wanted to do simple tasks quickly.
As a teacher, I’m tempted (and often succumb) to set goals whose achievement I would find satisfying. I’ve learned that if I set writing goals at a level that students think they can achieve and that they would be satisfied to achieve (I call it “C-level” for competence level), students are much more likely do the assigned work and achieve that level or higher.
Save information for use
People doing an information task for the first time waste a great deal of time and endure a great deal of frustration because they don’t know how to record the information they gather.
By contrast, experienced knowledge workers doing an information task develop strategies and templates for gathering, sorting, labeling, and saving the information they gather.
As a teacher, I try to give my students the benefit of my experience by providing strategies and templates that I and colleagues have found helpful.
Even though the materials I provide might not be useful to every student or in every situation, it’s generally easier for them to modify a prepared structure than to develop one from scratch.
Sequencing precedes skill
To an uninformed observer, skills look like an automatic response to a particular type of stimuli. Actually, skills are sets of tasks performed in such rapid sequence that the tasks seem to melt into one fluid action.
Before people are skilled, they learn to go through component tasks in sequence. Because tasks have both mental and physical components, the learners must:
- Remember the next action required.
- Physically position themselves to perform the action.
- Perform the action.
- Verify that the action was performed successfully or backup to #2.
- Remember the next action required and go through steps 2-5.
When my writing students “get it” they will behave—and feel—as if they were born knowing how to write.
I need to remember that getting to that point will require many repetitions of the underlying process to get their eyes, brains, and bodies to perform the necessary actions automatically.