Collaborative Inquiry
Collective inquiry is the engine that turns a PLC's shared vision into improved student learning. It is a repeatable cycle: teams frame a question, gather evidence, analyze it together, test a high-leverage change, act, and reflect — then begin again. All examples below are illustrative.
❓ The Four Critical Questions of a PLC
Every inquiry cycle is organized around four questions that keep the team focused on learning rather than on activity:
- What do we want students to learn? — the essential standards and skills.
- How will we know if they have learned it? — common, formative evidence.
- What will we do if they don't learn it? — a timely, systematic response.
- What will we do if they already have? — meaningful extension.
The Collaborative Inquiry Cycle
A repeatable six-stage cycle
- Stage 1
Frame a question of practice. Pick a focused, student-learning question tied to an essential standard. (Critical question 1) - Stage 2
Gather evidence & student work. Collect common formative data and samples of student thinking. (Critical question 2) - Stage 3
Analyze together. Describe the evidence without judgment, then infer what might explain it. - Stage 4
Decide a change to test. Choose one high-leverage instructional move and define how you'll measure impact. (Critical questions 3 & 4) - Stage 5
Act. Teach the change across the team and collect the next round of evidence. - Stage 6
Reflect & repeat. Ask what worked, what didn't, and what the next question is — then start the cycle again.
The cycle is continuous: reflection feeds the next question, so improvement compounds over time.
① Frame · ② Gather
Start narrow. A sharp question ("Can students compare fractions with unlike denominators?") beats a broad one ("How's math going?"). Decide in advance what evidence will answer it.
③ Analyze · ④ Decide
Look at the work together before drawing conclusions. Separate observation ("38% used a common denominator") from inference, then commit to one change everyone will try.
⑤ Act · ⑥ Reflect
Teach the change, re-measure, and reflect honestly. A cycle "succeeds" when the team learns something it can act on — even when the change didn't move the needle.
Worked example: a Grade 4 fractions inquiry
The Grade 4 Math PLC noticed students struggling to compare fractions with unlike denominators. They ran one full inquiry cycle over three weeks. (Illustrative sample data.)
- Frame
Question: "Can our Grade 4 students accurately compare two fractions with unlike denominators and explain their reasoning?" (Essential standard 4.NF.A.2.) - Gather
Evidence: A 6-item common formative assessment plus written explanations. Baseline: 54% accuracy across 71 students. - Analyze
Pattern: Most errors came from comparing numerators only. Students who drew a model or found a common denominator were far more accurate. - Decide
Change to test: All four teachers would teach a shared "benchmark & common-denominator" mini-routine with visual models, three times that week. - Act
Re-measure: Re-administered a parallel assessment. Accuracy rose to 65%; reasoning explanations improved most. - Reflect
Next question: "Why are two classes still below 60%?" — leading into the next cycle, focused on those student groups.
The team logged its common assessment in the Knowledge Library so other grade teams could reuse it.
Where inquiry teams spend time
Illustrative breakdown of a healthy cycle's meeting time.
Common pitfalls & fixes — click to expand
Fix: Use a structured data protocol that separates observation from inference. Describe what the evidence shows before anyone proposes a cause or a cure.
Fix: Anchor the question to one essential standard and one piece of common evidence. If you can't measure it in a cycle, it's too big.
Fix: Co-create a short common formative assessment so the team is looking at comparable evidence — not six different snapshots.
Fix: Time-box the cycle and end with reflection. Name what you learned and the next question before moving on, even if results were mixed.
Collaborative inquiry only thrives where there is trust. Dr. Barbara Z. Franks' doctoral research on leadership behaviors that build trust and a collaborative culture found that teams take the risks inquiry requires — sharing student work, admitting a strategy didn't land — only when leaders make collaboration safe and routine. The protocols in the Meeting Hub exist precisely to lower that risk. (Illustrative summary for this portfolio platform.)
All data shown is illustrative sample data created for demonstration.