Quest Future Pioneers keeps this page on qfp.org because demo day is part of making, not a ceremony that ends the quest. Visitors touch the object, ask hard questions, and leave notes. The two weeks after are when the team decides what those notes mean for the next build. If the studio goes quiet after applause, the pioneer cycle broke at the exact moment it should have tightened.
This page is a revision plan for project-based STEM learning. It assumes a prototype existed on the table and a test could fail in private before the public demo. Student prototyping as a future skill shows up here as judgment: what to keep, what to cut, and what not to decorate.
Capture feedback before it becomes myth
Within twenty-four hours, write down what visitors actually said. Separate praise from usable constraints. “Cool” is not a revision item. “The lever slips when a younger sibling pulls it” is. Photograph the demo table as it was, including the messy cables you wanted to hide. The messy middle is evidence for the sequel.
Assign one teammate to own the feedback log. If feedback lives only in group chat, it will be rewritten by whoever speaks loudest next week. QFP wants a short log: visitor question, observed failure, proposed change, owner, due date.
Re-open the constraint card
Demo day often reveals that the quest was still too wide. Shrink it. Rewrite the one-page quest brief with a sharper user, a tighter materials limit, and a demo promise that fits five minutes. Unlimited ambition stays unbuilt. A materials budget is a teacher.
Ask: what can a visitor hold, press, or watch in under five minutes in the revised version? If the answer is still a speech about a world problem, you are pitching again. Pioneers demo objects.
Re-run the test that embarrassed you
The skipped private test always returns during Q&A. In the two weeks after, schedule that test again on purpose. Write pass and fail notes on a card. If the team hides failed builds so the quest looks clean, the sequel will fail in public louder than the first demo.
Cheap materials first. Do not buy tools to look advanced. Cardboard revisions that prove a mechanism beat expensive parts that delay learning. Mentors shrink scope; they do not steal the build.
Fix roles, not only parts
If one student presented while others became furniture, the social design failed. Reassign pioneer roles for the sequel: builder, tester, demo lead, documentation. Each person must be able to touch the object. Spectating is not a future skill.
Rehearse a five-minute demo with a visible constraint card. Practice handing the object to a visitor. Practice answering “what failed earlier?” without changing the subject to a slogan about changing the world.
Choose three revisions, not thirty
Over-revision is how sequels miss the calendar. Pick at most three changes that a visitor could notice. Example set: strengthen the slipping lever; shorten the explanation to one sentence; add a test card that shows last week’s fail. Everything else goes to a parking list for a later quest.
End week one of the two-week window with a working revised prototype, even if ugly. End week two with a short internal demo to a different adult than the first audience. Public polish without a new test is decoration.
Documentation that survives the sequel
Keep a revision photo sequence. Keep the updated brief. Keep the test card. These files are how STEM learning as a quest stays reviewable when the term ends. A poster about future skills without an object is the wrong artifact for QFP.
If the team wants to claim progress, they should be able to point at what changed between demo day and the sequel table. Claims without photos of the messy middle are theater.
What mentors should demand
Mentors should demand a written constraint rewrite before new parts are ordered. They should demand a dated failed test. They should refuse daily quest changes that prevent shipping. They should notice when one student owns the narrative while others cannot explain the mechanism.
Calendar honesty matters: if the first revised prototype is scheduled after the poster refresh, the quest is inverted again. Put the object earlier than the speech.
Name the next quest without declaring victory
Close the two weeks by naming the next build in one sentence: smaller, harder, clearer. Do not declare the future solved. Pioneer culture is a shorter path to a first version and a clearer constraint for the sequel — not a victory lap.
If a visitor returns, they should see a different object, not a louder story about the same object. That difference is the revision plan working. That is what QFP means by project-based STEM learning for future pioneers.
A sample two-week calendar
Day one: feedback log and photo of the demo table. Day two: rewrite the constraint card with the team present. Day three to five: rebuild the weakest mechanism with cheap materials and run one embarrassing test. Day six: internal critique with roles rehearsed. Day seven to ten: integrate at most three changes and update documentation. Day eleven to fourteen: second internal demo, then freeze scope so the sequel does not melt into endless tinkering.
If a school holiday interrupts the window, shorten the change list rather than skipping the failed test. The test is the learning. The calendar is only a container. Teams that protect the poster and abandon the test are practicing theater, not pioneer STEM.
When not to revise
Sometimes the honest revision is to retire the quest. If the object cannot be made safe, if authorship collapsed into one student doing everything, or if the brief was never real, stop. Write that decision down. Starting a cleaner, smaller quest is better than polishing a hollow demo for another public night.
QFP would rather see cardboard and an honest stop than a second stage performance of an unowned build. Future skills include the courage to end a bad quest without inventing awards for it.