Process-Driven MDM is a two-prong concept. As with successful data governance initiatives, it advocates MDM projects should not be solely driven by IT and not focus only on technical data management criteria. Unfortunately, IT initiatives have a higher rate of failure. Business can write the check, but if it fails to proactively partner and support MDM, success is automatically compromised from the onset of implementation.
Secondly, PDMDM insists that any new process improvement initiative (Billing, order entry, order-to-cash, etc.,) be tied to the data quality improvement of a particular procecsses' data sets in order to maximize success. Process-Driven MDM is very much about organizational collaboration.
The title of this blog, therefore, is about using MDM as the tool that helps structure that critical collaboration between technical and business parties.
- Trust – MDM discussions tend to use “trust”, or more typically “trusted” as a way of categorizing the approved Gold Copy data that has been validated through MDM and can now be deployed across the digital enterprise as trusted data. But, I place it first to represent a trusted implementation plan for governance within the MDM system. Increasingly, I encounter RfIs wanting to understand how MDM (or in my case, webMethods OneData), will support a pre-established data management paradigm affiliated with role-driven data governance. In that conext, “trust” means trust the plan for execution.
- Verify (or validate) - This is core to MDM’s mission for producing SVOT (Single-Version-of-Truth). In MDM, the schematics, the plans – even the philosophies of data governance - need to be realized and supported by a versatile and flexible data management tool. MDM verification is two-fold: Firstly, there needs to be a high-performance and automated way of consolidating and centralizing data quality activities, including data merges from divergent systems and elimination of duplication for customer or product records. Additionally, location verification and geocoding is key – not to mention data enrichment, including IoT generated sensor data - which is increasingly adding an innovated level of SIZZLE to MDM in general.
- Collaborate! - Returning back to RfIs and RfPs as a way of gauging market trends, I find that MDM collaboration is repeatedly emphasized. But how could it be otherwise? Some MDM solutions are so preoccupied with collaboration, or stewardship collaboration, that they position the “concept” as product unto itself.
For webMethods OneData (especially for its workflow/approval process), collaboration is the name of the game. Automated workflow, in fact, should be the very place where a data governance team comprised of both IT data management and business specialists interact to validate, approve or reject changes. It should be IT influenced, but ultimately business driven, as in this webMethods OneData workflow demo that relies on timely collaboration between data stewards an HR specialists.