Some folks "storyboard" directly into Storyline. Others use a spiral development method. A few of the handy features that help to plan within storyline are the story view, slides, off-slide objects, the notes field, and .
The story view provides a neat block diagram view of your structure. This is handy for creating a picture of the experience. The downside is this isn't printable and if your diagram is dense, it's hard to read.
The slide area is a nice way to block in planning elements. Using color blocks to indicate types, or adding in brainstormed graphics can help designers pull together plans.
Off-slide objects can contain descriptions of narrative and interactions. A shape with some text that appears to the developer "Allow the participant to practice X part of Y." These aren't printable but they work well to guide development or capture documentation of the process.
The Notes field is the only one that is faithfully exported to Word output. This is handy for sending stuff for review.
The Translation export / import feature produces a Word document containing all of your text elements. This could also be handy but it contains a lot of noise. This noise is necessary if you want to round-trip text back into Storyline.
By rapid prototyping, Bruce means build-as-you-go with a "function as hypothesis" approach. This might occur live in a client meeting as a discussion rages on. Tools like Storyline make it possible to put things together and immediately show stakeholders. "Like this?" style.
9 Replies
Hi Norma,
Well - some of us feel that the tool for storyboarding is Storyline.
If you are going to use PowerPoint, why not just use SL, and if Word, just use the Notes fields.
Or use Rapid Prototyping if your client/culture will allow it, and build directly into the product.
Bruce
Thanks for the quick reply, Bruce. What exactly is meant by Rapid Prototyping?
Hi Norma -
Some folks "storyboard" directly into Storyline. Others use a spiral development method. A few of the handy features that help to plan within storyline are the story view, slides, off-slide objects, the notes field, and .
The story view provides a neat block diagram view of your structure. This is handy for creating a picture of the experience. The downside is this isn't printable and if your diagram is dense, it's hard to read.
The slide area is a nice way to block in planning elements. Using color blocks to indicate types, or adding in brainstormed graphics can help designers pull together plans.
Off-slide objects can contain descriptions of narrative and interactions. A shape with some text that appears to the developer "Allow the participant to practice X part of Y." These aren't printable but they work well to guide development or capture documentation of the process.
The Notes field is the only one that is faithfully exported to Word output. This is handy for sending stuff for review.
The Translation export / import feature produces a Word document containing all of your text elements. This could also be handy but it contains a lot of noise. This noise is necessary if you want to round-trip text back into Storyline.
Very helpful, Steve. Thank you!
By rapid prototyping, Bruce means build-as-you-go with a "function as hypothesis" approach. This might occur live in a client meeting as a discussion rages on. Tools like Storyline make it possible to put things together and immediately show stakeholders. "Like this?" style.
S
Thanks Steve - well put...
Hope that helps Norma, apologies for not explaining the first time around.
Bruce
Hi Norma! Looks like you got some great feedback and tips here from Bruce and Steve
Hi Leslie! I had forgotten to subscribe to replies, so I missed the last couple of posts until I happened to revisit this subject today.
Excellent feedback and explanations from Bruce and Steve.
Thanks so much!
I'm glad Bruce and Steve were able to help you out here Norma, and thanks for the update!
This discussion is closed. You can start a new discussion or contact Articulate Support.