Blogs

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

Technical marketing documents are produced with specific attention paid to document design.  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 12: more about images and technical marketing documents....

Yesterday's readings addressed the use of images. As I’ve mentioned a number of times this semester, images function in pretty much the same way as does text – to communicate information to a target audience in ways that reflect the topic, the immediate writing situation, and the individual, team, or company/organization sponsoring the document.

Tracy's blog 10: reactions to technical marketing documents

I’ve
read your reactions to, and questions about, the Technical Marketing Presentation Project,
and after spending these past few hours thinking about them, here
are some responses. These are designed not only to answer questions that have been raised, but also to guide project planning and research.

Tracy's blog 8b: document design principles

Chapter 25 of our text covers items related to desktop publishing and graphic design (which I'll refer to here as document design).  Although you'll be working with information presented on 8 1/2" X 11" pages, it's important that you take advantage of the many design elements commonly offered by desktop publishing software.  Yes, Microsoft Word can be considered a desktop publishing program -- and many of the updates found in Word 2007 considerably expand Word's range as a desktop publishing program.

Tracy's blog 8a: integrating graphics into your white paper

This week's class sessions focus on the use of visually-oriented items within your white papers.  Yesterday's readings focused on incorporating graphics, while today's emphasize document design features -- so I'll consider these items here in that order.  Blog 8B, which I'll post later today, will look at document design strategies.

Some examples of graphics commonly presented within white papers:

Tracy's blog 7: white paper research, revisited

Tracy's blog 6: research on target audiences

This past Friday, we began the first of a series of units related to research and the white paper. We'll focus here on research and audience analysis. Before beginning to gather information for your white papers, it's essential that you do some background investigation on your target audience. After all, the audience toward which you direct your white paper -- and the position that you'll argue -- will directly influence what kind of information you present, and how you present it.

 

Tracy's blog 5: more on the white paper genre

To gain better understanding of white papers and the White Paper Project as a whole, we should further examine the white paper genre, its history, its constituent sections, its audiences, and its goals.

History

Tracy's blog 4: Important issues related to the White Paper Project

This week's readings explore 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 we will consider at some point during the course of the White Paper Project:

Project Log Week 8

We did very little for the White Paper Project this week.  After sending in our third revision on Monday and recieving a grade of A we all seemed to stop communicating and accepted our good grade.  The final coming together of the paper was mostly done by Mimi, who edited all of our revised sections and made a few changes herself. 

Technical Marketing Project Log 8

We had aim discussions Sunday, Monday, Tuesday, and Thursdy night to discuss design detials and content. We choose on a four column brochure format for our doucment and divided tasks among the group. Kyle did the document specifications, production issues, and design update posts. He also did the FAQ section of the document. I designed the doucment, created the title, results, safety, treatment effects, and how it works panels of the document and added visuals. Matt wrote the comparison panel of the document and did much of the drug interactions content.

Project Log Week 8

Throughout the week both teams have been communicating thru emails and on AIM almost daily.  For the White Paper, we each continued to update and refine our own section of the paper and got everything sent out for review by sunday.  On monday, it didn't seem like anybody else wanted to make any changes because nobody was responding to emails or was on AIM.  Since Chris, Mimi and I were online discussing our Technical Marketing project, we collaborated everybodies sections and submitted our revision to Tracy,

 

Project #3 Project Log Week 8: Completion

The peer review draft was created and submitted. After
feedback was received we worked to make modifications. The first draft was
turned in on Tuesday. This draft received feedback on Wednesday. We worked on
draft 2 of the Technical Marketing Document after receiving feedback from Tracy.

White paper, Final Log

Our group recieved our draft 2 feedback from Tracy and decided to submit another revision. There weren't a lot of changes that needed to be made, so each of us took our section and made any changes that were needed.  The new draft came together very quickly. Our communications were via e-mail because we didn't feel we needed a meeting to make the revisions.  After everyone submited their changes, the draft was reassembled and posted. This was our final revision. We were happy with the feedback we recieved and the project is now finished.

Technical Marketing Project, Final Log

This was the last week for this course as well as the last week for the Technical Marketing Project.  Our group pushed through to the end and were able to deliver a respectable final draft.

Sunday - The team worked hard today to get a peer review draft together. We had an AIM meeting to finalize any changes that we needed to make. I submitted the draft that evening.

Monday - Peer review day. Today we submitted our peer reviews to our partner team and we recieved comments from them.  We didn't work on the poster this day.

Syndicate content