I've just finished my Certificate III and IV in Training and Assessment. That's a slightly odd thing for a web person to go and do, so it's worth explaining why — and what it actually changes for the people I work with.
The reason: handover is where projects quietly fail
In twenty years of building websites, the projects that disappointed people almost never failed at the build. They failed a fortnight after launch.
The site went live, it looked good, everyone was pleased. Then the person who was going to keep it updated sat down in front of it, couldn't remember which button did what, decided they'd work it out later, and never did. Six months on the news page still says Christmas hours and nobody has added a product since launch.
That is not a technical problem. Nobody needs a better CMS. What's missing is that the handover was a demo, not a lesson — a confident half-hour of someone clicking through a thing they built themselves, at their pace, using words that mean something to them and not much to anyone else. People nod along in those sessions. Nodding is not learning.
I got tired of watching good work go stale for that reason, so I went and learned how teaching is actually supposed to be done.
What the qualification is, and what it isn't
The Certificate IV in Training and Assessment is the standard Australian qualification for people who train and assess adults — the one a TAFE teacher or a workplace trainer holds. It covers planning learning around what someone actually needs to be able to do, delivering it in a way that suits the person in front of you, and — the part that matters most here — checking they can genuinely do the thing afterwards, rather than assuming.
To be straight about the limits: holding this qualification does not make It's Your Idea a registered training organisation, and I'm not issuing anyone a nationally recognised certificate. What it means is that when I train your team, it's built and delivered properly instead of improvised — planned around your business, pitched at the people in the room, and checked at the end.
What changes for website clients
Handover stops being a demo. It becomes a short, planned session built backwards from the jobs you'll actually need to do:
- Your real tasks, not a feature tour. Add a product, put up a job ad, change the trading hours, load the new team photo. We work through the things your business genuinely does, on your own site, with your own content.
- You drive. You do it, not me. Watching someone else do a thing is how you learn that it's possible, not how you learn to do it.
- Checked, not assumed. At the end you do one unaided, so we both know it landed. If it hasn't, that's useful information while I'm still in the room.
- Something to come back to. A short written guide for your site specifically, or a recording of the session. Nobody remembers a Tuesday afternoon in March.
- More than one person. If only one person in the business can update the website, you have a staffing risk, not a website.
This applies whether it's a site we built for you, a Shopify store, or something you already own that you'd simply like to feel confident in.
What changes for AI
This is the one I'm most interested in. Nearly every small business I speak to has now had the "we should be using AI" conversation, and most have ended it in the same place: someone tried a chatbot, got a paragraph of confident waffle, and quietly went back to doing it the old way.
The gap is almost never the tool. It's that nobody was ever taught how to use it, what it's genuinely good at, or — the important half — where it will let you down.
Training a team on AI properly means covering:
- Which of your jobs it actually suits. Drafting, summarising, rewriting, first-pass research, getting unstuck on a blank page. Not deciding things, and not anything where being confidently wrong is expensive.
- How to ask. The difference between a useless answer and a useful one is nearly always the context you gave it. This is a learnable skill and it takes about an hour to get the hang of.
- What to never trust unchecked. Numbers, dates, prices, legal or safety wording, anything about a real person, and anything a customer will read as a promise.
- Your obligations. What you should not paste into a public tool — customer records, health information, anything commercially sensitive — and why.
- Where it fits your week. A tool nobody has a habit around gets used twice and abandoned.
I use these tools every day in real client work, including on builds where AI drafts and a person decides. That's the honest version I'd teach: useful, unglamorous, and firmly supervised.
Other things worth training on
Once you're thinking about capability rather than deliverables, a few other sessions make obvious sense:
- Reading your own numbers. What your analytics and search data are actually telling you, and which figures are noise. Related: the GA4 numbers worth caring about.
- Getting value from your own tools. If you're on Insights or Monitoring, an hour on what the reports and alerts mean is worth more than another feature.
- Writing for your own website. Not copywriting theory — how to write a service page that answers what people actually ask.
- Not getting caught. Practical security for a small team: passwords, two-factor, and spotting the invoice email that isn't from your supplier.
For existing clients
If I've built or currently look after your site and you've never had a proper session on it, get in touch. I'd genuinely rather you were confident using what you're already paying for than politely stuck.
And for the stalkers
If you've been keeping half an eye on what I'm up to — and going by my analytics, some of you have — the short version is that this is deliberate rather than a mid-career detour. Building things and explaining things have always been the same job for me. This just means the explaining half is now done properly instead of by instinct.
The other half of what I've been doing is in this post: the platform, the tooling, and where the AI and automation work has got to.
Want your team trained on your website, your tools, or AI?
Ask about training → Existing client? Raise a ticketRelated reading
- What I've been building — and what it means for you
- Izzy levels up: she doesn't just explain your reports
- The GA4 reports that actually matter
- Accessible websites: the small changes with the biggest payoff