Tableau: First of all, what was different about the Tableau Drive methodology?
Mat Hughes, Revenue Analytics Manager: Drive was our first real tangible example of a cross-departmental project that was led by the business and the IT, and achieved greater results because of that.
Jim VanSistine, Business Consultant, IT: So it's much less of a ‘tell us what you want and let us building you something’ and much more of a ‘let's figure out together what's the right thing to build.’
It really let us pick and choose the good parts that IT is able to bring to project—some of the governance models and support—without doing some of things that just create a bottleneck and a slowdown that wouldn't have been conducive to this kind of rollout.
Tableau: What sort of a result has this had on the two departments—IT and the business?
Mat: The relationship between IT is so much better than what it was before. Everyone has kind of realized that It's not the zero sum game and that we don't have to be pushing up against each other and battling to see who does what, right?
Tim Kraft, Senior Director, Data & Analytics:So the business users are focusing on building reports and building them rapidly, failing fast, gaining insights about their data, and IT is focused on really building that data infrastructure for us, focus on providing us the tools that we need to create the visualizations.
Tableau: Jim, from the IT side, how was your experience with Drive?
Jim: It made it so, so easy for me, because there was a long list of sort of prepackaged steps that we could follow. It laid out a good portion of the project plan, and it really made it easy for us to dialogue with the business.
There are things we learned in this Drive project that we'll be able to apply for years on future IT projects unrelated to Tableau.
IT's not in the way of the progress anymore, we're a partner. It's like, 'Well, what do you want to do and how do we help you do it?'