Strategies to prevent the "telephone game syndrome"

In fairness- document document document, I always follow up with and email reviewing the details and reviewing / recapping the important points in the conversation. This supports understanding and also shows your awareness to the challenges/tasks at hand. Also builds a stronger accountability to the everyday hussle and bussle of the fast moving world. good luck!

Francisco,

Agile purest have long held that the “telephone game” demonstrates the original sin of linear models; unfortunately, every time they attempt to illustrate the effect, their message gets lost in the translation—sorry, I couldn’t resist the opportunity. :-)

On the serious side, even the most precise and contextually correct words stated verbally or in document form are fodder for mistranslation.

Hence, I use a two-step approach to gain “high fidelity” knowledge:

[1] Supplement or replace the raw knowledge with an interpretive “basis perspective” that removes content noise (i.e., superfluous information) and elevates the read to a conceptual level, providing the consumer with clarity of point.

[2] Visualize the key elements and place them into their lifecycle constructs if applicable.

Conceptualized and visualized knowledge withstands the rigors of change we experience in projects. Stated differently, the fidelity of the knowledge maintains its shape regardless of where it is contextually applied in the realization process.

Meanwhile, non-visualized and non-conceptualized knowledge creates high levels of rework for project teams, as resources find it challenging to apply the knowledge to their work product due to contextual nuances that create misinterpretations of intent.

George