AI governance workshop · company, department, team

Your teams use AI.
Don’t leave them guessing what’s allowed.

Turn your policies and procedures into accessible answers: for this task, with these data and this tool, what can we do — and who decides?

Discovery · 1 half-day · €2,500Complete framework · 4 half-days · from €6,000

The problem

The policies may exist. How to apply them is still a guessing game.

  • Employees are unsure which data and tools they can use.
  • The same questions keep coming back to managers, IT or the DPO.
  • Each team pieces together its own answer from several documents.
  • A change of tool, rule or owner calls previous decisions into question.

Governance is reconstructed with every request. The workshop makes the framework explicit, shareable and testable within an initial scope.

What changes

A rule becomes a way forward.

Not blanket permission to use AI: an answer tied to a situation, its conditions and the people responsible.

For whomBeforeAfter
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.
ManagerDecisions made over again, case by case.A shared framework, with approval requirements and cases that need a decision.
AI leads, IT, DPO, legalRepeated questions and scattered interpretations.Rules linked to their sources, owners and limits.

Is this the right time?

You want to guide AI use without blocking everything.

We start with a specific process. You do not need to cover the whole company at once.

  • A policy exists, but teams struggle to apply it.
  • AI assistants are spreading into everyday work.
  • Agents will access data or carry out actions.
  • The same questions regularly occupy your experts.
  • You need workable permissions with explicit limits.
  • You want to test the framework on one process before extending it.

Complete framework · your deliverables

What you will have to work with.

A map of use cases

The selected situations, people involved, data and tools required.

Operational rules

What is allowed, under which conditions and with which responsibilities. Decisions awaiting approval remain identified.

Business questions

The questions employees, managers and specialists need to be able to ask the framework.

A model and an interactive prototype

An initial mindBrain model and an interface to query the covered scope, not just a static map.

Test scenarios

Permission, conditions, refusal, required approval and missing information: answers are checked against the agreed expectations.

Support resources and handover

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

Same task. Different context. Different decision.

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.

Local simulation · fictional internal rules

Change the context. Observe the answer.

The same tool does not give the same answer in every situation. Change the settings or choose a starting case.

Allowed with conditions

Yes, to draft a reply.

In this example, internal data can be used in the approved environment. The outcome remains a draft to review, with no automatic sending.

Fictional rules F-R03 · F-R04 · Example policy v1
Your support pointFictional guide “Draft a customer reply” and the team’s AI lead.

Educational illustration calculated in your browser. No connection to mindBrain, no AI call, no real-data processing and no external action.

See the fictional rules used by this simulator
  • 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.

How does this demonstration work?

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

We start with what you do. Not a modelling course.

You describe real situations. Together we structure them in five acts, then formalise the agreed framework. You do not need to code.

  1. NounsThe people, data, documents and tools.
  2. VerbsThe actions to prepare, control or authorise.
  3. QualifiersThe categories and states that change the answer.
  4. ConditionsThe limits, permissions and approvals.
  5. SearchThe questions the framework needs to answer.
Explore the five acts and flip the cards
Act 01 / 05 · business language

What are we talking about?

We describe a real situation before writing a rule. The cards reveal the people, documents, data and systems involved.

  • Who is trying to accomplish what?
  • Which information and tools are being used?
  • Who can help or make the decision?
What we identifyA shared vocabulary and the scope of the case to govern.
YOUR WORK TABLEClick to flip a card ↗

A connected framework · not five separate projects

Link a decision to what supports it.

For the chosen process, we connect only the elements needed to answer work-related questions.

SourceRulePerson · data · toolActionConditionDecisionResource · owner

mindBrain makes the model queryable, testable and maintainable. Interpretations, approvals and decisions remain the responsibility of qualified people. Missing information remains visible.

Explore how the model works
From workshop to model · fictional example

What you named becomes connected.

Objects, properties and links help retrieve the rules relevant to a situation. Click an element to explore its place in the model.

Business use

Draft a customer reply

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?”

01 · Describe

The semantic model: what exists and how it is qualified.

02 · Connect

The graph and links between domains: rules, relations and conditions.

03 · Expose

Projections: useful views for people and agents, without inventing information.

Explore sources, rules, resources, data and applications

Texts, connected to their application.

We distinguish the source, its interpretation, its applicability and the operational rule adopted. Uncertain points remain visible.

LegislationSector regulationContratsSelected standards
A business question becomes accessible
“Which obligations have been identified for this use?”
Source textApplicability approvedRuleUse

Legal interpretations and approvals remain the responsibility of competent people. An internal rule cannot override a legal obligation.

Complete framework · the workshop

Four half-days.
From the first case to testing.

  1. Half-day 01

    Uses & situations

    Choose the process and describe the cases that need a clear answer.

    Deliverable: the scope, use-case map and first business questions.

  2. Half-day 02

    Rules & support

    Clarify conditions, approvals and available help.

    Deliverable: proposed or approved rules, owners and open issues.

  3. Half-day 03

    Model & prototype

    Formalise the links in mindBrain and prepare the questions to query.

    Deliverable: the initial model and interactive prototype for the agreed scope.

  4. Half-day 04

    Tests & handover

    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

Choose how far you want to go.

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

Discovery workshop

€2,500

One half-day to structure real situations and try the method with your team.

  • Scenarios described through the five acts.
  • Initial rules and explicit conditions.
  • Uncertainties and decisions requiring review.
  • An initial static map of the scope.

No mindBrain model or interactive prototype.

Put an initial framework to work

Complete operational framework

From€6,000

Four half-days to build, query and test the framework for a process we define together.

  • Formalised use cases, rules and responsibilities.
  • A mindBrain model for the agreed scope.
  • An interactive prototype for business questions.
  • Test scenarios and their results.
  • Support resources, handover and next steps.

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

The questions that matter now.

Do we need an existing AI policy?

No. We can start with use cases, available documents and decisions to make. An existing policy becomes an input, not a prerequisite.

Do participants need to know how to code?

No. They describe the work, review the rules and validate expected answers. We handle model formalisation.

Is this a compliance audit?

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.

Do we need to connect our CRM, ERP or other tools?

Not to get started. Situations and tests can be built without connections, using synthetic data. Any integration is specified and priced separately.

Who should take part?

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

Which process needs a clear answer?

Book a meeting directly. Together we will clarify the scope and the right format.

To prepare for the discussion, consider four points:

  • The process to cover.
  • The people involved.
  • The recurring question.
  • The functions that need to make decisions.

Bookings are handled by Calendly, an external service. If the calendar does not appear, open the booking page in a new tab.