Our first event of 2025 was a book release party for CBUSDAW’s very own Tim Wilson!
If you’ve ever been to a CBUSDAW event before (or listened to his podcast the Analytics Power Hour) you’ll know that Tim has a lot of things to say about analytics. Smart things, funny things, cranky things, etc. To our benefit, he’s organized many of these thoughts together into a book (with co-author Dr. Joe Sutherland) called “Analytics the Right Way: A Business Leader’s Guide to Putting Data to Productive Use“.
This is an excellent book that may be targeted towards “business leaders” with its title, but can also be incredibly useful for analysts themselves in terms of how to think about doing analytics in a productive way. There’s a lot of books out there covering tools, methods, and technology — but Tim and Joe’s book stands out in being about actually using analytics within an organization to further business goals. (NB: this is Jason writing this recap, and not Tim awkwardly hyping his own book in the third person. Also Tim I promise I will get around to writing that Amazon review at some point.)
But this wasn’t just a book signing with free beer, Tim did also give a talk about some of the topics he covered in the book! We had a great crowd, with friends and colleagues of Tim’s coming in from as far as Chicago, Nashville, and Boston.
We also had Jim Gianoglio jump in behind the camera (Tim’s normal job) and get some great action shots:





















































































We all deal with data on a regular basis, though we usually are focused on only a small part of the whole lifecycle process of that data. Thinking more broadly about the whole journey of data, from ingest to insight, requires broadening our horizons past the details of analytical tactics towards a more holistic approach.
The traditional way of dealing with data starts from a fundamental assumption that the process and business requirements are static. A naive idea that once we figure out how to ETL the data and get the business the reporting it needs, that we’re done. Of course we all know that’s not how things work in the real world, thus we need to have methods to deal with this constant change and evolution. We’re still allowed to complain when the business stakeholders change the requirements just when we’re almost done with the project (that’s a basic human right), but perhaps if we’ve built more flexibility into our process from the start that won’t mess us up quite as much.










