Use-case workshop
From a recurring task
to a first draft.
A half-day with one team. We collect the tasks that keep taking time, rank them by value and effort and assess the best ones in a use-case profile. For the most important case, we build a first draft.
- Task
-
Answering recurring enquiries from the inbox
- Today
-
Every reply is pieced together from old emails
- Data
-
Previous replies, text modules, terms; partly personal data
- Human
-
Every reply is checked before sending
- No AI?
-
Text modules alone are not enough, the enquiries vary too much
- Success
-
Less rework per reply than today
- Draft
-
Assistant with templates, ready to demo internally
Who it is for
For teams with tasks
that keep taking time.
Answering enquiries, drafting offers from templates, checking documents. Many teams suspect AI could help here and do not know where to start. The workshop turns this into a well-founded order of priorities.
One team, its own tasks
The workshop works with one team on its own work. All the team needs to bring is the people who handle these tasks every day.
With your organisation’s knowledge
Good solutions use what already exists: templates, previous results, internal rules. We work out which knowledge the AI needs and where it is kept.
No prior knowledge needed
The team knows the tasks, and I bring the experience with AI. No technical knowledge is required.
How we assess
Every case goes through the same questions.
Value and effort
How much time and energy the task costs today and how much work a solution would be. That decides the order.
Fit
Whether the task follows a recurring pattern and the knowledge it needs already exists somewhere in your organisation.
Data
Which data the case needs, where it is kept and which of it is sensitive, such as personal data.
Human and machine
Whether a person checks every result before it is used. If so, the case is a good start. If the AI works without checks, the case needs rules of its own and comes later.
Proportionality
What the simplest solution without AI would be. Sometimes a good template or some practice with the existing tool is enough.
Ownership
Who looks after the case with real capacity and how you will later know that it works.
Process
From the first call to the use-case profile.
Prepare Beforehand
In a short call beforehand, we clarify which team takes part, which tools it uses and which rules apply to your data. If you like, the team sends a first list of tasks, which I sort into themes.
Collect Half day
We add the tasks that most often cost time and energy, especially for managers and project leads. That is usually where the greatest value and the greatest willingness lie.
Rank Half day
Every task goes on a sticky note onto a matrix of value and effort. Then the team votes with dots. High value with low effort comes first.
Assess Half day
For the favourites, we fill in the use-case profile together: current process and effort, data, the role of the human, risks, the solution without AI and who takes the case forward.
Draft Half day
For the most important case, we build a first draft, depending on the task an assistant, a template or a workflow, and try it on examples from the team’s daily work.
Write it up Afterwards
You receive the matrix as an overview and the profiles neatly prepared. With profile and draft, the team can present the case internally.
Format
A half-day, remote or on site with you. One team per session.
Participants
The colleagues who handle the tasks every day. If leadership joins, the ranking carries further. Your IT can join if you like.
Materials
On site, sticky notes, dots and a wall. Remote, a shared digital whiteboard.
Data
We work according to your rules, with anonymised examples where needed.
Common pitfalls
What is often overlooked when choosing cases.
The most valuable case needs a foundation
Cases built on existing knowledge often require that documents and files are searchable. Then the question is the order, not whether.
Not every case needs building
What already works well with the existing platform gains more from templates and practice than from a system of its own.
Decisions about people
Cases in which AI assesses job applications or people’s performance are deliberately put on hold. The EU AI Act sets stricter obligations for them.
Tools without an exit
For every provider, we check whether data can be exported and the contract can be terminated.
Without an owner, nothing moves
A well-rated case without a responsible person with real capacity does not move forward. That is why ownership is part of the profile.
What your team takes away
A well-founded order of priorities
and a first draft to show.
An overview of all tasks
All collected tasks, ranked by value and effort. The cases that do not win today are on it too, with an assessment.
Profiles for the favourites
One page per case with the current process, data, the role of the human, risks and the solution without AI. It gives you a basis for deciding internally whether and how to proceed.
A first draft
An assistant, a template or a workflow for the most important case. It is not finished yet, but it makes the case tangible.
A clear next step
For every favourite, it is settled who takes it forward and how you will know that it works.
And then?
If the case is worth it, it can become a build project. I then turn the solution into a running system, connected to your data and with a defined result: Build, AI development through to operation →
If all staff should first learn the basics and the rules: AI literacy half-day →
Questions about the workshop
Which tasks are suitable?
Tasks that recur regularly, follow a similar pattern and take noticeable time. Typical examples are answering enquiries, drafting texts from templates and summarising or checking documents. Whether AI pays off for the task is something we work out in the workshop.
What goes into the use-case profile?
One page per case: the task and who handles it, the current process and effort, the data needed and which of it is sensitive, whether a person checks every result, risks, the simplest solution without AI, the priority from the matrix, who looks after it and how you measure success.
How are cases ranked?
Every task goes onto a matrix of value and effort. Then the team votes with dots. The result is an order the team has justified itself and can stand behind internally.
What happens to the cases that do not win?
They stay on the overview with an assessment. Some are solved with templates and practice, others come up once the first cases are running.
What happens to the draft after the workshop?
The draft is a prototype. The team can present it internally and gather first experience. If it is to run permanently and with real data, it needs your IT and data protection teams. If you like, I build the solution as a separate project.
How does this differ from the vibe coding workshop?
In the vibe coding workshop, staff build small tools themselves in the browser. The use-case workshop starts from a team’s tasks and works out which of them AI can support with your organisation’s knowledge, and in which order. It ends with profiles that serve as the basis for a decision.
Can several teams take part?
The workshop works with one team per session, so there is enough time for its own tasks. For several teams, there are several sessions.
What does the workshop cost?
On request. You get a concrete quote after the first call.
Contact
Email me at info@slworks.de or book a free intro call right away.
Loads the Cal.com booking calendar (USA). This transmits your IP address to Cal.com. More in the privacy policy (German).