The decision and its context
Name the question, the person approving the decision and the deadline. Review what has already been tried and distinguish evidence from assumptions. This keeps the consulting work tied to the organisation’s actual need.
The AI practice · The Blueprint
AI consulting your team can act on
Decide where AI belongs, what should happen first and who needs to be involved.
For leaders who need a clear plan before training, adoption or a build begins.
The scope
What does the Blueprint include?
The Blueprint is the planning stage of the LOKAL AI practice.
It examines the business question, the work, the available information and the people involved. The output is a plan that makes the priorities, responsibilities and next decisions explicit enough for a team to act on.
Priorities across the work
Compare possible workflows against the business purpose, the information available and the effort required to use and maintain them. Explain what should happen first, what needs preparation and what should wait.
Responsibilities and review
Identify who provides information, who reviews outputs and who takes over when the workflow needs a person. Connect those responsibilities to the people who will use and manage the work after launch.
A brief for the next stage
Turn the agreed plan into a scope that can be reviewed before work begins. Name the intended output, dependencies, acceptance checks and handover. The organisation can use the plan with LOKAL, its internal team or another implementation team.
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
Name the question
Agree the business decision, approver and context before defining the consulting work.
- 02
Inspect the existing work
Use examples, interviews and current processes to understand the inputs, tasks and handoffs.
- 03
Compare the options
Explain the priorities and trade-offs in terms the people making and delivering the decision can use.
- 04
Agree the plan
Record the next step, responsibilities, prerequisites and questions that still need an answer.
The record
Planning beside practical implementation.
Joshua Pielago is a Claude Certified Architect – Foundations and a member of the OpenAI Champions Network.
LOKAL is a member of the Claude Partner Network and the OpenAI Partner Network. Joshua’s background includes eight years at Uber and earlier work as Lead Product Manager at Axadra. Roles and dates are on About.
“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 decision you need to make, the deadline and the person who will approve it.
- Examples of the work involved, the tools it touches and the information it needs.
- Any evidence from previous pilots, the people using them and the questions that remain unresolved.
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.
Training ↗
Help people practise the tasks identified in the plan.
The Program ↗
Connect the plan to adoption across the organisation.
Applied AI ↗
Build the agreed workflow with defined inputs, outputs and review.
AI consulting Australia ↗
Read the Australian consulting context and local pages.
Common questions
Before we start.
These questions help establish the people, responsibilities and starting point for the work.
Is the Blueprint an implementation project?
The Blueprint produces the plan and the brief for the next step. Implementation belongs in Applied AI with an agreed scope. Separating the decision from the build lets your team review the plan before committing to implementation.
Can we bring an existing pilot?
Yes. Bring the workflow, the people involved and the evidence from its use. The consulting work can examine why it has stalled, what needs to change and whether continuing it is the appropriate next step.
Will the plan specify a platform?
Where a tool decision is needed, the plan explains the choice in the context of the workflow, existing access and operating requirements. We recommend the tool that fits your workflow and access, not the one we hold a badge for.
Can our internal team deliver the plan?
The brief records the work and responsibilities so the organisation can decide who should implement it. You can proceed with an internal team, LOKAL or another approved team.
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.