TOGAF

Clear roles == Clear communication == Safe Sailing In the words of Susanne Kaiser: “if the underlying system does not evolve…” — here are some risk examples: AI mirrors broken structures: in a big ball of mud with messy models and fuzzy boundaries, it propagates inconsistencies and hallucinates domain meaning AI amplifies organizational frictions: with repeated handoffs between teams, AI-accelerated code generation creates bigger queues at the handoff. It does not increase throughput, but inventory. AI builds the wrong things faster: without strategic guidance, it custom-builds commodities for non-differentiating problems that already have off-the-shelf alternatives. For details: Building Foundations for Continuous (AI-accelerated) Change ...

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. ...