Enterprise software companies all promise a better future. The absolute core of their business is Marketing.  They all want to offer you a game changing software solution that , although very expensive, is worth every penny to the customer. (Whether this change is successful or not is up to us. We are the ones to make sure that the software is implemented well, and delivers one ( or more) of the six possible optimizations that delivers meaningful results for the organization. )

These companies must continuously innovate to try to stay ahead of each other. They are reading the trends, and trying to stay ahead of what you may ask for, or what they fear that competitors might tout at a Gartner conference. Good marketing is a vital input into product planning, always trying to anticipate what buyers will want next.

There is a bit of “creative imitation” in this, but most of the time, this works to the buyer’s benefit. Consider native cloud hosting of applications—not that long ago, this concept was pretty foreign to most organizations. Now, I don’t think there are more than a handful of companies left that would host their own email or E-commerce servers.

For Enterprise Software companies, AI is the new Cloud (Or the new NoSQL, or Consumerization, or SaaS, or etc, etc.), still high on the hype cycle promising lower long-term costs and better results. In their marketing efforts, they are trying to convince CIOs and other executives to sell the case to the leadership of why and how a new technology, whether it’s a big upgrade, a platform change, or a new application is going to solve important, existential challenges. As one Tech leader says, his goal is to use Marketing to position his product as “the reflex response for a CIO who is replacing legacy technology for the functional area of the asset.”

Something happened that completely surprised me, however—Salesforce reported a big slowdown in new deals, even with all of the AI hype. In fact, all Enterprise software companies seem to be struggling a bit right now.

In thinking about this, I think that AI has the same Marketing problem that the Cloud had 10 years ago—Security and Privacy.

With AI, the unspoken concerns are worse—because whether we can articulate it or not, we are not just worried about sensitive data, breaches, and so forth, but we are worried about the security and privacy of our insights.

We take the software company’s word ( and legal documents) that they won’t share our customer or product data.  That is step one in a basic agreement, and the infrastructure in a multi tenant architecture has proven safe enough to be trusted.

However, we can see clearly that our data, and more importantly, our questions, prompts and refinements are being used to make the AI smarter and more useful, not just for us, but for competitors, snooping governments, and potential bad actors.

Software companies need to address these concerns head on (again, even if we are not saying this out loud yet).  Organizations need to understand what ideas and insights are being shared between instances of these systems, as well as what is being exposed externally.   The concern that I have is that the Software companies themselves may not know the answers to these questions.

Helping CIOs and their colleagues gain confidence that the intelligent “soul” they are inviting to the organization can keep secrets is the marketing leap needed.  Keep your eyes open for whose Marketing department figures this out first.

Not that it’s relevant to anything important, but I stopped admiring people who “speak truth to power” quite some time back.

It isn’t that I’m against the practice. It’s that I long ago read enough about epistemology (roughly three medium-length paragraphs) to understand that none of us have access to “the truth.” As we don’t have access to it we sure shouldn’t take it upon ourselves to share it.

Understand, I do have some experience in this game, as when I debated Gartner about their total cost of ownership metric: I spoke “truth” (my opinion) to power (Gartner being a force in the industry.

But I wasn’t, in truth, speaking truth to power at all. The best I could and can claim was that I provided my honest opinion, based on the best evidence, logic, and withering ridicule I could come up with.

None of us know the truth about anything. But on the other hand we’re all capable of honesty – a more advisable because less arrogant alternative to pretending to truth-telling.

None of which has anything to do with this week’s subject, which begins with my new favorite word, polysemy, which is when different words have closely overlapping meanings. Drawing on the subjects of recent weeks – integration and data warehouses in particular – this week’s polysemes are “system of record” and “source of truth.”

There are those in technical architecture circles who use these terms interchangeably, as if they were the same thing.

But like the difference between truth and honesty, systems of record and sources of truth are distinct and different concepts: a system of record is a matter of technical choice, while a source of truth is a matter of design.

Imagine your applications portfolio includes three different applications that manage customer information – maybe a CRM suite, an ERP suite, and a third-party database marketing company. Your job: make it easy for a sales representative to find a customer’s primary business address. It isn’t easy now because often the three applications contain different addresses for each customer.

What you need is a more-or-less arbitrary decision as to which of the three applications will, from this point forward, contains the address that will be used. That application is the “system of record” – the application developers will consult whenever they need a customer address.

Compare that to a source of truth. A source of truth is an integration point, often an API, possibly an “operational data store, enterprise service bus connector, or for different uses a data warehouse. What makes a source of truth invaluable is that someone has constructed a single software locale that knows, for each chunk of information, which application is its system of record and … and this is the crux of the biscuit … how to reconcile any discrepancies.

Systems of record are concrete. Sources of truth are abstractions.

To put a dot on it, anyone wanting to make use of corporate data must have a map that identifies, for each piece, which application is the system of record for that data.

Or else they need to ignore the individual applications and, for each piece of data they want they should consult the sources of truth.

Bob’s last word: When it comes to IT, understanding and making use of sources of truth in lieu of systems of record is a handy way to get work done faster and more accurately. But the same thought process can play out in non-technical situations.

Each of us has sources of truth for information we need. These sources take the time to collect and summarize information so we don’t have to. Maybe Gartner is one of them (good luck!). Greg and I hope KJR serves this purpose for you in your professional life. Microsoft wants you to start relying on Copilot, encouraging you to obey our future robotic overlords.

Regardless, given the flood of information available to us should we need any of it, perhaps our biggest challenge will be vetting our summarizers. For the ones we choose the minimum standard can’t be truth. The raw sources are, after all, in the cloud.

And the internet doesn’t trade in truth.

Now in CIO.com: Want more along these lines? Read Bob’s newest CIO Survival Guide post, “CIO risk-taking 101: Playing it safe isn’t safe”, about how organizations often get risk-taking wrong.