Book contents
- Frontmatter
- Contents
- List of figures
- Preface
- Acknowledgements
- About the authors
- Glossary of Technical Terms
- 1 The Accidental Entrepreneur
- 2 A Reflection on the First 300 days
- 3 Why does any Organisation need a Chief Data Officer?
- 4 The Secret Ingredients of a Chief Data Officer
- 5 The First 100 Days
- 6 Delivering a Data Strategy in the Cauldron of BAU
- 7 Avoiding the Hype Cycle
- 8 Relating to the rest of the Business, Especially the C-Suite
- 9 The Chief Data Officer as a Disruptor
- 10 Building the Chief Data Officer Team
- 11 The next 300 Days
- 12 The Different Generations of Chief Data Officers
- 13 What type of Chief Data Officer are you?
- 14 How to Present Yourself as a Chief Data Officer
- 15 The Chief Data Officer and the Technology
- 16 The Hoarding Mentality and how to Break it
- 17 Data and Information Ethics
- 18 The Chief Data Officer and Data Governance
- 19 The Data Revolution
- 20 Advice to Business owners, CEOs and the Board
- 21 Conclusion
- Index
8 - Relating to the rest of the Business, Especially the C-Suite
Published online by Cambridge University Press: 18 February 2021
- Frontmatter
- Contents
- List of figures
- Preface
- Acknowledgements
- About the authors
- Glossary of Technical Terms
- 1 The Accidental Entrepreneur
- 2 A Reflection on the First 300 days
- 3 Why does any Organisation need a Chief Data Officer?
- 4 The Secret Ingredients of a Chief Data Officer
- 5 The First 100 Days
- 6 Delivering a Data Strategy in the Cauldron of BAU
- 7 Avoiding the Hype Cycle
- 8 Relating to the rest of the Business, Especially the C-Suite
- 9 The Chief Data Officer as a Disruptor
- 10 Building the Chief Data Officer Team
- 11 The next 300 Days
- 12 The Different Generations of Chief Data Officers
- 13 What type of Chief Data Officer are you?
- 14 How to Present Yourself as a Chief Data Officer
- 15 The Chief Data Officer and the Technology
- 16 The Hoarding Mentality and how to Break it
- 17 Data and Information Ethics
- 18 The Chief Data Officer and Data Governance
- 19 The Data Revolution
- 20 Advice to Business owners, CEOs and the Board
- 21 Conclusion
- Index
Summary
Introduction
This chapter explores the idea that the CDO is different to the Chief Technology Officer (CTO) or Chief Information Officer (CIO) and discusses the relationship that the CDO might have with the Chief Executive Officer (CEO). The key role of the CDO and data ownership is examined. This chapter is aimed at the business stakeholders.
There are more C-Suite roles than there used to be. The longestablished roles of Chief Executive and Chief Information Officer now have to compete for room at the table with roles like the Chief Information Security Officer, Chief Operating Officer, Chief Finance Officer, Chief Customer Officer, Chief Digital Officer and, of course, the Chief Data Officer – it's getting a bit crowded around the table.
Key relationships
Relationship building is a key skill for the CDO. Working with the data means you, the CDO, are cutting across the silos in the organisation and therefore potentially messing around in everyone's backyard, so you had better be able to ask nicely before you do, or have some air cover for when an area feels pain for the greater good! While the CDO needs to form a working relationship with any other stakeholders in the company, not just the rest of the C-Suite, the one that causes the most concern is the relationship with CIO or CTO; it definitely generates the most questions at conferences. Of course these roles and their scope vary from organisation to organisation.
The difference between a CIO and CDO (apart from the words ‘information’ and ‘data’) is best described using the bucket-and-water analogy. The CIO is responsible for the bucket (the technology), ensuring that it is complete, without any holes in it, that the bucket is the right size, with just a little bit of spare room but not too much and it's all in a safe place. The CDO is responsible for the liquid (the data) you put in the bucket, ensuring that it is the right liquid, the right amount, and that it is not contaminated. The CDO is also responsible for what happens to the liquid; making it available when it's needed. In this analogy the CIO has a responsibility to make the water accessible to the CDO (the business).
- Type
- Chapter
- Information
- The Chief Data Officer's Playbook , pp. 79 - 84Publisher: FacetPrint publication year: 2020