Why training matters
After a website project, your team needs to know how to manage the site. Good training helps teams feel confident and avoid common mistakes.
For more on training services, see training and workshops.
What to cover in training
1) Content updates
How to update content without breaking the site.
- Editing pages: How to edit text, images, and other content.
- Adding pages: How to create new pages and structure them.
- Managing media: How to upload, optimise, and organise images.
- Content best practices: Writing for the web, accessibility basics, SEO basics.
2) Basic maintenance
Essential maintenance tasks teams can do themselves.
- Software updates: When and how to update CMS, plugins, themes.
- Backups: How backups work and when to restore.
- Security basics: Password management, user accounts, basic security.
- Monitoring: What to check regularly and when to get help.
3) Common tasks
Tasks teams will do regularly.
- Form management: How to view and manage form submissions.
- User management: How to add, remove, and manage user accounts.
- Analytics: How to access and understand basic analytics.
- Troubleshooting: Common problems and how to fix them.
4) What not to touch
Important: what teams should not change without help.
- Code: Do not edit code unless you know what you are doing.
- Core settings: Do not change critical settings without guidance.
- Database: Do not modify the database directly.
- When to get help: When to contact support instead of trying to fix things.
How to structure training
1) Hands-on practice
Training should be practical, not just theoretical.
- Live examples: Use the actual site for training, not dummy content.
- Practice tasks: Let teams practice common tasks during training.
- Real scenarios: Cover real situations teams will face.
2) Documentation
Provide written documentation teams can refer to later.
- Step-by-step guides: Clear instructions for common tasks.
- Screenshots: Visual guides showing where to click and what to do.
- Video recordings: Record training sessions for later reference.
- Quick reference: One-page cheat sheets for common tasks.
3) Follow-up support
Training does not end when the session ends.
- Q&A sessions: Schedule follow-up calls to answer questions.
- Support access: Provide access to support for questions.
- Review sessions: Schedule review sessions after teams have used the site.
Training formats
1) In-person training
Face-to-face training works well for hands-on learning.
- Best for: Teams who prefer in-person learning, complex topics.
- Benefits: Immediate feedback, easier to ask questions, better for hands-on practice.
- Considerations: Requires scheduling, may need travel.
2) Remote training
Remote training works well for most teams and topics.
- Best for: Most teams, flexible scheduling, no travel needed.
- Benefits: Convenient, can be recorded, accessible from anywhere.
- Considerations: Requires good internet, screen sharing, and clear communication.
3) Hybrid training
Mix of in-person and remote training.
- Best for: Large teams, multiple locations, different learning preferences.
- Benefits: Flexibility, can accommodate different needs.
- Considerations: Requires coordination and planning.
Who should attend
Training should include everyone who will manage the site.
- Content editors: People who will update content regularly.
- Site administrators: People who will manage users, settings, and maintenance.
- Decision makers: People who need to understand what is possible and what is not.
How long training should take
Training length depends on site complexity and team needs.
- Simple sites: 2-3 hours may be enough for basic content updates.
- Complex sites: Full day or multiple sessions for complex sites with many features.
- Ongoing training: Series of sessions over time for comprehensive skill building.
Making training stick
1) Start with basics
Begin with the most important tasks teams will do regularly.
- Prioritise: Focus on tasks teams will do most often.
- Build confidence: Start with simple tasks to build confidence.
- Add complexity: Gradually introduce more complex topics.
2) Use real examples
Use the actual site and real scenarios, not dummy content.
- Real content: Train with actual pages and content teams will manage.
- Real scenarios: Cover situations teams will actually face.
- Real problems: Show how to handle common problems.
3) Provide documentation
Give teams documentation they can refer to later.
- Written guides: Step-by-step instructions for common tasks.
- Visual guides: Screenshots and videos showing how to do things.
- Quick reference: Cheat sheets for common tasks.
4) Offer follow-up support
Provide ongoing support after training.
- Q&A sessions: Schedule follow-up calls to answer questions.
- Support access: Provide access to support for questions.
- Review sessions: Schedule review sessions after teams have used the site.
Common training mistakes
Avoid these common mistakes:
- Too much at once: Overwhelming teams with too much information.
- Too theoretical: Not enough hands-on practice.
- No documentation: Not providing written guides teams can refer to later.
- No follow-up: Ending training without ongoing support.
Summary
What to cover: content updates, basic maintenance, common tasks, what not to touch.
How to structure: hands-on practice, documentation, follow-up support.
Formats: in-person, remote, hybrid.
Making it stick: start with basics, use real examples, provide documentation, offer follow-up support.
For more on training and workshops, see training and workshops. For more on handing over websites, see handing over your website. For more on working with developers, see working with web developers. You can also get in touch to discuss your training needs.