Enterprise Intelligence

I’m called a Business Architect. But if I mostly create capability maps for IT programs, I am not necessarily defining business anatomy. But unless the capability map defines D1–D15 × P1–P6, it remains a business view. Not architecture.

A capability model answers one question: what areas exist in the enterprise? Architecture must answer what outcomes must be achieved (P1), how activities are sequenced (P2), how systems interact across rules, functions, UI, data, and timing (P3), and what components exist (P4). A capability map does not define these.

This principle challenges traditional models by asserting that every enterprise, and every project within it, shares a single anatomy

Understanding and leveraging the six key perspectives in enterprise architecture can significantly enhance an organization's efficiency, sca