Tpack

A teacher who is brilliant at their subject and bad with technology is not automatically worse than one who is the other way around.

For years the conversation in education has swung between two poles. Either you emphasise deep content knowledge and treat technology as a minor delivery mechanism, or you emphasise technical fluency and assume the subject matter will take care of itself. Both moves are mistakes, because neither knowledge alone nor technology alone is what makes a good lesson. A researcher named Mishra and a researcher named Koehler worked out a framework in the mid-2000s that made this obvious once stated. Teaching well with technology requires three different kinds of knowledge, each with its own texture, and more importantly it requires the three of them to intersect in a way that is its own distinct competence.

There is content knowledge, which is knowing the subject deeply enough to recognise the hard parts and where students typically get lost. There is pedagogical knowledge, which is knowing how learning actually happens and what moves tend to help at which moments. And there is technological knowledge, which is a real understanding of what a given tool can and cannot do. Their framework, which they called TPACK, argues that the interesting place is not any one of the three but the tiny overlapping middle where all three meet. A teacher who sits inside that middle can pick a technology for a reason that is grounded in both their subject and their pedagogy, rather than importing a tool because it was fashionable or avoiding one because it was unfamiliar. Most teacher training programmes still teach the three separately, and most teachers still have to find the overlap on their own. When you saw a teacher use technology well, what was different about how they chose the tool in the first place?

Last week we looked at designing for everyone from the start. This week we look at what a teacher needs to know to use technology well, which is not just being good at the technology.