Practice 02

AI adoption, done safely

Your people are already curious about AI assistants such as Microsoft Copilot, Claude and ChatGPT. We help you choose where they add real value, set the guardrails that protect your data, and give staff the confidence to use them well.

Who it is for

  • Organizations that want staff to use AI assistants such as Microsoft Copilot, Claude or ChatGPT
  • Leaders who want the benefits of AI without putting client or company data at risk
  • Regulated firms that need governance in place before broad rollout
  • Teams that bought AI licences and want to see them used well

Signs you need it

  • Staff use personal AI accounts for work tasks
  • There is no written AI usage policy, or nobody follows it
  • Nobody is sure which tasks AI should and should not be used for
  • Licences were bought, but use is low or uneven
  • Security, legal or compliance teams have questions nobody can answer yet
The entry step

AI Adoption Diagnostic

Every engagement in this practice starts with a fixed-scope diagnostic. We agree the exact scope, access and timeline with you in writing before any work begins, and you decide afterwards whether to go further.

Scope: what we look at

  • How AI tools are used today, officially and unofficially
  • Candidate use cases, ranked by value and risk
  • Data handling: what may and may not be shared with AI tools
  • Guardrails and governance needed for your sector
  • Training needs for the people who will use the tools

What you receive

  • A written findings report
  • A prioritized list of use cases to start with
  • Recommended guardrails and the outline of an AI usage policy
  • A walk-through of the findings with your leadership team
How it runs

How the diagnostic runs

  1. Step 1

    Scoping call

    We agree the teams in scope, who we will speak with, what data we will see and the timeline.

  2. Step 2

    Discovery

    We talk with the people who will use AI and review the tools, settings and policies you have today.

  3. Step 3

    Analysis

    We rank use cases by value and risk and identify the guardrails needed.

  4. Step 4

    Findings and plan

    We walk your leadership team through the findings and a practical plan to start.

After the diagnostic

Follow-on options

None of these is required. You can act on the plan with your own team.

Team training

Practical sessions so staff use AI assistants well and within your guardrails.

Workflow builds

Help building AI-assisted workflows for the use cases you choose to start with.

AI usage policy

A clear, workable AI usage policy written for your organization.

Experience

AI enablement our Principal has led

Our Principal led an organization-wide rollout of Microsoft 365 and GitHub Copilot in a regulated firm, with the security guardrails and governance standards that let the firm adopt AI safely.

See the work

FAQ

Common questions

Will AI replace our staff?

That is not the goal of this work. We focus on tasks where an AI assistant helps people do their jobs better and faster, with a person still responsible for the result.

Do you work with one AI vendor?

No. We are vendor-neutral. We help organizations adopt AI assistants such as Microsoft Copilot, Claude and ChatGPT, start from the tools you already have, and recommend what fits your security and data needs.

How do you keep our data safe?

Data handling is part of the diagnostic. We look at what information staff may share with AI tools, which plans and settings the vendors offer for business data, and what guardrails and policy you need. We agree in writing what data we will see during the work.

Do we need technical staff to take part?

It helps to have someone from IT or security involved, but most of the diagnostic is about how your people work. We talk to the teams who will use the tools.

Why is there no price on this page?

We agree the scope on a first call and then send a fixed quote for that scope before any work begins.