How design thinking solves the 3 hardest problems for chief data officers

I operated some of the most challenging data analytics landscapes, and I am grateful for those experiences. Namely, early on in my career, I saw exceptional chief information officers struggle landing on their feet, trying to pioneer novelties in how to capture value across the data use cases. At the time I began working in information technology in 2011, the formal implementation of a data officer did not exist in the federal government. Again, we are talking about the U.S. federal government, not the private sector and other industries. Even prior to 2019 (when the data officer function really accelerated for adoption and implementation), the role itself had always existed, whether it be through leadership cells embedded across information officers, information security officers, governance specialists, even cloud architects.