ASSESSMENT AND IMPLEMENTATION

Teach the team to use AI on the work they actually do.

A compelling demonstration can leave everyday work unchanged. Stolen Orbit proposes practical adoption programmes built around real tasks, approved tools and explicit output checks. The aim is to help people choose an appropriate approach, verify the result and recognise when to stop or ask for help.

Let’s discuss your process

Different skills for preparing, reviewing and managing work.

A person drafting an answer needs to supply useful context. A reviewer needs to spot missing facts, weak sources and unsupported conclusions. A manager needs to know who receives exceptions and when a workflow should be paused. In a small company one person may hold several roles, but the skills remain different.

Start with the tools the organisation has approved and the tasks people are permitted to perform. Use synthetic examples or data authorised for training. Participants should not need to upload confidential documents into personal accounts simply to complete an exercise. For multilingual groups, agree the working language and examples before the programme.

Example workshop: review a support response.

In this illustrative exercise, participants receive a customer request and a short procedure. They prepare a response, then compare it with an answer containing a plausible detail that is deliberately absent from the source. Their task is to identify the defect and improve the review method.

Activity and observable learning
ActivityEvidence of understanding
Supply contextName the objective, audience, source and missing information
Review the draftSeparate documented facts from inferences and proposals
Handle uncertaintyRequest missing details without inventing an answer
Hand work overProvide the draft, sources and unresolved approval points

A possible structure for the programme.

  1. Establish the starting point

    Collect frequent tasks, concerns and tools already in use. An initial exercise helps distinguish unfamiliarity with the interface from difficulty judging the output.

  2. Practise a few relevant tasks

    Use role-specific exercises and reusable task instructions. Participants compare different results for the same input and discuss what makes an output acceptable.

  3. Rehearse failures

    Introduce incomplete sources, conflicting instructions and out-of-scope requests. Practise explaining a limitation, inspecting the source and handing the case to its owner.

  4. Support early use

    The agreed scope can include a later review of examples collected by the team, revisions to task sheets and an internal owner for recurring questions.

Assess independent judgement, not just attendance.

Activated accounts and positive feedback at the end of a session do not establish improved work. A useful assessment gives participants an unfamiliar example and checks whether they select a relevant source, identify an error and complete the handoff without continuous assistance.

Training should leave concise task sheets covering permitted work, approved data, review criteria, failure examples and escalation owners. Update those materials when a tool or procedure changes. One session should not be assumed to solve access, adoption and process ownership at once.

Choose training that fits the operating environment.

NIST places clear responsibilities and personnel preparation within AI risk management. It provides organisational context, not a certification of the training. Any formal, regulatory or professional training requirement needs its own agreed scope and the relevant qualified owner.

  • Exercises correspond to tasks participants genuinely perform.
  • Data, tool and process owners approve the scope before the workshop.
  • Practical evaluation and error discussion accompany feature explanations.
  • Materials can be revised and have an owner after delivery.
FROM IDEAS TO A BRIEF

A template to work from.

AI team training plan

A role-based plan with exercises, approved materials, readiness criteria and a support channel after the session.

Download the Markdown template

Human review plan

Routing and approval rules with named roles, review evidence, handling windows and a fallback when the reviewer is unavailable.

Download the Markdown template

AI rollout plan

A staged plan with owners, acceptance evidence and instructions for stopping and recovering work.

Download the Markdown template

Practical questions

Does the team need prior AI experience?

No. The programme can begin with fundamentals, but it should match the group’s actual starting point. Substantially different roles or experience levels may need separate exercises and assessments.

Will we receive a prompt library?

The scope can include reusable task sheets and instructions for the selected work. Each needs approved-data boundaries and output checks. A phrase to copy without review criteria is not sufficient to establish a reliable process.

Does this certify organisational compliance?

No. This is a practical training proposal. Formal requirements, qualifications or compliance assessments require a specific scope and are not implied by the programme described here.

References and method

NIST — AI Risk Management Framework 1.0: Core

Organisational reference for operator responsibilities and preparation, separate from certification or legal assessment.

Which process should improve first?

Start with a concrete process, the systems you use and the people who will operate it every day.

Let’s discuss your process