By organisation
Growing teams
The capability jump without the enterprise machinery
Smaller organisations do not have an L&D department, a transformation office or time for a maturity model. They have a handful of people doing several jobs each, tools bought in a hurry, and a spreadsheet that has quietly become the operations system. Training here is short, practical and done on the team's own work.
1.Getting value from what is already paid for
The situation
Licences were bought as the team grew - a plan upgrade here, an add-on there. Most of the capability inside them has never been switched on, and there is talk of buying something new to solve a problem an existing tool already handles.
In practice
A working audit of the licences the team actually holds, switching on the highest-value features during the session, and making the case to drop what nobody uses. The next purchase decision starts from what is genuinely missing.
2.The whole team using AI on real work in one day
The situation
A couple of people use AI constantly, a few tried it once, and the rest are waiting for permission or a reason. Everyone is too busy for a course that talks about AI in the abstract.
In practice
One facilitated day where every participant brings three real tasks and leaves having done them with an assistant - plus the failure modes, the boundaries, and a plan for their first unsupervised week.
3.Automating the work nobody was hired for
The situation
Weekly reports assembled by hand, data re-keyed between systems, the same email written forty times. In a small team this is a meaningful share of someone's week, and it is nobody's actual job.
In practice
Each participant maps one recurring task, builds a working automation for it during the session, tests it against the awkward cases and hands it over - so it keeps running when its author is on holiday.
4.Growing out of the spreadsheet before it breaks
The situation
The pipeline, the rota or the stock list lives in a spreadsheet one person understands. It has survived every 'we should sort that out' conversation so far, and it will fail at the least convenient moment.
In practice
Recognising which spreadsheets are load-bearing, choosing the smallest real system that replaces each one, and running the migration without breaking the team that depends on it.
Start with the measurement, not the course list
The 8 courses cited above are a starting point. The assessment scores your teams across five dimensions and recommends training against the gaps it actually finds.