Is what you deliver to stakeholders truly human-consumable - or just human-frightening? For over five decades, we have witnessed a pervasive problem: professionals produce lengthy strategy documents, complex maps, flows, and diagrams that business decision-makers simply skim or ignore. Having developed, implemented, managed, and perfected more successful Enterprise and Business Architectures worldwide than any other firm, we firmly believe your architecture deliverables must prioritize human consumption and stakeholder comprehension above all else. Through expert training and coaching from the Enterprise Architecture Center Of Excellence (EACOE) and the Business Architecture Center Of Excellence (BACOE), you will master how to create stakeholder-focused, easily digestible representations that generate clear understanding, actionable outcomes, and measurable success. Link to the full video is in the replies

The Purpose Of Strategy And Competitive Advantage. A clip from "What is Strategy? An Understanding For Business Architects and Enterprise Architects:" Watch the full video: architecturescoe.org/resourc… #EnterpriseArchitecture #Strategy #EnterpriseArchitect

A consistent set of components is required for Enterprise Architecture success; there are four “keys:” •A thinking tool - a frame of reference - a framework •A methodology that is a "recipe" (Not just a general body of knowledge) •Human-consumable Architecture models •Human-consumable Relationship models These four elements are used to develop the true result of Enterprise Architecture - a prioritized set of Initiatives that enable the Enterprise strategy. The techniques outlined in EACOE Enterprise Architecture Programs are universally effective techniques, regardless of the planning domain. Learn more about developing, delivering, and managing Enterprise Architecture on our website: eacoe.org/workshop-preview-a… #EACOE #EnterpriseArchitecture #EnterpriseArchitect

It is hard to "see" and understand business strategy, business change, and solutions in "700 pages of text." A lack of clarity in business understanding is due to the complexity and non-human-consumable business representations and technology transformations that are often declared “Architecture.” EACOE and BACOE Architecture is the enablement of business strategy and Enterprise agility (flexibility). Develop a set of prioritized, aligned initiatives and capabilities needed to meet the organization’s goals. Human consumable graphical representation are the key to simplifying and understanding complexity. Watch "Why Managers and C-suite needs Architecture" on youtube: youtu.be/XLUsGN6ZZfc #EnterpriseArchitecture #EnterpriseArchitect #EACOE

Strategy is frequently used in competitive environments (Business, IT, Politics, Sports, War, etc..), yet its true essence often needs to be discovered and understood. This three-part paper on "What Is Strategy" aims to shed light on what strategy truly means, its common pitfalls, and how it can be harnessed for success. Download and read the article "What Is Strategy: A Three-Part Exposé" using this public resource library link: architecturescoe.org/resourc… In the first installment, we dive into the question, "What is strategy?" In part two, we discuss "Fool’s Gold" and its relationship to strategy. Section 3 of “What Is Strategy: A Three-Part Exposé” identifies the one sentence vital in developing a strategy statement. #RealTalkWithSamHolcman #TipsFromSam #EACOE #BACOE #EnterpriseArchitecture #BusinessArchitecture

An extensive article on "The Value of Enterprise Architecture" by Tony Brown. Read the full article: architecturescoe.org/resourc… In this article, Tony Brown uses case studies to review six commonly reported EA benefits, namely: 1.Readily available documentation of the enterprise; 2.Ability to unify and integrate business processes across the enterprise; 3.Ability to unify and integrate data across the enterprise and to link with external partners; 4.Increased agility by lowering the "complexity barrier"; 5.Reduced solution delivery time and development costs by maximizing reuse of enterprise models; 6.Ability to create and maintain a common vision of the future shared by both the business and IT communities, driving continuous business/IT alignment. "Without doubt, the Volkswagen of America example is a model EA success story, reflecting the full, top-down value of EA to the enterprise. The specific points cited in the case study could perhaps serve as a benchmark for a fully mature EA program." - Tony Brown Read the full article: architecturescoe.org/resourc… #RealTalkWithSamHolcman #TipsFromSam #EACOE #BACOE #EnterpriseArchitecture #BusinessArchitecture

Significant confusion remains as to what Enterprise Architecture is and what it produces. We suggest one reason for this confusion, is the Certification and Training Organizations that are providing an Enterprise Architecture definition that parallels what they teach. Let us look at the different foci. Watch on Youtube: youtu.be/J2CfqZ1bUiE Watch or listen on the ArchitecturesCOE website: architecturescoe.org/resourc… Listen on Apple Podcasts: apple.co/44CBHwr Listen on Spotify: open.spotify.com/episode/0BL… #RealTalkWithSamHolcman #TipsFromSam #EACOE #BACOE #EnterpriseArchitecture #BusinessArchitecture

