grad-tpack

asgard-ai-platform ｜ 寫作與文件 ｜ 原文 ｜ MIT

用 TPACK 評估科技融入教學是不是有教學法當根基

---
name: "grad-tpack"
description: "運用 TPACK 框架，在技術、教學法與內容知識的交會處，評估並設計融入科技的教學。當使用者需要評估教師整合科技的準備度、設計教育科技的專業發展，或評估科技的使用是否有教學法作為根基時使用，即使他們說的是「怎麼在教學中整合科技」「教育科技評估」「教師的科技素養」也適用。"
metadata:
  category: "WP-33 傳播/教育/公共行政"
  tags: ["education", "tpack", "educational-technology", "teacher-knowledge"]
---

# TPACK 框架

## 概述

TPACK（Technological Pedagogical Content Knowledge，科技教學內容知識）描述教師要有效整合科技所需的知識。它指出由技術知識（TK）、教學法知識（PK）與內容知識（CK）交會形成的七個知識領域，並主張有效的整合需要同時理解這三者。

## 何時使用

**觸發條件：**
- 評估教學中的科技使用是否具備教學上的合理性
- 設計教師整合科技的專業發展
- 評估教育者知識領域上的落差

**何時不要使用：**
- 依認知層次分類學習目標（改用 Bloom 分類學）
- 設計有鷹架的學習經驗（改用建構主義）
- 評估資訊系統的品質（改用 IS Success Model）

## 假設

```
鐵律：有效的科技整合需要「三種」知識「全部」具備

沒有教學法或內容的科技，只是工具，不是教學。
七個領域：
  TK — 技術知識（工具怎麼運作）
  PK — 教學法知識（怎麼教）
  CK — 內容知識（教什麼）
  TPK — 科技如何促成教學策略
  TCK — 科技如何呈現內容
  PCK — 如何教特定內容（Shulman）
  TPACK — 三者「全部」的交集：最佳點
「任何」一個領域薄弱，都會拉低科技整合的品質。
```

## 方法

### 步驟 1：描繪知識領域
針對授課教師或教學情境，評估各個知識領域（TK、PK、CK）及其交集目前的狀態。

### 步驟 2：找出整合的機會
找出科技在哪裡真的能為特定內容強化教學法。要問：「學生『用』了科技能做到什麼，是『沒有』科技就做不到的？」

### 步驟 3：在 TPACK 交會處設計
設計學習活動，讓科技的選擇是由教學目的「以及」內容需求驅動，不是因為科技很新奇。

### 步驟 4：評估並迭代
評估科技整合是否達成學習目標。要檢查：科技有沒有為教學法服務？有沒有準確呈現內容？學生是否用得到？

## 輸出格式

```markdown
# TPACK 分析：{情境/課程}

## 知識領域評估
| 領域 | 目前狀態 | 證據 | 落差 |
|--------|-------------|----------|-----|
| TK | ... | ... | ... |
| PK | ... | ... | ... |
| CK | ... | ... | ... |
| TPK | ... | ... | ... |
| TCK | ... | ... | ... |
| PCK | ... | ... | ... |
| TPACK | ... | ... | ... |

## 科技整合設計
- 內容目標：{學生該學會什麼}
- 教學策略：{他們要怎麼學}
- 科技的角色：{為什麼偏偏是這個科技}
- TPACK 對齊：{三者如何交會}

## 建議
{針對最弱領域的有重點發展}
```

## 常見陷阱

- **為了用科技而用科技：** 這是最常見的 TPACK 違規。沒有明確教學目的就加進科技（例如用 PowerPoint 取代黑板，教學法卻完全沒變），就是只有 TK，沒有 TPK 或 TPACK。
- **TPACK 取決於情境：** 一位教師可能在某個主題上 TPACK 很強，在另一個主題上卻很弱。它不是一般性的特質，會隨內容領域和科技類型而變。
- **測量上的挑戰：** TPACK 通常用自陳式問卷來測量，分數會被灌水。以觀察和表現為基礎的評量比較有效，但較難規模化。
- **科技變化快速：** 隨著科技演進，TK 衰退得很快。TPACK 的發展必須持續進行，不是一次性的訓練活動。
- **PCK 是基礎：** Shulman 的 PCK（知道如何教特定內容）比 TPACK 早出現，也是它的底層。PCK 薄弱的教師，不管技術多好，都無法發展出強的 TPACK。

