Export to Powerpoint from Storyline

I agree with most on here that the ability to export or "save as" a PowerPoint is a requirement in our industry.  PowerPoint is not going away and it is the preferred medium for developing training in a training department setting.    I have many instructors that provide me with their raw PowerPoint presentations on a variety of different courses.  It is my job to take the PowerPoint info and create an eCourse, save as an LMS and upload to ur company LMS.  Simple right?  Why is PowerPoint needed you ask...

1 - Prior to publishing, the course is reviewed by our leadership for accuaracy, recommended changes etc.  To do this I need to save the SL project as an HTML5 file,  upload to our server and provide them with a shortcut to the link.  I also need to unlock all navigation restrictions to allow them to scrub each slide for content etc.  They do not have the ability to make changes to the presentation.  Furthermore, without the timeline counter they can't tell me exactly where the change needs to be made.  IE. "Change ....at 1.03 on slide 8."

2 - We are required to keep our source files in the event (all the time) that changes or revisions need to be made later on.  Happens all the time as companies grow.  Most of my instructors do not have StoryLine.  For them to make changes they must use the original source file which of course requires me to duplicate the SL back on to PowerPoint to allow them to make changes. Sorry but a static image on a word document doesn't work.

Don't get me wrong, I like using StoryLine because it's the best software out there to use for our LMS but it has some serious limitations. 

I am not sure why you would want to take all the work in Storyline, export back to Powerpoint, edit it and bring it back to Storyline.   All the scripting and cool stuff will be gone.

I export the Storyline to Word and get people to go through the Storyline interactive and type on the Word file all the changes they want to make.

I then update the file and let them look again.

Seems to work well as 99.9 % of staff can use Word but Powerpoint is not so good for staff except as initial screens to load into Storyline to save cut and paste. 

My opinion has changed on this, I have always said why would you want to export to PPT. However Ppt is almost universal and it may be good or bad most SMEs will deliver content in PPT, being able to export something backing PPT that is editable (if only the text) can be better for reviews. Also I have known a few companies want PPTs that they can translate for niche markets where the cost of a full translation is not financially viable.

Looking for urgent options in converting Storyline course to PPT. Reason: Need to support standup ILT. We tried options mentioned by Leslie but they dont turn out to be good quality in PPT format.

Instead of using ppt you could use storyline in the classroom just publish to CD, otherwise I dont see any way apart from taking screen shots yourself

For my 2 cents I would just prefer that Articulate Storyline output functions properly from a local drive. Currently the .exe version either ignores the keyboard or performs random actions when a key is pressed. The html versions are very limited when launched from a Windows 7 environment locally - and not supported.

From my perspective Storyline has a significant disadvantge in support of online/offline presentation vs. Captivate. 

Hi Timothy,

I just sent you the instructions privately on how to share your file with me, so I'll look into your keyboard navigation.  It's also important to note that when requiring users to press a specific key or combination of keys in your Storyline content, be sure to thoroughly test your published output to ensure it works as you expect. Some keystrokes are common keyboard shortcuts in web browsers (F1, ALT+D, CTRL+T, etc) and may result in unexpected behavior.

The parent application—your web browser—will always receive the keystrokes. This behavior cannot be changed. If a conflict occurs, it's recommended that you adjust the design or requirements of your content to avoid the conflicting keystroke(s).

OK, so this may be a different approach...

I am required to submit storyboards for every course I build. I do this first in PowerPoint. Once the storyboard is approved, I import into Storyline and proceed to add all the interactivity.

Now, if some asks for a PowerPoint of my E-learning, I give them my storyboard (or a doctored storyboard).

Hi! I've been asked to quality check a storyline module and the word document export has all the overlays combined into one slide which makes it unreadable and impossible to qa for content. Is there a setting in the export to word that would enable a breakout of the separate callouts individually? 

When I read through Bruce's comments the first time, I have to admit I was a bit confused as to the intent behind it. Looking through all the comments though, it seems to me that his point is valid from the perspective of a classroom trainer. Those of us who do have extensive classroom teaching experience would certainly agree that Power Point is something that should be avoided except as an aid to the points you make during instruction. For classroom instructors, Power Point is something that is not a primary tool, but really more of something we use every now and then when we need a better way to help our participants understand a complex concept that is difficult to just talk through. Converting a WBT course to Power Point is, from this perspective, counter-intuitive.

Now, not all WBT developers actually have classroom experience, and many may not have even written a course. Perhaps these days it may be that most WBT developers have not. In many training shops these days, a course developer will write the course, and then partner with a WBT developer to turn it into a WBT, who may be more talented with graphics and slide design, etc. From this perspective, I think the impulse to turn an SL course into a Power Point is understandable, and may be the only way they can translate the meaning of each slide into something that SMEs can take apart and make comments on, post development IF a storyboard was not used during the design phase.