The key to getting professionally recognized and making more money as an Enterprise Architect does not come from a "logo" next to a name or having read a bunch of books. Enterprise Architect proficiency and success come from practice with a proven, high-return, cost-effective approach to Enterprise Architecture and stakeholder-focused deliverables that enable business strategy, reduce complexity, drive innovation, increase efficiency, and manage change. We get you ready to develop Enterprise Architectures "next Monday morning!" More than theory alone, EACOE Certification has you participating in all the phases of Enterprise Architecture and certifying your ability to transfer that knowledge to your organization. There are four distinct member badges to recognize the professional accomplishments of EACOE Certified Enterprise Architect Practitioners: eacoe.org/enterprise-archite… #EnterpriseArchitecture #EnterpriseArchitect #EACOE

Enterprise Architecture has a problem. For decades, architects have churned out complex diagrams and binders of documentation that only a handful of technical specialists can interpret - while the business quietly moves on without them. Stakeholders do not care about your meta models, capability maps, cryptic diagrams, or colorful maps; they care about growth, risk, and ROI. That is exactly what Enterprise Architecture 5.0 is designed to fix. Instead of starting with frameworks or reference models, EA 5.0 starts with measurable business goals and uses two simple but powerful ideas HACs ™ (architecture of intent) and HICs TM (architecture of delivery) - to create living architecture that connects vision directly to execution. Stakeholders see why something matters, delivery teams see what to build, and both are tied back to the same intent. The outcome is a different kind of architecture conversation: •From documentation to direction. •From governance for its own sake to guidance that drives decisions. •From paralyzing complexity to clarity that leaders can act on with confidence. This is not hypothetical. EACOE has been training professionals in this approach for decades, and with agentic AI accelerating everything from decisions to delivery, an EA 5.0 model that is business led, explicit, and traceable is rapidly shifting from “nice to have” to unavoidable. If you are tired of architecture no one reads, and ready to practice architecture that actually changes outcomes, this is where to start: 👉 eacoe.org/enterprise-archite… #EnterpriseArchitecture #EnterpriseArchitect #EACOE

Planned obsolescence in Enterprise Architecture or Business Architecture certification takes on a unique and often contentious form when certifying bodies release a recent version of a credential, effectively making earlier versions less valuable or even obsolete, despite earlier assurances of permanence or lifetime validity. This scenario can have significant repercussions for certified professionals and organizations alike. One indicator of this phenomenon is a certification that is attached to a named and shown certification version number. Enterprise Architecture or Business Architecture Certification Planned Obsolescence: The Impact of New Certification Releases. Read the full article on this link: architecturescoe.org/resourc… -- #RealTalkWithSamHolcman #TipsFromSam #datamodeling #SmallLangaugeModels #EAI #AI #AugmentedInformation #ArtificialIntelligence #EnterpriseArchitecture #EnterpriseArchitect #EACOE #BACOE #BusinessArchitecture #BusinessArchitect

If your executives cannot actually use your enterprise architecture to make strategic decisions, you do not have Enterprise Architecture. You have expensive technical documentation. REAL enterprise architecture - Realistic, Enabling, Actionable, Logical - has one non negotiable rule: it must speak the language of business, not the language of frameworks, not the language of technology. If the C suite needs a translator to understand it, it is already failing its job. EA 5.0 is built on that premise. It uses H.A.Cs™ (Holcman Architecture Containers) to capture what the organization is trying to achieve and which initiatives matter, and H.I.Cs™ (Holcman Implementation Composites) to turn that intent into delivery - funding logic, transformation pathways, and measurable strategic impact. No thousand arrow diagrams. No jargon driven complexity. Just clear, traceable connections from business vision to execution reality. This is exactly the connective tissue most AI initiatives are missing. Boards want AI to restore growth and productivity, but too many programs jump straight into tools and models without mapping them to strategy, operating model, or the processes that actually create value. The result: lots of AI, not a lot of ROI. EACOE enabling Enterprise Architecture fills that gap by making architecture consumable in the boardroom and executable in delivery - something it has been doing for decades while the rest of the field argues about frameworks. With agentic AI increasing both complexity and urgency, EA 5.0 stops being a “nice upgrade” and starts looking like the only sane way to run an enterprise. If you want architecture that your executives can read, trust, and act on, it is time to move past documentation and into EA 5.0. Start that transformation here: eacoe.org/enterprise-archite… #EnterpriseArchitecture #EACOE #EnterpriseArchitect

