Over the past few weeks of client interactions, it’s becoming more common for Chief Data Officers (CDOs) to “own” the data lake initiative in enterprises. The data warehouse and mart environments stay with the CIO’s team. This creates a massive amount of tension within the organization and leads to competition between groups that should be collaborating. It also leads to data lake failures.
CDOs, often new to the role, are eager to claim ownership of data lakes because they’re hyped as an innovation center and these new executives want to put their stamp on a cool new thing. The goals are typically vague, like “democratizing data access” or creating some single version of the truth by combining systems of record in the lake. These CDOs approach the challenge as a purely technical one, forgetting that data silos are a reflection of the organization that created them. Without broad buy-in across the enterprise, including the CIO, CDOs face an uphill battle.
Unless CDOs work with the CIO and carry a solid data management practice into their data lake implementation, success is unlikely. And based on hundreds of client interactions over the past couple years, data lake successes are hard enough to come by. Give yourself a better chance at success by collaborating.
This pattern is only one of the data lake failure scenarios we’ve seen. Adam Ronthal and I recently published a research note on how to avoid data lake failures, which includes a number of other patterns. If you’re a Gartner client embarking on a data lake implementation, I encourage you to give it a read. If you don’t, I look forward to speaking with you about your failed data lake in 6-8 months.
Predicts 2019: Data and Analytics Strategy
Data and analytics are the key accelerants of digitalization, transformation and “ContinuousNext” efforts. As a result, data and analytics leaders will be counted upon to affect corporate strategy and value, change management, business ethics, and execution performance.Read Free Gartner Research
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.