You have invested a lot in rolling out AI.
How much has the team gained, together?
Combined in one shared AI collaboration system, it can change how you work as a team.
I help teams design tomorrow's way of working together. Faster decisions. Broader creativity. Same people.
We start with one workflow you are already in, and land one decision you own.
01
Different on one point
There are many good AI workshops that give ideas for what AI can be used for. Mine is different on one point. We take one real case you are already in. You walk out with the decision made. And the way you made it becomes the team's shared way of working with AI.
The decision date is agreed before we start.
02
Two starting points
Most teams come in through one of two doors.
The first: an important decision that has been stuck for too long. A product choice. A direction. Something that gets reopened in every meeting.
The second: the AI tools have been bought, but the team lacks a shared way of using them. On their own, people move faster. Together, things stand still.
Both doors lead to the same process.
03
The timeline
Week 0. We choose the case and the workflow together with you, the person who owns it. Data boundaries are agreed in writing. The team chooses three numbers everything will be measured on. All session dates are locked, including the decision date.
Four sessions over about two weeks. SEE, TRY, LAND, DECIDE. A cross-functional team of five to ten people tries the new way of working, on its own case, before deciding on it. Between the sessions, the team's shared AI brain is built, on your own work.
Day 30. We measure the effect on the three numbers the team chose. The decision stands. The way of working is in use.
Afterwards, the process can continue as a 30-day run-in period, if you want support while the new way of working settles in.
04
What you walk away with
- One decision, made on the agreed date.
- The workflow mapped and rebuilt.
- A shared AI brain, so the team's knowledge stays in one place.
- Two to three shared workflows, built on your own work.
- A decision log and clarified roles in the handovers.
- The team's own ground rules for where AI is used, and where it is not. Written down, with a training log.
- Baseline and follow-up measurement on the team's own numbers.
The rules and the log can also contribute to the documentation the AI literacy requirement in the EU AI Act points towards. In the EU the requirement is already in force. In Norway it is expected in national law, probably during 2027. This is preparation, in good time.
05
One requirement
There has to be a real case. Without a real workflow and real material, this becomes a course. Then I politely decline.
I promise no percentages. We measure on the team's own numbers.
Bring one workflow that keeps stalling.
In 30 to 45 minutes we find out whether there is a concrete bottleneck worth testing.
Book a conversation