Review Tool for Storyline?

Aug 15, 2012

Hello all.  Anyone know of a good way to collect feedback from users on feedback on deployed courses?  I am sending my course to my client to review and they want to know the best way to provide feedback to me outside of screen captures and Word documents?

Thanks!

65 Replies
Stephen Cone

I know the following is a bit old school, but this is what I have used with some success in the past. I'd be happier if Articulate would expose certain variables so the entire process can be automated:

  1. I add a small text-box to each slide that cotains the "Scene.SlideNumber" (e.g. 1.4, 2.15) that matches the Scene/Slide Number of the slide in Storyline.  Unfortunately, at this time it's a manual task. *
  2. I have on occasion placed this text-box into a "Debug Layer" that can be exposed via a trigger if I want the functionality to continue after development is completed
  3. I publish the course for review and ask that the Reviewers reference the Scene/Slide Number.  This way I don't have to guess what scene/slide they are referring too when the comment is similar to "On the Introduction slide, remove the extra space"
  4. After I receive final sign-off I go through and hide the text-boxes. It seems that hidden content is not included as part of the export process

Granted it's a bit manual intensive but it can be quicker than getting budgetary approval for a new solution.

* I have submitted a feature request asking that Articulate expose the variables that populate the Scene/Slide Numbers and Scene/Slide Titles that are used by the Menu tool so we can create more dynamic templates.  After all if the Menu builder can pull in all the of the titles, we should also be able to.

onEnterFrame (James Kingsley)

Stephen,

I totally agree that Articulate needs to expose those variables and I think it's on their TO DO list. 

We did find a way in our ReviewMyElearning tool to grab the slide number automatically so that the developer doesn't have to add them to every slide. This way you don't have to remove them later. We do it in background and each comment is saved with the scene.slide number. But we have found a way to grab the slide title yet. 

Jason Johnson

Anna Veach said:

So I take it the final answer here is to use a word doc or spreadsheet of some sort and there is not a review tool available - yet. I hope Articulate was reading this discussion. I've worked with a company which had a review tool for their CBTs and it was pretty awesome. You could review each screen, log comments and tag them based on your role (ISD or Graphic Artist) plus who would be responsibel for correcting the issue. So if it was a functionality issue it would be assigned to the designer, etc. Then reports could be run. One other thing that I've noticed that Storyline is in need of is some sort of numbering for the pages. I realize that with truly branching scenarios and such you may not want to have page numbers, but it would be nice to have that option to add it in if you're just creating a quick fairly linear module. It makes it easier to find the page that needs editing or is having functionality issues. Just my two cents! 


Couldn't agree more. Slide numbers need to be available in the IDE for export (Word & otherwise), not just some SDK future roll-out. Even with branching, it would be easy to do a 1.1, 1.1a...or the like.

onEnterFrame (James Kingsley)

I agree they should be available in the IDE. Not just for export but as a variable you could use on screen or in triggers. 

Slide titles as well... on ReviewMyElearning.com we were able to get the slide numbers but not the titles (with constancy) .

Maybe we'll see some of this stuff in the next release. SL is still my favorite tool and these types of items would be icing on the cake!

Jeremy Huntsman

Suggestion: For review, a simple PDF output I believe is the best option for review. In my experience, most of my course ware I create is proprietary and restricted to  very few eyes for viewing, so a third party review tool of filehosting is out of the question. If PDF output was an option, It would make internal/external review an easy process.

Jeff Forrer

I will do my best to provide what I can here for you.  I use it as well as with Allen Interactions (an eLearning company) and we use it on all projects.  We used to use a Flash based tool which was great called QA Buddy which tied to a database, but because of Flash lack of acceptance, moved to JIRA.  It allows us to add JIRA to any tool (Storyline, Captivate, Flash project etc) that we need to get feedback on in regards to internal QA and then client QA on our projects.  There are swimlanes that you can customize for the feedback collected so you can drop issues into buckets as they progress through the QA process.  All parties can see the progression of issues, see which slides they occur on, add comments, pictures, audio, video etc. and change status (you can control this as well which is needed sometimes).

We add it as script to a button in the player in Storyline.  Once clicked you can enter comments/captures etc. and those are collected and stored into your JIRA project forever.  You can change status or deactivate a project or issue any time.

If you want to see screenshot examples or have other questions, feel free to let me know.  JIRA is not free, but it works well and people pick up on it pretty quickly.  Setting it up initially however takes training and there is a bit of a learning curve, but once it is set up, it works very well and the usability which is most important is great.

Sarah Morgan

Hi Jeff! I've used this as well in previous courses and loved it, but I always had a developer on hand to do the script for me. I don't have a developer, but I'm wondering if I can figure it out myself. I know it's a long-shot, but do you have any tips on the script to use? I'm going to take a stab at it, or find someone else who can help me if I can give them some direction.

This discussion is closed. You can start a new discussion or contact Articulate Support.