--- title: Storyline vs. Rise Course Design type: article created: '2026-04-05' updated: '2026-04-05' source_docs: - raw/2026-04-03-agility-recovery-soar-course-135240425.md tags: - elearning - articulate - rise-360 - storyline - instructional-design - tech-stack layer: 2 client_source: null industry_context: null transferable: true --- # Storyline vs. Rise Course Design When scoping e-learning projects, the choice between Articulate Storyline and Rise 360 has significant implications for build complexity, required skill sets, maintenance burden, and hardware requirements. This decision came to a head during the [[clients/agility-recovery/_index|Agility Recovery]] SOAR project, where a planned set of four Storyline simulator courses was pivoted to simpler Rise video-based courses. ## Overview Articulate offers two distinct authoring tools under the same subscription: - **Rise 360** — a browser-based, responsive course builder suited for linear, content-forward modules - **Storyline 360** — a downloaded desktop application capable of building fully interactive simulations with branching logic and forced click-through interactions These tools are not interchangeable. They require different skill sets, different hardware, and produce courses with fundamentally different learner experiences. --- ## Comparison | Dimension | Storyline | Rise | |---|---|---| | **Build complexity** | High — requires deep authoring expertise | Low to moderate — template-driven | | **Interactivity** | Full simulator: forced clicks, branching, state-based logic | Limited — video embeds, quizzes, accordions | | **Hardware requirement** | Windows only (no macOS support) | Browser-based, any OS | | **Maintenance cost** | High — updates require the original tool and expertise | Low — edits made directly in browser | | **Learner experience** | Active practice: learner must perform the action | Passive observation: learner watches a walkthrough | | **Best for** | Evergreen process simulations (e.g., CRM setup steps) | Frequently updated content, video-led training | | **Designer skill bar** | Significantly higher; not a general design skill | Accessible to most instructional designers | --- ## The Agility Recovery Case Study The original SOAR project agreement included **four Storyline courses** to train new hires on the tech stack (Salesforce, SalesLoft, ZoomInfo). The intent was to create true simulators where learners would click through the actual interface steps and could not advance until completing each action. ### Why the Pivot Happened Three compounding factors drove the decision to abandon Storyline in favor of Rise: 1. **Skill gap** — The assigned designer (Isalia) did not have deep Storyline expertise. An attempt was made to learn on the job, but the output did not meet expectations. 2. **Hardware constraint** — Storyline requires a Windows machine. The designer was borrowing a Windows laptop to attempt the work, which was not a sustainable setup. 3. **Maintenance reality** — Tech stack tools change frequently. Storyline courses are labor-intensive to update, making them a poor fit for dynamic content like SalesLoft or ZoomInfo workflows. Any future edits would require someone with Storyline expertise and a Windows machine. > "Whatever we put in Storyline has to be very evergreen because it is labor intensive to do." — Gus Donelson, Agility Recovery ### The New Approach The four Storyline courses were replaced with **Rise modules built around screen-recording walkthroughs**: - **Gus (client-side)** records the tech stack walkthroughs, potentially with actual sellers demonstrating daily workflows - **Melissa (Asymmetric)** edits the video recordings and assembles them into Rise modules - Long recordings are chunked into shorter segments to avoid fatigue This approach trades interactivity for maintainability. The learner experience shifts from active simulation to guided observation, which is a meaningful tradeoff — but one the client accepted given the constraints. --- ## When to Use Each Tool ### Choose Storyline when: - The content is **evergreen** (process steps that rarely change) - The learning objective requires **active practice**, not just observation - A designer with **deep Storyline expertise** is available - The team has access to **Windows machines** - The client has internal capacity to **maintain the courses** after delivery ### Choose Rise when: - Content will need **frequent updates** - The team's expertise is in **Rise or general instructional design** - The project involves **video-led walkthroughs** or content-forward modules - Speed of delivery and **ease of maintenance** are priorities - The designer is on macOS --- ## Implications for Scoping When a client agreement specifies Storyline, it should be treated as a distinct line item with explicit skill and hardware requirements confirmed before the project begins. Promising Storyline delivery without a verified Storyline-capable designer on the team is a scope risk. If a pivot to Rise is needed mid-project, the conversation should address: - What interactivity is being lost and whether the client accepts the tradeoff - Who will own video recording (often shifts to the client) - Whether the original contract scope needs to be renegotiated In the Agility Recovery case, the pivot was accepted by the client, but it surfaced underlying tension about what had been sold versus what could be delivered — a dynamic worth surfacing early in future engagements. --- ## Related - [[clients/agility-recovery/_index|Agility Recovery]] - [[meetings/2026-04-03-agility-recovery-soar-course-sync|SOAR Course Project Sync (2026-04-03)]] - [[knowledge/elearning/rise-360-review-workflow|Rise 360 Review Workflow]]