Report Expectations

259 views
217 views

Published on

Published in: Education, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
259
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Report Expectations

  1. 1. Great expectations – what’s in a final report? Ros Smith 06/07/09 | | Slide Joint Information Systems Committee Supporting education and research
  2. 2. What’s in a final report? <ul><li>Activity </li></ul><ul><li>In small groups, discuss the examples on your table and identify good and bad points (20 mins) </li></ul><ul><ul><li>How easy was it to get the information you needed? </li></ul></ul><ul><ul><li>What was exemplary? </li></ul></ul><ul><ul><li>Was anything missing? </li></ul></ul><ul><ul><li>Is there a right and wrong way to produce a final report? </li></ul></ul><ul><li>Use a notetaker to record (10 mins) and feed back your findings (20 mins) </li></ul><ul><li>Collect guidelines (10 mins) </li></ul>06/07/09 | | Slide
  3. 3. Your guidelines – report content (compiled by workshop participants) <ul><li>A good executive summary is vital </li></ul><ul><li>Ensure you provide details of main project aims / statement of intent </li></ul><ul><li>Make it easy to understand for non technical people </li></ul><ul><li>Include only relevant/items </li></ul><ul><li>Include what has been learned </li></ul><ul><li>Make your outputs and findings clear to the reader </li></ul><ul><li>Repetition of relevant points can be good </li></ul><ul><li>Good to have concrete examples </li></ul><ul><li>Include ‘human’ elements e.g. quotes – as a break from more complex wordy text </li></ul><ul><li>Avoid </li></ul><ul><ul><li>Acronyms </li></ul></ul><ul><ul><li>Lots of needless detail </li></ul></ul><ul><ul><li>Too much detail about project planning </li></ul></ul><ul><ul><li>Waffle. Keep to the point! </li></ul></ul><ul><ul><li>Poor quality diagrams </li></ul></ul>06/07/09 | | Slide
  4. 4. <ul><li>Avoid density of information </li></ul><ul><li>Consider length of report (too short can mean not enough info vs an off-putting thesis!) </li></ul><ul><li>Clear layout of objectives and activities </li></ul><ul><li>Make it easy to find key messages </li></ul><ul><li>Use white space </li></ul><ul><li>Include a proper table of contents </li></ul><ul><li>Make use of appendices – keep the report concise and easy to read </li></ul><ul><li>Highly structured is good </li></ul><ul><li>Signposts within the document can be helpful </li></ul><ul><li>Don’t forget to number your pages </li></ul><ul><li>Ensure pictures/diagrams are properly referenced </li></ul><ul><li>Bullets or numbered points good </li></ul>Your guidelines – report structure (compiled by workshop participants)
  5. 5. <ul><li>Think about what the reader can do as a result of your report </li></ul><ul><li>Get someone outside of the project to read and feedback on your report - the people writing the report generally appear to be too close to the project </li></ul><ul><li>Ensure your report does not come across as ‘defending’ the project and instead communicates the benefits to other people </li></ul><ul><li>Take into account DDA (Disability & Discrimination Act) / Accessibility – this benefits everyone </li></ul><ul><li>Remember that your report may be read on screen </li></ul><ul><li>Give alternatives for people to read / access it in different ways / on and off screen </li></ul><ul><li>Tagging topics can be useful </li></ul><ul><li>Think about longevity </li></ul><ul><li>Would be good to consider to using other formats when creating their outputs e.g. video, e-learning type tools </li></ul>Your guidelines – additional points (compiled by workshop participants)

×