Do You Storyboard Before Building in Rise?

It depends! If I'm the subject matter expert on the course I'm creating I don't always storyboard. If I'm creating a course for someone, I will sketch my rough ideas into a storyboard, so they can give me more fleshed out content. 

Ai has revolutionized how I storyboard. I prompt with create a storyboard for... (add content). This gives me a great starting point. I also use it for scripts/dialogues in my storyboard. I'm working smarter not harder and Ai is the best assistant ever.

After building courses in Rise both ways, I have found that using One Note works the best for me. In One Note I build the outline completely, with links, references, and notations about what type of interaction to use, along the way. Once the content is fully outlined there, I have that on one screen while building the course in Rise on the other. That process has gone very smoothly and quickly for me. 

I actually do a combo... I start the Storyboard in Excel, then, jump into Rise to help with "how" I'm going to present a particular piece of content.

I don't usually storyboard for Rise, but I will draft an outline with the text I want to include. I'll create interactions and add images and links as I go. 

This is perfect timing for me as I am just getting started creating courses.  My workflow so far is to start with the documentation I have created and as I transfer that to Rise, I check for updates and documentation I can attach for reference, which usually is the documentation I am working from.  I'm looking forward to seeing other workflows for this to improve what I am doing.

Given a choice, my ideal is for the content to have been presented as a webinar, with a PPT with detailed speakers notes. I then add additional copy using the recording.

Either way, I like to start the first draft in PPT because my SMEs are used to PPT, and they can add their notes/comments in the review function.

Also, my current project has Vyond videos throughout. I can use the speaker notes to create a first draft of a script and then use the Vyond AI tool to create a first draft.

I love using Rise to store all of my gathered content and leave notes to the SMEs/myself - it helps to have everything in one place.

I typically do an outline, but not a storyboard. I know the content I want to include but how I choose to include it is decided on the way :)

I will generally have some sort of source materials that I am working from, but I actually find Rise a really intuitive way of organising content. I will sometimes have a word doc to get a rough outline together but I will often create an outline directly in Rise, by adding lesson titles, then content headings. I will then flesh out this skeleton with the required information/ text. This is what I will usually send to the SMEs for content clearance, before adding in images/ interactive elements/ scenarios/ case studies/ knowledge checks etc. to bring the content to life. Finally, I can get sign off from SMEs and any senior individuals using the review feature. I also like that if the flow feels off, I can quite easily move sections, or even lessons around.

I’ve found that starting with an outline or storyboard works best for me—it gives me just enough structure to visualize how the content will flow and how each piece will be presented. I typically use Google Docs, especially when collaborating or when SME/stakeholder input is needed without the distraction of visuals.

Storyboarding helps me plan the most effective block types, interactive elements, and supporting graphics. It keeps me intentional with design choices. I don’t even like to open Rise until the outline feels solid. 

That said, it also depends on the project’s complexity—if I’m incorporating Storyline blocks, I follow a different process for that.