Recommend what to keep, drop or tighten from the TOGAF Content Framework given your engagement's size, speed and risk profile.
ADM-wideDerived from TOGAF
TOGAF tailoring runs as a closed cycle: scope, scale, review, adjust
Four steps arranged as a clockwise ring form the tailoring cycle. The closing arrow loops the adjusted method back to the first step, so the method one programme leaves behind becomes the starting baseline for the next.
Tailoring is not a one-shot choice made at kick-off. The cycle forces a review of the method against actual delivery and an adjustment for the next programme, so each cycle leaves the method fitter than the last.
Keep 11, simplify 6, drop 3 of 20 artefacts.
Business architecture
Organisation/Actor Catalogue
Keep
catalogue, Phase B
Essential for traceability of who owns what across the architecture.
Driver/Goal/Objective Catalogue
Keep
catalogue, Phase B
Always required. Without stated goals, the tailoring itself has no anchor.
Role Catalogue
Keep
catalogue, Phase B
Roles must be explicitly stated so RACI assignments are defensible.
Business Service/Function Catalogue
Keep
catalogue, Phase B
Needed to trace business capabilities through to application and technology layers.
Business Interaction Matrix
Drop
matrix, Phase B
The overhead of a full interaction matrix is not justified at this scale.
Business Footprint Diagram
Simplify
diagram, Phase B
A simplified version gives enough context without full production effort.
Data architecture
Data Entity/Data Component Catalogue
Keep
catalogue, Phase C
Data entities underpin every integration contract. Full catalogue is warranted.
Data Entity/Business Function Matrix
Simplify
matrix, Phase C
Existing data governance can be referenced. A delta view is sufficient.
Conceptual Data Diagram
Simplify
diagram, Phase C
A simplified conceptual diagram helps align stakeholders without full formal notation.
Logical Data Diagram
Keep
diagram, Phase C
The logical data model is the primary contract between data and application architects.
Data Dissemination Diagram
Drop
diagram, Phase C
The cost of a full dissemination diagram is not justified for this profile.
Application architecture
Application Portfolio Catalogue
Keep
catalogue, Phase C
Without an application catalogue, the architecture has no systems inventory.
Interface Catalogue
Keep
catalogue, Phase C
Interface contracts are the primary source of integration risk. Full catalogue required.
Application/Organisation Matrix
Simplify
matrix, Phase C
A simplified mapping of applications to organisational units is sufficient.
Application Communication Diagram
Keep
diagram, Phase C
Application-to-application communication is a primary failure mode. Full diagram required.
Technology architecture
Technology Standards Catalogue
Keep
catalogue, Phase D
Without a standards catalogue, technology choices are ungoverned.
Technology Portfolio Catalogue
Keep
catalogue, Phase D
The technology portfolio underpins licensing, support and lifecycle planning.
Application/Technology Matrix
Simplify
matrix, Phase D
A simplified matrix covering critical applications is sufficient.
Environments and Locations Diagram
Drop
diagram, Phase D
Single-environment engagements do not need this artefact.
Platform Decomposition Diagram
Simplify
diagram, Phase D
Existing platform documentation can be updated. A delta view is sufficient.
Governance justification
This tailoring covers 20 TOGAF Content Framework artefacts for a programme-level, medium-risk engagement with a developing architecture practice. Of these, 11 are retained in full, 6 are simplified to reduce overhead, and 3 are dropped as not cost-effective for the engagement profile. This tailoring should be reviewed by the architecture governance board and recorded as a decision in the Architecture Decision Log.