Start With the Work Your Team Does Every Week
Before you add logins and folders, look at the actual work that happens in your office, on site and after hours. A food programme in Cape Town may need one shared calendar for distribution days, while a Johannesburg team may rely on joint document editing for donor reports and board packs. Start there, not with every possible feature.
Keep the first rollout tied to 2 or 3 simple tasks. For most non-profits that means sending mail from named addresses, checking a shared calendar, and saving files in one common space. If staff can see how it helps them answer faster, avoid double bookings, and stop losing versions, they are more likely to use it properly.
Before training day, agree on who needs what access. A volunteer coordinator does not need the same control as a finance manager or an MD. That small bit of planning saves a lot of admin later on, especially when people join mid-project or leave after a short contract.
Set Clear Rules for Message, Calendar and File Use
People adapt quicker when the rules are simple and practical. Write down how your organisation wants mailboxes named, who can share calendars, where final documents are stored, and what must never be kept in personal inboxes. Keep it on one page if you can.
- Use role-based addresses for shared functions, such as projects, finance, support or fundraising.
- Use one calendar for events, leave and deliveries so no one books over a site visit.
- Save working files in the shared document space, not on one laptop or a flash drive.
- Agree on file names, for example date, project name and version number.
- Decide who can edit, who can only view, and who approves final changes.
Each rule should come with a clear reason behind it. Staff are more willing to follow a process when they know it reduces missed meetings, duplicate work and the usual “I thought someone else had sent it” problem. A small organisation in Pretoria can run just as neatly as a bigger team if everyone follows the same basic habits, even when load-shedding interrupts the day.
Run a Short Hands-On Session, Not a Long Lecture
Training works best when people do the task in front of you. Keep the session short, practical and based on real examples from your organisation. Show them how to open mail, accept a calendar invite, share a document, and find older files without digging through ten messages.
For teams spread across Cape Town, Durban, Bloemfontein and beyond, it helps to split training into smaller groups. A support team may need a different focus from a fundraising team, and volunteers may need a slower pace with more repetition. In our experience, 45 to 60 minutes is enough for the first session if it is well planned.
- Demonstrate one task at a time.
- Pause after each step and let people try it themselves.
- Use the organisation’s own examples, not generic dummy files.
- Repeat the steps for mobile phones as well as laptops.
- Give time for questions at the end, not only at the start.
Have one person lead the session and one person available to help quietly with logins and device issues. That keeps the pace moving and cuts the awkward waiting around that usually kills attention.
Help New Users Through the First 30 Days
The first month matters more than the training day. People often remember the demo but forget the steps once they are back under pressure. Plan light follow-up support for the first few weeks, especially if your staff are juggling fieldwork, meetings and inbox overload.
Use a simple check-in routine. Ask what is working, what is still confusing, and which task takes too long. If someone cannot find a shared document or misses a calendar invite, fix the process early rather than waiting for a bigger mess. A few short reminders usually work better than another full session.
A good rule is to confirm the basics after one week, then again after one month. That gives people enough time to test the system in real life. It also gives you a chance to spot devices that are not syncing, permissions that are too tight, or team members who are still using old habits out of convenience.
Prepare Simple Checklists for Staff and Volunteers
Checklists remove guesswork. They are especially useful for volunteers, temporary staff and branch teams that only use the system part time. A short checklist helps everyone know what to do before, during and after a task, whether they are based in Observatory or working remotely in another province.
- Before training: confirm names, roles and device access.
- During training: test message, calendar sharing and file access.
- After training: update passwords, bookmarks and saved contacts.
- Each week: review shared calendars and move final documents into the correct folder.
- Each month: check who still needs access and remove accounts that are no longer used.
Put the checklist somewhere people can reach quickly. If it is buried in a long policy file, it will not be used. A simple version that fits on one page is often enough, and it makes handover easier when someone new joins the team without much notice.
Keep the System Healthy After Go Live
Once the team is working comfortably, do not let the setup drift. Review mailbox names, shared folders, calendar access and mobile device setup from time to time. Staff changes, new projects and board turnover can all create gaps if nobody is watching the admin side.
Security should be part of the routine too. Check that passwords are changed when people leave, that shared access is still correct, and that important documents are not sitting in old personal folders. For non-profits, this is not only about safety, it is also about continuity. When one person is sick or away, the work should still carry on.
Keep one person responsible for admin handover and one person for support queries. That makes it easier for your team to know where to go when something stops syncing or a new volunteer needs access. With the right habits, hosted tools become part of the day-to-day work rather than another thing to manage.
