# Data-Driven Instruction & Data Teams (Workshop) > A ready-to-run PD workshop on data-driven instruction: analyze, respond, recheck. Run-of-show, handout, follow-up. 15, 45, or half-day. *A ready-to-run professional learning workshop from K12 Academics. Source page: https://pd.k12academics.com/data-driven-instruction-workshop.html* Data only helps if it changes what you do next. Data-driven instruction is the cycle of looking at real evidence of learning, finding the specific gaps, and planning a concrete instructional response, together as a team. Data helps only when it drives a concrete next instructional move; the cycle is analyze, plan a response, teach, and check again. ## Why it works Effective data use is not about more testing or dashboards; it is a disciplined cycle in which teachers analyze student work for specific error patterns, plan a targeted reteach, and check whether it worked. The research points to frequent, low-stakes evidence, analyzed closely, and acted on quickly. **The research:** Bambrick-Santoyo on data-driven instruction; research on data teams. ## The run-of-show ### Staff meeting (15 minutes) A fast introduction to plant one routine. **Goal:** everyone leaves with one thing to try. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 3 min | Hook | After a test, do you move on or dig into the errors? Name it. | You are surfacing move-on-ism. | | 0:03 | 5 min | Mini-teach | Analyze the why, plan a response, recheck. One slide. | | | 0:08 | 5 min | Plan one | Pick an assessment and one error pattern to examine. Turn and talk. | | | 0:13 | 2 min | Commit | Each person names the gap they will reteach. | | ### PLC / team meeting (45 minutes) The standard version. **Goal:** every teacher leaves with something designed for a real upcoming lesson. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | 0:00 | 5 min | Hook | A score report vs a close look at how students erred. Compare. | Let them feel the difference. | | 0:05 | 8 min | Mini-teach | The data cycle and a focused data meeting. | | | 0:13 | 12 min | See it in action | Analyze a shared work sample for the error pattern. | Model digging into the why. | | 0:25 | 12 min | Design | Plan a targeted reteach and set a recheck date. | Protect the full time. | | 0:37 | 5 min | Share | Swap plans in pairs; sharpen the reteach. | Keep it in pairs. | | 0:42 | 3 min | Commit + follow-up | Lock it in and confirm the recheck date. | | ### Half-day institute (~3 hours) A deep session for a PD day. **Goal:** built, practiced, and a rollout planned. | Start | Length | Segment | What happens | Facilitator note | | --- | --- | --- | --- | --- | | Block 1 | 45 min | Experience + why | Move-on vs analyze, then the data cycle. | | | | 15 min | Break | | | | Block 2 | 60 min | Run data cycles | Teams analyze a shared assessment and plan reteaches. | Group by subject. | | Block 3 | 45 min | Practice | Facilitate a focused data meeting with peers. | Keeping it tight is the skill. | | Close | 15 min | Plan the rollout | Set a data-meeting rhythm; set the check-in. | | ## The core activity: run a mini data cycle Teams leave having analyzed one assessment for its error pattern and planned a targeted reteach with a recheck date. - Bring a recent common assessment or work sample. - Analyze it for the specific error pattern, not just the score. - Plan a targeted reteach for that specific gap. - Set a date to check whether the reteach worked. ## Facilitator notes - Analyze student work, not just scores. - Keep meetings short and focused on one assessment. - End every cycle with a concrete plan and a recheck date. ## Adapt it - **Elementary:** team analysis of common assessments and work samples. - **Secondary:** department data cycles organized by standard. - **All teams:** protect short, focused data time. ## Participant handout One page for every teacher. Print it, or save it as a PDF. ### Data-Driven Instruction: analyze, respond, recheck **A tight cycle:** analyze the error pattern, plan a targeted reteach, set a date to check it. - The assessment or work sample: __________ - The specific error pattern: __________ - My targeted reteach plan: __________ - The date I will recheck: __________ - How I keep the meeting focused: __________ ## Make it stick - Analyze work, not just scores. - Always plan a response and a recheck date. - Bring a reteach that worked to the next PLC. ## Common questions **Isn't this just more testing?** No. The best data is often student work you already have. The discipline is in analyzing it closely and acting on it, not in collecting more. **What does a good data meeting look like?** Short, focused on one assessment, digging into specific error patterns, and ending with a concrete reteach plan and a date to check it. **What if the data shows most students failed?** That is useful information. Plan a reteach that addresses the specific misunderstanding, then recheck. A first-pass failure is data, not a verdict. ## Go deeper - [The Learning Scientists](https://www.learningscientists.org) ## Build it into a bigger day - [Checking for Understanding](https://pd.k12academics.com/checking-for-understanding-workshop.html) - [Standards-Based Grading](https://pd.k12academics.com/standards-based-grading-workshop.html) - [Feedback That Moves Learning](https://pd.k12academics.com/feedback-that-moves-learning-workshop.html) --- Full workshop page: https://pd.k12academics.com/data-driven-instruction-workshop.html All workshops: https://pd.k12academics.com/