Samuel Holcman: Thank you for tuning in to Real Talk. Be sure to join your host Sam Holcman again for another edition of our program. We'll have more Real Topics of discussion then. How do you sort out the so-called jargon from Enterprise Architecture and Business Architecture practices that work? Do the members of your organization find some business or technology advice utterly confusing? Welcome to Real with Sam Holcman. ⁓ In this program, we the record straight ⁓ and in terms that business people and technology people can understand. Now, here is host, Sam Holcman. ⁓ From Exams to Practice, a manifesto for the professionalization of enterprise architecture and business architecture. This is Real Talk with Sam Holcman. I'm Sam Holcman. Enterprise architecture and business architecture are at the same inflection point that software engineering has reached. When a field confuses vocabulary for competence, titles for capability, and exams for professional readiness, it creates a class of certified people who can describe the work without being able to actually do the work. This model is no longer good enough. The next year of Enterprise Architecture and Business Architecture certification must move away from exam-centric credentialing and toward practitioner-based professionalization grounded in evidence, judgment, and demonstrated delivery. Now is the problem with exam-only certification? Exam-based certification has always had one attractive feature. It's easy to scale. It is standardized, marketable, and administratively efficient. But efficiency and credentialing is not the same as validity in professional formation. A person can memorize terms, sequence frameworks, and reproduce definitions under time pressures without ever providing or proving the ability to diagnose a transformation problem, reason through trade-offs, or guide an organization through uncertainty. This manifesto parallels a broader point about software engineering. Organizations create expensive failure conditions when they allowed non-technical managers to lead technical work without the education, practice, or evaluative judgment required for the role. The result was not merely philosophical disagreements. It was churn. It was avoidable cost. It was architectural fragility. It was poor decision-making. It was delayed delivery. Enterprise architecture and business architecture suffer from an analogous problem. The field has tolerated too many professionals who are architecturally literate, but not architecturally seasoned, certified but not battle tested, fluent in framework language, but weak in live application. Exam-only certification has produced too many architects who can explain architecture and too few who can practice it under real conditions. Now why is architecture actually a practice. Architecture is not the resuscitation of meta models and meta frameworks. You can recite these all day long. It is the disciplined practice of framing complexity, making trade-off visible, designing viable futures, and governing change across time. Like software management, Architecture requires more than abstract knowledge. requires the ability to evaluate quality, risk, maintainability, economics, dependencies, and unintended consequences before failure becomes obvious. Inexperienced software managers tend to ignore non-functional requirements because they cannot defend them, measure them, or justify their investment in front of equally non-technical leadership. The architecture equivalent is familiar. Exam-trained architects often over-emphasize artifacts that are easy to present and under-emphasize qualities that are hard to govern, such as resilience, adaptability, interoperability, strategic coherence, decision latency, and organizational sustainability. The result is architecture that looks complete in a repository. but collapses in execution. Unmanaged technical debt eventually becomes structural failure. And that poor architectural decision spread costs throughout the landscape until major rework becomes unavoidable. The same thing is true in the enterprise domain. When enterprise architects and business architects lack real practice, organizations accumulate portfolio debt, capability fragmentation, governance theater, duplicated initiatives. Contradictory roadmaps and change fatigue. These are not academic defects. They are the business equivalent of spaghetti architecture. The end of framework tourism. What is this? It's the shiny object syndrome. The habit of selecting things because they are fashionable, heavily marketed, or socially validated rather than fit for purpose. Enterprise architecture and business architecture have their own version of the same pathology. It appears as framework tourism, method hopping, buzzword inflation, and the ritual adoption of whatever is currently sold as modern. Agile transformation, digital operating models, capability first planning, value stream mapping, AI strategy, platform thinking, or composability, and I can go on and on and on. None of these ideas are inherently wrong. Let me say it again, none of these ideas are inherently wrong. The problem begins, when certification rewards recognition of terminology rather than the disciplined evaluation of applicability. A real practitioner must be able to answer harder questions. Under what conditions does this method work? What assumptions does it carry? What trade-offs does it introduce? What evidence would justify using it here rather than somewhere else? Experienced professionals evaluate against requirements, not hype. Architecture certification should demand the same. Professionalization means demonstrated competence. Education and practical experience must work hand in hand, and that one without the other is insufficient for serious professional responsibilities. That principle should become the foundation of enterprise architecture and business architecture and certification. A professional architectural credential should require candidates to demonstrate actual practice. That means case-based assessments, peer reviews, mentor evaluation, and live defense of decisions. Candidates should show that they have framed real problems, developed architectural options, identified dependencies, reasoned through quality attributes, engaged stakeholders, and learned from outcomes. They should be assessed on judgment, not recollection. In practical terms, this means moving from asking, can the candidate name the phases, to asking, can the candidate use architectural reasoning to improve the odds of enterprise success? It means evaluating whether a business architect can connect strategy to capability change, whether an enterprise architect can identify cross-domain impacts, and whether both can prevent avoidable complexity before it becomes institutionalized. Now, what should practitioner-based certification require? A practitioner model should include four elements. Of course, structured knowledge, because professionals still need a shared language, conceptual discipline, and common standards. Evidence of practice, because architecture is proven in application, not in abstraction. Scenario-based evaluation. Architects must make decisions under ambiguity, competing interests, and incomplete information. And finally, ongoing development. Serious professional work requires continuous learning rather than one-time exam certification. The shift would change the social meaning of certification. Instead of signaling that a person has studied architecture, certification would signal that the person can practice architecture responsibly. Instead of rewarding exam performance alone, it would validate professional maturity. This is the new standard for enterprise architecture and business architecture. Enterprise architecture and business architecture now be treated as professions of consequence. They influence investment decisions, transformation sequencing, operating model design, technology coherence, and business adaptability. Roles with that much leverage should not be certified solely through memory tests. The future belongs to practitioners who can work across strategy, design, economics, and delivery, who can recognize debt before it spreads, who can resist hype, who can defend quality attributes, who can make architecture useful to real enterprises under real constraints. The age of exam-only certification should end. ⁓ has become too high. The next step is clear. Enterprise architect certification must move from exam-based qualification to practitioner-based validation. Business architect certification must do the same. Professionalization is not a branding exercise. It is the overdue recognition that architecture is a craft, a discipline, and a responsibility that must be demonstrated in practice. Please reach out to us. at www.eacoe.org and www.bacoe.org. We can assist you in moving in this direction today.