Successfully capturing the value of a Holistic Enterprise Architecture is very achievable if you approach the task in a thoughtful, guided fashion. This article shares the four significant components or four “Pillars” of any successful Holistic Enterprise Architectural effort. The Four Pillars Of Holistic Enterprise Architecture. Driving Efficiency and Innovation by Consistently Managing Complexity and Change. Read the full article on this link: architecturescoe.org/resourc… Designing an Enterprise Architecture is a people-oriented analysis and solution, not one only of technology. Peoples’ business knowledge forms your enterprise’s foundation. We recognized in many actual Holistic Enterprise Architecture engagements, a consistent set of required components for success; these four “pillars” are. •Architectural Models, •A Framework, •A Methodology, and •Solution Models. #EnterpriseArchitecture #EnterpriseArchitect #EACOE

What is the right question to ask about AI in your enterprise? It is not "Which model do we use?" It is: "What architecture will that model be reading from?" Last week on our live broadcast, we unpacked exactly this. AI without an ontology-based Enterprise Architecture is just guessing in an exceptionally large room. AI with architecture is operating inside a designed, navigable, and auditable enterprise library. Dewey turned a room full of books into a navigable system of knowledge. An EACOE ontology-first Enterprise Architecture does the same for AI. Watch the full session here: architecturescoe.org/resourc… #EnterpriseArchitecture #EACOE #EnterpriseArchitect #AI

Unpopular opinion: Your certification logo isn’t what makes you a great Enterprise Architect or Business Architect. There, it’s said. We just hit publish on a no-BS deep dive into what actually separates "paper architects" from the people executives fight to get into the room. Spoiler: Passing a multiple-choice exam isn’t it. After more than five decades in this field, we’ve lost count of how many “certified” architects we’ve seen crank out gorgeous reference models, colorful maps, and eye-watering diagrams… that nobody uses. The business moves on. The slides stay in PowerPoint. The architects who matter? - They’re in the room before the decision is made. - Leaders treat them like trusted advisors, not documentation machines. - Their work shows up in outcomes, not just in binders and modeling tools. Here’s the uncomfortable truth about what really matters: - Turning complexity into clear, simple choices executives can act on. - Earning trust by delivering quick wins and showing your work, not hiding behind jargon. - Thinking strategically across business goals, data, process, organization, location and events – and connecting the dots. - Influencing without authority, aligning stakeholders who want different things, and navigating politics without drama. - Operating with stakeholders, for stakeholders — not worshiping a framework as if it’s a religion. And the problem with most certification exams? - They test recall, not judgment. Memory, not mindset. - They reward people who can recite terminology, not those who can broker trade-offs in a tense steering committee. - They quietly encourage “model freaks” who love governance theater more than business value. In the new article, we lay out the full picture: the behaviors that build real stakeholder trust, the red flags that scream “paper architect,” and the soft skills that separate theory from tangible enterprise impact. 👉 Read: “What Makes a Great Enterprise Architect or Business Architect.” architecturescoe.org/resourc… Your turn: ► What do you think makes a great Enterprise or Business Architect? ► Have you ever seen a “highly certified” architect completely miss the point? Drop your experience in the comments — the next generation of architects is reading. #EnterpriseArchitecture #BusinessArchitecture #EnterpriseArchitect #BusinessArchitect #RealTalkWithSamHolcman

This is a clip from our recent broadcast, "Federated Architecture: Currently the Most Practical Approach to Business Architecture and Enterprise Architecture." From our five decades of field practice with thousands of organizations around the world, it was in the late 90s when we ran into our first version of this approach to "Federated Architecture." Access to the full broadcast can be found here - architecturescoe.org/resourc… #EnterpriseArchitect #EnterpriseArchitecture #BusinessArchitecture #BusinessArchitect #RealTalkWithSamHolcman

