In March, 2015 Anthony Algmin became the first Chief Data Officer for the Chicago Transit Authority. He had been an external consultant to the CTA prior to this transition, so he knew the organization and its data management challenges very well when he came on board to do the job, and intimately understood the objectives and priorities of the new CDO role.
Many organizations are debating on what a CDO should be, and whether or not they need one. The answers will vary, but as Anthony has been down the path of helping an organization create this position, and eventually being offered and filling the position himself, he can provide valuable insight on that process. He’ll talk about the things that were essential to allow the CDO to be successful at the CTA, and which apply to most other organizations as well. He’ll share lessons learned during his transition from consulting into a CDO role, and offer insights into the “start-up” challenges in his first few months into the position. Other topics of the discussion will include:
The key capabilities of a CDO and some unexpected places you may find good candidates
Where the CDO should sit in an organization, and why the CTA has structured it the way they have
The principal objectives of a CDO’s department, and how they differ from those of IT. How does the CDO role differ from the CIO?
A few months into the job, what has gone well and what does he wish he had done differently?
What can other organizations learn from Anthony’s experience?