REAL Talk With Sam Holcman

Ford’s new electric truck program is being called its “Model T moment” – not because it’s just another vehicle, but because Ford is tearing up a century of manufacturing practice to build something fundamentally different. In doing so, they have replaced the traditional assembly line with what they call an “assembly tree”: a modular way of building that uses far fewer parts, far less complexity, and a completely new production logic.Enterprise Architecture (EA) and Business Architecture (BA) are at a similar crossroads. Most organizations are still using an architectural “assembly line”: long sequences of phases, hand‑offs, documents, and exams that were designed for a slower, more predictable world. These legacy, exam‑centric certifications, methodologies, and frameworks add steps and artifacts, but struggle to produce architectures executives actually use to run and change the business.The Enterprise Architecture Center Of Excellence (EACOE) and The Business Architecture Center Of Excellence (BACOE) represent the modern alternative. They are not “another framework” running down the same line. They are the architecture equivalent of Ford’s assembly tree: a new way of producing outcomes, built around a small number of powerful, reusable components that can be combined quickly to solve real business problems.

Enterprise Architecture (EA) and Business Architecture (BA) have moved decisively toward the center of enterprise transformation in the last 30 days, especially as organizations try to operationalize AI at scale. Recent market and thought-leadership signals show a clear shift away from architecture as static documentation and toward architecture as a business decision capability focused on speed, risk, investment, and operating-model change.

This topic is one that should sound familiar to anyone who has been around enterprise architecture, transformation, or banking, as one example, for more than a few years: everything old is new again. The latest version of the old story is being told through “purchased models,” “off-the-shelf ontologies,” and what some are now calling the semantic operating system for banking, as one example. Buying somebody else’s model of your industry is not a new idea. It is a very old idea in very new packaging. Twenty-five years ago, it was sold as reference architectures, industry models, enterprise blueprints, and packaged best practices. Accenture sold it. IBM sold it. The Big Four sold it. Entire consulting practices were built around the claim that if you adopted a prebuilt model of your enterprise, you could move faster, reduce risk, and leapfrog the painful work of figuring out your own organization. But here is the Real Talk.

I want to talk about legacy thinking.Not old thinking. Not wrong thinking. But thinking that was right - sometimes brilliantly right - and then calcified into doctrine.Look up at the sky. Something remarkable just happened in space.Blue Origin flew New Glenn - their massive, orbital-class rocket - for the third time.And they flew it on a booster they already landed and refurbished. The same first stage. Flying again.That is not a space story. That is a legacy story. And yes, there was a glitch on cargo release.The exact same pattern is playing out in enterprise architecture and business architecture right now. The certification became the thing itself. Organizations stopped asking whether the certification and framework served the mission - and started asking whether the mission was being performed according to the certification and framework. Do not keep flying Atlas V missions in a New Glenn world.The new paradigm is not coming. It has arrived.The only question left is whether your organization will be the one catching up - or the one leading the way.

Let us be honest - most Enterprise Architects and Business Architects start the day the same way.You roll out of bed, scroll through overnight emails, open at least six tabs of frameworks you will only partially read, warm up yesterday’s coffee because the meeting starts in five minutes, and think…Maybe today I will finally fix that capability model.Because let us face it - every good architect knows their day does not really start until they have had that first cup of caffeine.And speaking of coffee - let me share something interesting that caught my attention.Despite what your friend who refuses to drink anything, but single‑origin pour‑over might tell you, becoming a real coffee expert is not easy. And oddly enough, that is a problem for Wall Street.Starbucks may be on every corner, but qualified coffee graders - the folks who certify bean quality for the commodities market - are in serious short supply.According to the Wall Street Journal, these graders endure a brutal three‑stage competency program: a written exam, a three‑hour coffee grading session, and then a live tasting in front of proctors, identifying defects right down to the bean.Miss one - and you start over.Only five to eight percent pass. That is tougher than passing the California bar exam – or any EA or BA exam I have seen.And it got me thinking: imagine if our industry had that kind of rigor.In Enterprise Architecture and Business Architecture, too many certifications promise instant expertise.Take TOGAF®, for example - you memorize a framework, pass a multiple‑choice test, and suddenly you are called “certified.”Or the Business Architecture Guild’s® CBA® certification - memorize definitions, answer questions, check a box.It is like calling yourself a coffee grader because you can tell the difference between a cappuccino and a macchiato.Look, learning theory matters. But real-world skill does not come from picking the right answer on a multiple-choice exam - it comes from building, evaluating, and adapting.That is why I sometimes say: certifications that only test recall create “credentialed beginners.” You may have sixty percent of the vocabulary, but not the muscle memory.And that is exactly where EACOE and BACOE take a different approach.

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.

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.

Many CEOs excel in vision, leadership, and financial acumen - yet remain only vaguely familiar with the disciplines of Enterprise Architecture (EA) and Business Architecture (BA). They hear the words. They see the frameworks. But they do not always connect with the business value that drives strategy, change, and decision-making. That gap can be dangerous.

Organizations have been stockpiling data for years, expecting that one day it will become a strategic asset. With generative AI, that moment has arrived - but without disciplined data practices, the promise quickly turns into frustration. The differentiator is no longer access to powerful models; it is the ability to shape, govern, and trust the data that feeds them, which is exactly the gap the AI Data Modeling Masterclass is designed to close.

Project Management, most notably in the Enterprise Architecture and Business Architecture realm has become significantly more difficult and complicated. We will describe the four project management approaches to these Architecture development efforts and the skills required in the post-November 2019 environment.

A technology department's goal should be to put the computing processing and storage in the right location that supports the Enterprise's needs and business objectives. We suggest that an Architected Cloud approach – that optimizes both on-premises and off-premises environments is not only gaining traction but is optimal. We explore the reasons for this and how to optimize what many organizations are considering to be their long-term approach – an architected hybrid deployment strategy.

In this Broadcast, we will define Business Architecture, what it is, its components, audience, and its output – Business Capabilities to achieve the Organization’s Goals, and Objectives.

In the age of digital transformation, big data, cloud computing, one fundamental fact remains. What we in organizations are doing is processing data. Technology departments have many names nowadays. But fundamentally, they process data. We outline our approach to understanding processes – Process Mining that leads to a Business Process Warehouse. We review benefits & challenges, & outline field-proven approaches to obtaining benefits. We will also outline the methodology used to guide efforts.