Use-Case Discovery Workshops
The best AI ideas are already in the building.
A working session that pulls the real opportunities out of your team's heads, scores each one on the same axes, and ranks them, so you leave with a shortlist your people believe in and a clear place to start.
The wall
47 cards · one morning
“Every Friday I rebuild the same report from four exports.”
“We answer the same eight questions all day long.”
“I re-type invoice numbers into the system by hand.”
“It would be cool if the website had a chatbot.”
Six of the forty-seven made the shortlist. The rest stay on the wall with the reason they didn't.
½–1 day
In the room
Scored
Not brainstormed
Quick wins
Flagged to start
Owned
By the people in it
The brief
Your team knows where the friction is, better than any consultant
A vendor can tell you what AI does in general. Only your people know which fifteen minutes of their day is soul-destroying, which report eats a Friday afternoon, which question gets asked a hundred times a week.
The workshop turns that lived knowledge into a scored, ranked set of opportunities. And because they built it, they back it, which is what decides whether anything actually gets done with it.
We bring the AI literacy and the structure. You bring the business.
What the session is for
Your team's knowledge, on the wall
The best AI use cases are already in your people's heads. Nobody outside the building knows which fifteen minutes of the day is soul-destroying, and the session exists to get that said out loud and written down.
Scored, not just collected
Every card is rated on the same axes, so what you leave with is a ranking instead of a wish-list. A wall of ideas nobody ordered is just a wall.
A backlog they'll actually run
Because the team built it, they back it. A shortlist handed down from outside gets nodded at in the room and quietly ignored by March.
What the session does
Four moves, in this order for a reason
Surface the pain
We map where time, money, and patience leak today. No AI ideas yet, just the friction, in the words of the people who live with it.
Generate use cases
Structured ideation turns those pains into concrete, AI-shaped opportunities. This is where we bring the literacy: you know the problem, we know what's buildable.
Score and rank
Every idea is rated on impact, effort, feasibility, and confidence, scored privately first and then argued out loud with the numbers already on the table.
Shape the front-runners
The top picks get fleshed out into something ready to scope: what it touches, what data it needs, and what it would take to build.
The running order
One day, and the first hour has no AI in it
Where does it leak?
No AI talk at all for the first hour. We map the friction first, because a room that starts with the technology finds problems to fit it.
What could take this?
Each pain gets turned over for the AI-shaped opportunity inside it, and for the ones where the honest answer is a spreadsheet or a process fix.
Score in silence, then argue
Everyone scores privately before anyone speaks. This is the whole trick: score out loud and the room anchors on whoever went first, or whoever is most senior.
Shape the top three
The front-runners get written into one-page briefs while the people who raised them are still in the room to correct us.
Around the day
The session is the visible part
Prep
We learn enough about your business beforehand that the session isn't spent explaining it to us. The room's time is the expensive part.
The session
A half or full day, facilitated, with the running order above and the scoring done in the room instead of promised afterward.
Synthesis
We do the writing-up, so you don't have to. The cards, the scores, and the briefs get turned into a document within a few days, while it's all still warm.
Handover
A walkthrough of the shortlist with whoever needs to approve it, and a recommended first project you could scope next week.
How we score
Four axes, and everyone scores before anyone speaks
Every card is rated on the same four questions, so the shortlist reflects value and feasibility instead of who spoke last. That's what makes a ranking the room will still stand behind a month later.
Impact
If this works, how big is the outcome?Measured against the pain it came from (hours back, errors avoided, revenue moved) instead of how interesting it is to build.
Effort
What does it cost to get there?The build, the data work, and the change management. The last of those is the one rooms consistently score too kindly.
Feasibility
Can your stack support it today?Grounded by the systems owner in the room, so nothing scores well on a capability you don't actually have.
Confidence
How sure are we about the other three?The honest one. A high score held with low confidence is a research task, and it isn't ready to be a project.
What the room changes
What a facilitated day actually buys
The loudest idea stops winning
Private scoring before discussion means the ranking reflects value and feasibility instead of seniority or who spoke last. That's what makes it something the room trusts afterward.
The quiet people get heard
The person who actually does the work five days a week is rarely the person who talks most in a workshop. Facilitation is mostly the job of fixing that.
The bad ideas die in a day
Better on the wall in the morning than in a build six months later. Cards go back with a reason attached, so nobody re-raises them next quarter.
You leave with a decision as well as the energy
Workshops that end in good vibes and photographs of sticky notes are the ones nothing comes from. This one ends with a ranked list and a first move.
Selected work
When the loudest ask wasn't the real one
What comes off the wall
A shortlist you can act on
No photographs of sticky notes. A ranked, scored set of use cases with briefs on the front-runners and a recommended first move, written up by us within days while it's still warm.
- 01A ranked shortlist of AI use cases, scored on the same axes
- 02The impact and effort read on every idea raised, as well as the winners
- 03The quick wins flagged as the place to start
- 04A one-page brief on each front-runner
- 05The data and dependencies each one needs
- 06A recommended first project, ready to scope
Rooms we have run
Every wall fills up differently
Operations-heavy businesses
The wall fills fastest here. Repetitive, rule-based work is where the room has the most to say and the least of it has been written down.
Professional services
Usually document and drafting pain, and usually raised by the juniors doing it instead of the partners commissioning the session.
Software companies
The opposite problem: plenty of feasible ideas and no shared way to rank them, so the session is mostly about the scoring.
Field and logistics teams
The friction is out in the vans and the warehouses, which is why those people have to be in the room, and usually aren't.
Who to bring
The people who feel the pain
Frontline and ops people know exactly where the friction is. If they aren't in the room, the wall fills up with management's guesses about their jobs.
Someone who can say yes
A decision-maker, so the priorities set in the room still mean something on Monday instead of needing to be relitigated upward.
A data or systems owner
So feasibility is grounded in what your stack can actually do today, and nothing scores well on a capability that doesn't exist.
Half a day
Get the right people in one room and find out what they already know.
You bring the business. We bring the structure, and the marker pens.
Choosing Flaidex for this
Facilitation is the product
We facilitate, we do not present
You aren't buying a deck about what AI can do in general. The room does the work; our job is the structure that lets it, and the AI literacy to name what's buildable.
The scoring is private first
Everyone rates before anyone speaks. It's a small mechanic that decides whether you get the room's real opinion or an echo of the first confident voice.
Not yet is a result
Every business has work worth examining, but if the honest read is that none of it is worth building this year, you learn that in a day instead of after a pilot.
We write it up, you do not
The synthesis is ours. Sessions where the client leaves holding the sticky notes are sessions that quietly produce nothing.
Working with us
What the engagement itself is like
Half a day or a full day
Depending on how many teams and use cases are in scope. The prep and the synthesis happen around it, so the session itself stays focused instead of becoming a marathon.
No AI knowledge required
That's the point of us being there. You bring the knowledge of your business; we translate the pains into AI-shaped opportunities as we go.
It's the front half of a roadmap
The workshop generates and ranks the use cases. If you want them sequenced and costed, that's the roadmap, but the shortlist stands on its own.
Questions
What people ask about the workshop
Q1How long is a workshop?
Usually a half or full day, depending on how many teams and use cases are in scope. We do the prep and the synthesis around it, so the session itself stays focused and energizing instead of turning into a marathon.
Q2Do we need to know anything about AI first?
No. That's the point. We bring the AI literacy and the structure, and you bring the knowledge of your business. We translate your pains into AI-shaped opportunities as we go.
Q3What if we come out with no good ideas?
That's rare. Every business has repetitive, rule-based, or judgment-heavy work worth examining. But if the honest answer is "not yet," you'll leave knowing that too, which saves you a wasted build.
Q4Is this just the strategy roadmap?
It's the front half of it. The workshop generates and ranks the use cases; the roadmap sequences and costs them. For a quick engagement we can run the workshop and hand you the shortlist directly.
Q5Who facilitates it?
We do, with a mix of AI expertise and facilitation so quieter voices are heard and the loudest idea doesn't automatically win. The scoring keeps it honest.
Q6What do we walk away with?
A ranked, scored set of use cases, one-page briefs on the front-runners, the quick wins flagged, and a recommended first project: enough to move straight into scoping.
Elsewhere in AI Transformation & Consulting
Let's talk
Running a large platform, shaping a first MVP, or getting a product ready for a funding round? Tell us where you are. We'll shape the process around it, and stay with you after launch.
