I think I do a "pared down" version of a storyboard based on what I've read in the discussion so far. I have two columns in my storyboard (in Word). The first column is content. I put all the written content for a course (audio and written text) into this column. This is what I focus on with the SMEs. I actually don't start developing in Storyline until I get sign-off from the SMEs on this column in the document, which I call a storyboard. I explain to my SMEs that I need a relatively finalized version in order to develop most efficiently (e.g. if I develop with 3 bullet points...and then the SME adds a fourth...I may have to redesign the slide entirely). I find that SMEs don't really care about the final navigation, as long as it flows...which I typically show in an iterative cycle (usually a few slides for the first meeting, and then a couple more times throughout the process to make sure I don't go too far without buy-in). As I go through development, I take a screenshots of my content and put them in the second column in my storyboard called "graphics." If there are multiple layers, I typically just put in one as a sample. Since my SMEs don't have access to Storyline, I find this "Storyboard" document a great way to get feedback. I typically ask my SME to use "track changes" for any content changes and comments for any feedback on graphics. It has worked great for me!