Broad-based enablement
A four-person team scales AI across 900 employees by organizing self-help instead of building solutions. The decisive lever remains visible buy-in from leadership.
Monthly thinking room
Where does free experimentation with AI end, and where does regulated operation begin? This edition shows how companies select AI tools, give agents permissions and independent review, and take employees' fears seriously.
For working with your own AI assistant. How it works

We handpicked 46 podcast episodes released in May 2026 and distilled 138 insights from them. These ten patterns show how companies move from experimentation to a structured approach to using AI and which rules, roles and decisions recur along the way.
RAPS Group gives its field sales staff, who have ten to twelve customer appointments a day, a CRM-linked AI sales assistant that briefs them by phone call in the car before the appointment and records the report afterwards.
Verena Pausder dictates on the go between blocks of appointments with Whisper Flow, in which she has stored proper names and style preferences. Marie Kilg (Bayerischer Rundfunk) advises beginners to speak freely instead of typing prompts.
Deutsche Bahn tested the voice AI avatar Kiana at BER airport, where international travelers could ask about connections in their own language and buy a digital ticket directly.
Status: unchanged
Supported by these conversations
Ulrich Gerkmann-Bartels (enpit) reports that an agent wrote an API key into the repository despite precautions and only a second, independent agent found it. He calls for a guard that does not come from the same LLM vendor.
Strong DM has one LLM context write code from the specification and a second one, which knows only the specification and acceptance scenarios, test against it, so that agents cannot turn tests green with “return true”.
In a client project, MaibornWolff sends every pull request created with Claude Code through four review stages; Upvest adds a technically enforced human approval to AI reviews from Claude and Copilot.
Status: unchanged
Supported by these conversations
At Haufe Group, hard technical limits prevent payroll data from flowing into open systems; CIO Andreas Plaul allows employees to submit their own payslip to ChatGPT, but not those of other employees.
Upvest processes internal documents and personal data via Gemini in Google Workspace with zero data retention and a European data center, but handles coding work via Claude Code, because code is considered less sensitive.
IONOS lets teams working with public open-source code use US vendors freely, while customer-related or highly sensitive data stays in self-hosted IONOS models or under agreed data processing agreements.
Status: unchanged
Supported by these conversations
With a subscription
With a subscription you read all 10 with their sources and download them as a text file.
The complete collection
46 conversations, ordered from newest to oldest.
Broad-based enablement
A four-person team scales AI across 900 employees by organizing self-help instead of building solutions. The decisive lever remains visible buy-in from leadership.
With a subscription
With a subscription you open all 46 conversations of this room with their insights, search the catalogue and download the files.
1 conversation added · none removed · 1 revised
9 unchanged · 1 sharpened
With a subscription you see which conversations, findings and recommendations changed.
Compared with V1 · 03 Aug 2026.