Month: July 2026

Need to reuse a lesson you’ve already created? Instead of rebuilding it from scratch, copy the entire lesson to another Rise course in just a few clicks.

If you develop Articulate Rise courses regularly, chances are you’ve created lessons that you’d like to reuse. Maybe it’s a course introduction, a knowledge check, a company policy, or a standard resources page.

While you could recreate the lesson—or even copy blocks one at a time—there’s a much faster option. Rise lets you copy an entire lesson from one course to another, preserving all of the text, images, interactions, and formatting.

It’s a simple feature that can save a tremendous amount of development time.

Why Copy Lessons?

Copying an entire lesson is ideal when you have content that appears in multiple courses, such as:

• Course introductions
• Learning objectives
• Navigation instructions
• Accessibility information
• Knowledge checks
• Company policies
• Resource pages
• Contact information
• Course conclusion pages

Instead of rebuilding these lessons each time, copy them and make any minor edits needed for the new course.

How to Copy a Lesson to Another Course

Copying a lesson takes less than a minute.

1. Locate the lesson you want to copy.
2. Click the three-dot menu next to the lesson.
3. Choose Copy to Another Course.
4. Select the destination course.
5. Open the destination course.
6. Drag the copied lesson to its desired location in the course outline.

That’s all there is to it.

What Gets Copied?

When you copy a lesson, Rise copies everything in it, including:

• Text
• Images
• Videos
• Interactive blocks
• Knowledge checks
• Buttons
• Flashcards
• Labeled graphics
• Accordions
• Process interactions
• Formatting

The copied lesson becomes part of the destination course, so you can edit it without affecting the original.

Create Your Own Lesson Library

Here’s a productivity tip: create a dedicated Rise course that serves as your personal lesson library.

Populate it with lessons you use repeatedly, such as:

• Welcome pages
• Course introductions
• Learning objectives
• Navigation instructions
• Accessibility information
• Frequently used interactions
• Knowledge checks
• Resource pages
• Course conclusion pages

When you begin a new project, simply copy the lessons you need into the new course and arrange them as desired. Over time, you’ll build a library of polished, reusable content that can dramatically speed up course development.

Final Thoughts

Copying lessons between Rise courses is one of the easiest ways to eliminate repetitive development work. Instead of recreating an entire lesson—or copying assets one at a time—you can move complete lessons into another course in seconds.

If you routinely build multiple Rise courses, this feature is well worth adding to your workflow. You’ll spend less time rebuilding content and more time creating engaging, effective learning experiences.

Rise Training

If you need to learn Rise fast, check out my 2-hour virtual instructor-led Rise class.

If you need to show learners exactly where to click, how to enter data, and what happens next, knowing how to create software simulations is one of the fastest ways to build training that actually gets used. The trick is not recording everything. The trick is recording the right task, then editing it into a clean demo, a guided practice, and a scored assessment.

Choose The Right Task First

Before you open any authoring tool, pick one business task, not an entire application. Good simulation topics are short and measurable, such as creating a customer record, submitting an expense report, or updating a ticket status.

Write the task as a simple sequence of steps. Then clean up your screen before recording. Close chat tools, hide notifications, increase display scaling only if text is hard to read, and decide whether you want captions, highlight boxes, or both. This prep work saves far more time than trying to fix a messy capture later.

How To Create Software Simulations In Storyline 360

In Articulate Storyline 360, start a new project and choose Record Screen. Select the application area you want to capture and record the task at a steady pace. Do not rush. Small pauses between actions help Storyline create cleaner step slides.

When the recording ends, import it as step-by-step slides instead of a single video. Storyline can generate view mode, try mode, and test mode. For most projects, create all three, then delete what you do not need.

View mode works for demonstration. Try mode adds prompts so learners can practice. Test mode removes hints and scores the interaction. That structure gives you three deliverables from one recording.

Edit The Slides, Not Just The Recording

Open each slide and tighten the timing. Replace vague captions like Click Here with action-based text such as Click Submit to save the request. Check every hotspot. Auto-generated objects are fast, but they are not always precise.

If a field requires text entry, confirm the typing box is large enough and the acceptable answer matches what the learner should enter. If multiple answers should count as correct, add alternate text entries. Also verify the tab order and focus states if keyboard access matters in your environment.

Build The Same Workflow In Adobe Captivate

If you are using Adobe Captivate, record the task in demonstration, training, or assessment mode. Captivate follows the same logic as Storyline 360, but the editing approach is slightly different. You will typically work with click boxes, text captions, highlight objects, and success or failure actions on each slide.

After recording, review every slide for timing, cursor path, and object placement. Captivate often captures more detail than you need, which is useful but can clutter the lesson. Delete extra captions and shorten long pauses. A shorter, cleaner simulation usually performs better than a perfect but slow replay of the entire process.

Add Practice Without Frustration

A software simulation should feel guided, not punishing. In practice mode, give learners enough support to succeed the first time. Use hint captions, visual emphasis, and clear feedback when they click the wrong area.

For assessment mode, be stricter. Remove hints, limit attempts, and score only the steps that matter. If your real-world task allows variation, your simulation should too. For example, if users can reach the same result from two menus, it depends whether you are teaching the exact path or the business outcome.

Test Like A User, Not A Developer

Previewing is not enough. Publish the simulation and complete it as a learner would. Test mouse clicks, text entry, slide timing, feedback layers, and score reporting. Pay close attention to steps that involve scrolling, small icons, or dynamic menus. Those are common failure points.

If the simulation will be viewed in an LMS, test it there as well. A simulation that works locally can behave differently after upload, especially when completion depends on quiz reporting or browser settings.

Keep The Final Version Tight

The best answer to how to create software simulations is usually this: record once, edit aggressively, and publish only what supports the task. Learners do not need every screen. They need a fast path to correct performance.

When your simulation shows the task clearly, lets learners practice safely, and confirms they can do it on their own, you have built more than content. You have built something people can rely on when the work is real.