Justification for rapid development (no storyboard)
I have a client who gave me an incredibly fast deadline... develop 3 modules, and the first draft of each was essentially due within two weeks. I gave them the option of having me storyboard in PPT with descriptions of interactions, or to rapid prototype right in Storyline, where I could actually program the interactions in about the same time that it would take me to describe them. I showed them Storyline, and they told me to go for rapid prototyping.
I designed directly in Storyline, and even recorded and synced narration. I demo'ed the modules to them, we tweaked them real time, and they were pleased. They sent Draft 1 out to a very large review team, and now... their major stakeholder who holds the purse strings for their funding (and whether they get renewed funding, which is dependent on the success of these modules), is questioning everything.
Now they're asking me to create storyboards, in PPT or Word. I explained to them that it's tedious work to create a storyboard AFTER THE MODULE IS DEVELOPED, and it does not actually achieve anything.
So... do any of you have any advice on how to explain that the whole point of rapid prototyping is to progress quickly beyond time-consuming storyboards and essentially storyboard/develop right in the tool?
Any help is welcomed!