Technology
Identity provider
Most organisations have an internal identity provider (IDP). Often it's using a Microsoft or Google hosted system. This allows employees to use the same login approach for every attached system.
If you're providing training for customers, and if there's any chance at all that you'll end up with more than one system for them to log into, then you also should consider having a single IDP. Something like Okta or Auth0 by Okta.
Content management
Your precise needs will depend on the types of content you're using. In general, though, a content management system will allow you to store, find, use and reuse content items in multiple contexts.
It should also allow you to manage the full content lifecycle: commissioning, drafting, editing, approval, publishing, and retirement. It should be possible to compare and revert to previous versions, and to define workflows.
You might get away with something as simple as Jekyll with git version control, or need more sophisticated tools like GitBook, Umbraco, Contentful, Xyleme, Inc. or Cadmore Media.
Conversation
Whether it's in conversation with an AI or a real person, we learn by being challenged, by asking and responding to questions. Conversation is (or should be) at the heart of our learning approaches. So, having systems to help facilitate those conversations is essential.
It could be Slack, Zoom (even Microsoft Teams if that's all you have). Or more sophisticated combinations of chatbot and human interaction like you get with modern support systems like Zendesk.
Events management
Even with high-quality asynchronous online learning, we still need times to gather (whether online or face-to-face) - to exchange ideas, to challenge each other, to be enthused.
You might be able to organise those gatherings using tools like Eventbrite or Doodle, or you may have these types of tools built-in to your existing toolset, in your LMS (too many to list) or your ERP software (like Odoo).
You'll probably need something that can handle the marketing, communication, wait lists, perhaps payments, resource planning, even data analytics - and all the processes that make an event happen.
Simulations and assessments
For real learning to take place, you need to give people the opportunity to practice in a safe environment and to receive feedback.
You can do a lot of this using technology, ranging from simple (but well-designed!) multiple choice questions, text or video-based branching scenarios, through to full, virtual reality simulations. The common thread throughout is that the feedback is instant, and decisions or actions have consequences.
The closer to the real-life situation that you're preparing people for, the better.
Of course, the technology needed will depend on the type of things you're creating - but there are generally two parts: the tools used to build, and those used to deliver. As always, the more complex your requirements, the more complex the technology.
People / skills / credentials
Within your technology stack, you will probably need some way to keep track of who you are working with, what skills they should have, and what credentials they have to demonstrate they have those skills.
You might find this capability in your HR system, or may need to add on a Talent Management system or similar.
If possible look for systems that use open standards, like Open Badges or Rich Skills Descriptor. And maybe consider those that integrate with skills libraries like Lightcast Open Skills.
Data analytics
The data analytics components should pull data from across all the other components in order to help you answer questions about how well you're doing.
It's tempting to collect everything and then work out what questions you can ask. If you do, you'll like end up with measurements that mean nothing (like hours of learning for example). It's far better to identify the questions first so you can then decide what meaningful measurements to capture.
