Rubber ducking is an underutilized skill that is often overlooked. It is a simple skill that everyone can do but is never the first method they use. The first method is often googling it up or asking for help. The skill is simple. Explain your problem to an inanimate object like a rubber duck. This is often utilized in a developer /programming setting. Developer often needs to debug their code and need to understand what is going on. This way so they can not run into the same issue again. Explaining it and hearing it back themselves. It helps break it down and suddenly they get an epiphany. The next level is bringing in someone that has some expertise. They can give you some insight into your problem. Additionally, rubber ducking with someone that has no experience at all is helpful as well. This can give you insight into the fact that you might be overcomplicating the problem. Keeping it simple is often the answer. This skill is transferable to any problem you want to solve. This can be used when you are preparing your presentation. Rubber ducking will break down your thought process and help you make a strong argument for your method choice. This can help you rethink what you have and if it makes sense to you and your audience. This is especially useful for the viz that is being used to apply to the Data school. Some questions that you should be asking yourself from making the viz to presenting it are:
What is the data and how to represent it?
Is this the best method to represent this data?
Does my audience understand my viz?
Why have I chosen this chart or design choice?