I read this book as someone coming from a long and very technology-intensive background to learn more about the challenges of being a data officer. Since the terms "data officer" and "chief data officer" are relatively new, there aren't many resources that discuss these, and show how they relate to other roles in a company. In fact, when I searched for books last year, I could find only one other book who used the term "data officer" in its title, and even that book didn't seem to have broad coverage enough.
I'm pretty satisfied with this book's coverage of data officer role, and its recommendations. It presents a realistic picture without being limited to a single domain such as data governance. Its focus on identifying this role as a primarily "business" role, and not a technical role is also important for positioning data officers, I believe. Having said that, the book also does a good job of showing how people from different backgrounds end up being data officers, and how they should view the challenges based on their background.
Even though the book is written at a high level, its advice for the first 100 days and 300 days shows the tactical and strategical actions to be taken. Of course, depending on the industry you work in as a data officer, you will be faced with very different styles, but I agree with the authors about the common themes that a data officer will deal with whether they are working in a bank, or a multinational manufacturing company. For example, having the strongest support of top management, at CEO or president level, being in very healthy communication with all the stakeholders, having a very good overview of data assets of the company, not forgetting tactical achievements while constantly fine tuning the long-term strategy are some of the points that are valid independent of your industry. These will be decisive factors when it comes if your tenure will extend to more than 2.5 years as Gartner predicts for the average chief data officer.
I think I'll go back to this book every now and then in the upcoming months, and I can recommend this book to anyone who wants to know what it means to be a (chief) data officer, or whether their company needs one.
I wish the book had a more detailed reading and reference list at the end, and maybe a better index, but I can't complain much I believe. Unless a much better book is written in the future, this is the book that you'll have to consult for any kind of overview and understanding of being a data officer and working with data officers.