Re: Storyboarding for an Established Application

Subject: Re: Storyboarding for an Established Application
From: jlshaeffer -at- aol -dot- com
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Sun, 08 Feb 2009 20:28:52 -0500

My guess:Â

Someone feels that the pop-up help is going to be weak inÂ

* giving a top-down overview

* describing how parts of the system relate to each other

* describing how users navigate from one part to anotherÂ

Since a storyboard is (in essence) a visual narrative, it makes sense for conveying that type of overview and workflow information.Â

My take:Â

Don't get hung up on formal systems. Screen captures with connecting arrows and highlights on screen elements that might otherwise be missed should do it.Â

But, I'm not in your shoes, so what do I know?

Good luck,

Jim Shaeffer

-----Original Message-----
From: Anthony <italian_scribbles -at- yahoo -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Sun, 8 Feb 2009 7:37 pm
Subject: Storyboarding for an Established Application

Hello Everyone,

I have the oddest situation at my workplace and would like to get some input.

Late last week my boss asked me to storyboard an internally developed piece of
software that essentially tracks and captures the details of technical issues
worked by one of our technical teams. Essentially a trouble ticket system
similar to those used by help desks. The application uses a web based GUI.

The oddest part is that the application has already been launched and has been
in active use since October of last year. A user manual has already been
published, but is outdated and the storyboards are not intended to be used to
update th
e manual. In fact, the manual is going to be replaced by a pop-up type
of help that will explain most of the individual fields, screens, menus,
buttons, etc. in the system.

In qualifying this project I found that there is no desire for highly technical
UML diagrams or the like that I have done in the past. The resulting
storyboards are to be used by the users and the assigned programmers who code
upgrades and correct bugs in the system. It is to give everyone a better
understanding of the system.

My thinking is that we need some very narrowly defined use cases as well, but I
am unsure.

Has anyone else run into such an odd situation?

What details would you include and exclude in the storyboarding process?

It is a first for me in my many years of software development and documentation.


Thank you for your assistance.

- Anthony


ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Storyboarding for an Established Application: From: Anthony

Previous by Author: Re: Exempt status for Tech Writers
Next by Author: Re: Help with job titles, pleaes
Previous by Thread: Storyboarding for an Established Application
Next by Thread: Re: Storyboarding for an Established Application

What this post helpful? Share it with friends and colleagues:

Sponsored Ads