The Final Presentation and Final Report Work Together and Support Each Other

The final report and the final presentation work together to meet the needs of both decision-makers and technical members of the company. You were informed earlier that decision makers often prefer the top-down commercial style of report because it provides information transmission in a way that facilitates decision making. On the other hand, technical people and implementors of strategy often prefer the academic or journey style of presentation because it allows them to increase their trust in the findings and recommendations because they can see how the data was collected, and the analysis completed. It also helps them in the implementation of the recommendations or the repeating of the activities.
 
But what if both decision makers and technical/implementors are in the room for the final presentation, will not one of the groups be frustrated by the presentation if it is not presented in their preferred style. Frustration by both groups can be averted by a simple solution.
 
By sending out the final report prior to the final presentation, the technical people can see the information presented the way they want to see it. And it is unlikely the decision-makers will read the final report or any more of it than the executive summary prior to the meeting. But remember the executive summary is written in the same style as the final presentation, so it will facilitate decision making if it is read prior to the meeting.  
 
So, by sending out the final report a few days before the final presentation so it can be read by the implementors, and then presenting the final report in the top-down commercial style, you meet the needs of everyone in the meeting. And you will increase the satisfaction of everyone at the sponsoring company.
 

This content is provided to you freely by Ensign College.

Access it online or download it at https://ensign.edtechbooks.org/projectbasedinternship/the_final_presentation_and_final_report_work_together_and_support_each_other.