A rapidly decreasing number of enterprise architecture teams still keep a “principles” catalog. “Reuse before build.” “One source of truth.” “Align with business objectives.” It sounds serious. It looks professional on a slide. But here is the uncomfortable question: Has a single project in your organization ever been stopped, redesigned, or reprioritized because it violated one of those principles? If the honest answer is no, then those principles are not governing anything. They are decorations around decisions made for other reasons. That is not architecture. That is a legitimacy costume. In the late 1980s through the 2000s, principle catalogs had their moment. Frameworks put 10–20 “architecture principles” front and center as required deliverables. Then the mid 2010s arrived. Product-centric ways of working forced EA to prove value in speed, customer impact, and cost. Static, unmeasured principle lists did not survive that scrutiny. The problem was never the idea of principles. The problem is how they are practiced. Vague, unmeasured slogans do not constrain decisions. They never show up in incentives, funding, or governance. And the organizations with pages of EA principles often still measure architects on document production and standards compliance - not on cost, speed, risk, or customer outcomes. What actually works is a small number of explicit goals with concrete measures. Instead of “Standardization and interoperability,” try: “Reduce the application portfolio by 25% in 3 years while improving time to market for new products by 20%.” Now you have a real target. Standards, patterns, and decisions either move those numbers or they do not. The difference is accountability: “We believe in good architecture” versus “We are accountable for these movements in the enterprise - and here is how architecture is moving those needles.” Take the classic: “Reuse before Buy, Buy before Build.” On its own, it cannot be measured and will not change behavior. Run it through an EACOE™ SMART lens and it becomes: “By Q4 2027, increase the percentage of new solution needs satisfied by reuse of approved platforms from 25% to 60%, cutting application run cost by 15% and reducing time to market by 20%.” The center of gravity in EA shifts from: ❌ “What do we believe?” to ✅ “What are we trying to achieve, how will we know, and how does architecture get us there?” Principles can still exist in that world - but they are distilled from goals and metrics, not invented as free-floating statements. 🎧 Listen to the podcast: architecturescoe.org/resourc… 📘 Read the full article: architecturescoe.org/resourc… If you’re ready to move from platitudes to real EA performance, reach out at: EACOE.org #EnterpriseArchitecture #BusinessArchitecture #EnterpriseArchitect #BusinessArchitect #RealTalkWithSamHolcman #EACOE #BACOE

CIOs are under intense pressure to harness AI to drive efficiency, innovation, and competitive advantage - but as the CIO article on "reimagining business processes" makes clear, the first step is not to “automate faster,” but to rethink how work actually happens before a single model is deployed. In this context, the EACOE Process Visualization approach emerges as a best practice methodology for reworking processes in preparation for AI, ensuring that organizations automate optimized workflows, not legacy inefficiencies. "Process Visualization: A Best Practice Blueprint for Reworking Processes Before AI" Watch on YouTube: youtu.be/JQ3h4_Xi5lo Watch or listen on the ArchitecturesCOE website: architecturescoe.org/resourc… Watch or listen on Spotify: open.spotify.com/episode/4tz… Listen on Apple Podcasts: podcasts.apple.com/us/podcas… #RealTalkWithSamHolcman #ProcessVisulization #EACOE #BACOE #EnterpriseArchitecture #BusinessArchitecture #AI #EAI #SmallLangaugeModels

Most AI initiatives don’t deliver real ROI. And it’s not because the models aren’t good enough. It’s because the enterprise isn’t. Boardrooms are betting on AI to restart growth and productivity, yet almost no one is wiring AI into the connective tissue between strategy, operating model, and the real data and processes agents will act on. That gap is exactly where Enterprise Architecture should live - and too often doesn’t. For years, traditional architects have been trapped in framework wars, technology-first focus, meta-model purity, and static diagrams that look great in slide decks while the business quietly moves on without them. The result? Beautiful models. Minimal impact. EA 5.0 flips that script. No more “models for models’ sake.” It starts with hard, measurable business goals and uses architecture as a decision tool for strategy, investment, and risk - not as a documentation exercise. Why does this matter for Agentic AI? Because agents will blindly amplify whatever business logic, constraints, and assumptions architects have - or haven’t - made explicit. As agents begin planning, deciding, and acting across customer journeys, supply chains, and support operations, the complexity doesn’t just increase - it explodes. Non-deterministic models suddenly sit in the middle of real workflows, changing real data, affecting real customers. At that point, hand-waving about “governance” isn’t enough. You need deterministic guardrails: - Clear data boundaries and ownership. - Strong segregation of duties between humans, systems, and agents. - End-to-end traceability from every autonomous decision back to goals, capabilities, initiatives, and rules. That’s not academic. That’s what it takes to keep AI powerful and safe in production. EACOE’s EA 5.0 methodology gives CIOs and architects technology-neutral views, explicit governance rows, and full traceability from business intent down to execution - so agents operate inside a clearly modeled business context, not a chaotic pile of disconnected systems and APIs. Agents don’t need to be feared, but they do need a well-architected arena to play in. If your architecture is business-led, explicit, and traceable, agents become force multipliers. If it isn’t, they become very fast, very confident amplifiers of your existing chaos. For a deeper breakdown of how Agentic AI and EA 5.0 fit together, including the concrete patterns and guardrails, read the full article: 👉 “Agentic AI, EA 5.0, and EACOE” architecturescoe.org/resourc… #AI #ArtificialIntelligence #EnterpriseArchitect #EnterpriseArchitecture

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. But if you take that message into the C‑suite or the boardroom, and you lead with “data debt” and “process standardization,” you will lose the audience that matters most. 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. "Purchased Models, Off-the-Shelf Ontologies, and Why Everything Old Is New Again" Watch on YouTube: youtu.be/mC9p8IVF-2w Watch or listen on the ArchitecturesCOE website: architecturescoe.org/resourc… Watch or listen on Spotify: open.spotify.com/episode/6bt… Listen on Apple Podcasts: podcasts.apple.com/us/podcas… #RealTalkWithSamHolcman

