A team adopts. The region follows.
We bring AI through an organisation in rounds per team. One manager signs, the first team works on day 15, and every step below has a measured reason.
Day 15
the first team works
Less of your time, and the team works sooner.
46%
fewer hours from your organisation
Against the usual regional approach.
Day 15
the first team works
Eight weeks per work process, then the next team.
10%
of your teams in round one
After the pilot with one team. Their how-to films, agreements and formats carry the next rounds.
From the first decision to business as usual.
This is what we do. Your team leaders make or break it, so we start with them.
Decide One meeting
One note and one management meeting: the plan, IT, the leaders’ role, the owner of the process.
Find the job Week 1
The paste census, or three to five questions per team. The opening question: where do you lose the most time?
Connect Weeks 1 and 2
Sign-in first. Then the sources by theme and team, with an owner per source. Formats go into the product, so nobody has to learn to prompt.
First group Day 15
One team, in large organisations up to ten per cent of teams, accounts group by group. Sixty minutes on the floor with their own cases, hands on the work within ten minutes.
The first three weeks Weeks 3 to 5
Aim for a third active day in week one. Short check-ins at the morning start and handover, through whatever channel the team picks.
Close the gaps Continuous
Every missed answer goes to the source’s owner, every missing format to the product, in days.
Find the front-runners Weeks 4 to 8
We read the usage, not the org chart. One or two ambassadors per team.
Show the board Weeks 4, 8, 12, month 6
Measured at week 4, week 8, week 12 and month 6: admin time, out-of-hours support, use of own knowledge, fewer questions to colleagues.
Next process, next team From week 8
The first team’s how-to films, agreements and formats carry the next round. A new process opens once the first runs.
Stay Ongoing
Plan, do, check, act four times a year. One partner for product and floor, also after the project ends.
Builder and implementer are one team.
What the floor asks is in the product the same week. A client’s request became product standard in four days, tested by its own occupational therapists.
- What the floor teaches
- Every missing format goes straight to the people who build the product.
- Prompting is not your care workers’ job.
- What the measurement says
- A pilot can reach its KPI while the impact never comes.
- So we measure process and outcome per team, continuously.
- Who counts as the team
- A team is also the kitchen, the psychologist and the informal carer.
- Tie a round to a theme, such as challenging behaviour.
Sixty minutes. Then the team works.
Run bookFor programme leads and team leaders
The session and the ambassador pack.
Your own cases, chosen in advance, hands on the work within ten minutes, ambassadors in the room. Per role the cases that work.
What it holds
- The session, minute by minute
- Cases per role
- The ambassador pack and the check-ins after
Start with the first process.
- Choosing the first processThree tests and one sum per setting.
- ReportThe first three weeksOn day 21 you know who stays.
- The AZWA applicationReady for use is this method.