An AI workshop is useful when a process is already on the table: a support process, back office workflow, finance check, sales task, or another specific work area.
We examine that process with the department, IT, and decision-makers, then clarify what implementation would require: task, data, systems, edge cases, rights, approvals, and MVP scope.
When the process is already on the table.
An AI workshop is suitable if you are no longer looking broadly for AI potential, but want to examine a specific process in more detail.
We look at recurring work in support, finance, sales, or operations and bring the department, IT, and decision-makers together. The goal is a sound basis for an MVP, pilot, or internal implementation.
The compact format is suitable when the process is known, but the task, data, roles and boundaries are not yet clearly described.
The in-depth format moves closer to implementation. We clarify data, rights, escalations, quality criteria, and a realistic MVP scope.
The workshop is not meant to produce as many AI ideas as possible. It clarifies one specific process enough to make a decision: build it, prepare it internally, or stop it for now.
For teams that know which process should be considered, but have not yet formulated a clear AI task, boundaries or success criteria.
For processes where domain knowledge, edge cases, and daily reality matter as much as the technical solution.
For processes involving CRM, ERP, tickets, emails, documents, tables, or internal databases.
For companies that want to know after the workshop what exactly needs to be built, tested, and approved.
Workshop experience from projects where AI touches real work.
The workshops come from thirdmind's implementation perspective: digital employees need tasks, data, rights, system context, and clear handovers.
This background shapes the work in the room. The goal is not to make AI seem impressive. It is to understand a process well enough for a viable next step.
Depending on the format, a workshop goes to different depth. The central question stays the same: is this process ready for the next step?
A workshop is not a substitute for implementation. But it can prevent an AI project from starting with an unclear task, incorrect scope or missing approvals.
Not a long list of ideas. No promise that this process should be automated.
We do not run workshops that end with only a long list of ideas. We also do not assume that every process should be automated.
Sometimes the best outcome is to clarify the process internally first. Sometimes a small MVP makes more sense than a large rollout.
Workshop length depends on scope. Compact formats focus on process clarification; deeper formats cover data, edge cases, rights, approvals, and MVP scope.
It makes sense to involve the relevant department, the process owner, IT or data protection, and someone who can decide on the next implementation step.
Only at the edge. The focus is a specific process: task, data, systems, edge cases, rights, approvals, and quality criteria. Tools come later.
Yes. Workshops can take place remotely or on site.
Not automatically. A workshop creates a better basis for implementation. If the process, data, rights, and MVP scope are clear enough, a pilot can emerge.
The AI Compass evaluates several possible use cases and provides a decision basis. The workshop goes deeper into one specific process and clarifies what an implementation or MVP would require.
Yuno asks four short questions about the process, subject area, data, and goal. After that, it is clearer whether an AI workshop or the AI Compass makes sense first.
