Run of show
The day, session by session
For the workshop team: the schedule, what to say in each session, who's where, and what to print, all on one page.
- Everyone reads the five rules.
- Read the schedule. Moderators read the full scripts for sessions 1–3.
- Check your name in Who's where, and on the morning go through the checklist.
- Print the materials (the Print button prints everything, including every script).
00Five rules for everyone
- We're here to learn, not to be right. Never explain or defend the product. Say "Tell me more."
- Don't lead. Ask "What do you think it does?", not "This button does…". Never mention a vision, or who designed what.
- Stuck for 2 minutes? Ask "What would you do if I weren't here?" After 4 minutes, give the smallest possible hint and log it as an
ASSIST. - Behaviour beats opinion. Write down what people do (hesitations, wrong clicks, a smile) and their exact words.
- Silence is fine. Count to seven before you fill it. If one person dominates, say "Let's hear from someone who hasn't spoken yet."
Phrases to swap optional
| Instead of | Say |
|---|---|
| "Do you like it?" | "What's going through your mind right now?" |
| "Would you use this?" | "When did you last need something like this? What did you do?" |
| "Great idea!" | "What problem would that solve for you?" |
| "Actually, the idea is…" | "Tell me more about that." |
01Schedule
Each row has the plan for that session. Open "Full script" when you're preparing or running it. Moderators run sessions 1–3; Jeet takes the kickoff, sessions 4–5 and the close.
| Time | Session | What happens | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 08:30 | Team setup All rooms | Screens, Wi-Fi, staging logins, Scribe test, materials laid out. Huddle at 09:15. | |||||||||||||||||||||||||||||||||||
| 09:30 | Arrival & breakfast Main | Badges show first name, participant ID and breakout colour. The idea wall is open all day. | |||||||||||||||||||||||||||||||||||
| 10:00 | Kickoff · 15 min Main · Jeet |
Full scriptKickoff 1. WELCOME (2 min)
"Thanks for giving us a day. You do the actual work at Crypto.com, and ai.com is meant to help with exactly that. Today we're building it with you, not presenting it to you."
2. WHAT YOU TOLD US (6 min)
Three slides from the sign-up questionnaire: the AI tools people use and how comfortable they are, the biggest time drains (anonymous quotes), and what people would hand to an AI agent first and what it should never do.
3. THE RULES (4 min)
• Harsh feedback is the most useful kind. You can't break anything.
• There are no wrong answers. If something's confusing, that's on us.
• The idea wall is open all day.
• Notes use your participant ID, never your name. Some sessions are recorded for our notes only.
4. THE DAY (3 min)
Morning: try things. Afternoon: create. Your breakout colour is on your badge. Lunch is at 13:00.
DON'T: pitch a vision, show a roadmap, or say who designed what. | |||||||||||||||||||||||||||||||||||
| 10:15 | 1 · First time on ai.com · 45 min Test Breakouts · moderator |
Full script observer + B/C instructionsObserver script: Group A INTRO (3 min)
"We're testing ai.com, not you. Please think out loud: what you see, what you expect, what you're unsure about. I'll mostly stay quiet, even when you ask me things. That's on purpose."
GOALS (about 35 min). One at a time. Move on when a goal's done or after about 7 minutes.
1. "Here's the link. Sign in and look around. What do you think this is for?"
2. "Get it set up so it could help with your work."
3. "Ask it something about your work." (Their data will be thin. Note what they expected.)
4. "Send a message to someone in this room."
5. "Find one thing you'd come back for tomorrow."
AFTER (7 min)
1. "In a word or two, how was that?"
2. "Best moment? Worst?"
3. "What do you think ai.com is for, now?"
4. "What would make you open it tomorrow morning?"
Log each ▲ ▼ ? and each ASSIST as its own row, with session = s1-first-use. Groups B and C (printed on their sheet) While your colleagues try ai.com for the first time, work quietly on your own. Please don't watch or help them.
PART 1 (about 20 minutes): fill in the "My week with ai.com" map
• Draw how you've felt about it, from your first time to now
• Mark the most useful moment and the most annoying one
• Finish "I wish it…" three times
• If you stopped using it: what made you stop?
PART 2 (until 11:00): ask ai.com about your work
• On your own account, ask real questions about your work, the kind you'd normally ask a colleague
• Rate every answer on the answer sheet, and keep going in session 2
• If you get stuck or it breaks, write down what happened. Don't ask the Group A table. | |||||||||||||||||||||||||||||||||||
| 11:00 | 2 · Ask about your work · 45 min Test Breakouts · moderator |
Full scriptModerator script INTRO (2 min)
"Ask ai.com real questions about your work, the kind you'd normally ask a colleague. Rate every answer on the sheet. If you're pairing, the laptop owner types and you decide together."
Groups B and C: keep going on the sheet you started. If you're pairing with a Group A colleague, switch to their sheet so the questions are theirs.
ASK (30 min). At least 5 questions each:
1–2. Anything you like
3. One from the question list on your table (built from the survey)
4. One you'd normally ask a colleague
5. One about something that happened last week
Walk the room. When someone reacts ("wait…"), ask "What just happened?"
DISCUSS (10 min)
1. "Show us your best answer, and your worst."
2. "What made an answer useful, or useless?"
3. "What would you ask it every day?" (Write these down word for word.)
Collect the rating sheets, including the questions B and C asked in session 1. Session = s2-ask. | |||||||||||||||||||||||||||||||||||
| 11:45 | Break · 10 min | ||||||||||||||||||||||||||||||||||||
| 11:55 | 3 · Two concepts → Concept 3 · 65 min Both Breakouts · moderator |
Setting up the two concepts. Use the same theme (light) for both. Hide anything that isn't part of the product: the prototype toolbar on Concept 1, and the development error badge in the corner of Concept 2. Concept 2 runs as a local web app, so start it on the room laptop before the session. Full scriptModerator script INTRO (2 min)
"These are two early, very different ideas for how ai.com could look. They're clickable pictures, not finished products, and neither is 'ours'. Take the best of both, then design your own."
EACH CONCEPT (20 min, then repeat for the other)
a. 5-second test (3 min): show the home screen for 5 seconds, then hide it. Everyone writes: "What do you remember? What is it for?"
b. Explore in pairs (12 min):
• "Where would you start your day?"
• "Find the most important thing waiting for you today."
• "Send a message to a teammate, or to a team room."
• "Ask the AI to help you with something."
• "What on this screen would you never use?"
c. On your own: fill in KEEP · CUT · STEAL on the sheet (5 min)
CONCEPT 3 (23 min)
"Now it's yours. Design the home screen you'd want to open every morning. Steal from either concept, add anything. Stick figures are fine."
• Sketch on your own (4 min)
• Share (6 min)
• One group sketch on the A3 sheet (12 min)
• Pick someone to pitch it this afternoon (1 min)
Photograph the A3 sheet and collect the K/C/S sheets. Session = s3-concepts, concept = 1 or 2. | |||||||||||||||||||||||||||||||||||
| 13:00 | Lunch · 50 min. Team huddle at 13:05 (10 min): anything to change for the afternoon? | ||||||||||||||||||||||||||||||||||||
| 13:50 | 4 · Your work, reimagined · 50 min Create Main, 4 mixed tables of 5 · Jeet |
Full scriptFacilitator script PROMPTS: write these from the sign-up questionnaire's top time drains and lost-information themes. Examples of the form:
• "How might we never chase people for the same information twice?"
• "How might we find out why something is the way it is, without knowing who to ask?"
ROUND 1 (30 min)
• Alone, in silence (5 min): "As many ideas as you can, one per sticky note. Wild is fine, and so is small."
• Pairs, or one trio (10 min): "Share, build on each other's, pick your best two."
• Table (15 min): "Pick the top two. Write each on an idea card: the problem, the idea, who it helps, what today's tools fail at."
ROUND 2 (15 min): swap prompts with the next table
• Alone (4 min), then the table (11 min): add one more idea card.
READ ALOUD: Ideas don't have to be AI, or ai.com. Build on ideas instead of shooting them down.
The idea cards go straight into session 5. Note-takers: capture the story behind each idea ("because last month…"). Session = s4-ideas. | |||||||||||||||||||||||||||||||||||
| 14:40 | Break · 10 min | ||||||||||||||||||||||||||||||||||||
| 14:50 | 5 · Futures & vote · 55 min Create Main, same tables · Jeet |
Full script + scenario orderFacilitator script SETUP: each table gets an envelope with the six scenario cards in its order, the 12 capability cards, 2 blank cards, its own idea cards, and 10 tokens per person.
FUTURES (15 min)
"Six short stories about a normal Tuesday for different people at Crypto.com. Whatever your own role, ask yourself: would I want something like this in my work? Read each one on your own. Tick 'I want this tomorrow', 'Maybe' or 'No', and finish the 'because…'."
• Silent (10 min), then the table (5 min): "Which would you fight for? Which would you refuse?"
• Don't explain the scenarios or say where they came from. If asked: "What would you want it to mean?"
TOKENS (15 min)
"Twelve things a work tool could do, plus your own ideas, plus blanks for anything missing. You have 10 tokens each. Put them on what would make the biggest difference to your work. Think silently for 2 minutes first."
• Then (3 min): "Why did the biggest pile get so big?"
• NOTE-TAKERS: photograph every table before anything moves.
PITCHES (10 min)
• Red and Blue each pitch their Concept 3 (3 min each)
• Each table pitches its top idea card (1 min each)
Everything pitched goes up on the wall.
DOT VOTE (10 min)
"Three dots each. Put them on whatever on the wall you most want us to build, including the idea wall. At most one dot on your own work."
Photograph the wall afterwards. Session = s5-futures. Scenario order per table
No scenario always comes first. The letters don't mean anything. The roles are spread across functions so nobody feels the day is only for engineers. Before the Fri 2 Oct run-through, Jeet and Aaron check that none reads as more polished, or as more "ours", than the others. | |||||||||||||||||||||||||||||||||||
| 15:45 | Close · 15 min Main · Jeet |
| |||||||||||||||||||||||||||||||||||
| 16:00 | Team debrief · 30 min Main · Jeet | Top 3 from each of us, bug triage, check everything's collected. Agenda: Capture & readout. | |||||||||||||||||||||||||||||||||||
02Who's where
| Red breakout | Blue breakout | |
|---|---|---|
| Participants Red: 2 Fresh · 3 Early-setup · 5 Alpha Blue: 3 Fresh · 2 Early-setup · 5 Alpha | [Fresh User #1] [Fresh User #2] [Early-setup User #1] [Early-setup User #2] [Early-setup User #3] [Alpha User #1] [Alpha User #2] [Alpha User #3] [Alpha User #4] [Alpha User #5] | [Fresh User #3] [Fresh User #4] [Fresh User #5] [Early-setup User #4] [Early-setup User #5] [Alpha User #6] [Alpha User #7] [Alpha User #8] [Alpha User #9] [Alpha User #10] |
| Moderator | Sunny | Engineer 1 |
| Note-taker (+ Scribe) | Engineer 2 | Engineer 3 |
| Session 1 observers 1 per Fresh User | Sunny → #1 Engineer 2 → #2 | Engineer 1 → #3 Engineer 3 → #4 Jeet → #5 |
| Session 3: concept shown first | Concept 1 | Concept 2 |
Placeholders only: real names go in the private roster, never on this page. In the room, the concepts are only ever called "Concept 1" and "Concept 2". Jeet sits in Blue, so they aren't in the room when their own concept goes first. Afternoon sessions are in the main room, with both note-takers circulating. Jeet keeps time and moves between rooms. An AI Eng contact is on call in the team chat for staging problems.
03Morning-of checklist
- A test login to staging works on the guest Wi-Fi
- Group B and C accounts show their data (also checked Fri 2 Oct)
- Group A accounts exist but have never been opened
- Both concepts open on each breakout screen, in light theme, with prototype toolbars and error badges hidden. Concept 2 needs its local app running.
- Scribe test recording made in both breakout rooms
- The notes sheet opens and everyone can edit it
- Badges match the roster
- Survey slides are loaded and the exit survey QR works
Printing & supplies by Fri 2 Oct
- First-use goals card ×5 · journey map ×15
- Answer sheet ×25 · keep/cut/steal sheet ×25
- Concept 3 template ×2 (A3) · idea cards ×100
- Scenario cards ×4 sets (one per table, in its order)
- Capability cards ×4 sets
- Tokens (e.g. poker chips) ×250 · dot stickers ×80
- Sticky notes, sharpies, badges in 2 colours, a visible timer
Every sheet is in Printable materials below.
04If things go wrong
| Staging is down | Session 1: Group A tries the concept prototypes instead. Session 2 becomes paper: "Write the 5 questions you'd ask it, and what a great answer looks like." Move session 3 earlier. |
| An account has no data | They pair with a teammate who has data. Note it as a first-run finding. |
| No-shows | Rebalance at 09:45. Each breakout needs at least one Group A. |
| Trust or privacy concerns | Acknowledge it, note it (type trust), and say "we'll take that to the AI team". Don't debate it. |
Running late? Cut in this order: (1) table idea pitches in session 5, (2) "What didn't we ask?" (move it into the exit survey), (3) the "what would you ask it every day?" discussion in session 2. Never cut session 1, the silent-writing steps, or the photos of the token tables.
05Printable materials
Click a sheet to preview it. The Print button prints all of them, one per page. Quantities are in the checklist.
First-use goals card Session 1 · observers · ×5
First-use goals card · Session 1
- "Here's the link. Sign in and look around. What do you think this is for?"
- "Get it set up so it could help with your work."
- "Ask it something about your work."
- "Send a message to someone in this room."
- "Find one thing you'd come back for tomorrow."
Feeling timeline: ▲ delight · ▼ frustration · ? confusion · A = assist
My week with ai.com Session 1 · Groups B and C · ×15
My week with ai.com · Session 1
Participant ID: ________ · Draw a line showing how you've felt, from the first time you opened it (left) to today (right).
😐
😣 awful
Answer rating sheet Sessions 1–2 · ×25
Answer rating sheet · Session 2
Participant ID: ________ · Pairing with (ID): ________
| # | Your question (word for word) | Useful? Y / Partly / N | Correct? Y / N / Can't tell | Showed source? Y / N | Surprising? Y / N |
|---|---|---|---|---|---|
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 | |||||
| 6 |
Keep · Cut · Steal Session 3 · ×25
Keep · Cut · Steal · Session 3
Participant ID: ________ · Breakout: ________
| Concept 1 | Concept 2 | |
|---|---|---|
| 5-second test: what do you remember? What is it for? | ||
| KEEP: what works for you | ||
| CUT: what you'd never use, or found confusing | ||
| STEAL: what you'd take into any design |
Concept 3 template Session 3 · A3 · ×2
Concept 3: our home screen · Session 3
Breakout: ________ · "The screen we'd want to open every morning."
Idea cards Idea wall + session 4 · 4 per page · ×100
Idea cards
THE PROBLEM
THE IDEA
WHO IT HELPS
WHAT TODAY'S TOOLS FAIL AT
THE PROBLEM
THE IDEA
WHO IT HELPS
WHAT TODAY'S TOOLS FAIL AT
THE PROBLEM
THE IDEA
WHO IT HELPS
WHAT TODAY'S TOOLS FAIL AT
THE PROBLEM
THE IDEA
WHO IT HELPS
WHAT TODAY'S TOOLS FAIL AT
Future scenarios Session 5 · 1 set per table · ×4
Each card is a different Crypto.com role, with the same structure and roughly the same length. Participants rate them for their own work, not the role on the card. Stack each set in its table's order. Participant ID: ________
It's Tuesday. You're a compliance analyst at Crypto.com, and the monthly compliance report is due Friday. You tell ai.com: "Pull this month's figures, chase the three teams that haven't sent their sections, and draft the report." Through the day it sends the reminders, collects what comes in, and puts a draft in front of you. Nothing goes out until you approve it.
Because… _______________________________________________
It's Tuesday. You're a mobile developer at Crypto.com, wondering why the app asks for an extra confirmation before some withdrawals. Nobody ever wrote down why. You ask ai.com. It explains the reason, drawing on a discussion from last year and a meeting from before you joined, shows you where each part came from, and tells you who knows the most about it.
Because… _______________________________________________
It's Tuesday. You're a product manager at Crypto.com, launching a feature that needs four teams. There's no weekly status meeting any more. Everyone's progress shows up on its own, taken from the work people are already doing. When someone asks where the launch stands, they can see it without asking you, and you can see theirs. The hour you spent in that meeting is yours again.
Because… _______________________________________________
It's Tuesday morning. You're a data engineer at Crypto.com. Overnight, another team changed the format of the trading data your pipelines read. Before you start your day, ai.com tells you what changed, which of your jobs and dashboards it affects, and who made the change. You didn't have to go looking, and you didn't find out when a report broke.
Because… _______________________________________________
It's Tuesday. You're a customer support lead at Crypto.com, and your team is tired of tracking recurring complaints in a spreadsheet. You describe what you need to ai.com in a few sentences. Ten minutes later your team has a small working tool: a shared list, an alert when a problem starts spiking, and a weekly summary. When you want it changed, you just ask.
Because… _______________________________________________
It's Tuesday. You're a product designer at Crypto.com, back after two weeks away, or starting on a new project. Instead of scrolling through hundreds of messages and design comments, you ask ai.com to catch you up. In five minutes you know what happened, what was decided and why, what's waiting for your review, and who to talk to first.
Because… _______________________________________________
After reading all six
Capability cards Session 5 · 1 set per table · ×4
What a work tool could do, in plain language, including things ai.com doesn't do yet. Shuffle them on the table.
Direct messages and team rooms, in the same place as the AI.
Voice and video calls with automatic notes and follow-ups.
Answers from your team's messages, docs and meetings, with the source.
What changed, what needs you, and what's coming up today.
Slack, Jira, Confluence, Calendar and others, visible from one place.
One search across every tool and conversation.
It drafts, chases, updates and files. You approve before anything goes out.
Set up a workflow once, and it runs every week without you.
A tracker, dashboard or form, made in minutes without code.
Before each meeting: what it's about, what happened last time, what's open.
Find the right person for any question, even outside your team.
What the team is working on, has decided, and is waiting for.
Workshop kit · Overview · Participants · · Capture & readout