Monday, March 25, 2019

Week Nine: Mar 11-15


Image result for spring breakOn Monday, I spent an hour after working in the Writing Center working on the power-point presentations I started.  Tuesday of this week, I was able to met with Dr. Lancaster and Ms. Campbell. They told me that they really like the manual and were happy with my work.  I mentioned that I started work on a presentation explaining the manual and how to use it.  They thought this was a great idea and wanted me to present it to some of the faculty who will be using it.  They also want me to lead a workshop on a different day to see if these faculty can use my manual to solve common problems.  Dr. Lancaster also asked for me to find information on semester dates, and the order market segments are sorted.  On Wednesday, I spent time looking for this additional information.  I found information on the semester dates, but I am having a harder time on the market segment information.  I continued this on Thursday morning.  If I am still not able to find this information early the week after spring break, I will go talk to Dr. Lancaster for suggestions.  Also on Thursday, in the afternoon, I spent three hours working on the informative presentation about the manual and created cases for the workshop.  I also began the presentation I will be giving at Honors Showcase over my internship experience next month.  I left for spring break on Thursday evening, so I was not able to work on Friday.
I read two more chapters in The Essentials of Technical Communication, 9 and 10, as well as appendix A.  Chapter 9 was about proposals and progress reports.  I have some experience writing proposals, as I wrote one for my Honors thesis and for this internship, but it was nice to understand them in more detail.  This chapter went over effective arguments and standard sections of proposals.  For progress reports, it discussed structures for them.  It also included multiple examples and style suggestions.  This will be helpful information for the future when I will need to give proposals or progress reports.  The next chapter was about instructions, procedures, and policies.  This chapter most directly relates to my project, as it is like an instruction manual.  It discussed how to plan for instructions and procedures and the structure and organization.  Under the latter section, it went over introductions, theory governing the procedure or instruction, warnings, conditions under which the task should be preformed, and the name of each step.  Following this was examples and exercises.  I think adding an introduction to my manual would be helpful, as it allows the user to better understand what they will be able to do with my manual.  The theory governing the procedure or instruction was also insightful.  It basically said that users will preform tasks better if they understand the process.  I should keep this in mind for my manual, specifically when explain what each section does.  Appendix A was a "Brief Guide to Grammar, Punctuation, and Usage."  I thought this would be a helpful review for me, and I believe it was.  It went over commonly misused punctuation, sentience structures, and words.  This was a helpful refresher that I can use when proof reading my manual.

Hours worked:
Monday - 1 in office, 1 reading
Tuesday - 1.5, 1 reading
Wednesday - 2 in office, 1 reading
Thursday - 1.5 in office, 3 at home
Total - 12
Running Total - 90 

Monday, March 11, 2019

Week Eight: Mar 4-8


Related imageThis week I focused on proof-reading and starting on my power-points.  I mostly focused on the power-point going over the content of my manual.  Next week, I will work on the power-point about how to use the manual.  I was able to set up a meeting with Dr. Lancaster for Tuesday the 12th at 8 am.  Hopefully, at this meeting I will get some good feedback on my manual that I can use going forward.  I went to Oklahoma Research Day on Friday, so I was not able to work.  I plan to make up this hour on Monday.  I will also be gone next Friday so I will find time to come in to make up for that as well.  
In The Essentials of Technical Communication, I read chapters 6 and 8.  They may not have been directly related to my specific project, but they had a lot of information.  Chapter 6 "Designing Illustrations" was about pictures or other animations.  It went over different types of visual aids and how to create them.  It covers tables, bar and column graphs, circle graphs, lie graphs, organization charts, flow charts, project schedule charts, diagrams, photographs, info-graphics, and video clips.  In my manual, I am including snapshots from the Jenzabar system to illustrate my instructions.  The chapter did make me think of some things that I could do with these illustrations.  These include placement, labeling, and more.  Next week I will look over my pictures to make sure they are clear and if they need any changes.  Chapter 8 "Technical Reports" was full of interesting information.  The chapter was about every step to making different types of technical reports.  These include recommendation, evaluation, feasibility, progress, trip, personnel, and economic justification reports.  The most relevant information for my manual was over the table of contents.  I went over the most important components of a table of contents.  While there wasn't a section specifically about this, spread throughout the chapter was suggestions on how to logically order your report.  I will have to look at my manual in the following week to see if it is laid out in the most understandable way.

Hours Worked:
Tuesday - 1.5
Wednesday - 2
Thursday - 1.5
Weekend - 3 at home
Total - 8
Running Total - 78

Saturday, March 2, 2019

Week Seven: Feb 25 - Mar 1


Image result for the essentials of technical communicationOn Monday I emailed my manual to Dr. Lancaster and asked for feedback.  I spent Tuesday, Wednesday, and Thursday working on the spacing and starting a detailed proof-reading of my manual. Friday, I emailed Jennifer Campbell, who I've worked with for one part of my manual, a copy of my manual to ask for her feedback.  Next week, I am going to try to get a meeting with Dr. Lancaster.  I am also going to begin making power-points explaining my manual and how to use it.  After I have finished proof-reading and making these power-points, I will begin creating my presentation over my internship that I will give at Honors Showcase at the end of April.  
On Friday I also began reading The Essentials of Technical Communication.  I already feel like this is going to be an extremely useful book!  The chapters in this book are very dense with information, so they took me longer to read than in the last book.  I read chapters 4 and 5 over Friday and Saturday.  Chapter 4, "Achieving a Readable Style," was tips on the most efficient ways to write you document.  This includes structuring paragraphs and sentences.  Because of the focus on technical writing, most of the advice was about how to get you message across in as few words as possible, from using concrete verbs to active voice.  It also focused on making the document easy to read by using topic sentences, short paragraphs, lists, and more. While I thought some of the tips seemed a little too strict, overall it gave me ideas of what to look out for when proof-reading my manual.  5, "Designing Documents," was tips on making your document fit the project you are working on and easy to read.  It laid out five guidelines to plan you document: know what decisions are yours to make, choose a design that fits your situation, plan you design from the beginning, reveal your design to your readers, and keep you design consistent.  Except for the last one, these don't apply to my manual as I am past the planning stage.  However, I think they will be useful to keep in mind in the future.  The suggestions for designing effective pages and screens, four in total, I found very helpful.  The first was to use blank space to frame and group information.  This means that using blank space isn't wasteful but used to group the information in a way that was easy to read.  The next, set the spacing for easy reading, was related to the first.  The third was to use a medium line length.  I hadn't thought of this before, but it makes sense when writing a technical document to not have lines that are too long or too short.  The last two, use a ragged right margin and position words and illustrations in a complementary relationship, I was already using.  But I enjoyed learning why they are important to do.  Both chapters included helpful examples that I was glad to have.  

Hours Worked:
Tuesday - 1.5
Wednesday - 2
Thursday - 1.5
Friday - 1 in office
Weekend - 3 at home
Total - 9
Running Total - 70

Week Fifteen: April 29 - May 3 This is the last week of my internship.  I spent Monday and Tuesday adding the last section of my manual...