A named lead
Agree who coordinates adoption inside the organisation and who can make the decisions the work raises. Participants need a clear place to ask questions and a person who can connect those questions to the wider plan.
The AI practice · The Program
A supported AI adoption program.
Help your team move from individual experiments to shared ways of working.
For organisations that need people, training and workflows to move together.
The scope
What does the Program include?
The Program is the adoption work that connects a plan to the people using AI.
It brings the audience, the priority workflows and the review rhythm into one scope. The work is to support use in the organisation, examine what is happening and decide what should change next.
Priorities people can use
Choose the first workflows and explain why they matter. Give each participating team a defined task to practise, the context needed to do it and a way to review the result. Avoid asking everyone to explore every tool at once.
Training with follow-through
Connect the learning to the work people will do next. Review the questions that appear when participants try the task and use those questions to improve the instructions or the next session.
A review rhythm
Keep a record of what the team is using, where it needs support and which workflows need changes. The review is a decision point: continue useful work, change what is not working and stop activity that no longer fits the priority.
How it starts
Agree the work before it begins.
Use these four steps to turn the business question into a scope your team can review.
- 01
Agree the adoption question
Name the business priority, the teams involved and the person responsible for decisions.
- 02
Select the first workflows
Choose a manageable starting set and agree what participants need to practise.
- 03
Support use in the team
Connect training, questions and workflow changes as people apply the work.
- 04
Review and set the next priority
Use the operating evidence and participant feedback to decide what to continue or change.
The record
Adoption across five APAC markets.
Before LOKAL, Joshua Pielago ran Uber’s AI Everyday programme in 2025–26 across five APAC markets.
Approximately 4,000 employees were trained, the teams shipped more than 300 working bots and the programme’s modules reached about 8,000 people. It was his employer’s programme, not LOKAL’s, and it is not a promised adoption result for another organisation.
“He was one of the earliest people in the company to treat AI adoption as a change-management problem rather than a tooling problem, and he was right.”
What to bring
The context your team already has.
Bring what is available. The consultation identifies what else is needed before the scope is agreed.
- The business priority and the teams that need to participate.
- Existing AI access, any training already completed and examples of work people have tried.
- The person coordinating adoption and the people who can approve workflow or access changes.
Connected work
Choose the next step around the need.
The stages connect, but your team does not need to begin every piece of work at once.
The Blueprint ↗
Begin with the planning stage if priorities and responsibilities are not yet clear.
Training ↗
Build practical skills around the work participating teams need to do.
Applied AI ↗
Build a defined workflow when the plan calls for implementation.
Run ↗
Agree ongoing management when a workflow becomes part of daily work.
Common questions
Before we start.
These questions help establish the people, responsibilities and starting point for the work.
Do we need the Blueprint first?
The Program needs an agreed plan. If your organisation already has a clear plan, bring it to the consultation. If the priority or scope is still unresolved, the Blueprint is the planning starting point.
Who leads this inside our organisation?
The scope names an internal lead and the people who can approve decisions. The practice supports the work, but adoption also needs someone who can coordinate the organisation’s own teams and responsibilities.
Does the Program include every AI build?
Implementation is scoped around the workflows the plan identifies. A build belongs in Applied AI with clear inputs, outputs and review points. The Program connects that work to the people using it.
What happens next?
Start the form with your work email, then tell us about your team and the work. We reply within one business day to arrange a 30-minute consultation. That conversation establishes the context and the next step for an agreed scope; it does not commit your team to a program.
Your next step
Tell us what your team needs.
Start with your work email. The form then asks about your organisation and the work, so we can come to the 30-minute consultation prepared.