alohahands.com Blog

Storyboarding for Organizational Framework?

August 10th, 2008

I mentioned in my last post that the user should be able to get through the website and know what’s going on.  A lot of animation can be a distraction and could cause the user to leave your site without completing the task you attracted the user there in the first place.  The site should be as simple as possible to navigate.  I read somewhere before that each page should look as if it were and serve as a possible landing page.  I know I’ve often landed on something other than the “home” page and wondered how to get “home” for the substance and contact information.  I really don’t like the feeling that the “contact” information is hidden from me.  Maybe, a search engine feature is not such a bad idea, even for our 5 page project.

Without a clear purpose, how can a project be streamlined for success?  

Organizational framework may call for a storyboard to help resolve a lot of confusion.  A storyboard may just be what’s prescribed for a large project with different contributing divisions.  Storyboards offer a visual identity for the script writers, developers, graphic artists, technical editors, and of course the client.  With a visual reference for everyone to point to, omissions are more likely to be recognized and pointed out.  With the use of a document control system, all users will be able to modify and add to the storyboard when required.  Or, the users will be able to reference the storyboard to answer development questions.  Without a visual reference, everyone could assume to be in agreement and find out later each had something different in mind.  Again, saving time and money and maybe saving a few tears also. 

Entry Filed under: All, web design