If you’re writing a report about statistics, you have to expect that many readers will lose interest after a while, if they even had it to begin with. So, in writing the report, think about how you might engage your audience. Here are five ideas.
Find common ground
Every relationship begins with having something in common. Fighting a common foe or solving a common problem can form the strongest and longest lasting of bonds. So the first thing you should try to establish in your report is that common ground. This isn’t so difficult if you are working on an analysis at the behest of a client. The client is already immersed in the data and has invested in you to help solve the problem.
Establishing common ground is not so easy if you are proffering an uninvited message. Some people, perhaps subconsciously, don’t really want the message you are offering, especially when you’re analyzing data in their area of expertise. Try to establish common ground in other areas. Perhaps your analysis touches on a similar or analogous issue the reader might have. Maybe the analysis procedure could be used on a different problem the reader might have.
Clear the decks
Get rid of everything that doesn’t add to the progression of the report. That doesn’t necessarily mean you have to omit the content. You can relegate it to an appendix, which is pretty much the same thing. Unless required to be in the body of the report, things like the data, data collection surveys and forms, and scrubbing and analysis procedures should all be put in an appendix.
Set the tone
Your writing style can either add to or detract from the readability of your report. A formal tone, with strict adherence to grammar rules, complex sentence structures, use of third-person point-of-view and passive voice, and plentiful jargon, is appropriate for most data analysis reports. Formal tones are good for describing details, specifications, and step-by-step instructions. However, formal tones can be more difficult to understand, especially for individuals not accustomed to reading technical reports.
An informal tone, with simple grammar and vocabulary, colloquialisms, contractions, analogies, and humor, works well for blogs. Informal tones are good for discussing ideas and concepts, and for inspiring readers or communicating a vision. They are more engaging and tend to be easier for most individuals to understand. If you’re being paid to write the report, a formal tone is usually more appropriate. This is problematical, of course, because formal writing is usually harder to read and maintain an interest in.
Add mind candy
A Harry Potter novel consisting of page-after-page of text will keep readers, young and old, transfixed for hours. A data analysis report consisting of page-after-page of text will put readers into a coma faster than a handful of barbiturates taken with a glass of warm milk in a tub of hot water while meditating. The difference is that the novel engages readers with mental images. Data analysis reports need to use visual imagery, which for the most part means good graphics.
Granted, most readers won’t understand anything more complicated than a pie chart or a bar chart, but don’t add to the confusion. Three-dimensions are a no-no. Avoid graphing data in more than a few categories to avoid making the slices and bars uninterpretable. And most importantly, make sure they add to the analysis. You can do more, too. Break up the text with subheadings and bullets. Reiterate information nuggets in boxes instead of just letting them get lost in the text. Use tables for explaining differences in data groups and not just for number buckets. Add footnotes or hyperlinks to explain collateral concepts.
Make it better
Just when you think you’re done writing, you’re not. That’s the time when you have to do even more to make the report better. First, take some time off if you can. Then, read it through again making improvements along the way. Check for grammar and spelling mistakes and consider using a paraphrasing tool to enhance the words. Read it aloud if you need to, even record it when you read it aloud and then play it back so you can engage both your vision and hearing.
Consider getting a second opinion, especially if you can’t distance yourself from the report by setting it aside for a few days. A second opinion may come from a data analysis peer, but don’t ignore nontechnical editors. A good editor can help with spelling, grammar, punctuation, word choice, style and tone, formatting, references, and accessibility. It’s usually worth the effort. This is the time to go for perfection.