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
2 - A Reflection on the First 300 days
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
As we talk about the first 100 and 300 days and I have completed this cycle a few times now, I thought sharing what I have learnt during the more recent iterations would be useful. A while ago I found that the LinkedIn algorithm had been sending out notices to my friends and colleagues informing them that I was celebrating my first anniversary at Southern Water. First, thank you to everyone who sent me best wishes on this event; and second, it was a celebration. I thoroughly enjoyed my first year at Southern Water, a fascinating and exciting place to work, which is going through many positive changes. For me as Southern Water's first CDO it was a challenging year, full of opportunity and learning.
It was a busy year. It now seems odd to reflect that halfway through the year the first edition of The Chief Data Officer's Playbook was published and I am now writing a chapter in the second edition. Several of the chapters in the first edition were pertinent to my first year at Southern Water:
Chapter 3 The first 100 days
Chapter 4 Delivering a data strategy in the cauldron of BAU
Chapter 5 Avoiding the hype cycle
Chapter 8 Building the Chief Data Officer team
One of the key things a new CDO should do at the end of the first 100 days, before they embark on the next 300 days, is to reflect. So here goes.
My first reflection is that things (change/transformation, call it what you will) take time. By that I mean some things do have their own natural pace, whether that is procurement, technical delivery or perhaps most significantly cultural change. The cultural change is most important, because this is the thing that builds the data vision/data strategy. The story of the vision has to be repeated throughout the business and that takes time – there is the natural rhythm of booking meetings, getting into people's calendars, management meetings, leadership meetings, board meetings … and then the story has to be understood and adopted … and then repeated over and over again. It takes time to understand how a business works as an organisation, and also to understand what a business does. I was not from the water sector, or from utilities, so I had a lot to learn, and learn quickly.
- Type
- Chapter
- Information
- The Chief Data Officer's Playbook , pp. 9 - 16Publisher: FacetPrint publication year: 2020