## 參考資料

- TPACK 的測量工具，見 `references/tpack-instruments.md`
- TPACK 的課程設計範本，見 `references/lesson-design.md`

---
name: "grad-tpack"
description: "Apply the TPACK framework to evaluate and design technology-integrated instruction at the intersection of technological, pedagogical, and content knowledge. Use this skill when the user needs to assess teacher readiness for technology integration, design professional development for ed-tech, or evaluate whether technology use is pedagogically grounded — even if they say 'how to integrate technology in teaching', 'ed-tech evaluation', or 'teacher technology competency'."
metadata:
  category: "WP-33 傳播/教育/公共行政"
  tags: ["education", "tpack", "educational-technology", "teacher-knowledge"]
---

# TPACK Framework

## Overview

TPACK (Technological Pedagogical Content Knowledge) describes the knowledge teachers need for effective technology integration. It identifies seven knowledge domains formed by the intersections of Technology (TK), Pedagogy (PK), and Content (CK) knowledge, arguing that effective integration requires understanding all three simultaneously.

## When to Use

**Trigger conditions:**
- Evaluating whether technology use in instruction is pedagogically sound
- Designing teacher professional development for technology integration
- Assessing gaps in educator knowledge domains

**When NOT to use:**
- When classifying learning objectives by cognitive level (use Bloom's taxonomy)
- When designing scaffolded learning experiences (use constructivism)
- When evaluating information system quality (use IS Success Model)

## Assumptions

```
IRON LAW: Effective Technology Integration Requires ALL THREE Knowledge Types

Technology without pedagogy or content is just a tool, not instruction.
The seven domains:
  TK — Technology Knowledge (how tools work)
  PK — Pedagogical Knowledge (how to teach)
  CK — Content Knowledge (what to teach)
  TPK — How technology enables pedagogical strategies
  TCK — How technology represents content
  PCK — How to teach specific content (Shulman)
  TPACK — The intersection of ALL three: the sweet spot
Weakness in ANY domain degrades technology integration quality.
```

## Methodology

### Step 1: Map Knowledge Domains
Assess the current state of each knowledge domain (TK, PK, CK) and their intersections for the instructor or instructional context.

### Step 2: Identify Integration Opportunities
Find where technology can genuinely enhance pedagogy for specific content. Ask: "What can students do WITH technology that they couldn't do WITHOUT it?"

### Step 3: Design at the TPACK Intersection
Create learning activities where technology choice is driven by pedagogical purpose AND content requirements, not technology novelty.

### Step 4: Evaluate and Iterate
Assess whether the technology integration achieved learning goals. Check: Did technology serve the pedagogy? Did it represent content accurately? Was it accessible?

## Output Format

```markdown
# TPACK Analysis: {Context/Course}

## Knowledge Domain Assessment
| Domain | Current State | Evidence | Gap |
|--------|-------------|----------|-----|
| TK | ... | ... | ... |
| PK | ... | ... | ... |
| CK | ... | ... | ... |
| TPK | ... | ... | ... |
| TCK | ... | ... | ... |
| PCK | ... | ... | ... |
| TPACK | ... | ... | ... |

## Technology Integration Design
- Content goal: {what students should learn}
- Pedagogical strategy: {how they will learn it}
- Technology role: {why this technology, specifically}
- TPACK alignment: {how all three intersect}

## Recommendations
{Targeted development for weakest domains}
```

## Gotchas

- **Technology for technology's sake**: The most common TPACK violation. Adding technology without clear pedagogical purpose (e.g., PowerPoint replacing a blackboard with no pedagogical change) is TK without TPK or TPACK.
- **TPACK is context-specific**: A teacher may have strong TPACK for one topic and weak TPACK for another. It's not a general trait — it varies by content area and technology type.
- **Measurement challenges**: TPACK is typically measured via self-report surveys, which inflate scores. Observation-based and performance-based assessments are more valid but harder to scale.
- **Rapid technology change**: TK decays quickly as technology evolves. TPACK development must be ongoing, not a one-time training event.
- **PCK is the foundation**: Shulman's PCK (knowing how to teach specific content) predates and underlies TPACK. Teachers weak in PCK cannot develop strong TPACK regardless of technology skills.

## References

- For TPACK measurement instruments, see `references/tpack-instruments.md`
- For TPACK lesson design templates, see `references/lesson-design.md`