If your AI and analytics investments still feel like disconnected projects instead of an enterprise capability, this episode of Real Talk with Sam Holcman shows how Palantir quietly turned ontologies into a strategic moat - and how the same ontology‑driven principles behind EACOE and BACOE can turn your architecture into an execution engine for real business outcomes.

If you are a CIO, CTO, or Architecture Manager, you are already paying an “architecture tax” you never approved.

It shows up as overlapping platforms, programs that cannot finish, and “strategic” projects that quietly die after burning millions. The surprising culprit: ten everyday EA/BA words that your organization thinks it understands - but does not.

When these words are fuzzy, your architecture is fuzzy. And fuzzy architecture is expensive.

In both EACOE enterprise architecture and BACOE business architecture, ontology is the backbone: it tells us what kinds of things exist in the enterprise, how they relate, and how those meanings stay consistent as we automate, integrate, and apply AI.

Today, that makes ontology not just a theoretical idea, but one of the most valuable, underused skills in the AI job market – and a critical success factor for serious Enterprise Architecture and Business Architecture work.

What an Ontology Really Is: Kinds of Things Together and Their Relationships In information and computer science, an ontology is a formal description of knowledge in a domain – the kinds of things (concepts/classes) and the relationships between them. It is more than a glossary; it is a structured model of meaning that both humans and machines can use.