Visual models for decision-making
Food for thought #2
In my last post I presented a conceptual model to visualize the risk, when deciding whether to enter into a new market, especially one that bears several risks, from a marketing perspective. As already stated, this was a static approach, but nevertheless such simple visualization approaches to model a specific and challenging situation can be of use to get an idea of given dependencies.
Modelling strategic dependencies in a specific frame for decision-making can help to communicate complex problems in a quick to digest way
The following article shall pick up on this notion and highlight the capabilities, a visual model can have, to communicate effectively situational factors that influence decision-making processes. In communication theory, there is always a sender and a receiver of a given signal. The signal should be built on characteristics that the receiver will be able to decode and to transform into context he can understand and use. Therefore, the sender should plan for this circumstance already in the beginning, when developing the signal and also, when sending the signal. If a sender ignores this fact, then the signal can be misinterpreted. This, we want to avoid - and we also want to avoid this, when thinking of the creation of a visual model to present the findings of research.
I propose, that a visual model, even if it only is conceptual, can be a great communication tool to induce a sound decision-making process. But please, although I'm serious here, you know you can see this thesis as a rhetorical one. In theory, marketing models, and in many consulting businesses there a plenty of visual models to induce good decision-making processes. But as I mentioned, with this post I would like to highlight aspects, that hopefully give some guidance, on how to build visual models. And also, these aspects could be seen as criteria to assess, if a visual model is really of help. See the following list and hopefully, it is some food for thought to you.
Aspects to think of when creating visual models:
- cut out nice-to-know information
- just say and show what is relevant and needs to be shown for the problem / solution assessment
- interesting data can be put in an appendix for a deep dive if there is interest
- don't get me wrong, more data is mostly helpful, especially for exploration and knowledge building, but keep it simple in the model visualization
- put the additional information that supports the findings in an extra area
- keep in mind the initial problem situation
- digging through data can lead you sometimes astray
- explore your data, but structure the findings to find matching factors for the solution
- look for dependencies that can be visualized
- think of your audience
- are the main factors of the model known within the audience; if not are they easy to comprehend?
- color me blind - check your color usage for good contrast and highlighting the elements that induce the findings and the main focal points
- can clear decision possibilities be extracted from the model visualization?
- does your audience need to explain your model to other people?
- think outside the box
- remember, you can get ideas from existing models
- combine them if needed or use abstracts of them to build what you need
- if you can, build your visual model in a systematic way, so others can use it as well - as you know: knowledge sharing is caring
Aspects to think of when finalizing and presenting visual models:
- a clear title and a short depiction of the findings
- quick to grasp the full picture
- be able to explain it in one or two sentences
- be able to quickly see the main takeaway
- in short, it should be self-explanatory
- not overflowing with information
Just by counting the mentioned bullet points which were listed here, you can see, that preparation and understanding the problem and your audience is key.
Thereby, build your visual models around these cornerstones:
- finding factors that influence decision, positive or negative
- visualize for your audience to understand, not yourself
- be systematic so it can be shared and reproduced
Well, some of these aspects seem like common sense, but then again, it never hurts to hear, read them over and over again. You know, just in case. And in the end, this article is also just a reminder for myself.
Sincerely, Mario
Source: Jia, Schumm, Sitter (2013)