How your team names courses, lessons, and other content within the LMS can set the stage for a high level of organization and efficiency.
You as an admin are building a lesson. This lesson will include introductory concepts for onboarding new managers. At first glance, it may seem the easy option to simply name this lesson “Introduction Concepts.” However, this only tells us one part of the lesson and therefore, not enough to make sure another admin can easily find it.
A better option is to name this lesson “Introduction Concepts - Onboarding - New Managers”.
This may seem like a long title, but it tells us exactly what we need to know about what is covered in the lesson. This also gives us an idea of what course it can be included in and what content will need to be included in the lesson. All bases are covered and it will be easily organized.
Below are a few tips for determining a Naming Convention for your team:
- Create a naming template
- However your team decides to name items within the LMS, set a standard to be followed in all cases. Type up this template to make it official and save it for all administrators to have access to so that it can be referenced when creating a new item.
- A template example for lessons, following the above use case, could be: “what will be covered - stage of learning - who is the lesson for”.
- Collaborate with your team
- Individually, you can set rules and follow a pattern for naming items within the LMS. However, if the other Tovuti admins within your organization aren’t on the same page, item lists can quickly become cluttered with others’ version of naming conventions.
- This doesn’t mean that the other admins are doing things incorrectly, it just means that there needs to be a level set across your entire team. When formulating your organization’s rules for naming, make sure the rules are ideated and set with the entire group.
- If changes need to be made, communicate them thoroughly
- Your admin team is unique to any other team using Tovuti. As you continually master Tovuti, your organizational needs will evolve. All changes should be done in council with the rest of the team and never individually.