SAS Fans 2024 - Understanding Analogies in Data - Part 2

For part 1 of Henry’s explanation of analogies within the data sphere, give it a read here.

More Considerations

Over Usage

Analogies can be overused and can be used in many difference situations, and this can be distracting. As an example, using the Recipe analogy is a good way for describing different concepts and ideas:

·        DevOps concepts like Containerisation (Another industry recognised analogy).

·        Following a set of instructions

·        Software development.

The audience, however, may start to think about what they're going to have for dinner and what they need to get at the shops.

Cognitive styles (Visual vs Verbal thinkers)

It’s important to consider the way the audience will process the concept or idea being described. This is being aware of the experiences they may have had and being able to relate to the concept or idea being described.

Talking in terms of pictures and imagery helps the Visual, where-as, talking in terms of words and concepts help the verbal thinkers.

Abstract vs concrete.

Asking the audience to imagine something abstract, like mythical creatures, may have the audience visualising different things. Asking the audience to think of well-known landmarks (e.g. The Eiffel Tower) will help keep their focus on the same thing.

Depth and Detail

Good Analogies need to be simple yet have enough depth to them so that you can easily describe some details of the concepts being described.

The Cloud analogy is good to a point and relies on imagination. Once you start to describe the details, the data centres are firmly on the ground and the Cloud concept is lost.

Conclusion

Analogies used in the correct way are an excellent tool to help describe concepts or ideas to an audience who may not understand them. It’s important that Analogies have a context, without this, you can find yourselves with weak analogies to help describe your idea or concept. Having an Analogy with multiple layers allows to use the same analogy for different perspectives. It avoids ending up In a ‘dead end’ when using them. Within an organization that has many different departments, understanding and communication are essential. Analogies, when used thoughtfully, can simplify complex information, making it accessible to a broader audience. For example: Non-IT people interacting with IT people. Or Experienced IT Professionals explaining a concept to junior team members. The risk with Analogies is that they can be used in way that can cause misunderstandings, ambiguity or offend. To use another well-known analogy “Rumour Mill”, is an example of how they can be used in the wrong way.

Being sympathetic to the audiences shared experiences, will help to tailor the analogy to help to illustrate abstract ideas but also foster a shared language that can improve collaboration and clarity across departments.