The operating flow
A pragmatic order that takes you from a first assistant to AI adopted and governed across the organization.1
Train at scale
Start with acculturation for everyone: what AI can and cannot do, and the rules (AI Act). People govern themselves better when they understand them. It is the cheapest, highest-leverage step, and it comes first.
2
Identify and train AI champions
Use Insights to spot the most active and relevant builders. Internal committees select the AI champions, give them deeper training, and grant them the right to share. Everyone else keeps building for themselves.
3
Open: choose your strategy
Decide how widely to open creation: everyone builds (self-care), or only selected use cases (curated). Then give access accordingly. By default no one shares or publishes; sharing is granted, never self-assigned. See Opening strategies.
4
Organize the squads
Stand up the teams that keep the platform alive: a Platform squad (run and releases), a Use-cases squad (onboard complex use cases), an Animation squad (drive adoption), and Architecture (standards and reuse). See Who does what.
5
Deliver critical use cases in project mode
A small set of critical use cases gets the full engineering treatment: the use-case lifecycle and the environments and Git model in Deployment strategy. This is where infrastructure and CI/CD come in, for those use cases only, not for every self-care agent.
Before you open: one org or several?
The structure decision most teams hesitate on, and where groups fit, is covered in One organization or several.The one principle
Governance runs on levels, and each level can only tighten the one above, never widen it. On conflict, the tightest limit wins. Inside its own envelope, each level distributes freely. It is detailed in Opening strategies and in Governe.Explore
Opening strategies
Open to everyone or curate, and how to open without chaos
Who does what
The squads, committees, and champions, and who holds which right
One organization or several?
The structure decision, and where groups fit
Critical use cases in project mode
The lifecycle and the deployment model for the use cases that need it