A map of use cases
The selected situations, people involved, data and tools required.
AI governance workshop · company, department, team
Turn your policies and procedures into accessible answers: for this task, with these data and this tool, what can we do — and who decides?
The problem
Governance is reconstructed with every request. The workshop makes the framework explicit, shareable and testable within an initial scope.
What changes
Not blanket permission to use AI: an answer tied to a situation, its conditions and the people responsible.
| For whom | Before | After |
|---|---|---|
| Employee | “I want to try. But am I allowed?” | An answer for their use case, the conditions to meet and the support to ask for. |
| Manager | Decisions made over again, case by case. | A shared framework, with approval requirements and cases that need a decision. |
| AI leads, IT, DPO, legal | Repeated questions and scattered interpretations. | Rules linked to their sources, owners and limits. |
Is this the right time?
We start with a specific process. You do not need to cover the whole company at once.
Complete framework · your deliverables
The selected situations, people involved, data and tools required.
What is allowed, under which conditions and with which responsibilities. Decisions awaiting approval remain identified.
The questions employees, managers and specialists need to be able to ask the framework.
An initial mindBrain model and an interface to query the covered scope, not just a static map.
Permission, conditions, refusal, required approval and missing information: answers are checked against the agreed expectations.
Useful resources, the support route, owners and next steps to maintain the framework.
The discovery format produces an initial static map and structured scenarios. The model, interactive prototype, tests and handover belong to the complete framework.
A practical example · customer complaint
A CRM case file, an ERP order and a reply to prepare. Can these data be used in this environment? And can the reply be sent to the customer?
In this example, permission to draft does not mean permission to send automatically. Change the parameters to see the conditions and limits.
The same tool does not give the same answer in every situation. Change the settings or choose a starting case.
In this example, internal data can be used in the approved environment. The outcome remains a draft to review, with no automatic sending.
Educational illustration calculated in your browser. No connection to mindBrain, no AI call, no real-data processing and no external action.
F-R01Internal or confidential data is not allowed in an unapproved personal account.F-R02An unknown data category or assessment requires review. A personal tool still needs assessment, even for public data.F-R03The environment must be approved for the example scope.F-R04Drafting a reply requires review before any external use.F-R05An external send requires approval by the authorized person.These rules only illustrate the method. They are neither a policy recommended for every company nor a legal decision.
This simulator applies fictional rules in your browser. It does not read a CRM or ERP, call mindBrain or perform any external action.
The answers illustrate the difference between permission, conditions, approval and a case requiring review. They are neither your internal policy nor a compliance assessment.
The method · in business language
You describe real situations. Together we structure them in five acts, then formalise the agreed framework. You do not need to code.
We describe a real situation before writing a rule. The cards reveal the people, documents, data and systems involved.
We follow what people actually do. Reading, sharing, drafting a reply and sending it are different actions and may require different controls.
We qualify information, environments and decisions. A proposed use is not an approved use. Unclassified data is not public data.
We turn intuitions into explicit conditions. Event cards reveal exceptions: sensitive data, missing approval or a changed contract.
We formulate the questions employees, managers and agents will need to answer. The framework becomes searchable from their situation.
A connected framework · not five separate projects
For the chosen process, we connect only the elements needed to answer work-related questions.
mindBrain makes the model queryable, testable and maintainable. Interpretations, approvals and decisions remain the responsibility of qualified people. Missing information remains visible.
Objects, properties and links help retrieve the rules relevant to a situation. Click an element to explore its place in the model.
A purpose, data, an environment and an action. This use connects the domains without conflating them.
Associated question: “Can I draft this reply in this situation?”
The semantic model: what exists and how it is qualified.
The graph and links between domains: rules, relations and conditions.
Projections: useful views for people and agents, without inventing information.
The outcome, its justification, its limits and accessible support. Choose a question to see a possible answer.
For this fictional file classified as internal, prepare only a draft in the approved environment. The external reply must follow the required approval.
Missing data or assessment: the answer would become “requires review”.
Prewritten examples based on the fictional model. In the workshop, questions and expected answers are defined with the scope owners.
A positive answer is not always the right outcome. A model must also refuse, request approval or acknowledge missing information.
| Fictional situation | Expected decision | Actual result |
|---|---|---|
| Draft / approved framework | Allowed with conditions | To test |
| Confidential data / personal account | Not allowed | To test |
| Unknown data category | Requires review | To test |
| Sending / approval missing | Approval required | To test |
| Sending / approval present | Allowed in this example | To test |
| Environment not assessed | Requires review | To test |
Compare answers, justifications and support guidance with the approved expectations.
Document gaps, coverage, sources and missing approvals.
Track response times, requests for help and uncovered cases, using the data available.
The score compares only the decisions for these six synthetic cases. It measures neither your compliance, production effectiveness nor any real time saving.
Living does not mean all-knowing. New information must be added, its effects identified and changes approved before publication.
The assessment of the new environment is missing. Dependent uses must be reviewed.
It is provided by an owner or received from an integrated source.
Draft preparation, sending approvals and related resources.
The missing assessment must be provided and reviewed before a decision is made.
The revised version and its resources become available within the chosen scope.
The button simulates adding missing information and approval. It does not approve any real tool. A policy change is separate from executing controls in applications.
We distinguish the source, its interpretation, its applicability and the operational rule adopted. Uncertain points remain visible.
“Which obligations have been identified for this use?”
Legal interpretations and approvals remain the responsibility of competent people. An internal rule cannot override a legal obligation.
Security, publishing, purchasing and retention rules are connected to concrete tasks and decisions. One procedure can govern several teams.
“What should I check before sharing this document?”
The source, version, owner and review date are kept. Modeling a control does not mean it is already enforced in a tool.
We connect roles and responsibilities to useful resources: guides, approved examples, learning paths and people who can help.
“Which method can I follow, and who can help me?”
A learning need becomes a support path. Approval depends on the chosen mandate, not only on a job title.
We describe the purpose, environment, configuration, data categories and flows. The agent’s level of autonomy is handled explicitly.
« Is this environment appropriate for this task and data? »
Access rights, information freshness and unevaluated points are part of the model. Production connections are defined separately.
We connect rules to the objects that move through the process: a customer file, an order, an invoice, a role or training. Existing applications remain in place.
« What can the agent do with this file, and under which mandate? »
We model the objects useful to the chosen case, not the whole application estate. A relation in the model is not an API connection already deployed.
Complete framework · the workshop
Choose the process and describe the cases that need a clear answer.
Deliverable: the scope, use-case map and first business questions.
Clarify conditions, approvals and available help.
Deliverable: proposed or approved rules, owners and open issues.
Formalise the links in mindBrain and prepare the questions to query.
Deliverable: the initial model and interactive prototype for the agreed scope.
Compare answers with expectations, make corrections and organise next steps.
Deliverable: test results, the revised framework and handover resources.
The schedule and participants’ involvement are adjusted during scoping.
Two formats
Explore the method with your own cases or build an initial operational framework: the starting point is the same, the deliverables are not.
Explore before committing further
€2,500
One half-day to structure real situations and try the method with your team.
No mindBrain model or interactive prototype.
Put an initial framework to work
From€6,000
Four half-days to build, query and test the framework for a process we define together.
Scope, deliverables and commercial terms are confirmed before the workshop. Licences, hosting and integrations with external systems are scoped separately. Moving from discovery to the complete framework is agreed separately; no automatic discount is promised.
Before deciding
No. We can start with use cases, available documents and decisions to make. An existing policy becomes an input, not a prerequisite.
No. They describe the work, review the rules and validate expected answers. We handle model formalisation.
No. The workshop builds an operational framework within an agreed scope. It replaces neither an audit nor the required legal interpretations and approvals. An internal rule cannot override a legal obligation.
Not to get started. Situations and tests can be built without connections, using synthetic data. Any integration is specified and priced separately.
People who know the process, a scope owner and the functions needed for decisions: business, IT, security, an AI lead, DPO or legal, depending on the cases.
An initial discussion
Book a meeting directly. Together we will clarify the scope and the right format.
To prepare for the discussion, consider four points:
Bookings are handled by Calendly, an external service. If the calendar does not appear, open the booking page in a new tab.