Donโ€™t write business reports like stories

Writing a chronological narrative puts conclusions and recommendations at the end, which busy readers might not see (especially if your story is boring!). Here are ๐˜๐˜„๐—ผ better ways to structure a report. If you are writing a short report or an email on a single topic, try the ๐—ฝ๐—ฟ๐—ผ๐—ฏ๐—น๐—ฒ๐—บโ€“๐—ฐ๐—ฎ๐˜‚๐˜€๐—ฒโ€“๐˜€๐—ผ๐—น๐˜‚๐˜๐—ถ๐—ผ๐—ป. First you describe the problem/issue, then explain why it has occurred before stating your recommended action(s). For longer reports there is the ๐˜๐—ฒ๐—น๐—ฒ๐˜€๐—ฐ๐—ผ๐—ฝ๐—ฒ approach. This puts the most important information first. 1๏ธโƒฃ Start with the summary, conclusions, and/or recommendations. 2๏ธโƒฃ Follow this with analysis of the issues, context and evidence. 3๏ธโƒฃ All the background material, the methodology, research findings, processes, etc comes last (possibly in appendices or in a separate document at the end of a hyperlink). Save the stories for books and movies. At work, your reader just wants to know how the story ends.