This also defines the purpose and content of the resulting report. Gather as much information as you can during the usability activity. It is easy to discard useless information, but extremely difficult to recreate or recall data you have failed to gather. Refer to 'Handling Logged Data' for more on this topic. Know your audience It is necessary to have a good understanding of who will read the report, and why.
Most reports have more than one audience.
For example, developers may read the report in detail, whereas management may read only summary pages. Develop a Table of Contents After you have gathered your data, write a detailed table of contents. Then make a 'shell' document based on this table of contents. It is quite normal to need to change the table of contents as you write, although radical changes may mean that the initial table of contents was not sufficiently well planned. Writing the report Starting at the lowest level, fill in the blanks in your document.