Demos need a calendar
Project-based STEM quests fail when every team invents a new idea in week six. Pace pioneer demos across a term so constraints, builds, and public tests have room.
If you cannot prototype with this week’s materials, it is not this week’s quest.
Brief, small public tests, close the file
Month one chooses buildable briefs and ends with an object or an honest empty. Month two uses short frequent demos. Month three submits brief, constraints, test log, and a script another team could run.
Skip brief, build, or present and the quest becomes theater. No invented awards or partner brands.
Operational checklist 1
Treat block 1 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 2
Treat block 2 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 3
Treat block 3 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 4
Treat block 4 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 5
Treat block 5 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 6
Treat block 6 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 7
Treat block 7 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.
Operational checklist 8
Treat block 8 as a named deliverable with an owner, a filename, and a review date. Write the failure mode before you write the polish. If the file cannot be opened by a second reader, the cadence failed even if the conversation felt productive. Prefer a smaller scope that closes over a larger scope that only exists as intention. Keep a decision log that states what changed after feedback and what remains unknown. Refuse silent disappearance; pause with a note to the coordinator when school load collides. End the week with a shutdown ritual: save, name the next block, and calendar it. Do not invent metrics, partners, or outcomes this page cannot defend.