owl home || writing lab and owl || handouts || workshops and presentations || internet resources

Getting Started With Your Report

Understanding the Sections of Your Report

Title page
Abstract
Table of contents
Introduction
Body
Recommendations
References
Appendices

General Technical Writing Guidelines

 

Works Cited

Recommendations

You may or may not need to include a section titled “Recommendations.” This section appears in a report when the results and conclusions indicate that further work needs to be done or when you have considered several ways to resolve a problem or improve a situation and want to determine which one is best. You should not introduce new ideas in the recommendations section, but rely on the evidence presented in the results and conclusions sections. If you find that you need to include a recommendations section you have another opportunity to demonstrate how your research fits within the larger project of science, and the section can serve as a starting point for future dialogue on the subject. It demonstrates that you fully understand the importance and implications of your research, as you suggest ways that it could continue to be developed. Do not include a recommendations section simply for the sake of including one; this will waste your readers’ time and take up unnecessary space in your report.

Amy Gatian offers some specific recommendations for future research in the paper “Discussion Of The Effects Of Screen Layout And Feedback Type On Productivity and Satisfaction Of Occasional Users,” published in the Journal of Information Systems.

Future Research

In the context of this article, an interesting study would be to look at whether visual feedback is actually counter-productive. The implications from findings in this study are that audio feedback from computers is like the audio feedback you get from an alarm clock: it may be annoying, but it is effective. In fact, in this study audio feedback alone was more effective than a combination of audio and visual feedback. One hypothesis potentially worth testing is whether visual feedback, because of the time involved in message translation, i.e., reading, decreases user productivity. Indeed, one of the habits of good data entry personnel is to focus on the data to be entered rather than the visual image of the data on the screen. This procedure speeds up data entry because the operator is not continuously switching back and forth between the screen and the data to be entered.

As previously mentioned, Gibson notes that there is a great deal of diversity in screen layouts and feedback type provided. Given the diversity in screen layouts, it seems appropriate to question which screen layout best promotes user productivity and satisfaction. Clearly, only a few variables can be examined in any given study. While this study addresses lines per entry screen, future research focusing on some of the other variable could provide valuable insights.

 

 

next page go back

This hypertext written by Angela Laflen
HTML and image maps by Erin Karper
August-September 2001


owl home || writing lab and owl || handouts || workshops and presentations || internet resources

This page is located at http://owl.english.purdue.edu/workshops/hypertext/reportw/recommendations.html


topica
Receive weekly tips and updates from Purdue's OWL and Writing Lab!
       

Copyright ©1995-2004 by OWL at Purdue University and Purdue University. All rights reserved.
Use of this site constitutes acceptance of our terms and conditions of fair use.
To contact OWL, please refer to our contact information page so that you email the appropriate person. Requests for help sent to the wrong address may not receive a timely response.