Kadosh AI
The Programme Directory
Ecosystem
Forty five programmes · Ten themes · Nineteen departments

We do not teach a tool. We take the task your people dread, and give the hours back.

Every programme here starts from a pain point somebody actually named, on a Monday, in their own department. Not a curriculum. A complaint. Then it gets built in the room, tested, owned and measured.

The tools change every quarter. The pain does not. Which is why every programme runs on Microsoft and on Google, and why the ones that matter most run on neither.

Efficiency is the hours removed. Productivity is what those hours become.
One complaint, five moves

The sequence behind every programme in this directory.

01 · The complaint
Named by the person who does it
02 · The task map
Human, machine, or both
03 · The build
A flow, an agent or an app
04 · The proof
Success path and exception path
05 · The hours back
Efficiency counted, productivity decided
45Programmes
10Themes
19Departments
One programme, two ecosystems. Written in full for Microsoft and for Google. The competencies, the tasks and the outcome do not change. Only the buttons do.
?

Which of these forty five is yours?

None of them, exactly. Every programme in here is rebuilt around the tasks your own people name before day one, on your own documents, in the system your organisation already pays for. What you are reading is the starting shape. The finished one is written after we have sat with your departments and heard what actually eats their week.

Pick the department. Pick the role. Tell us where they stand.

Three choices and the climb draws itself, left to right. It shows where to start, what to build, where the applications come from, and how it is held after we leave.

1The department

Nineteen functions. The programmes are cut for the work each one actually does.

2The role

The role is not replaced. It absorbs a second one.

3Where they stand today
AwareUses AI and believes the output

Where the room sits, and where it is going

Move the thermometer and the room moves with it. The goal is the right hand end, where the department runs its own cohorts and we stay on as coaches.

The goal
Aware
Operator
Builder
Architect
Specialist

The climb we would run

All staff · Executive or Officer · today they are at Aware
Today
Executive or Officer
=
Learns
AI in their own workflow
Becomes
AI Operator
The three tasks that move first
  • Drafting documents
  • Re keying data
  • Formatting reports
Stop 00
Stop 01
They start here
Stop 02
Stop 03
Stop 04
Programme content is drawn from KadoshAI proposals and delivered cohorts. Days shown are classroom days.
Specialists in teaching corporate people AI in their workflows