⚖️ Judging Guide
Thank you for judging. For many of these students, this will be the first time they've pitched a tech idea in public. The job isn't to score perfection — it's to recognise the thinking, effort, and heart that got them to the stage.
This guide covers what to look for, how to give warm and useful feedback, and how to help every team leave the room feeling good about what they built.
🎯 Judging Purpose
- Focus on learning, effort, and potential impact — not polish.
- Judge the idea, the thinking, and the clarity — not technical perfection.
- Reward purpose, creativity, and understanding.
Most of these students have never written code before today. What they've done is taken a real-world problem, worked through it as a team, and built something with an AI tool in a few hours. That's a big deal.
🔍 What to Look For
Six criteria to weigh as you watch each pitch. They don't need to be scored formally — think of them as lenses.
1. Problem and Impact
- Is the issue clearly explained and meaningful?
- Do they explain who is affected and why it matters (ideally relevant to Aotearoa New Zealand)?
2. Solution
- Is the solution clear, logical, and relevant to the problem they described?
- Is it appropriate for the intended users?
3. Use of Kiro
- Can the team explain how and why Kiro is used, even at a basic level?
- Is Kiro used intentionally — not just mentioned in passing?
Understanding matters more than technical depth. A student who can say "we asked Kiro to add a form and fix this bug when it didn't save" has shown real use — they don't need to quote code.
4. Feasibility
- Is the idea realistic as a prototype or a next step?
- Do they acknowledge limitations or future improvements?
5. Creativity and Innovation
- Is the approach thoughtful, clever, or human-centred?
- Innovation can be a new combination of ideas, not entirely new tech.
6. Communication
- Is the pitch clear and structured?
- Are students confident explaining the idea in their own words?
- Is teamwork visible — do they all have a role in the pitch?
💬 Giving Positive, Constructive Feedback
Students will remember how your feedback felt long after they forget what was said. A simple recipe:
- Start with strengths — be specific about what landed.
- Use "next step" language, not criticism.
- Aim for 2 positives to 1 suggestion.
- Focus feedback on the idea, not the person.
- Ask curious, supportive questions — not "gotchas".
Phrases you can reuse
- "One strength that really stood out was…"
- "One next step you could explore is…"
- "Have you thought about how users would…?"
- "I'd love to hear more about why you chose…"
Examples
| ❌ Less helpful | ✅ More helpful |
|---|---|
| "Your app doesn't handle edge cases." | "One next step you could explore is what happens when someone enters no data — how might your app handle that?" |
| "The design needs work." | "Your idea is really clear. Have you thought about how the colours or layout could help Mere find the info faster?" |
| "You didn't really explain the tech." | "I'd love to hear more about how you got Kiro to add the map — that sounded like a great moment in your build." |
😊 Facial Expressions and Body Language
Students often read your face before they hear your words.
- Smile, nod, and keep friendly eye contact.
- Sit forward and look engaged.
- Avoid frowning, whispering, or reacting negatively during the pitch.
- If something confused you, save it for Q&A — and explain it kindly.
Other students about to pitch are watching how you react to the team on stage. A warm, engaged face helps everyone.
🤝 Supporting Student Confidence
Many students are pitching publicly for the first time. Small things go a long way.
- Be calm, warm, and encouraging.
- Thank every team genuinely — not as a ritual.
- Simple phrases help:
- "Well done for presenting."
- "Thank you for the effort you've put into this."
- "That was a clear and thoughtful idea."
🌟 Final Reminder
Students may forget their score — but they will remember how it felt to present to you.
Your encouragement matters. Kia ora for being here.