After doing a powerpoint presentation for a large online meeting to a global audience of mostly engineers and engineering leadership of various departments, my boss assembled me and my team into his office for a chat.
He asked to give ourselves a grade of our presentation. We gave ourselves As, Bs, maybe even a C thrown in.
The boss said "I generously give you folks a D."
He continued that the presentation included far too much detail on how much time was spent troubleshooting, collecting data, and other related analysis issues and obstacles getting information.
He concluded our feedback session "reminding" us that the audience really didnt care how hard it was to get the needed data and how long it took, their interest was the results and any corrective action recommendations.
I think of this lesson when publishing a Project or Road Test report.
If a video is made to share a project, no one is really interested that it took 15 takes or 12 hours to edit the video (unless the article is about the video editor).
The audience probably doesnt care if you filled your hard drive taking hi-rez photos and had to get cloud server space.
If publishing a schematic, it doesnt matter if there are 5 revisions or 50 revs from start to finish unless there is a key knowledge point to learn in one of those revs. If someone cares, they will ask.
Its OK to share an anecdote the major milestones and challenges about the journey if it helps tell the story.
What's your experience ?
