I like this approach (could discuss aspects of it). I believe more and more that after federating data platforms, data catalogues and other data-enabling or data-driven processes and applications, we should look into federating data governance as well with local ‘champions’ rooting for it. Your proposed roles and phases might just enable that.
Happy to discuss! The intention is to define enduring responsibilities of data governance and a technology agnostic process. What needs to happen, and how.
I realized throughout the years of working in data governance, that even though we experience similar problems, root causes and wya to solution different. Thus, blue print data governance programs are an illusion.
So what remains valid no matter the maturity or choice of data catalog tool. For me it is the triad and it's activation patterns.
I like this approach (could discuss aspects of it). I believe more and more that after federating data platforms, data catalogues and other data-enabling or data-driven processes and applications, we should look into federating data governance as well with local ‘champions’ rooting for it. Your proposed roles and phases might just enable that.
Happy to discuss! The intention is to define enduring responsibilities of data governance and a technology agnostic process. What needs to happen, and how.
I realized throughout the years of working in data governance, that even though we experience similar problems, root causes and wya to solution different. Thus, blue print data governance programs are an illusion.
So what remains valid no matter the maturity or choice of data catalog tool. For me it is the triad and it's activation patterns.