TOGAF presents years of IT implementation experience dressed up as “enterprise architecture.” But it does not present an architecture, nor a true architecture development approach. That’s Bernard Baillargeon’s conclusion after a 17-page, point-by-point comparison of TOGAF® and EACOE™. His bottom line is blunt: TOGAF is IT-focused. EACOE is business-focused. TOGAF buries Business Architecture as a peer to IT-centric domains - applications, information, and technology - when it should be the driver. That framing quietly erodes the real power of business intent and turns “business” into just another checkbox in an IT method. Worse, TOGAF says Business Architecture is a prerequisite, then runs phases that barely depend on it. You get weak traceability, composite documents instead of crisp, traceable artifacts, and “architecture” that looks more like prescriptive IT solutioning than true enterprise design. EACOE flips this script. It starts with business language and human-consumable artifacts that leaders can actually read, challenge, and use to make decisions. No initial IT bias. No baked-in technology assumptions. Just a platform of knowledge built through comparison, discovery, investigation, and refinement - until there’s a clear, shared picture of how the enterprise works and where it needs to go. Only then does technology enter the conversation as “make to order” implementations that align to that evolving business vision - not as handcrafted apps chasing the latest tool or vendor trend. That’s where enterprise agility really comes from: •A living, changing representation of the business. •Explicit, traceable decisions from intent → design → implementation. •Technology following the business, not the other way around. EACOE also calls out a hard truth the industry often dodges: Enterprise Architecture is a practice, not a multiple-choice exam. Skills are forged in real engagements, with stakeholders, constraints, and consequences - not in a proctored test center. TOGAF’s strength is clear: over 300 IT vendors and IT clients behind it. But that strength comes with a cost: heavy IT emphasis, committee-driven evolution, and a pace of change that lags what modern enterprises actually need. If you’re leading IT projects, TOGAF offers useful guidance. If you want true Enterprise Architecture - business-led, human-consumable, deeply traceable, and outcome-focused - EACOE delivers what TOGAF structurally cannot. Curious what that looks like in detail? Bernard Baillargeon’s full 17-page comparison pulls no punches: 👉 “TOGAF® and EACOE™: A Comparative Review.” architecturescoe.org/resourc… #EnterpriseArchitecture #EnterpriseArchitect

“I wanted something I could start tomorrow. Not spend six months building a practice the business sees as more red tape.” That was the reality for Mohammed Khalil - and it is painfully familiar for a lot of Enterprise Architects. They are stuck with: - No common ground for enterprise architecture or business architecture. - EA seen purely through a technology lens. - A complex, federated environment with many departments and agendas. - Methodologies that demand endless customization before delivering any value. Mohammed went a different route with the EACOE Enterprise Architecture approach, built around three blunt principles: 1. Traceability and transparency: Harvest everything, trace it back to real sources, and surface what is outdated so people can see the truth instead of debating opinions. 2. Human consumable representation: No thousand arrow diagrams that make stakeholders shut down - just clear visuals and language leaders can understand in minutes. 3. Immediate implementation: Tools, methodologies, and frameworks you can use Monday morning, not theory you study for months while the business loses patience. The impact? Initiatives that are prioritized, ranked, and ingested straight into their intake process – a living ecosystem of strategy instead of static diagrams rotting in a repository. The phrase Mohammed kept hearing from stakeholders was simple and powerful: “That makes sense.” Because enterprise architecture shouldn’t mystify. It should clarify. 🎥 Watch Mohammed’s full story: youtu.be/74lfKxzP8lw 🔍 Curious about the training and methodology behind it? Start here: EACOE.org #EnterpriseArchitect #EnterpriseArchitecture