At the close of our 2015 Enterprise Information and Master Data Management summit yesterday Deb Logan hosted a “master mind” interview with Dr. Eugene Kolker, CDO, Seattle Children’s Hospital. It was an awesome session and I just had to tweet as many of the pearls of wisdom Gene was kind enough to throw out into the crowd. Here is my list – in no order of importance (they are all important!):
#GartnerMDM Talking CDO:
- CDO might stand for Chief Diplomatic Officer!!! Get reconciling and collaborating.
- Business acumen critical, more so than analytics, data or technology skills.
- Who do you report to? Requires access, minimum dotted line, to CEO.
- Recommend Wolf in CIO Clothing, Tina Nunno. Page 27. (note I recommend this too – see my book review)
- Measuring CDO success- did business value get realized, not did technology get installed on time.
- Works with IT and CIO who provide fulfillment, solution and technology support.
- CDO office owns, leads and defines (offensive) information and analytic strategy.
- Defensive roles like chief risk officer handle this. Offensive work is CDO work.
- CDO is a business role. Use ‘data stories’ to explore and explain with business the process change.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Category: analytics business-intelligence chief-analytic-officer chief-data-officer chief-digital-officer cio cio-first-100-days information-governance information-innovation information-innovation-yield-curve information-leadership information-organization information-strategy information-trust
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.