AI training for teams who need it to stick, not just impress

Who this is for

This is for businesses where a few people quietly use AI tools already, most do not, and nobody is sure what is safe to put into them. The goal is a team that uses AI well on the work it is actually paid to do — and knows where the limits are.

• —Staff pasting customer information into free AI tools with no guidance on what is safe.
• —One enthusiast automating their own corner while the rest of the team watches.
• —Managers asked to 'do something with AI' without knowing what good looks like.
• —Teams that tried ChatGPT, got one bad answer, and wrote the whole thing off.
• —Owners who want a sensible usage policy without commissioning a 40-page document.

What the training actually changes

1. 01

   Everyday work gets faster, visibly

   Each person leaves with two or three of their own recurring tasks — drafting, summarising, checking, formatting — running noticeably quicker, using prompts built in the session on their real material.

2. 02

   A shared line on what is safe

   The team gets a short, plain-English usage agreement: what can go into which tools, what never does, and what gets reviewed by a person before it leaves the building.

3. 03

   Judgement, not just buttons

   People learn to spot when an AI answer is confidently wrong, when to stop wrestling with a prompt, and which jobs are simply not AI-shaped. That judgement is what stops the expensive mistakes.

If your team's AI usage is one keen person and a lot of guesswork, training is the cheapest fix available.

What a first engagement looks like

Honest scope: useful training is measured in sessions, not semesters. Most teams need a half-day to start and a follow-up a few weeks later, not a curriculum.

1. 01

   A short scan of how the team works now

   Before any training, a conversation about the team's actual tasks and tools, so the session is built on your enquiries and your documents rather than generic examples.

2. 02

   A hands-on working session

   Small group, laptops open, working on real tasks. Everyone builds prompts they will reuse, and the safe-usage rules get agreed in the room rather than imposed afterwards.

3. 03

   A follow-up once reality has had a go

   A few weeks later: what stuck, what did not, and what new questions came up. This is where the habits either set or quietly die, so it is part of the engagement, not an upsell.

When another path is better

• If the problem is one specific workflow rather than general capability, skip training and look at AI automation instead — a built system beats a trained habit for repetitive work.
• If leadership has not yet decided where AI fits at all, start with AI consulting so the training lands somewhere deliberate.
• If the team is mostly working in one tool already, tool-specific help such as ChatGPT consulting may be the faster route.

Frequently asked questions

How long does AI team training take?

The usual shape is a half-day hands-on session plus a follow-up a few weeks later. Larger teams split into groups by role, because the useful examples for an admin team and a field team are different.

Which AI tools does the training cover?

The ones your team will actually use — typically ChatGPT, Claude, or Copilot, depending on what your business already pays for. The skills transfer between tools; the safety rules are written to be tool-agnostic.

Do you provide an AI usage policy?

You leave with a short, plain-English usage agreement the team helped write — what data goes where, what gets human review, and who to ask when unsure. It is deliberately one page, because policies nobody reads protect nobody.

Our team is sceptical. Does that matter?

Sceptics are useful in the room. Training on the team's real work tends to land better than demos, and where AI genuinely is not the right tool for a task, saying so out loud builds more trust than overselling.

Is this NZ Privacy Act aware?

Yes. The safe-usage rules are framed around handling personal information under the Privacy Act 2020 — in plain terms, what staff may put into which tools and what must stay inside your systems.

Bring the team. Bring the scepticism.

A short call is enough to work out whether training, automation, or neither is the right next step for your team. If your people do not need a course, you will hear that too.