Forum Discussion
New in Labs: Connected Packages
Can someone please summarize the risks with this? It seems like the Articulate server's are a big dependency of the course(s) working, and this may only be a good option for translated material if you do the multi-language publishing of the course using Articulate's own AI translation capabilities?
Their business model demands Rise be available for authoring and content delivery, so them ceasing to operate is an existing risk for your authoring and content delivery that you will need to risk manage.
The likely risk I anticipate is internal authoring process management of a team, so similar business process to manage this as already.
The big win is an option to keep version control and testing responsibility within the Rise 360 authoring team, removing updates burden from a separate LMS admin role/team.
The best use cases they've outlined, where audit trail of content is not required automatically through the system. Although you can meet that need by archiving published versions within your document repository version control. Again, this is already the case I do for various non-LMS formats as part of contingency workflows where it's a snapshot related to snapshots from other systems used in the larger training and assessment product. That ensures offline digital, offline paper, online localisation, offline digital translated, offline paper translated, all have a version bill of materials.
For information delivery awareness courses where formal assessment is not tied to the course outcome, you can now have a live Rise 360 document delivered via your LMS catalogue, own and maintain it, only one-time bothering with the LMS course creation, testing and comms processes your org or 3rd party provider may have.
Have your cake and eat it to, as many times as you want, quietly making it better each time :)