Great insights in regards to change management. It is difficult to get people to understand that Tableau is not set to replace other tools as much as it is to compliment. The immediate expectation, when discussing creating items in Tableau, is to make it a static dashboard or report and just recreate old reports so that they are now accessible in Tableau. The discussion needs to be made about what makes sense to develop in Tableau and what may be best developed in a report writer or kept as is. Getting people to realize that Tableau is not a report writer is essential when implementing and seeking user adoption, otherwise users won’t see the value in the analytical functions.
I find this information from the article to be an especially important piece of the puzzle
Data visualization tools are only as good as the information that is inputted. If organizations lack an enterprise-wide data governance policy, they could be relying on inaccurate or incomplete information to create their charts and dashboards. Having an enterprise-wide data governance policy will help mitigate the risk of a data breach.
Like how the interview addresses the fact that you can, and probably should, have both ETL/Warehousing and other Data Integration tools. Use the solution that is best suited for the specific data and the business need.