What Training Does Our Team Get on a Cirro Project?

What training does our team get, and who gets it?

Training is split by role. End users are trained on the specific tasks they do rather than the whole system, and administrators receive a separate session covering configuration, what is safe to change, and what is not. Training is delivered close to go-live so it is still fresh when people start using the system.

Why one session for everyone does not work

A single all-hands training session fails in both directions. End users sit through configuration detail they will never use and lose attention before their own section. Administrators get a shallow pass over the parts they most need. Splitting by role takes marginally longer and works considerably better.

  • End users learn the handful of things they personally do: how to log an activity, move a deal, raise a ticket, or run their own report. Nothing more, because more is forgotten.
  • Administrators learn how the system is put together, how to make routine changes, and which changes have consequences elsewhere. This is the session that determines whether you stay independent.
  • Managers learn the reporting and what the numbers mean, which is usually what determines whether they enforce use of the system.

Timing and repeats

Training too far ahead of go-live is wasted, because people forget. Training is scheduled close to launch. A short follow-up session two to three weeks after go-live is often more valuable than the original, because by then people have real questions rather than hypothetical ones.

What this means for you

Decide early who your administrator will be and make sure that person attends the administrator session. Sending someone who will not own the system afterwards is a common and expensive shortcut.

Next step

For what documentation accompanies the training, read How does Cirro hand over the system to our team?

Related articles