What is the end result of this insight? That a piece of data doesn't provide answers, but it prompts a teacher to ask: Why?
What did you have to do to prepare technically for this deployment? We built out a data warehouse that served as a central repository for all of our organizational data, student achievement data, financial data, survey data. We built that infrastructure and we wanted to ensure that many, if not all, of our core operational systems were integrated. Unlike corporations that have the option of [using multiple] ERP systems, education technology doesn't have that type of system, so not all things are integrated like in an ERP. In education technology, there are software and tools that do one specific thing, so you have to piece your systems together and work to integrate them. The integration of our operational systems and the building out of our data warehouse happened over two years, and we continue to build it out and integrate systems as we add them.
What was the biggest mistake you made with this project? When we implemented the data warehouse and Tableau, the large appetite for data analysis increased even more. It seemed like the appetite was insatiable. And we were A1/4ber-responsive. So there were hundreds of reports built out, but there's not a lot of structure around how they're organized. Simple things like [how to] make sure they're named correctly, what are the right folders they should be in, security issues around who should have access to what -- that knowledge management we didn't necessarily think about ahead of time. It's sort of biting us now in that there are literally hundreds of reports out there, and we're trying to figure out which ones are most useful and which ones we can archive or delete.
You have a background in the financial and operations side of the house. What was the biggest benefit of having experience in those areas as you switched to leading IT? It helps me understand that IT should be grounded in a particular process and should support that process and not hinder it. As technology people, a lot of my team is really excited about new technology, but if it's not grounded in work that needs to get done, it doesn't really matter.
What was the biggest liability of that background? Because I'm not a highly technical person, there was a learning curve [in, for example, understanding things] as simple as our network infrastructure. I had a little bit of a blind spot to very foundational technology that's necessary to support things like the data warehouse and analytics. So that learning curve has been a little bit steep for me. But I ask good questions, and I'm getting up to speed.
Sign up for Computerworld eNewsletters.