Podcast · Ep34
Systems Management - Managing People Including Staff & VAs

Three stories of losing a team member, an agency or a VA, and what to put in place so your knowledge and business assets stay with you when people move on.
In the last episode I introduced the five Ps of systems management: people, processes, platforms, passwords and products. This episode is about the first of them, the people involved in your business, whether they're employed directly or they're associates, suppliers and freelancers you hire by the task in today's gig economy.
I want to challenge you with one question. If you lost a member of staff, your web person or a VA, what impact would it have on your business?
I'll answer that through three stories about people I've worked with this year. I won't name anybody, because that would be unfair and some of the stories are a little embarrassing. With each one, I'll give you my thoughts on how to reduce the impact.
Story One: The Junior Team Member Who Left
A Great Opportunity at a Bad Time
The first business had a small team, happily working away on a number of projects. The most junior member was a marketing executive who seemed to love the role and had a great rapport with everyone.
At a particularly busy time, this person received an offer to work at another business, with quite a salary increase. As a young, eyes-wide-open member of the team, they saw a chance to further their career quickly and earn more, and it was a great opportunity for them.
Unfortunately it came at a critical point for the business. They were in the middle of multiple client projects, and everyone on that small team was highly involved. The standard four weeks' notice wasn't enough to keep delivering the work and do a full handover.
The business owner decided to focus on delivery and pull the team's knowledge together later. The marketing executive had come in to relieve busy people doing multiple roles, and those people still understood the day-to-day processes, so the business wasn't massively affected.
What Was Left in One Inbox
Something small and innocuous did hurt their continuity. The business ran on Google Workspace, which bundles Gmail, Google Drive and other apps, much like Microsoft 365, and lets several people share and work on things at once.
They'd left themselves exposed. Many of the resources the marketing executive had worked on lived only in their own account. Some important documents hadn't been shared with the team, and important communications with suppliers, leads and prospects were buried in that one inbox.
When you close down a user's account in Google Workspace, you can transfer everything in it, documents and emails, to another user. Nothing disappears when the person's laptop is wiped, but this marketing executive hadn't kept a good paper trail, used good naming conventions or kept their emails in sensible folders.
Use Role-Based Logins
Newer members of the team, who haven't built themselves into the organisation, are generally the most likely to leave first.
So if you use Google Workspace or Microsoft 365, think about whether those roles should log in to an account with a role-based username, such as support@, office@, help@ or marketing@. That doesn't stop the person having an email alias, perhaps their first name at your domain, for their day-to-day emails. What they log in to is an account that continues beyond their involvement in the business.
If you're about to hire your first VA or member of staff, give some thought to role-based accounts on the services you use. In this example it would have given the business a clearer picture of what that person had been working on, and given the next person in the role access to the inbox and shared folders, so they could see what had gone before.
Experienced business owners often overlook simple systems like this: where we put things, how we name and file them, how we communicate and how we report. Junior, temporary or part-time team members are unlikely to think about them for you.
Story Two: The Agency That Walked Away
Pink Flags Before the Break
My second example is a classic solopreneur whose passion project grew through word of mouth and good self-driven marketing, until the owner became too busy to run the marketing alongside the client work.
About 18 months before the problem, they hired a marketing agency, which wasn't cheap. It ran lead generation through ads, replatformed the website and set up a simple follow-up process that got segmented leads ready for sales conversations with the owner. Without wanting to make it sound too grand, it was an outsourced marketing function.
Over time there were some slightly pink flags, if not fully red ones. Work started taking longer, ad campaigns weren't refreshed often, and the A/B testing had dropped away. The owner had also got wind that the agency was focusing its energies on an entirely different niche.
It culminated in a frustrating conversation in which the agency owner announced they could no longer carry on with this client. Most agencies I've worked with would diligently hand a client over to somebody else. This agency owner's integrity wasn't at that level, and they dropped the client and left them to pick up the pieces.
The Black Box Problem
The business owner relied heavily on the agency, and there was a real risk they would lose their business. They were introduced to me, and I helped keep the systems and process side running.
As I onboarded them, it became plain that the owner hadn't thought to ask how things happened, or to get training so they could do some of it themselves. They'd treated the marketing almost as a black box they didn't want to get involved in.
I get that some clients find digital marketing hard to grasp and never want to manage it. But even associates, VAs and agencies have holidays, things break, and you'll have ideas you want to put in place quickly. Even in an organisation of one, you need knowledge inside your business that goes beyond the people you outsource to.
“Always have a backup plan, and always have a good enough understanding of whatever providers you're working with that you can do some of the key processes yourself.”
Licences That Stopped Working
It was made worse because some of the licences for digital assets the business used had expired, or were no longer accessible to us. That created what I'd describe as technical debt, an inability to keep using something the way it was designed. Resources the owner had paid for stopped working when the agency pulled out, which felt wrong to me.
Whether it's a blog post, digital media assets or social media, make sure you can do the key day-to-day tasks yourself, and stress test that process. Make sure you understand how those things work before either of you is ready to move on.
Agency licences are great because they reduce your costs, but where parts of a project are bought as one-offs or are specific to you as the client, try to get those licences in your own name, even if it means paying slightly more. A specific website plugin is a classic example, such as WooCommerce or its add-ons.
Another client of mine had recently stopped working with an agency, and her website was already out of date. When I reviewed it, the licence for the theme her WordPress site was built on had expired two years before she'd stopped working with the agency.
Whoever does the work, from an agency to a member of staff, make sure you have full control and understanding of how things work. Build in a knowledge share, so the knowledge doesn't leave the building when a relationship ends.
Story Three: The VA Using Their Own Canva
Errors and Back and Forth
The third example is so innocuous that you might be in it without realising. Another solopreneur uses several VAs, and one was creating branding assets in Canva for social media and the website.
Using a VA is a cost-effective way to scale yourself and make more of your working week.
In this case, the VA created assets with errors in them. Neither of them had picked up a couple of slightly incorrect colours and some misplaced fonts, and with deadlines looming there was a lot of back and forth to correct things.
Your Accounts, Your Assets
What surprised me was that the VA wasn't using the business's own Canva account. Canva is hated by designers but loved by business owners, because it makes consistent marketing assets straightforward to build. Team access costs a little more, but this business owner had let the VA use their own account.
That leaves you exposed in three ways. If there are problems, you can't go in and make quick edits or download something in a different format or size, so you rely on a two-way conversation to get it fixed. Any assets created go away when that person stops working with you, so you can't reuse or repurpose them. And your quality and standards are at risk. In your own Canva account you can create brand kits with your core colours, fonts, logos and image assets. A VA without that knowledge, and without those assets in place, is far less likely to match your specifications.
This Applies to Every Online Tool
This goes beyond Canva, because we use far more online software than we used to. ChatGPT and Claude AI are online, and Canva is an online design tool, where we used to install huge applications such as Photoshop on our own devices. Even this podcast is recorded on Riverside and edited in Alitu.
Most online tools let you add users. Make sure the tools you use to create, build or shape your business are your assets, on your logins, with access given securely to anyone working on them. Someone you've hired for design, audio or video editing may use the same tool as you, but if they do your work on their own login, those resources are only available to them.
If you get any push back on this, it's probably the wrong partner. Specialists in design, audio production or development will grasp why you need control and ownership of these assets.
Questions for You to Consider
- If your most junior team member left tomorrow, what would be stuck in their inbox?
- Do your staff and VAs log in to accounts that belong to the business?
- Could you run your key marketing tasks yourself if your agency walked away?
- Have you stress tested any of the processes you outsource?
- Which licences for your website or other assets are in someone else's name?
- Which online tools hold work that only someone else can log in to?
Take Aways to Action
- Set up role-based logins. Give newer or junior team members accounts such as support@ or office@, with their name as an alias.
- Agree naming and filing. Decide where things go and how they're named, so a successor can pick them up.
- Open the black box. Get trained on the key tasks your providers do, and test that you can do them yourself.
- Own your licences. Move project-specific licences, such as a theme or plugin, into your own name.
- Keep assets on your accounts. Give VAs and freelancers access to your Canva and other tools instead of letting them use their own.
Timecodes
Time | Topic |
|---|---|
00:00 | The first of the five Ps: people |
00:33 | What if you lost a member of staff, your web person or a VA? |
01:34 | Three anonymous stories |
02:07 | Story one: the junior marketing executive who left |
03:39 | Four weeks' notice at a critical time |
05:11 | What was left in a Google Workspace account |
07:48 | Role-based logins with email aliases |
10:22 | Simple systems for where things go |
10:53 | Story two: the solopreneur and the marketing agency |
12:25 | Pink flags and the agency walking away |
14:26 | Treating marketing as a black box |
15:59 | Expired licences and technical debt |
17:00 | Stress test your processes and own your licences |
18:04 | The expired WordPress theme |
19:38 | Story three: the VA using their own Canva account |
21:43 | Why your own accounts and brand kits matter |
23:14 | Every online tool, from ChatGPT to Riverside |
24:47 | The three risks of someone else's login |
25:17 | Wrapping up the people side |
26:50 | Contact and next episode |
Filed underSystems

