Skip to main content
Training and guidance

Training for the people who use the software every day

The most expensive software is the software nobody understands. A system that could save an hour a day per person achieves nothing if half the team never learned the shortcut, and no amount of engineering fixes that. Training is the cheapest part of a project and frequently the one that decides whether it succeeds.

Why most software training fails

The standard approach is a single long session on launch day covering every feature in order. Everyone attends, everyone nods, and within a fortnight most of it has evaporated. This is not a failure of attention. It is a failure of design. People cannot absorb a system they have not yet needed, and features demonstrated before anybody has a reason to use them simply do not stick.

We run training differently. Sessions are short and focused on the tasks each group actually performs, using your real data rather than a demonstration set full of fictional names. We teach the daily work first and thoroughly, and leave the occasional administrative functions for a later session with the two or three people who will genuinely need them.

Then we come back. A follow up session two or three weeks after real use has started is worth more than double the time spent on launch day, because by then people have encountered genuine questions. That is the moment training actually lands, and it is the session most suppliers do not offer.

Written notes people keep

Every session comes with written notes covering the tasks that were taught, in plain language, with the specific steps. Not a two hundred page manual nobody opens, but a short practical document that lives beside the keyboard and answers the question somebody has on a Tuesday when the person who knows is away.

For clients who want it, we produce short recordings of the common tasks. These turn out to be particularly valuable for organisations with staff turnover, since a new starter can be brought up to speed without occupying an experienced colleague for half a day.

Different training for different roles

A daily user, a manager and a system administrator need entirely different things, and teaching them together wastes everybody time. Daily users need speed and confidence in a small number of repeated tasks. Managers need reporting and the ability to answer questions from their own screen rather than asking somebody. Administrators need account management, permissions and the routine housekeeping that keeps a system tidy.

Where a client has technical staff, we run a separate and deeper handover covering the codebase, the deployment, the server configuration and the maintenance obligations, so your team can take on as much responsibility as they wish.

General technology training

Beyond our own systems, we provide practical training on the software organisations already use and on the general computing skills that quietly hold teams back. That includes spreadsheet skills beyond the basics, sensible file and document organisation, email management, safe password practice and how to recognise the fraudulent messages that reach every business inbox. These sessions are unglamorous and consistently produce more value than clients expect.

How we train

  • Short sessions focused on real tasks
  • Your own data rather than examples
  • Separate sessions per role
  • Follow up after real use begins
  • Written notes staff can keep
  • Short recordings of common tasks
  • Deeper handover for technical staff
  • Remote or in person as suits you

Topics

  • Systems we have built for you
  • Content management and website editing
  • Business software your team already uses
  • Spreadsheets beyond the basics
  • Security awareness and safe practice
  • Working with artificial intelligence tools

Training questions

Yes. Initial training and written notes are part of every build, because handing over software nobody has been shown how to use is not a completed project. Additional sessions, refresher training after staff changes and recordings are quoted separately.

Often, yes, particularly for widely used business tools and for systems we have taken over maintaining. We need time to learn the system properly first, and we will tell you honestly when a specialist trainer for that particular product would serve you better.

Smaller is better. Groups of up to about eight allow everyone to try things and ask real questions. Larger sessions become presentations, and presentations do not teach software. Where a whole organisation needs training we run several small sessions instead.

Yes, and for software training remote sessions often work better, because everyone is at their own machine using the system exactly as they will afterwards, rather than watching somebody else screen in a meeting room.

Is your team using only half of what you paid for?

A short round of focused training usually recovers more value than any new feature would, and it costs a fraction as much.