From Student Data to Action: Applied Decision-Making Cases
This lesson applies the full data-based decision-making framework to complex school cases. The emphasis is not on finding one “correct” score, but on deciding what the available evidence supports, what remains uncertain, what instructional explanation is most testable, and what action should follow.
This section provides the technical background and applied examples behind the guide's recommendations. Pay particular attention to the inquiry-cycle example, the use of multiple data sources, development and testing of hypotheses, student data-use examples, collaboration structures, and the descriptive evidence used to illustrate schoolwide and districtwide implementation.
Open the Reading ↗
Why Applied Cases Matter
The technical appendix makes an important point visible: real data-based decision making rarely begins with a perfectly clean data set. Teams often work with multiple sources collected for different purposes, incomplete information, historical context, and competing explanations.
The strongest decisions therefore depend on disciplined reasoning. Teams must distinguish what the data directly show from what they infer, consider plausible alternative explanations, choose a response that tests the most defensible hypothesis, and return to new evidence.
The Technical Appendix Reinforces Evidence Humility
Appendix D explains that much of the literature on educator data use consists of descriptive and qualitative studies rather than rigorous causal trials. The examples are useful because they show how schools and teachers have used inquiry cycles, student feedback, collaboration, and data systems in practice.
But an illustrative case is not proof that the practice caused improved achievement. This is especially important in applied decision making, where practitioners may be tempted to treat a compelling story as stronger evidence than it actually is.
Applied Case Pattern 1: Start With Multiple Sources
The Appendix D example for Recommendation 1 describes schools beginning an inquiry process by assembling information from several categories, including achievement data, language proficiency, demographics, program participation, attendance, and course history.
The point is not that every case requires every category. The example shows that teams can use multiple sources to describe a problem more accurately before settling on an explanation.
Describe current or historical academic performance.
May reveal discontinuities in curriculum, intervention exposure, or course sequence.
Help determine whether opportunity to learn may differ across students.
Can identify meaningful groups or conditions that warrant closer comparison.
Applied Case Pattern 2: Turn a Pattern Into a Testable Hypothesis
In the technical appendix, one secondary school noticed a possible achievement difference between students entering from the traditional feeder school and students entering from other schools. Rather than treating feeder status as the explanation, the school developed a hypothesis and compared achievement patterns across groups.
Further analysis suggested a curriculum discontinuity: the high school's mathematics sequence aligned with the traditional feeder school's sequence, while students arriving through other routes had experienced a different course sequence.
Applied Case Pattern 3: Modify Instruction Based on the Hypothesis
Once the school identified curriculum discontinuity as a plausible explanation, it did not stop at analysis. The school added instructional supports, including additional coursework intended to help affected students enter the mathematics sequence more successfully.
This illustrates the full logic of the inquiry cycle: identify a pattern, develop an explanation, change instruction in a way connected to the explanation, and examine subsequent student data.
| Weak decision | Stronger decision |
|---|---|
| “These students are low, so add more intervention.” | Identify the specific mismatch or skill need, then select a response that directly addresses it. |
| “The subgroup difference proves feeder-school quality is the cause.” | Generate competing explanations and examine curricular or instructional differences before attributing cause. |
| “The new course seems reasonable, so no further data are needed.” | Collect follow-up data to determine whether the instructional modification changes the pattern. |
Applied Case Pattern 4: Distinguish Intervention Failure From Implementation Failure
In school-based problem solving, a flat progress-monitoring trend can tempt a team to conclude that an intervention “does not work.” That conclusion is only justified if the intervention was actually delivered with sufficient fidelity, dosage, and opportunity for response.
If sessions are routinely shortened, missed, or substantially altered, weak student progress cannot cleanly evaluate the intervention itself. The team must first distinguish a problem with the intervention model from a problem with implementation.
Applied Case Pattern 5: Use Discrepancies as Information
Conflicting data do not necessarily mean that one source is wrong. A student may perform poorly on a benchmark but adequately in supported classroom work, or may earn acceptable course grades while progress-monitoring data remain weak.
These differences can reflect task demands, instructional supports, scoring practices, content coverage, timing, or student response conditions. The appropriate response is to investigate the discrepancy rather than average unlike measures into a single number.
Applied Case Pattern 6: Separate Status, Growth, and Goal Attainment
A student can be below benchmark and improving rapidly. A student can be at benchmark but showing declining performance. A student can demonstrate a positive slope that is still insufficient to reach a long-term goal.
These are different questions. Status asks where performance is now. Growth asks how performance is changing. Goal attainment asks whether the current trajectory is sufficient to reach the desired outcome.
Do not ignore the remaining gap, but do not describe the intervention as producing no response.
Current status may conceal an emerging concern that warrants monitoring.
The intervention may be helping but may still need intensification or refinement.
Correct implementation before concluding that the intervention model is ineffective.
Applied Case Pattern 7: Keep Student and System Explanations Open
Weak achievement should not automatically be located within the student. Data-based problem solving should consider curriculum, instructional match, opportunity to learn, implementation, grouping, task demands, and schoolwide conditions alongside student-specific skill needs.
This does not mean every problem is caused by instruction. It means the team should avoid deciding on the cause before examining evidence capable of distinguishing among plausible explanations.
Decision Rules Make Follow-Up More Defensible
Before changing instruction, teams should decide what evidence will count as an adequate response. Without a prospective decision rule, teams may move the standard after seeing the results.
What specific skill or performance indicator will be measured?
How often will the outcome be collected?
How much data will be gathered before reviewing the pattern?
What result will lead to continuation, modification, intensification, or discontinuation?
A Psychologist's Applied Decision-Making Framework
- Define the decision. What exactly is the team trying to decide?
- Describe the pattern. Separate observations from explanations.
- Check data quality. Consider timing, comparability, missing data, and measurement purpose.
- Triangulate. Determine where sources converge and diverge.
- Generate competing hypotheses. Avoid locking onto the first plausible explanation.
- Check implementation. Determine whether the current instruction/intervention was delivered as intended.
- Select the most informative next action. Prefer an action that both helps the student and tests the hypothesis.
- Define follow-up evidence. Decide in advance what will be reviewed next.
Evidence Calibration: What Can the Team Conclude?
Select every conclusion that is supported.
Match the Data Pattern to the Best Next Step
A. Flat progress-monitoring trend; intervention sessions are frequently missed.
B. Benchmark is low, but classroom performance is strong with extensive teacher prompting.
C. Overall reading score is low; item analysis shows accurate decoding but weak inference questions.
D. Student remains below benchmark but has shown strong, consistent growth for six weeks.
Sequence a Defensible Applied Decision
Click the steps in the strongest order.
Multi-Stage Consultation Case: Intervention Failure or Implementation Failure?
Stage 1: What information is most important before changing programs?
Stage 2: New implementation information
Stage 3: Implementation is corrected
Stage 4: Make the next decision
Distinguish Intervention Failure from Implementation Failure
Apply the full data-based decision-making framework to an intervention case. Your response will receive individualized feedback on whether you identify fidelity and dosage concerns, avoid premature intervention-failure conclusions, recommend implementation corrections, request additional progress data, and identify the next defensible decision point.
Distinguishing Intervention Failure From Implementation Failure
Applied data-based decision making requires disciplined movement from evidence to inference to action. Teams should triangulate sources, investigate discrepancies, distinguish intervention effects from implementation problems, and keep status, growth, and goal attainment conceptually separate.
The strongest next step is often the one that both supports the student and generates useful new evidence. For psychologists, this means helping teams make decisions that are specific, testable, and appropriately cautious rather than turning incomplete patterns into premature conclusions.