• Clear articulation of the problem or opportunity
• Relevance to company strategy, customer experience, or operations
• Potential impact if scaled (revenue, cost, efficiency, risk reduction, guest value)

Are we solving the right problem in a meaningful way? Strong problem framing and insight matter as much as code.

• Clarity of user journey and interaction
• Intuitive design and ease of use
• Evidence of user thinking (personas, workflows, pain points addressed)

Would someone actually use this? Rewards focus on adoption, not just functionality.

• Demonstrates the core idea end-to-end
• Works well enough to show intent (even if mocked or AI-assisted)
• Appropriate use of tools (code, no-code, APIs, AI, etc.)

Is this more than a concept? Judges assess fitness for purpose, not technical depth.

• Novel application of existing tools or ideas
• Creative combination of technology, data, or processes
• Fresh perspective on a known problem

Are we pushing beyond the obvious? Simple tools used creatively are not penalized.

• Clear next steps to pilot or test
• Awareness of constraints (data, compliance, integration, change management)
• Thoughtful assumptions—not hand-waving

Could this realistically move forward? Encourages pragmatic thinking without requiring deep engineering detail.

• Clear, compelling pitch
• Logical narrative from problem - solution - impact
• Reflection on what worked, what didn’t, and what was learned

Can the team communicate value and reflect? Gives credit for learning velocity, not just finished output.