GAILE has been set up to be the connective tissue. We want to meet these initiatives wherever they sit, from "I made something cool on the weekend" through to "I think AI can solve a problem here" and usher them into a shared, collaborative methodology. We have the expertise to ground innovations in pedagogy. We are building the infrastructure to connect people who are unknowingly solving the same problems in parallel. And we won't compromise on ethical and responsible AI use.
Here's how a pilot plays out through GAILE's five-stage methodology for AI/Edu experiments:
1. Consult
An idea surfaces, from the community or GAILE. This stage is about intuitive sense-checking and human conversation. We'll coach you on how to safely experiment locally, surface pre-existing tools and capabilities you may not know about, and work toward a shared understanding of the best path forward. There may already be other people piloting something similar. AI can't solve everything, and we probably wouldn't want it to. The output here is a recommendation: is this worth pursuing, and if so, how?
2. Discovery and framing
When there's genuine appetite, we co-create a pilot brief. The goals are to de-risk the project early and synthesise a plan. We address the riskiest assumptions up front: Is this even possible with today's technology? Do enough willing participants exist? Can we conceive of a realistic solution within RMIT right now? Is this aligned to RMIT’s strategic ambition and your own local context.
If this stage is successful, we have a proposal, and we begin working with learning and teaching leaders across the university to engage the right participants and bring them on board.
3. Design and plan
Now we get specific. What are we building, and how will we know if it works? We plan the experiment in enough detail to move confidently, without over-engineering it. If there's a tool or interface involved, we design it with the people who'll use it. We also figure out what we're measuring and how we'll ask for consent. The output: designs, a plan, and a clear methodology.
4. Execute and build
This is where the idea becomes real. We run the pilot, support the people involved, collect data, and iterate. Things will break, things will surprise us, and that's the point. The output: results, and a working version of the thing that's been shaped by actual use.
5. Communicate and archive
This is where the lab earns its name. Whatever was learned or produced gets documented with provenance, positive findings, negative findings, things that surprised us. The experiment should be repeatable and should survive the current team (as much as possible in this fast moving space) The output: defensible insights, a complete package of everything collected and produced, and a recommendation for what comes next.