Glossary
Shared language makes project review easier.
Students can use the same words when discussing assumptions, tests, evidence, limitations, and revision decisions.
Question designA strong project starts with a question that can be explored and verified.Students should define the phenomenon, problem, context, and evidence need before jumping to tools.VerificationIdeas become credible when evidence is visible.Useful evidence includes the question, map, test, result, feedback, and next decision.MentoringUseful feedback should change the work.Mentor comments are strongest when they target assumptions, test design, evidence quality, and communication.PlanningThe right program depends on stage, time, and output.Students should choose a format based on current evidence, not on the most impressive title.PathwaySTEM learning works best in milestones.A long pathway sequences question design, knowledge mapping, testing, prototyping, and communication.Project briefA brief keeps project work from becoming scattered.Before building, students should state the question, assumption, method, test, and expected output.AssessmentProgress is visible in stronger decisions.Better questions, cleaner evidence, and clearer revisions are more meaningful than decoration.Workshop designA good workshop produces one concrete skill.Workshops should leave students with a tested object, method, or decision they can reuse.TeamworkTeam clarity prevents duplicated work.Students need ownership for discovery, prototype, verification, design, writing, and presentation.PortfolioA portfolio should show decisions, not only finished slides.Reviewers should see question quality, evidence, feedback, revisions, and explanation.