Design it. Get it approved. Build it. Make it work.

What the Week Looks Like

The STEAM Challenge runs through the same six-stage illuminate innovation process – structured across two distinct phases. Phase one is about designing a credible solution and earning the approval to build it. Phase two is about building it, running it, and presenting what actually happened.

Stage 1 – Foundations
Teams build their working agreement and the shared language that will carry them through a week that moves between design thinking and hands-on making. The Team MOU established here matters more in the STEAM Challenge than in almost any other program – because when the building gets difficult and the prototype is not behaving as intended, teams need a foundation to return to.

Stage 2 – Ideation
Teams identify a real problem worth solving – drawn from their school, their community or a broader challenge they genuinely care about – and begin generating possible solutions. The STEAM Challenge has produced technology solutions built from available materials, experiments designed around questions students have always wanted to answer, electrical innovations developed with limited equipment, and sustainable design responses to environmental problems students see every day. The diversity of what students tackle reflects the breadth of what STEAM genuinely encompasses – science and engineering sit alongside arts-led design thinking and mathematical modelling, and the strongest solutions draw on all of them.

Stage 3 – Developing
Phase one of the build. Teams develop their proposed solution into a testable prototype – working through the design process, identifying what they need, figuring out what they can achieve within the constraints of available resources, and producing something that represents their best current thinking. The prototype is then presented for approval to the facilitation panel – a structured process that requires teams to explain what problem they are solving, how their solution addresses it, what they will need to build it, and what success will look like. Approval is not automatic. Teams may be asked to refine, reconsider or rethink before they are given the green light to proceed.

Stage 4 – Presenting
Teams develop the communication materials that will accompany their solution – including the challenge of explaining their concept to a Year 3 student. This constraint is deliberate. The ability to communicate a complex technical or scientific idea simply and accessibly is one of the most underrated skills in STEAM fields – and the Year 3 brief forces teams to find language and visuals that genuinely work for a non-expert audience, which almost always sharpens their understanding of the concept itself.

Stage 5 – Prototyping
Phase two. With approval confirmed, teams build and run their solution – conducting the experiment, testing the technology, demonstrating the prototype or implementing the design within the agreed timeframe and resource constraints. This is the part of the STEAM Challenge that no other illuminate program replicates: the moment where the idea has to actually work, or where what does not work becomes the most valuable learning of the week. Teams document what happened, what they learned from it, and what they would do differently.

Stage 6 – Implementation
Teams present real findings – not proposals, not hypotheticals, but the actual results of what they designed and built. Implementation beyond the week is often where the most interesting outcomes emerge: students who pursue the experiment further, solutions that get adopted by the school, and ideas that attract genuine community interest.

Every student leaves with something they designed, built and ran – not something they planned to do.

The artefacts from the STEAM Challenge reflect the two-phase structure of the program. The first set of outputs are design documents – the thinking that earns approval to build. The second set are execution outputs – the evidence of what students actually made and what it produced. Together they tell the full story of an idea taken from concept to reality within a single week.

Throughout the Challenge, teams produce:

• Team MOU. Before the design begins, teams establish the working agreement that will govern how they operate across a week that moves between focused thinking and active making. The Team MOU is the anchor teams return to when the build gets difficult and decisions have to be made quickly.
• Problem Frame. Teams identify a specific, meaningful problem and develop a precise statement that defines what they are trying to solve and why it matters. In the STEAM Challenge, the problem frame anchors the design – everything built has to genuinely address what was identified here, which means the quality of the problem frame determines the quality of everything that follows.
• Ideation Process. Teams generate a range of possible solutions – evaluated for scientific feasibility, engineering viability, available resources and the realistic constraints of the week. Students move through the obvious options into territory where genuinely creative and technically considered responses live.
• Mentoring & Approval Presentation. Teams present their proposed solution to the facilitation panel – covering the problem, the proposed solution, the design rationale, the resources required, and what success will look like. Approval is earned, not given. Teams that receive feedback are expected to incorporate it before proceeding.
• Engagement Strategy and Materials. Teams produce a communication piece – written, visual or both – that explains their concept clearly enough for a Year 3 student to understand it. The constraint produces better communication than any open-ended marketing brief, because the feedback loop is immediate: if a ten-year-old cannot follow it, the explanation needs work. This sits alongside other engagement resources teams develop for their broader audience.
• Written Strategy. A structured overview of the proposed solution – covering the problem, the design, the build plan, the resource requirements and the expected outcomes. The project outline is the document that connects the design phase to the execution phase and ensures teams are building what they said they would build.
• Financial Budget and Running Costs. Teams develop a realistic budget for their solution – working within the actual constraints of what is available, what can be purchased with the small equipment budget, and what can be sourced from school resources. The budget is a forcing function: it makes teams decide what is essential and what needs to be rethought.
• Pitch for Support. Teams deliver a structured presentation of their full process – the problem, the design, the approval process, the build, and the results – to a panel that includes industry representatives and community members. The pitch in the STEAM Challenge is grounded in evidence rather than aspiration, which changes the quality of the conversation it generates.
• Pressure Cooker. Teams face a short, unannounced challenge that tests their adaptability when something they did not plan for arrives – which, in any real STEAM context, is a regular occurrence.

All artefacts sit alongside a range of other tasks guided by our facilitators across the program.

The capabilities schools, employers and communities are asking for – right now, not eventually.

illuminate’s skills framework was developed through consultation with industry partners and a review of current literature. It describes the capabilities young people need to be confident, creative and capable – relevant to school, to community, to industry and to life. It has been developed through consultation with industry partners, educational research, and alignment to the Australian Curriculum. As AI reshapes the workplace, these are the skills no algorithm replaces.

We are focused on building skills like…

These capabilities are woven through every single illuminate Education Australia program.