Half day
4 hours
- Single topic, deep
- Core artefacts
09:0013:0017:00
How to hire us
One day · one team · one concrete result · in-house
One day. One team.
One decision.
42ideas on the wall
A workshop day in six blocks, from forty-two ideas on the wall to one decision with an owner.
01 · Why it works
A day that ends
with decisions.
Most AI workshops are presentations with sticky notes. Ours end with a ranked list, an owner and a date.
What goes wrong with workshops
Too many people, no clear question, a keynote about the future of AI, and a wall of ideas that gets photographed and forgotten. Everyone leaves inspired and nothing changes on Monday.
How ours run
One team, one topic, one question worth answering. We open with context and ground rules, collect ideas fast, evaluate them against the same criteria, design the most promising ones in enough detail to judge them, and then decide. Before anyone leaves, every decision has an owner and a next step.
What you take home
Depending on the topic: a ranked use-case list with the criteria behind it, workflow diagrams and tool requirements, a data readiness inventory, a policy draft and risk register, or a working prototype with an iteration plan. Always a written summary of decisions and actions.
Everyone leaves with a task.
- Formats
- Half day, full day, series
- Where
- In-house, with one team
- You leave with
- Decisions, owners, artefacts
02 · The day
Six blocks.
One question.
A full day, drawn to scale. The arc is the same for every topic: open, collect, judge, design, decide, hand over.
- 09:00–09:30Opening
The question, the criteria and the ground rules. Who decides what by the end of the day.
- On the wall after
- One question, four criteria
- 09:30–11:00Discovery
Everyone puts ideas on the wall. Fast and unfiltered, one idea per card.
- On the wall after
- Every idea, on a card
- 11:00–13:00Analysis
Each idea scored against the same criteria: impact, feasibility, data and risk. Clusters form.
- On the wall after
- A ranked list
- 13:00–15:00Design
The top candidates drawn as workflows, in enough detail to judge effort and risk.
- On the wall after
- Two or three workflows
- 15:00–16:30Decisions
Choices locked in: what starts, what waits, what is dropped, and why.
- On the wall after
- One pilot, one owner
- 16:30–17:00Wrap-up
Owners, dates and next steps, read back to the room.
- On the wall after
- An action list
The morning after
What lands
in your inbox.
A summary document, a prioritised action list, draft architecture artefacts and the open questions we flagged. A recording, if you want one.
- From
- Voidgap
- To
- Workshop team
- Subject
- Decisions, owners, next steps
Thanks for yesterday. Attached: what we decided, who owns what, and the questions we still have to answer before the pilot starts.
- pdfdecision-summary.pdfSummary document
- xlsxaction-list.xlsxPrioritised actions, with owners
- pdfworkflow-drafts.pdfDraft architecture artefacts
- mdopen-questions.mdFlagged follow-up items
- mp4recording.mp4Optional recording
03 · Topics
Five workshops.
One way to run them.
Pick the question you need answered. The day runs the same way each time; the artefacts change with the topic.
Use case discovery
Half or full dayGood whenEveryone has ideas. Nobody has a shortlist.
You leave with
- Ranked use-case list
- Selection criteria
- First project scope
Ask about this workshop plus summary and action list
04 · Formats
Half a day,
a day, or three.
Size it by the question. One clear question fits into four hours. Several connected ones need a full day, or a series with work in between.
Full day
8 hours most popular
- Several connected topics
- Complete artefact set
09:0013:0017:00
Workshop series
3 sessions · 2–4 weeks
- Progressive depth
- Work between sessions
session 1session 2session 3 · week 4
05 · Self-check
Which workshop
fits?
Four questions, one recommended format. Change an answer and the result follows.
result0 / 4 answered
- Half day.
One topic, one question, the core artefacts.
- Full day.
Several connected topics and the complete artefact set.
- Workshop series.
Three sessions over two to four weeks, with work in between.
01How clear is the question?
The clearer it is, the less time the opening needs.
02How many topics are on the table?
03How much should be built?
04How much time does the team have?
06 · Fit
Book it if.
Skip it if.
A workshop is for deciding. If you need something else, we will point you to it.
A good fit
- Your team needs to align on AI opportunities, quickly.
- You want concrete outputs, not just inspiration.
- You are launching an AI initiative and need a first decision.
Look elsewhere
- You want general AI education for many people. That is AI Trainings.
- You already know what to build and need hands-on help. That is Implementation.
- A live system is broken and costing money. That is Consulting.
07 · Questions
Before
you book.
Who should be in the room?
One team that owns the question, plus the person who can make the decision. A mixed audience without a shared question produces ideas, not decisions.
What do we get afterwards?
A summary document, a prioritised action list, draft architecture artefacts and the follow-up items we flagged during the day. If you want it, a recording.
Where does it take place?
In-house, at your offices, with your team. The people who run the process are in the room, and so are the systems we talk about.
How do we choose the topic?
Start from the question you need answered. If it is “what first”, that is use case discovery. If you already know the process, agent workflow design. If nobody knows whether the data exists, data readiness. The self-check above sizes the format.
What happens after the workshop?
The owners start on their next steps. When the next step is building, that is Implementation. When a live system needs fixing first, that is Consulting.
08 · How to hire us
Three ways in.
Pick by where you are: deciding, stuck with a live system, or ready to build.
01 / 03you are hereWorkshop
02 / 03ConsultingHalf or full day. Ends with decisions, owners and next steps.
When you need to decide
Retainer, fix-it sprints, embedded help. For systems that are live and hurting.
When a live system hurts
Two- to eight-week builds. From validated idea to real users.
When you are ready to build
What should your team decide next?
Book
the day.
Send us the question your team needs answered. We come back with a format and an agenda.