Enterprise-Architecture

Question: Why does DBJ begin with Capability Maturity Model assessment rather than jumping straight into technical delivery? Answer: Because transformation fails without measurable organizational readiness. The Foundation Problem Most enterprises attempt AI-assisted modernization while operating at ad-hoc levels. This creates: Misaligned expectations between business and technology Inconsistent terminology across stakeholder groups Undefined accountability for architectural decisions No repeatable process for evaluating technical risk Architecture-led, AI-assisted delivery requires stable foundations. CMM onboarding establishes those foundations before any work begins. ...

I dared to insert the term “Technical Debt” in standard text bellow Socrates then supposes that the prisoners are released. A freed prisoner would look around and see the fire. The light would hurt his eyes and make it difficult for him to see the objects casting the shadows. If he were told that what he is seeing is real instead of the other version of reality he sees on the wall of Technical Debt, he would not believe it. In his pain, Socrates continues, the freed prisoner would turn away and run back to what he is accustomed to (that is, the shadows of the carried objects of Technical Debt). The light “… would hurt his eyes, and he would escape by turning away to the things which he was able to look at, and these he would believe to be clearer than what was being shown to him.” ...

The AI hype cycle is running on fumes — and the fumes are labeled “Future,” “Promise,” and “More AI!” We’ve all seen it. A wobbly tower of buzzwords. Robots with megaphones. Executives cheering at a pile of rubble with “REALITY” written at the base. The cartoon writes itself because the pattern writes itself: Announce the AI initiative Stack acronyms until the tower looks impressive Call any collapse a “learning opportunity” Add more AI What’s actually out of hand isn’t AI. It’s the organizational incompetence that AI is being asked to hide. ...

There’s a word MIT hackers coined in the 1950s: cruft — useless, tangled, accumulated junk that makes a system incomprehensible and impossible to build on. Sound familiar? In 2026, we have a new variant: crufty AI. Chatbots bolted onto data silos. LLMs fed dirty, unstructured, undocumented inputs. Automation layered on top of processes nobody fully understands anymore. Pilots that never graduate. Dashboards nobody uses. Vendors paid. ROI: zero. This isn’t an AI problem. It’s a cruft problem. ...