Story-driven prioritization game • offline • choices with consequences
You are a junior ICT-operations consultant on a busy day. You’ll receive tickets from schools and businesses. Your goal is not “max tickets closed” — it’s to deliver reliable outcomes within limited time. Core mechanics: • You have 480 minutes. Every action costs time. • Trust increases when you communicate clearly, verify fixes, and document honestly. • Integrity drops if you fake work, hide risks, or “close the ticket” without real troubleshooting. • Hands-on measures how much you actually troubleshoot / verify (not just talk). Moral: Be trustworthy and do real hands-on work — shortcuts often come back as bigger incidents. Teacher idea: Ask students to export their log at the end and write 8–10 lines of reflection: “What did you prioritize, what did you postpone, and how did trust/integrity change your result?”