Three waves, everyone together
Everyone starts and finishes each wave together. The organisers open each wave on this site.
| Wave | Story day | Time | What you build |
|---|---|---|---|
| 1My agent | Sunday 25/10/2026 | Pro 20 · Expert 30 min | Build an agent for your own desk, using your department's data. |
| 2Connect the company | Tuesday 27/10/2026 | Pro 20 · Expert 30 min | A Customer Recovery agent with colleague agents from six departments, answering the CEO's memo. |
| 3Show the customer | Thursday 29/10/2026 | Pro 20 · Expert 30 min | A customer briefing from a reusable skill you fix, plus a one-page visual for Expert. |
Pro or Expert?
Each wave has one checklist. Pro: tick only the Pro boxes (about 20 minutes). Expert: tick every box, Pro and Expert (about 30 minutes). You can choose a different level for each wave.
Two long texts are copied, not typed: the Wave 2 build card and the Wave 3 half-finished skill. They appear on the wave page when it opens.
Sign in to Gemini Enterprise · 5 minutes
- Use your login card only. Never use your own work account on a venue PC.
- Open the Hackathon app from the bookmark.
- Start a new chat and ask: Summarise CEO Memo 1 in three bullet points.
- Check the answer lists its sources underneath. Something missing? Raise your hand now.
How to build an agent
- Open Agents, click New agent, then Chat agent. The agent designer opens: a chat on the left, Preview on the right.
- Describe the agent in plain words in the designer chat: its name, its job, which data sources to use, what every answer must look like, and what it must never do.
- Wait for it to build (1–3 minutes). Open the Flow view to see the agent and any subagents.
- In Preview, open the connectors (puzzle) icon and switch Google Search off. Then ask your test question.
- Not right? Tell the designer chat one change at a time and test again.
- Click Create. To improve it later, open it again, describe the change and click Update. Keep using the same agent.
Tips
- Preview says required fields missing? Type "Fill in any missing fields" in the designer chat, then check Google Search is still off.
- No answer after 2 minutes? Start a new chat and ask again.
- Name things with your first name, for example Incident Detective – Sara, so your supervisor can find them.
- Skills (Wave 3) are saved instructions you run by typing / in a new chat.
How to ask Gemini for what you want
Talk to Gemini like a capable new assistant on their first day. It is fast, but it knows nothing about your job until you tell it. Good instructions say five things.
| Say | Why | Example |
|---|---|---|
| 1. Who it is | Gives it a role and a name | "Create an agent called Week Planner – Sara that helps Najma staff plan their week." |
| 2. Which data | Stops it guessing or using the web | "Use only the Company Intranet. Never use Google Search." |
| 3. The job | One clear task per agent | "When I ask what is due this week, find every deadline in the CEO's memos." |
| 4. The output | You get it in the shape you need | "Answer in one table: Date | Deadline | Department | Source document. Then one sentence." |
| 5. The rules | Keeps it honest | "Quote dates exactly as written. Never invent deadlines. If something is missing, say so." |
Make me an agent for my week.
It has to guess the data, the task and the format, and it will.
Create an agent called Week Planner – Sara. Use only the Company Intranet, never Google Search. When I ask what is due, list every deadline in a table: Date | Deadline | Department | Source document. Quote dates exactly; never invent them.
Habits that pass checklists
- Read your checklist first and put each box into your instructions as a rule or an output.
- Ask for record IDs (email, ticket, shipment, invoice, contract, employee) and spot-check one.
- Separate facts from explanations: ask it to mark what Najma's records confirm and what someone only claims.
- Need a total? Ask for the list of records first, then the count.
- Wrong answer? Fix the instructions, not the answer: tell the designer what to change, then test in a new chat.
Golden rules
- Start a new chat for each task. Long chats start inventing details.
- Switch Google Search off so answers come only from Najma's data.
- One change per message, and don't type while it is working. Answers take 1–4 minutes.
- Check the record IDs. Ask for them, then spot-check one.
- Fictional data only. Never type or upload real company, customer or personal information.
Privacy notice
This site records your first name, the participant code on your login card, the boxes you tick, the hints you open and the times you start and finish each wave, so organisers can support you and report the event. It does not read your Gemini agents or chats. Najma's data is fictional: never type or upload real information anywhere today.