This page gives a clear short explanation of what Driven by STEM is and why it is designed the way it is. It works best as a concise description of the experience before moving into the fuller educator materials.
Driven by STEM is a MakeCode Arcade learning experience built for the F1 x Mercedes x Microsoft STEM and career exploration activation. It is designed to feel like a short, active invitation into engineering thinking: students make a choice, test it, notice what changed, and talk about why it changed.
What Educators Should Expect
Students will spend most of their time in a build-test-improve loop. They will make a decision, run the game, notice what changed, and explain what they think caused it. The educator’s job is to guide attention toward evidence, not to narrate every mechanic.
That means the most useful facilitation moves are usually short:
- point to one visible change
- ask for one prediction before a test
- ask students what became easier, harder, faster, riskier, or more efficient
- connect that observation to a role, system, or design choice
What Learners Actually Experience
Learners move through a guided skillmap rather than opening a blank coding workspace.
- In The Garage, they enter the mission, make setup choices, and run a first shakedown.
- In On the Road, they feel those choices in motion, encounter pit stop briefings, and adapt to changing conditions.
- In The Finish Line, they apply what they have learned, review the results, and connect the experience back to careers and next steps.
This structure matters because it keeps the session coherent. Students are not collecting disconnected activities. They are moving through one arc that starts with curiosity, becomes active decision-making, and ends with reflection.
Why Racing Works
Racing gives educators a concrete way to talk about engineering without making the session feel abstract.
- Tradeoffs are visible: students can feel the difference between raw speed, clean control, and long-run efficiency.
- Feedback is immediate: a setup change shows up quickly in movement, score, collisions, timing, or player confidence.
- Roles make sense: software engineers, strategists, telemetry analysts, designers, and sustainability leads all have a believable place in the conversation.
- Iteration feels natural: test runs, shakedowns, pit stops, and changing conditions all support a build-test-improve rhythm.
Who It Is For
The experience is designed primarily for middle school learners, especially students who may be new to coding or still deciding whether technical work feels like it is for them. It also works well in mixed-age classrooms, workshops, and public activations where some participants are ready to jump in immediately and others need a clearer on-ramp.
Educators can use it in several formats:
- a 45-60 minute classroom session
- a shorter museum or event-floor demo
- a longer facilitated activation with more time for remixing and discussion
The Agenda page includes a full 90-minute version plus shorter-format guidance for 60-minute classroom delivery and 30-minute event-floor use.
What Makes the Project Classroom-Ready
- It runs in the browser and launches through a single skillmap link.
- It uses MakeCode Arcade conventions that are easy to open, explain, and remix.
- It keeps controls simple and feedback visible enough for projector use.
- It treats mistakes as useful information instead of hard failure.
- It gives facilitators specific moments to pause, compare outcomes, and connect gameplay to real work.