What’s the data environment like at Invoice2Go?
Bob Briski (Director of Data Infrastructure): We have a pretty sophisticated process that involves an event logger that pushes data through an ETL system before finally getting into Amazon Redshift and SQL Server. We use data to optimize the customer experience and product here at Invoice2Go.
What are your current data initiatives and projects?
Bob: Our data initiatives revolve around creating a service-type organization out of the data team. We want data to be easily used and shared by everyone across the company to further drive business.
One current goal is to document data in an automated fashion so that knowledge around data is not stored in the heads of certain people. This will help us scale as an organization and make sure we don’t lose any knowledge if someone leaves Invoice2Go.
Another ongoing goal is sharing knowledge on data and queries throughout the team. Our team is growing and we need to be able to on-board new employees seamlessly and ensure everyone knows what data is available and what different fields and metrics mean.
We really aim to efficiently publish queries and data out to the entire organization to help with decisions. As a data-driven company, people across the organization rely on the data group to provide them with analysis and recommendations on decisions.
Invoice2Go + Alation
At Invoice2Go, Alation has helped
- automate documentation of data so the knowledge is right at an analyst’s fingertips as he or she writes the query
- increase productivity and allow analysts to explore and find the data they need, which also reduces on-boarding time
- allow for efficient sharing of data and queries
How has Alation helped Invoice2Go continue to be data-driven?
Bob: Alation helps our data team to be more of a service organization to the rest of the company with sharing actionable data and queries. We’re using Alation to for governing data, automating documentation, and publishing data for people to use across the organization.
We chose Alation because we needed a tool that does documentation right beside our data and right beside our queries. There was just nothing else on the market that I’ve seen that does that. Any other time where I needed that to happen, we usually had to write our own code.Bob Briski, Director of Data Infrastructure