English
6700

Document Design and Production

Spring
2016

 

Book and long report design

Readings

Design readings

 

Discussion questions

Q1.

Many designers recommend using storyboarding as a technique for organizing long documents. There you draw a sketch or a write a summary of the contents and hang them all on the wall. You could also use Post-it notes. This lets you rearrange them as you desire. It gives you a way of checking that the important knowledge is there without getting lost in the details.

weak answer Storyboarding helps the designer to explore the different design options available and identify with any difficult situations that could delay the design process. Arranging a storyboard on the wall allows the design team to focus on only the organization of a document. Storyboarding can be created on a computer but then the designer might focus on other elements of the design, such as size, color or typography. Creating a storyboard first will help to generate a document plan that offers consistency and saves time on each page.

Q2.

A design issue that often gets forgotten is that manuals undergo revision. You ship product version 1 and then start working on version 2. Most of the manual is the same, but some parts change. Without planning for maintenance from the beginning, the design can be very hand-tweaked and will break. (A trivial example is people who format papers with returns and type the running header as the top line of text. Add one line and everything breaks from the rest of the document).

What issues do you have to consider to make sure the design can handle later changes? How do you enforce the initial design choices when later in the development it becomes "just fix it so we can get it to the printer."

Oh yeah. Remember that often the people who buy your product may not upgrade (especially for hardware or mechanical systems) so that earlier versions must still exist and be updated. Some changes might be made to the documentation for customers who have versions 2, 3 and 4 of a product.

weak answer Maintenance of documents is important. You have to plan for it from the beginning. The author needs a good system of tracking files so they can find them when it is time for making revisions.

 

Thoughts to ponder

1.

Recent research has found that headings should be written as declarative statements. Tell the person what is in the section using a phrase. Rather than saying Electrical System, say "Design of the Electrical System" They've also found that Power Point slide titles should be a full sentence ....basically, take what is typically the first sentence on the slide and make it the title.

2.

Farkas says "Document structure remains implicit until it is made explicit." He then explains how both print and online documents tend to use hierarchies, since people naturally think of information this way. Yet, many web advocates seem to constantly claim the web is much better than print because of its use of links. (Interestingly, having a highly complex set of links is what causes people to get lost in hyperspace.) So, the question is: is information structuring really different for print and the web? Are the organizational schemes really different or are some people confused in thinking that flipping a page is totally different from clicking a link. As a follow-on question: what if the person must compare information at two different locations. One example is a physician looking at different test results that are stored in different places in your medical chart (I'm thinking of a person in the hospital , not a clinical setting.). Which works better paper or online? What are the advantages and disadvantages? And who benefits?

On page 62, Gribbons spends most of it talking about selective processing of information and information within a hierarchy. How does this actually translate to page or screen design? What methods and techniques can we use to exploit these factors? And how can the production level factors cause us trouble: different window sizes, not controlling the actually page layout, etc?

3.

In one student's paper, he said "Ultimately, if there is a client, they should have some input on which design is best." Ignoring that there is always a client, how can you trust the client to have much input? What do they know about design? What about the client that has decided it needs to have lots of blue with THIS image on it, even when blue and that image don't fit the message? Notice that Jobs gave the client (Apple product purchasers) basically no input. Of course, we are not a design genius like Jobs, but we still have to walk that line between giving the client what they think they want and what they need, even if they don't know they need it.

 

 

 

 

 

Design by Michael J. Albers Copyright 2016. All rights reserved.
Send me an email.