Ransford's NotesCourses
Workspace

Architecture Landscape Partitioning

Partition the architecture landscape into strategic, segment, and capability levels so the migration plan addresses the right level of abstraction for each work package.

Phase E, Opportunities and SolutionsDerived from TOGAF

Partitioning the architecture landscape on two axes: breadth and depth

Breadth on the vertical and depth on the horizontal slice the landscape into four partitions. Each quadrant carries the governance body that owns it and the weight it implies.

Partitioning is not a chart, it is a governance choice. Enterprise-wide and deep pulls a heavy central board, so the partition the architect picks is the governance load they sign up for.

Partitioning the architecture landscape on two axes: breadth and depth A two-by-two partitioning matrix on two blue axis rails: a vertical Breadth rail, local to enterprise-wide, and a horizontal Depth rail, shallow to deep. Each quadrant names a partition, with a blue marker for the body that governs it and a green marker for how heavy that governance is. Local plus shallow is Project level, owned by a local architecture lead with minimal governance. Local plus deep is a Domain deep model under central federation. Enterprise-wide plus shallow is Standards and policies, where a central body sets the rules lightly. Enterprise-wide plus deep, marked in red, is the Central deep model, owned by a central architecture board with heavy governance across all domains. Breadth: local to enterprise-wide Depth: shallow to deep Enterprise-wide, shallow Standards and policies Central body sets the rules Light touch, local teams implement Enterprise-wide, deep Central deep model Central architecture board owns it Heavy governance across all domains Local, shallow Project level Local architecture lead owns it Minimal, one gate per project Local, deep Domain deep model Domain architecture board owns it Local depth, central federation Who governs the partitionHow heavy the governance is Enterprise-wide and deep is the heaviest partition.It is the only quadrant that needs a central architecture board across every domain, so picking itcommits the work to that governance load.