Ask. Make. Test. Explain. Then repeat with better evidence.
The cycle gives technical projects a common structure without forcing every learner to build the same object.
Explorer, Builder and Innovator describe increasing independence rather than fixed age bands.Ask a precise, investigable question
A useful project question names a user, setting or observable behaviour. Learners separate what is known, assumed and still uncertain before choosing a tool.
Make the smallest model that can teach something
A sketch, simulation, circuit, code fragment or physical mechanism can all be valid first models. Complexity is added only when it helps answer the question.
Test under stated conditions
Learners define what will be observed, keep relevant variables visible and record results that another person can follow. A failed test is information, not a hidden outcome.
Explain the decision and the limitation
A project review includes what changed, why it changed, what evidence supports the claim and what remains unresolved. The cycle then begins again with a sharper question.
Choose a learning pathway
Explorer, Builder and Innovator describe increasing independence rather than fixed age bands.