Day two of the MDM summit was good but in many ways a consolidation of the messages from day one so rather than breaking down the points in to individual sessions, here’s a quick selection of things that made it on to my notepad, in no particular order. (Thanks to these speakers: Aaron Zornes, Cliff Longman, Sean Cassidy, Dileep Srinivasan, Simon Slocombe, Tony Ellis, Holger Wandt, Carsten Kraus, Colin Rickard, Kathy Hunter, Ed Wrazen and Brian Amo.)
Storing data is not the same as mastering it. You don’t have to slavishly master all data. Can have payload data along with master data.
Top ten MDM evaluation criteria includes developer productivity, which is something I’ve indirectly blogged about before. Time to value is important.
The presenters really don’t like people in business using spreadsheets to hold data! Should have kept a tally of how often this came up.
What risks can you reduce if you trust the data? What new risks might you be willing to take?
MDM isn’t a silver bullet for fragmentation. MDM projects are currently concentrated within departments, lines of business or geographies, with localised implementations. Companies could end up with several ‘single’ versions of the truth! Even if that wasn’t the case, companies with their own MDM hubs are going to start merging sooner or later.
These questions can be useful to uncover data ownership and escalation paths… What is it? How do you know when it’s wrong? What do you do when it’s wrong?
MDM is not really new. The problems are definitely not new. MDM is as much about the business processes around data as the technology, which is largely existing technology packaged in a new way.
Just discovered this post hiding in my pile of drafts, so before it makes itself at home there, I’m kicking it out, warts and all.
I’m also signing up to the Yahoo Master Data Management group to continue the quest to master MDM.