Corporate e-learning with Articulate: Storyline or Rise?
The first question on a corporate e-learning project is usually which tool to build it in. Within the Articulate ecosystem there are two answers, and the difference between them is not a matter of taste but of the type of work. A project started with the wrong tool tends to get rewritten halfway through.
Two tools, two different jobs
Storyline works on a slide basis and gives you full control over the state, triggers and variables of every object on screen. Branching scenarios, software simulations, decision trees and complex assessment logic are built with it. The trade-off is production time: the effort required for the same content is noticeably higher.
Rise 360 is block based and responsive by default. By stacking text, image, accordion, card and quiz blocks you can produce a professional lesson quickly. There is no free-form layout; that looks like a limitation, but it is precisely the limitation that guarantees the result works on a phone.
The choice comes down to three questions
First, depth of interaction. If the learner has to make a decision and see its consequence, Storyline. If conveying information in an orderly, readable way is enough, Rise. Second, update frequency: for content revised several times a year as regulation changes, the maintenance cost of Rise is dramatically lower.
Third, device. If the content will mostly be consumed on a phone, Rise does the right thing by default, whereas achieving the same result in Storyline takes a separate design effort. In practice many projects use both: the body is produced in Rise, with a simulation section built in Storyline and embedded.
SCORM, xAPI and the LMS side
Depending on the version and course settings, a SCORM package can send completion, success, score and some quiz-response data to an LMS. Which of those details the system stores and reports also depends on the LMS; video behaviour and every click are not reported automatically.
xAPI can send learning activities defined by the content as statements to a learning record store (LRS). The course, publishing settings and record system all need to support that setup. First decide what data you need and why, then check what the organisation's existing LMS or LRS can handle.
Accessibility has to be discussed up front
Public sector and large enterprise projects expect e-learning content to be accessible too. That is not a layer you can add at the end of production. A meaningful focus order, alternative text on every image, captions and transcripts for narration, and never using colour alone to carry meaning all have to be planned from the start.
Drag-and-drop style interactions in particular need an alternative that works with the keyboard. Adding that alternative afterwards usually means redesigning the interaction.
The mistake made most often
Taking an existing slide deck and simply making it clickable. What comes out is not e-learning, it is a page-turning PDF. Interaction does not mean adding buttons; it means the learner makes a decision and sees the result of that decision.
A production flow that works looks like this: agree scope and learning objectives with the subject matter expert, write the scenario as text and get it signed off, build a prototype of a single module and pilot it with a small group, then roll out the remaining modules. Projects that skip the prototype stage discover their mistakes in the most expensive place, after delivery.