The pitfalls of moving from pedagogical to curricular reform.
Where professors often get tripped up is moving from issues of
teaching to issues of curriculum. Shifting from pedagogical
innovation to curricular innovation can politicize the change (Kozma, 1985). Another
characteristic of this case similar to others we have seen is what
happens when a key innovator who is doing innovative teaching on her
own tries to involve her colleagues. Inevitably, the pedagogical
becomes curricular, and suddenly the unsuspecting person has wandered
into a quagmire of unseen issues and deeply held opinions. Although
many faculty may not worry about how others may teach (considering it
to be an individual matter), trying to change the curriculum can
awaken deep divisions of opinion that are otherwise papered over in
the name of collegiality.
The advantages of "tinkering" with one's teaching.
In a study of faculty who tried changing their teaching practices,
Stevens (1988) found that the most successful faculty tended to
"tinker" with their teaching--that is, they changed their teaching in
small and manageable ways rather than on a large scale. Stevens also
described two different kinds of "tinkerers": reactive and
reflective. Reactive tinkerers tended to change their teaching to
solve a particular problem by adopting a technique or trick (e.g.,
trying "think-pair-share" activities with seemingly bored students),
and when the technique didn't work, the reactive tinkerers tended to
give up. However, the reflective tinkerers that Stevens studied
tended to tinker regularly, seeking not necessarily to solve problems
but to engage in a kind of continuous improvement, knowing that one
never solves instructional problems permanently and for all groups.
Moreover, reflective tinkers tended to rely not on others, but on
themselves, as creators and evaluators of instructional innovations.
By analogy, we might say that reactive tinkerers are like computer
users who run into a problem and download a utility that they expect
to help them. If it solves their problem or meets their need, then
great, they press ahead. But if it doesn't, they uninstall it and
either give up or search for something else. Reflective tinkerers, on
the other hand, see teaching as "open-source code" and themselves as
programmers with a capacity for building their own innovations. And
although they too may borrow tools and utilities that others have
made, they are willing to "reverse engineer" an approach that doesn't
work and perhaps use it in a different context. As with computing,
those who can construct and evaluate their own approaches have
greater flexibility (and perhaps satisfaction!) than those who must
rely on programs or applications devised by others that may or may
not accommodate their particular circumstances.