Strategies

Data Driven Inquiry

Strategy · All strategies
Evidence · 1 claim (1 for) · 3 studies (2 quant-synthesis, 1 review), q2–q3 · 2 of 3 report an effect size

Description

Data driven inquiry is a structured, collaborative cycle in which educators examine evidence of student learning — assessment results, work samples, attendance, engagement data — to identify learning gaps, generate hypotheses about their causes, and design and test instructional responses. It is typically carried out in teams (data teams, professional learning communities) using a repeated protocol: collect data, analyze for patterns, infer causes, act, and re-examine. The strategy treats instructional decisions as hypotheses to be tested rather than assumptions to be defended.

Design Implications

Data driven inquiry operationalizes Assessment for Learning at the instructional-program level: evidence is used to adapt teaching rather than merely to certify outcomes Formative assessment practices improve achievement. [+S]. Its effectiveness depends on the quality of the inquiry, not the quantity of data — teams that move quickly from data to a pre-selected solution, or that read data without surfacing underlying assumptions about learners, show little instructional change [~M]. Structured protocols that slow the leap from observation to action are what distinguish genuine inquiry from data theater.

Context

Requirements

Constraints

Implementation Variability

Target Learners

Target Learning Goals

Instructions

  1. Frame a question of practice grounded in a learning goal, not a data source ("Why are students failing items on proportional reasoning?").
  2. Collect and display relevant evidence — common Assessment results, anonymized student work, and classroom evidence at a grain size actionable within weeks.
  3. Observe before interpreting — use a protocol that forces "noticings" to be separated from explanations, guarding against confirmation bias.
  4. Generate multiple causal hypotheses, including ones about instruction rather than only about students; prioritize using Class Discussion norms that invite dissent.
  5. Act on the leading hypothesis — design a targeted instructional response (reteaching, Coaching, revised tasks) and commit to a timeline.
  6. Re-assess and iterate — collect new evidence on the same goal and repeat the cycle; treat the first response as a test, not a fix.

Examples

Key Sources

Page metadata
Field Value
type strategy
id data-driven-inquiry
title Data Driven Inquiry
description A collaborative cycle in which educators analyze student learning data to identify gaps, hypothesize causes, and adjust instruction.
status review
generated by claude/unspecified on 2026-08-29
trust unverified — no one has confirmed this page's content

Frontmatter is the page's machine-readable record — see the Schema & Guide.