I'm in a new job where I need to storyboard rather than rapid prototype. I'm so used to rapid prototypes (and they work better for me, as I'm not able to visual things without seeing them) that I'm struggling with the transition.
Has anyone successfully made it or help me with any tips? At the moment I am making a very rough prototype in PowerPoint and storyboarding off that. This feels a bit like cheating though!
There's nothing wrong with putting a skeleton together in PowerPoint before fleshing it out with the detail. We'll often design a whole module in its entirety in PowerPoint and then import to Storyline to build.
Hi Katherine. I'm with you on preferring prototyping over storyboarding. If I found myself in your shoes, I'd probably do exactly the same thing!
As an aside, do you know why your new employer is so tied to storyboarding? Maybe there's an opportunity to pilot your rapid prototyping process with a lower-profile project so you can illustrate the benefits to them ...
I prefer prototyping way over storyboarding, but when I worked in an organisation where someone else was doing building there was no choice but to storyboard. I found that asking to see my designs once they had been implemented helped a lot in enabling me to imagine what things would look like and how they'd work once I'd created the design via the storyboard.
Sounds like your company now uses what I call a "text-based" storyboard though you gravitate toward a "mock-up" storyboard. Both of course aim toward the same goal. I would think that if you give reviewers and good feel for the CONTENT to be presented, along with the visuals, you will be successful.
I created a course for lynda.com/LinkedIn learning a few years ago on storyboarding that might give you some ideas on how to blend a text-based storyboard with a mock-up-type one. Instructional Design: Storyboarding
4 Replies
There's nothing wrong with putting a skeleton together in PowerPoint before fleshing it out with the detail. We'll often design a whole module in its entirety in PowerPoint and then import to Storyline to build.
Hi Katherine. I'm with you on preferring prototyping over storyboarding. If I found myself in your shoes, I'd probably do exactly the same thing!
As an aside, do you know why your new employer is so tied to storyboarding? Maybe there's an opportunity to pilot your rapid prototyping process with a lower-profile project so you can illustrate the benefits to them ...
I prefer prototyping way over storyboarding, but when I worked in an organisation where someone else was doing building there was no choice but to storyboard. I found that asking to see my designs once they had been implemented helped a lot in enabling me to imagine what things would look like and how they'd work once I'd created the design via the storyboard.
Hi, Katherine:
Sounds like your company now uses what I call a "text-based" storyboard though you gravitate toward a "mock-up" storyboard. Both of course aim toward the same goal. I would think that if you give reviewers and good feel for the CONTENT to be presented, along with the visuals, you will be successful.
I created a course for lynda.com/LinkedIn learning a few years ago on storyboarding that might give you some ideas on how to blend a text-based storyboard with a mock-up-type one. Instructional Design: Storyboarding
This discussion is closed. You can start a new discussion or contact Articulate Support.