Problems, then questions, then knowledge
PQK Lab is an inquiry workshop, not a poster factory. This page keeps inquiry project teams on the trail from friction to knowledge. PQK allows teams when roles map to the loop and each name can explain a page of the trail.
Teams hide weak questions behind divided labor. Someone cuts foam. Someone writes claims. Nobody owns the miss. For inquiry project teams, the lab's answer is inquiry-based STEM: notice a real problem, design a researchable question, gather evidence a peer could inspect, build a knowledge model, and only then communicate.
If inquiry project teams still lives at the level of a theme, PQK will not help a team jump to a showcase title. The sequence is the pedagogy. Problems, questions, knowledge.
The inquiry move this page trains
The habit here is credit that follows log pages. Practice is trail-first. Keep objects that make inquiry project teams visible, then ask for critique on those objects rather than on vibe.
Teams keep objects that make inquiry project teams visible: trail object, role note, critique question, and next track. Those objects are the curriculum. They are also the only honest rehearsal for a later science fair, design review, or classroom critique.
Mentors do not seize the build when the work is inquiry project teams. They ask for the trail. A visiting teacher should be able to follow the trail from the first noticing to the latest model without needing a speech.
- trail object
- role note
- critique question
- next track
How inquiry quietly turns into display
PQK watches inquiry project teams fail in predictable ways. The failure is usually not a lack of enthusiasm. It is a missing problem, an untestable question, or a knowledge claim that arrived before the evidence log.
Repair is always a return to the trail. Redesigning the poster comes last. For inquiry project teams, PQK would rather keep an ugly notebook with a live question than a beautiful board with a dead one.
- replacing the learner's noticing
- hiding misses
- chasing a theme that has no setting
Problem framing for students
Problem framing is a craft, including when the work is inquiry project teams. Students learn to separate a grievance, a wish, and a problem that can be investigated. A grievance may be true and still too large. A wish may be kind and still untestable. A problem has a setting, a friction, and a possible observation.
From a framed problem, question design produces variants. Some variants are too broad. Some hide the answer. Some require a laboratory the team does not have. The surviving question is researchable because evidence could confirm or embarrass it. That is the PQK meaning of researchable questions in inquiry project teams.
Evidence habits then take over in inquiry project teams. Teams decide what they will count, photograph, measure, or trial, and how they will record a miss. Knowledge is not a paragraph of certainty. It is a model that can be revised when the next trial disagrees.
Evidence, models, and builds
Practice is trail-first. Keep objects that make inquiry project teams visible, then ask for critique on those objects rather than on vibe. An evidence log for inquiry project teams is dated, located, and unit-aware. A knowledge model names causes, constraints, and uncertainties. An inquiry build is a test, a prototype, a protocol, or a data story that tries the model in the world.
Showcase communication about inquiry project teams is last because communication should carry knowledge, not conceal its absence. A poster that cannot point to a log is advertising. A talk that cannot admit a failed trial is theatre.
You are aligned with the lab when a visitor can follow the trail without a speech.
Who uses this lab page
Students use it to see how inquiry project teams is supposed to feel in the hands: messy at first, then sharper. Families use it to support the trail without replacing the noticing. Schools use it to design inquiry clubs that do not collapse into craft hour.
Inquiry mentors use this page as a shared critique language for inquiry project teams: problem, question, evidence, model, build, communication. Learning partners use it to see how a challenge brief can stay student-scale.
PQK does not publish rankings, invent faculty celebrity, or quote unnamed testimonials about inquiry project teams. The lab's proof is the quality of questions and the inspectability of evidence.
What to do after reading
Enter the matching curriculum track or read the FAQ for role boundaries. An inquiry about inquiry project teams should include a real setting, a first-pass problem, any question already attempted, and constraints of time, tools, and school context.
If you need a track for inquiry project teams, open the curriculum. If you need a format, use offerings and the compare page. If you are a school, describe the club or unit the module would sit inside. If you are a family, say how much authorship the student can actually sustain.
The lab will answer inquiry project teams with a smaller question more often than with a larger plan. That is a compliment to the work.