Hey Holly! I typically do the outline first, then I work on each lesson individually. I don't usually storyboard prior to developing since Rise is so fast and easy to use. If I end up having to re-do an activity it doesn't take that long and I find it gives me a better feel for what my couse will look like in the end.
One of the issues I've found with Rise is that it's so easy to create content that a course can get very large, very quickly and, although it all flows nicely, the menu (especially when uncollapsed) can be very intimidating for a learner (because they have no idea how long or short each lesson is).
It's important to think about whether or not every lesson needs to be in the same Rise product or whether a series of smaller Rise products would be better. It's relatively easy copy blocks within a product and to copy lessons between Rise products. The counter-argument too many small products is harder to maintain than a single 'large' product.
There's no right or wrong but an outline is the key in my opinion.
I created a document with the types of content/interactions/blocks and since I'm going to be passing the "outline" to someone else to do the development, I was wondering if others had already devised some kind of shorthand to connect the outline to the options. I'm not necessarily going to do the development myself.
Ah, I understand now. Haven't had to do this so far but I imagine that something similar to a storyboard might work (i.e. a column naming the block type, a column with the script/sketch, a column for any comments/description/clarification). I imagine that your developer will quickly let you know if that's sufficient. When you've devised a method between you I'm sure others will be glad to see your solution.
6 Replies
Hey Holly! I typically do the outline first, then I work on each lesson individually. I don't usually storyboard prior to developing since Rise is so fast and easy to use. If I end up having to re-do an activity it doesn't take that long and I find it gives me a better feel for what my couse will look like in the end.
I'm with Allison on this one - outline first.
One of the issues I've found with Rise is that it's so easy to create content that a course can get very large, very quickly and, although it all flows nicely, the menu (especially when uncollapsed) can be very intimidating for a learner (because they have no idea how long or short each lesson is).
It's important to think about whether or not every lesson needs to be in the same Rise product or whether a series of smaller Rise products would be better. It's relatively easy copy blocks within a product and to copy lessons between Rise products. The counter-argument too many small products is harder to maintain than a single 'large' product.
There's no right or wrong but an outline is the key in my opinion.
Thanks for the input so far.
I created a document with the types of content/interactions/blocks and since I'm going to be passing the "outline" to someone else to do the development, I was wondering if others had already devised some kind of shorthand to connect the outline to the options. I'm not necessarily going to do the development myself.
If I come up with a decent approach, I'll share.
Ah, I understand now. Haven't had to do this so far but I imagine that something similar to a storyboard might work (i.e. a column naming the block type, a column with the script/sketch, a column for any comments/description/clarification). I imagine that your developer will quickly let you know if that's sufficient. When you've devised a method between you I'm sure others will be glad to see your solution.
In that case I would probably create a table with multiple columns:
I hope that helps!
Maybe add another column for feedback (although not all blocks will have feedback)
This discussion is closed. You can start a new discussion or contact Articulate Support.