The Brief from a Johannesburg Advocacy Team
The organisation was based in Johannesburg and worked across policy submissions, stakeholder meetings and community support. Staff were using a mix of personal mailboxes and informal file sharing, which made it hard to keep a clean record of who sent what, when documents changed, and which calendar events were current.
The brief was straightforward: standardise message identities, make shared calendars available to project leads, and give the team one place to store working documents. They also wanted a setup that could cope with travel, low data allowances and load-shedding interruptions, because people were often checking messages from home, in taxis or between meetings.
- Organisation type: advocacy and public-interest non-profit
- Town: Johannesburg
- Need: consistent message identities and shared working tools
- Priority: low admin, low monthly cost, easy handover
Practical Constraints We Had to Work Around
There were a few real-world limits. The team had limited time for training, several staff members used older Android phones, and not everyone had the same level of confidence with folders, calendar invites and shared documents. A full-day rollout was not practical, so we planned the work in short sessions and kept the structure simple.
Security mattered too. The organisation handled sensitive correspondence with partners and needed clear control over who could access admin functions. We also had to make sure the setup would work for staff in Johannesburg, with no dependence on one person sitting at a single computer to keep things running. That kind of risk can cause delays when someone is out of office or power is off.
- Devices: laptops, tablets and mobile phones
- Access need: remote use by staff in different locations
- Admin requirement: clear control over shared mailboxes and calendars
- Support need: simple recovery steps if a password or device was lost
What We Supplied and Set Up
We linked the organisation's domain, created standard message identities for the team, and set up mailboxes so staff could send from a professional address instead of personal accounts. Calendar sharing was configured for project coordination, while document space was arranged for policy drafts, meeting notes and sign-off files.
We also handled contact imports, mobile device setup and admin handover. The setup included access rules for the people who needed to manage users, plus a clean folder structure so documents were not scattered across separate threads. Where the team needed it, we gave guidance on how to use shared calendars for hearings, travel dates and internal deadlines, which saved a lot of back-and-forth.
- Domain linking and mailbox setup
- Shared calendar setup for policy projects
- Document space setup for draft and final files
- Contact imports and mobile device setup
- Admin handover with clear access controls
The Rollout Timeline in Three Weeks
The rollout ran over three weeks. In week one we confirmed the user list, mailbox naming and access levels. In week two we completed the migration work, set up shared calendars and moved core contacts into the new structure. In week three we trained the team, checked mobile access and stayed on hand for go live support.
Because the group was busy with live advocacy work, we kept the process short and predictable. Staff did not need to relearn everything at once. We handled the technical side in stages and gave each user a clear start point, which kept the transition calm and reduced errors. There was a small bit of back-and-forth on folder names, but that was sorted quickly.
- Week 1: planning, mailbox map and permissions
- Week 2: migration, calendar setup, contact imports
- Week 3: training, go live support and final checks
- After go live: ongoing admin help as needed
Results for Daily Advocacy Work
Once the new setup was live, the team had one clear identity for each staff member and a shared structure for projects. Meeting invites no longer lived in separate inboxes, and policy files were easier to track from draft to final version. That made it simpler to prepare for board updates, external meetings and deadline-driven submissions.
The organisation also found it easier to onboard new staff and volunteers because the process was consistent. Instead of piecing together access from different accounts, new people could be added into the same system with the right permissions. The admin load dropped, and internal follow-up became much neater. It was not flashy, just tidy and dependable, which is what the team needed.
- Cleaner message identities across the organisation
- Shared calendars for policy and stakeholder work
- Less duplicate admin and fewer missed updates
- Better continuity when staff were out of office
What We Would Do Again for Similar Teams
For another advocacy group in Johannesburg, Pretoria or Cape Town, we would use the same approach: keep the structure simple, migrate in stages, and train the team in practical steps. That is especially useful for organisations that rely on a small number of people to keep many tasks moving at once. When the tools are easy to use, people actually keep using them.
We would also repeat the same checks on mobile access, admin handover and shared document permissions. Non-profits often need to work with tight budgets and changing project teams, so the setup has to be clear from day one. A good system should help staff focus on the work, not on chasing files or trying to remember where a meeting note was saved.
- Keep naming and permissions simple
- Train users before go live, not after
- Test mobile access for field staff
- Leave clear admin notes for future handovers
Key facts
| Client type | Advocacy and public-interest non-profit |
|---|---|
| Town | Johannesburg |
| Project duration | 3 weeks |
| Core services | Domain linking, mailbox setup, calendar setup, document space setup, mail migration |
| Extra support | Contact imports, mobile device setup, admin handover, security review, team training |
| Outcome | Standardised message identities and shared remote teamwork across policy projects |
