Learning paths for your work
Start with a task and choose the training that helps you address it. These paths show how programmes can connect around each person’s work.
Any stage may be enough on its own. Choose only the stages you need; your experience can replace a stage. Before starting, we agree tools, access and preparation.
Coordinate projects and documentationThe team records tasks, but priorities, context and next steps are unclear.
Where to start
Start by agreeing how to work if needed. If you can already prioritise and review tasks, enter at the tool you use.
What to prepare
A fictional project, brief and prepared tasks; an account and usage permissions for the selected tool. Configuration and connections are separate scope.
Agree the working routine
Choose the option that fits your work.
Work in your tool
Choose the option that fits your work.
Prepare plans and progress updates with AI, if useful
Include this stage if you need it.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
Keep criteria, priorities and context. If you combine tools, prepare a copy of the material in the selected one; AI-assisted updates can start from manually supplied text.
-
Agree the working routine to Work in your tool
- Useful material
- Completion criteria, priorities and fictional tasks.
- What to check before continuing
- Another person can explain the work and locate the blocker; a copy is prepared in the selected tool.
-
Work in your tool to Prepare plans and progress updates with AI, if useful
- Useful material
- A brief and progress record exported or supplied manually as text.
- What to check before continuing
- Distinguish progress from approval and commitments from proposals; check AI-tool access.
A useful next step
Check whether another person can find the context, explain the status and continue the task. If they can, this may be enough.
From everyday use to looking after the systemSomeone needs to configure and maintain the workspace the team uses.
Where to start
Everyday use is an optional entry point. Experienced users may begin at configuration; completing a user course does not grant permissions or automatically establish readiness to administer.
What to prepare
Choose one tool already in use, a classroom environment, configuration permissions and test profiles. Confirm required plan features before agreeing the next stage.
Know the tasks the team performs
Choose the option that fits your work.
Configure and maintain the same tool
Choose the option that fits your work.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
Continue in the same tool. Usage needs inform the structure, but configuration requires its own responsibility and permissions. Filtered views do not replace access controls.
-
Know the tasks the team performs to Configure and maintain the same tool
- Useful material
- Usage conventions, required fields and a work-handoff issue.
- What to check before continuing
- The participant can explain system usage and has classroom configuration permission; keep the same tool.
A useful next step
Leave a short maintenance guide and test a handoff with the classroom profiles. Choose further training when a specific need arises.
Automate a task and know how to review itThe team copies information between tools and needs to understand the workflow, failures and limits.
Where to start
Start from the environment your team uses. Basic creation can be skipped if you can already explain inputs, fields, actions and executions. Maintenance and AI cover shared principles adapted to your tools.
What to prepare
Classroom data, known fields and identifiers, and checking criteria. For execution in the chosen tool, confirm the test environment, accounts, connections and permissions. For AI, check model access through a native integration or API, features and usage limits for the edition.
Build in the available platform
Choose the option that fits your work.
Diagnose and recover in a controlled way
Include this stage if you need it.
Add an AI proposal with human review
Include this stage if you need it.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
The introductory tool courses are optional alternatives. Maintenance and AI adapt to the client’s environment without requiring a platform change or every stage. Retain the map, criteria and tests; check features, permissions and recovery or usage as applicable before each edition.
-
Build in the available platform to Diagnose and recover in a controlled way
- Useful material
- A field map, identifier, data-changing actions and test results.
- What to check before continuing
- Locate an execution and distinguish incomplete data from a failure. The continuation adapts diagnosis and recovery to your team’s tool; its options are checked before the edition.
-
Build in the available platform to Add an AI proposal with human review
- Useful material
- An input/output contract, test data and the human review point.
- What to check before continuing
- Explain the basic workflow and check model access, features and usage in the chosen environment. You can enter AI without taking maintenance.
-
Diagnose and recover in a controlled way to Add an AI proposal with human review
- Useful material
- Failure cases, execution checks and stopping or review criteria.
- What to check before continuing
- Distinguish controlled recovery from rerunning the whole workflow and agree how to add and check the AI step in your tool.
A useful next step
Keep the workflow map and tests of complete, incomplete and repeated inputs. Use them to decide whether you need to build, maintain or add an AI proposal.
Keep sales work movingThe team loses opportunity context or fails to leave a next step another person can continue.
Where to start
Begin with everyday CRM usage if needed. If you already maintain contacts, context and next actions, enter at AI-assisted sales preparation or configuration according to responsibility.
What to prepare
One client-selected CRM, a B2B process and fictional records. Configuration requires its own permissions; AI needs an authorised account and data review.
Keep context and the next action
Choose the option that fits your work.
Prepare the conversation and follow-up
Include this stage if you need it.
Configure only if it is your responsibility
Include this stage if you need it.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
Keep the chosen CRM. A fictional record can provide context for AI-assisted sales preparation; quality issues go to the configuration owner. Configuration is a branch based on responsibility.
-
Keep context and the next action to Prepare the conversation and follow-up
- Useful material
- A fictional opportunity or relationship record: context, agreements, gaps and next action.
- What to check before continuing
- Another person can resume the relationship; keep the CRM and confirm the AI tool.
-
Keep context and the next action to Configure only if it is your responsibility
- Useful material
- Data-quality issues and conventions needed by the user team.
- What to check before continuing
- The participant has configuration responsibility and permissions; CRM usage alone is not enough.
A useful next step
Hand over an opportunity or relationship another person can resume, with context and a next action. Take structural questions to the CRM administrator.
Use AI in the team’s toolsThe team wants to prepare useful information with AI and review the result in its usual environment.
Where to start
Fundamentals and Prompting are optional entry points. Start at the tool if you already supply context, give instructions and check a response. Choose one available tool; learning all four is unnecessary.
What to prepare
An authorised account and fictional text. For Copilot/Gemini check the specific application features; general chat access does not establish integrated access.
Understand and choose a task
Include this stage if you need it.
Prepare a reusable instruction
Include this stage if you need it.
Practise in the available tool
Choose the option that fits your work.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
Keep a source, context, instruction and review checklist. The task is adapted to the available tool; there is no need to change suites or take every option.
-
Understand and choose a task to Prepare a reusable instruction
- Useful material
- A task-selection and response-checking checklist.
- What to check before continuing
- Identify the objective, source and missing details without filling gaps.
-
Understand and choose a task to Practise in the available tool
- Useful material
- Guidance on context, review and authorised data.
- What to check before continuing
- Have access and a suitable task; taking Prompting is not required to enter.
-
Prepare a reusable instruction to Practise in the available tool
- Useful material
- A template and test record adapted to the selected course task.
- What to check before continuing
- Compare variants and retain unknown details as outstanding questions.
A useful next step
Repeat the task with another example, check the result against the source and leave the instructions and outstanding questions. Addressing that everyday task may be enough.
Decide where to try AI and how to review itLeaders need to choose a task, agree limits and decide whether a trial should continue.
Where to start
Enter Adoption directly with a known process, without coding. Tool practice is for the group performing the task; not everyone needs both stages.
What to prepare
A known process, decision and review owners, fictional notes and criteria covering quality and total effort. Agree the tool before the trial.
Prepare the decision and pilot brief
Include this stage if you need it.
Practise the selected task
Choose the option that fits your work.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
The pilot brief goes to those practising the task and returns with observations on quality, preparation and review. Each tool retains its own exercise; the shared case and criteria are agreed for the edition.
-
Prepare the decision and pilot brief to Practise the selected task
- Useful material
- A pilot brief: problem, manual alternative, permitted data, reviewer and criteria.
- What to check before continuing
- Participants understand the task and decision owner; tool and accounts are agreed. Training alone does not establish subsequent improvement.
A useful next step
Return to the pilot brief with trial observations and a documented decision: continue, adjust or stop. A prepared decision may itself be a sufficient outcome.
From a specific problem to a reviewable trialYou need to define an idea, test a user journey or review a small code change.
Where to start
Start with a clear brief or first work on selecting ideas. Choose the route and environment to fit the task and the team’s tools. Development programmes are an option for people with prior technical experience.
What to prepare
A defined user, task, fictional data and acceptance criteria. For prototyping, agree the chosen environment, access, features and usage; check specific requirements for the selected option. Development needs Git and a prepared repository.
Define what is worth prototyping
Include this stage if you need it.
Test a journey in the chosen environment
Choose the option that fits your work.
Review code with technical preparation
Choose the option that fits your work.
What you can carry into another stage
If you combine programmes, these materials help prepare the continuation. The classroom case is agreed for the selected edition.
The brief and criteria can inform another practice task. The Softr programme uses its native database; the vibe-coding catalogue adapts to the chosen tool using session data. Codex practises a request filter and Claude Code a CSV importer in independent classroom repositories.
-
Define what is worth prototyping to Test a journey in the chosen environment
- Useful material
- A brief: user, problem, minimum journey and trial acceptance criteria.
- What to check before continuing
- Explain what is outside scope and have data and access to the chosen environment.
-
Test a journey in the chosen environment to Review code with technical preparation
- Useful material
- A brief, acceptance criteria, checks and a bounded change list. Technical work is prepared in its own classroom repository.
- What to check before continuing
- Have experience reading and modifying code, with Git and tests working. The prototype and portal do not automatically become the Codex or Claude Code exercises; each programme needs its own technical preparation.
A useful next step
Hand over what works, how you checked it and what needs another phase. The next decision depends on the task and technical preparation, without requiring a move from prototype to code.
Choose the stage that addresses your task.
Each programme page sets out its scope and preparation. Return to the catalogue to compare a specific course.
View all courses