Google Workspace Training

Less than vendors usually suggest, and more than most businesses budget for — but the useful amount is small and specifically targeted rather than a day out of everyone's week. Most people can find their way around Gmail and Drive without help. What they will not work out on their own are the two or three habits that make the system worth having: that search has replaced filing, that archiving is not deleting, and that a link is better than an attachment. Forty-five minutes covering those beats a full day covering everything.

Because the content that matters differs sharply by role and the wasted time is real. Your administrator needs the console, user lifecycle and the security settings, and none of that is useful to the person in accounts — who needs Forms, Sheets discipline and version history, which in turn means nothing to a field supervisor. One combined session means everybody sits through the three-quarters that is not theirs, and the part that was theirs gets twenty minutes. Four short role-based sessions cost slightly more to deliver and work considerably better.

The administrator before cutover, because they need to be able to answer questions on day one. Everybody else on the day itself or immediately after, when they have an account in front of them and a reason to use it. Training delivered a fortnight in advance is almost entirely wasted — people cannot practise it, so they forget it, and all that survives is an impression that the new system is complicated. Later sessions are better run when a group actually hits the thing they need, rather than pre-emptively.

Not by attendance, which measures nothing, and not by a feedback form filled in while people are still being polite. Look at behaviour a month later. Are attachments still circulating internally, or are people sharing links? Is new work still landing in personal drives? Is the shared mailbox still one password that five people use? Have the questions changed from how do I to is it possible? Those are the signals, they are all observable, and they tell you whether to run a second short session rather than whether people enjoyed the first.

Yes, and for a lot of individual questions it is better than anything we would write — Google maintains a free learning centre covering the applications in detail, and it is the right place to send somebody who wants to go deeper on Sheets. What it cannot do is tell your team how your organisation has decided to work: which shared drives exist, what belongs where, who to ask, and which habits you are deliberately leaving behind. That part is specific to you and it is the part that actually needs a person.

They are usually the group that benefits most from this being done properly, and the group most poorly served by a large group session where nobody wants to ask the obvious question. In practice the answer is a smaller session, a slower pace, one page of written steps, and a named person they are not embarrassed to ask. It is also worth being honest that a few people will need a second pass a month later, and planning for it rather than treating it as a failure.

Per session rather than per person, so a role-based approach does not penalise you for splitting the group sensibly. We quote the sessions, the written one-pagers and the post-cutover availability as separate explicit lines, because the third of those is the one most often left out of a quote and most often the one that decides whether any of it worked.