“Shared documents aren’t shared understanding.”
The idea of using stories to effectively communicate ideas through many channels, as well as the ways in which they can be used differently and similarly, really caught my attention. A deeper approach to being on the same page is required to develop a common understanding, which is not always the same as just reading the same paper out loud.
In this instance, the example of the vacation snapshot is particularly relevant. Having personally experienced the event, the author is able to recollect every detail, including the drive over and the turtles on the beach, with ease. However, since the image is merely a picture of a moment rather than a memory, simply presenting it to a complete stranger is unlikely to bring back those memories.
“Good story conversations are about who and why, not just what.”
As a very technical person, this is something I have not given enough thought to. Engineers are constantly trying to solve problems and often become too focused on the solution and overlook the people the solution is affecting. It is very important to remind ourselves that we should not build for the sake of building and thoroughly think about the impact of our actions.
In addition, from the reading, I was inspired to include the maximization of output while minimizing input in my workflow. The concept of priority, which takes into account urgency, production costs, and impact magnitude, is what matters in the end. This aligns with my work view where I believe the best results are often obtained by understanding how to properly delegate the tasks to each member.
