The AI practice · Run
Give the work an owner after the build is finished.
For teams that need ongoing management, review and improvements to the AI workflows they use.
The scope
Run is the ongoing management of an agreed AI workflow.
It connects the people using the workflow with the people maintaining it. The scope names what is being managed, how exceptions are reviewed and which changes need a new decision before implementation.
Name the workflow, its purpose and the systems it connects. Agree the responsible people, the expected review points and the information they need to understand an exception. The scope makes clear which work is included in ongoing management.
Look at the situations where the workflow did not produce the intended result or needed a person to step in. Record the context and decide whether the issue belongs in instructions, inputs, implementation or the underlying process.
Business processes change. Keep the workflow’s instructions and supporting documentation connected to the way the team actually works. Changes should be reviewable so the people using the workflow understand what has changed and why.
Not every suggestion needs an immediate build. Collect the improvements, connect them to the operating evidence and decide what matters next. A larger change can move back into the planning or implementation stage with a separate agreed scope.
How it starts
Use these four steps to turn the business question into a scope your team can review.
Understand the workflow, its purpose, its connections and the people who depend on it.
Name the owner, review schedule and path for exceptions and changes.
Review the operating record, maintain agreed work and keep the instructions current.
Choose the next improvement based on the issues and needs seen in actual use.
The record
LOKI delivers approximately 80% of LOKAL’s own services.
In July 2026, the internal system had 433 tools and 19 skills. That record is specific to LOKAL’s work: another organisation’s operating scope depends on its own workflows, information and people.
Read the scoped record ↗What to bring
Bring what is available. The consultation identifies what else is needed before the scope is agreed.
Connected work
The stages connect, but your team does not need to begin every piece of work at once.
Build or change the workflow through a defined implementation scope.
Revisit the plan when the business need or operating scope has changed.
Support adoption when the people using the workflow need coordinated help.
Read about the internal system behind LOKAL’s own work.
Common questions
These questions help establish the people, responsibilities and starting point for the work.
Bring the workflow, its documentation and the people responsible for it to the consultation. We review the operating context before agreeing whether the practice can take on the work and what the scope should include.
The operating scope defines ongoing management. A new workflow or substantial change needs its own agreed implementation scope so the team can review the work, dependencies and responsibilities before it begins.
The scope names the responsible people on both sides. Your organisation remains involved in business decisions and approvals. The practice provides the agreed management and brings exceptions or proposed changes to the right people.
Send the form with a short description of 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
Describe the work, the people involved and the decision you need to make. We reply within one business day to arrange the 30-minute consultation.