Blogs

Tracy's blog 7: document design and technical marketing documents

Posted April 12th, 2008 by TracyC
in

Technical marketing documents are produced with specific attention paid to document design. As we discussed last week in relation to rhetoric and technical marketing documents, writers and designers make a series of key decisions related to the product, the manufacturer, target audiences, availability of resources used to produce the document, and the document’s point of distribution.

Document design: the basics

Tracy's blog 6: white paper research, revisited

Posted March 20th, 2008 by TracyC
in
Since you're about to submit Draft 2 of the white paper, I would like to direct your attention to items we discussed a couple of weeks ago related to research -- especially emphasis on including several types of professionally-oriented sources. When doing research for a document that is as professionally-based and topic/audience-driven as a white paper generally is, it's essential to your white paper's overall success that your research activities are both extensive and intensive. Give

Tracy's blog 5: suggested white paper structure, content/approach

Posted March 3rd, 2008 by TracyC
in

Listed below is a suggested format for your white paper. This covers both length and content:

General structure of white papers

Executive summary: This section is usually 1-3 paragraphs in length, and provides a general outline for the white paper. It will present the paper’s position, and often discuss research methodologies used.

Tracy's blog 4: sample annotated bibliography

Posted February 25th, 2008 by TracyC

Here's a sample annotated bibliography. You'll see that I followed the same basic format for each entry: bibliographic entry first (sequenced in alphabetical order), followed by a 50-100 word annotation in which I describe the information presented within that source, analyze the significance of that information, and assess that source's usability where my hypothetical project is concerned.

Tracy's blog 3: (re-)visiting some important open-source-related issues/questions

Posted February 18th, 2008 by TracyC
in

Last Tuesday's readings explored the the open source movement, its origins, and how it relates those proprietary options more recognizable to us -- namely, Microsoft and Microsoft products. Here are some issues/questions that you may have considered, along with some issues that we will consider at some point during the course of the White Paper Project:

Tracy's blog 2: a bit more regarding documentation review and usability testing

Posted January 30th, 2008 by TracyC
in

Activities for tomorrow and the following Tuesday involve usability
testing for your quick guides. I've placed each of you into a
two-person team, except for one group that has three people due to an odd number of students in the class.

Tracy's blog 1: a bit more about Week 3 activities....

Posted January 19th, 2008 by TracyC
in

This
coming week’s scheduled activities are designed to move you through the
planning stages of the Quick Guide Project to the project’s preliminary
writing and review stages. We will continue to work with project research – both of the product and of user characteristics and communities.

Project Log (Week 7)

Posted May 4th, 2008 by schumble
in

This week in class we were placed into groups for the White Paper Project. Then after getting together and deciding on a topic for the White Paper we completed a group - authored story post for the subject we plan to write about. As a group we decided to discuss Peer-to-Peer File Sharing. Also, during this week we discussed more sample white papers and how effectively or ineffectively they were written.

Project Log (Week 6)

Posted May 4th, 2008 by schumble
in

This week was an introduction to the White Paper Project. In class we read the project description and each deliverable expected. We also went over sample White Papers. We also discussed the Open Source and the Open Source Initiative.

 

Project Log, Technical Marketing Document

Posted May 2nd, 2008 by Qrk

Our group worked well together, but our document was a bit small do allow everyone to contribute. We all made much of our own ideas, but not everyone's got to go on the final project. I suppose this is necessary, as it was only a single page flyer. I, for instance, spent most of my time researching the side effects of Zoloft, but we decided, in the end, that our project didn't need a something that technical, it was more geared to nontechnical layman. I still think I got some excellent data.

123456789…next ›last »