Innovation Day - One-Pager
Print it, pin it, forward it. Everything you need to show up ready.
What today is
A hands-on day to use AI on real work, the right way. Two sessions run side by side; each runs twice (morning and afternoon). You do one session and leave with something you’ll actually use - not a slide deck.
The whole day in one line: AI doesn’t change the standards - it changes how fast we hit them.
The two sessions
| Build a Skill | Spec-First Build | |
|---|---|---|
| For | Programme / ops / admin / HR / procurement / finance - no coding needed | A full product team: Dev, Architecture, QA, Product, UI/UX |
| You’ll do | Turn a real weekly task into a one-page AI “Skill” anyone can reuse | Ship a feature spec-first against a real API contract |
| You leave with | A reusable recipe for your team’s shared drive | A feature built the way our standards say to build it |
| Tools | Any chatbot you already have | Your AI assistant + the workshop repo |
| Length | 2 hours | 2 hours |
How to pick
- You run programmes, ops, admin, HR, procurement, or finance and want AI to save you real hours? → Build a Skill.
- You build software? → Spec-First Build.
- Not sure / nervous? → Build a Skill. It assumes nothing. You’ll leave with a tool you use next Monday.
What to bring
- A laptop you can use freely.
- An AI chatbot you can sign into - ChatGPT, Gemini, or Claude, whichever you already have. This is the one prerequisite.
- No tool of your own? Don’t worry - a no-login browser option will be available on the day (tool: TBC). Tell registration in advance so we have a seat for you.
- One real, boring task you’d love to never do by hand again (Build a Skill folks - bring it in your head, we’ll build for it).
- Curiosity over confidence. Mixed-confidence rooms are the point.
One rule before you paste anything: treat every prompt like a public postcard. Bring synthetic or anonymised data only - no client names, no PII, no confidential figures. We’ll show you how. (That’s Way #3, below.)
The 5 ways we work with AI
The whole day runs on these five. Punchy version here; the full version with examples and the standards behind each one lives in ways-of-working.md.
- Describe before you generate. Say what “good” looks like before you ask. A clear spec beats a clever prompt.
- A human always signs the work. AI drafts; a person reviews and owns it. Nothing ships unread.
- Mind what you feed it. Public postcard, not sealed envelope. Anonymise first - when in doubt, leave it out.
- Small steps, not big leaps. One change at a time - easy to check, easy to undo.
- Keep it simple, write down the why. The simplest thing that works, plus a note on why you chose it.
Grab the print-ready take-away card:
assets/ways-of-working-card.md.
Where, when, who
| Date | TBC |
| Morning slot | TBC (door check ~30 min before) |
| Afternoon slot | TBC (identical agenda) |
| Rooms | Build a Skill → TBC · Spec-First Build → TBC (incl. Madrid) |
| Sign up | TBC - pick your session and flag your AI-tool readiness |
| Questions | Facilitators: TBC |
See you there. Bring the boring task - leave with the fix.