602 for 202C Notes

9.20.2007

Grading Library/Internet Guide: Stuart cares a lot about the front matter, possibly focus on that. Also use full draft review questions to determine grading criteria. “Worth at least a letter grade” (but not quite 50%). Representative / strategic comments throughout the document.

See Shannon’s big-ass list of stuff to do on ANGEL

• Friday:
  • Go over assignment sheet for job application packet.
  • Other chapter 2 activities.
    • Talk about choosing job ads (different and detailed). Think beyond entry level, boring job ads.
• Monday:
• Wednesday:

---

10.04.2007

Grading: Job ad / Cover memo first: for context. Application as a unit.

Friday:

• Rough draft

Monday:

• Go through assignment sheet for #3
  • Not too big (maybe a subset).
  • Easier to scale up than down.
  • Be familiar with the content, because you are unfamiliar with the form.
  • Stay away from well-understood processes, like how to use Webmail or ANGEL.
  • Mention that they can use HTML, InDesign, or Word (html, pdf, doc file(s) for turn-in).
  • Audience Analysis / Planning Worksheet (Planning Worksheet on Monday)
  • Think about beginning with background.
    

    ---

10.18.2007

Recommendation Report:

• Have to find people to write to: can’t write all PSU documents to Graham Spanier.
• Research driven: secondary research and some primary, but not from the standpoint of their engineering classes.
• Assignment #5: Progress Report is the progress report on the Recommendation Report.
• Markel chapter on reports is writing reports in general, with recommendation report being most ambitious. “Report For Decision Making”
  • Highlight they understand that it is the third report that we will be focusing on and actually writing.
• Topic must become question. Approve their research question (must take one of these forms).
• Think about it as an audience question: who are you talking to? what will this accomplish? Concrete and local, not abstract and universal.
• Discussion section on “Format” section is the bulk of the content.
  • Must cite sources using the style guide found on the Library Internet Guide.
• Criteria used in the assignment sheet are not in Markel. Documentation for this will be distributed by Shannon.

---

11.08.2007

• Give a work day next week.
• Possibly use visual supplement stuff.
• Go over Progress Report on Friday / Visual supplement stuff.
  • Mention persuasive aspects of report. Convince me you are getting work done and that things are going well.
  • Also use as an opportunity to communicate any changes being made within methodology and content.
  • Stress specificity. More is better (only time will say in tech writing).
  • Cover every detail you’ve done (even things that haven’t worked).
  • Use progress report in Markel. Good example.
  • 750-1000 words, well structured.
  • Pick organizing pattern that suggest you’ve done the most work.

Schedule:

• Friday: progress report assignment sheet. look at example.
• Monday: Visual supplement stuff.
• Wednesday: Work day.
  

  ---

  
  Examples of letters of transmittal

11.15.2007

Extend due date until Friday (maybe). For next semester, use week 14 for Recommendation Report.

• Monday: Rough draft review of Assignment #4
• Wednesday: Introduce Assignment #6

Annotations for Assignment Sheet:

• Don’t pick too good or too bad document.
• Don’t spend a lot of time on description, I want to hear what you think about the elements you find in the document.
• Maintain professional ethos (don’t say things like “this document sucks”; be constructive in your criticism).
  • Can serve as a writing sample.

Future Activities:

• Share documents with each other in class. Must be available via the internet.
• Discuss NSF catalog from Markel. Possibly other documents from the web.

11.29.2007

• Do survey at some point in next three weeks.

• Grading
  • Mostly focused on the body
  • Good problem statement in intro
  • Usage of sections
  • Check visual
  • Points off for wild claims
  • Points off for lack of research
  • Points off for inflating research

• For Friday:
  • Put them in groups to look closely at a sample usability memo.
  • Answer following questions:
    • What does the introduction accomplish?
    • What is the tone of this document?
    • Do you think the advice is likely to be accepted?

• For future: evidence, rather than research methods.
  

  ---

12.05.2007 Class Notes

• Talk about criteria. How do we arrive at them? Examples from the community.
  • Usability Evaluation Worksheet
  • pg. 542 in Markel

• Evaluate the NMFS website using criteria lists.

• Style & tone: Phrase criticisms constructively and positively, and justify them with good reasons. (i.e. �The format sucks� is less constructive than �Improving the format with clear, bold headings would help users locate information more easily.�) Another strategy is to lead off a section with good news, then move into the bad news. (i.e. �The visual design makes excellent use of color to highlight important information, but the layout of the document could be more consistent�).
• Details and evidence: Rather than just saying �The layout needs improvement,� say �Several aspects of the style could be improved to make the document more user-friendly. For example, the passive voice tends to de-emphasize the user�s actions; imperative commands would be easier for readers to understand. In other words, ��the key should be pressed� is less straightforwards than ��press the key.��
• Introduction and conclusion: Both of these sections should help to build the ethos of the writer and goodwill with the audience. Emphasize why usability is important and why these suggestions will benefit the company.