I led a storyboard review meeting with several of the stakeholders of a "using e-mail" project I am working on. The feedback was very good and was a reminder as to why you review the storyboard before starting development.
I had split the course into two sections: 1) e-mail policies and legal concerns; and 2) simple etiquette. As seems to happen in many of the review meetings I have, the discussion didn't go in the direction I thought it would. I thought discussion would center around the content contained in each slide (which it did eventually). Instead, if started with questioning the organization of the project into two sections. I was pleased to see this topic come up because it is good to catch significant contextual issues early in the project. Without context, learners will be confused about the purpose of the training.
While one suggestion to combine the two sections into one section was appealing (and would be acceptable). The decision was made to keep the sections separate but to try to answer the question "how does this relate to e-mail" in the policy section more obvious for the learners.
It turns out that I did not have to make significant changes to the content of the storyboard. But there were significant changes to the context in which the learning experience will occur. That is good to know before starting development.
What are some of the things that show up at your storyboard review meetings?