Not asking questions about various internal use cases
By Stephen Nunn (SumTotal), Indresh Chauhan (Sify), KC Rajkumar (Sify)
No matter what the size of your organization, in all likelihood, it is made up of various departments and divisions – each may have various use cases to consider with respect to onboarding and training. Why is it important to consider internal use cases? And how do you make it happen?
Most organizations have different departments, each with different uses cases, for example:
- When a new, specialized product is introduced in the market, how do you ensure that the training is delivered to the right audience? In the right location? At the right time?
- In another example, Sales and Marketing may have a different onboarding process than say, Finance and Manufacturing. Your LMS must be able to handle the training use cases for each department and their different situations.
- In industries with rigid compliance regulations regarding annual safety training, will your LMS identify which employees need to be certified annually depending upon their date of employment, location, role, etc.? This becomes even more important if an organization has global offices and must comply with different country-level regulations including availability in different languages. In such industries, it is also important to keep in mind the LMS’ ability to allow various training approval processes and reporting requirements.
Because of different use cases that an LMS may need to satisfy, it is important to establish a governance council with membership from all departments impacted early in the LMS buying process.
If you get push-back from departments for documenting the use cases, it is important to help them understand the benefits of the “investment” of time that should be made in documenting various use cases. Among the most important benefits are:
- Better user experience to encourage adoption by the intended audience
- Alignment of workflows to real-life day-to-day scenarios
- Streamlining workflows that may have been previously manual or built to align with a previous solution
- Reducing implementation timelines/costs
- Minimizing later scope changes or change management issues after implementing the LMS
