by twieberneit | Dec 2, 2019 | Blog |
After having covered some press releases about new releases and commenting some interesting organizational changes it is time to have a look at another topic – the need for consistency in a suite of cloud products. Consistency not only in the most obvious part of a family of products and solutions – the user interface – but the more important aspect of consistency, namely the data model. If you wonder how this relates to customer experience I invite you to read on. This post is actually spurred by a brief conversation that I had with Jon Reed of Diginomica about this very topic during one of the recent CRM Playaz episodes. Btw, if you do not yet listen in to the LinkedIn conversations of CRM Playaz Paul Greenberg and Brent Leary, discussing important developments and current events in the world of CRM – then you should. Really! But I digress. Back to the topic. The question is about whether it is necessary to have a unique data model or not. And this question might be answered differently, based upon the definition of ‘data model’. There is no doubt that a unique data model across applications is very helpful, actually a necessity. Where there is doubt, is whether this data model needs to be defined on database level or not in order to be really helpful. My point of view is that it does not need to be defined on database level. This point of view might be contradicting some ‘common sense’ wisdom and the strategy that some very successful companies are pursuing, including Oracle – as it seems –...
