Professional Learning  ›  EdTech & AI  ›  Workshops  ›  The TPACK Framework
a ready-to-run workshopThe TPACK Framework
EdTech & AI · Workshop

The TPACK Framework (Workshop)

Everything you need to lead this with your staff or PLC: a minute-by-minute run-of-show, what to say, what to hand out, and how to make it stick. Pick the length that fits your slot.

Key takeaway

Good tech integration lives where three kinds of knowledge overlap, the content, how to teach it, and what the technology does, so the question is never just is this a good tool but does this tool fit this content and this way of teaching it.

Format
PLC / team meeting
Length
45 minutes
Group size
Any (works 4-40)
Who can run it
Any teacher-leader
You will need
Slides (5)Printed handoutA lesson with tech in mindA timer
Aligned to
Learning Forward: Rigorous ContentInTASC 8: Instructional StrategiesThe TPACK framework (Mishra & Koehler)
Share / assign

Why it works

The TPACK framework, developed by Punya Mishra and Matthew Koehler, is a way of thinking about what teachers need to know to integrate technology well, and it is a useful complement to SAMR. Where SAMR asks how deeply a technology transforms a task, TPACK asks whether the technology actually fits the specific content and pedagogy. It names three bodies of knowledge: Content Knowledge (the subject itself), Pedagogical Knowledge (how to teach in general), and Technological Knowledge (what the tools can do), and argues that effective teaching, and especially effective tech integration, happens in the overlaps. Pedagogical Content Knowledge, knowing how to teach this particular content, is the long-standing heart of good teaching. TPACK adds technology to the picture: Technological Content Knowledge (which tools genuinely represent or extend this content, a dynamic graph for functions, a simulation for forces), Technological Pedagogical Knowledge (which tools support this way of teaching, a collaborative doc for peer revision), and at the center, the sweet spot where all three meet: choosing a technology that fits both the specific content and the specific pedagogy. The practical value of the framework is that it reframes the integration question. The weak question is is this a good app; the TPACK question is does this tool fit this content and this teaching move, which protects against the common failure of bolting trendy technology onto a lesson where it adds nothing, or where a simpler non-tech approach would teach the content better. The workshop uses TPACK as a lens on teachers' own lessons: naming the content and pedagogy first, then asking whether a given technology genuinely serves both, and discarding tech that does not.

The research: The TPACK framework for technology integration (Mishra & Koehler).

The run-of-show

Choose your slot. The agenda, timings, and length update to match.

    The core activity: judge tech by fit

    The heart of the session is using TPACK to ask whether a technology genuinely fits the content and the pedagogy.

    Does this tool fit this content and this teaching?TPACK locates good integration where content, pedagogy, and technology overlap. The weak question is 'is this a good app'; the TPACK question is 'does this tool fit this content and this teaching move,' which kills tech-for-tech's-sake.

    Facilitator notes

    'Is it a good app' is the wrong questionA tool can be excellent and still not fit this content or this teaching move. Name the content and pedagogy first, then ask if the tool serves both; if not, drop it.

    Adapt it

    Participant handout

    One page for every teacher. Print it, or save it as a PDF.

    K12 Academics · Professional Learning

    The TPACK Framework: integrate by fit

    Content + pedagogy + technology: name content and teaching first, then ask whether the tool fits both; discard misfits.

    1. The content of my lesson:
    2. The teaching move (pedagogy):
    3. Does the tool fit the content?
    4. Does it fit the teaching move?
    5. Tech I will discard or replace as a misfit:

    Make it stick

    TPACK works as a habit of judgment. Close by setting the follow-up:

    Common questions

    How is TPACK different from SAMR?
    They answer different questions and work well together. SAMR asks how deeply a technology transforms a task, from substitution to redefinition. TPACK asks whether the technology fits the specific content and pedagogy at all. A tool can rate high on SAMR and still be a poor fit for the content; TPACK catches that. Use TPACK to judge fit, SAMR to judge depth.
    Isn't this just common sense?
    It is, and naming it is what makes it usable. The framework turns a vague instinct into a concrete habit: name the content and the teaching move first, then ask whether the tool serves both. That sequence protects against the very common failure of choosing a tool because it is new or popular and bolting it onto a lesson where it adds nothing. Common sense is easy to skip; a lens is easy to apply.
    What if the best fit is no technology?
    Then use no technology. TPACK explicitly allows that sometimes the tool that best serves the content and pedagogy is a pencil, a manipulative, or a discussion. The framework is about fit, not about maximizing tech. Recognizing when a simpler non-tech approach teaches the content better is a correct TPACK judgment, not a failure to integrate.

    Go deeper

    Build it into a bigger day