Capture the smallest useful decision

A decision does not need an elaborate document to become discoverable. Record what was decided, the architectural assets affected, the responsible people, the rationale and the current status. A link to fuller evidence may be enough; avoid forcing the team to retype it.

Keep architecture and delivery tools in their lanes

A project tracker governs delivery tasks and milestones. An architecture catalogue governs the model and decisions about it. Referencing external work item IDs provides traceability without trying to turn the catalogue into another task management product.

Make future-state work explicit

Projects need a place to propose and review changes without rewriting the accepted architecture prematurely. Distinguish the current estate, proposed revisions, approved decisions and the moment a changed design becomes authoritative.

Design for practical adoption

Required fields should be truly essential, with recommended and optional information added progressively. A specialist workbench can simplify the workflow while using the same authoritative APIs as a comprehensive enterprise-wide view.

Practical lesson

Governance succeeds when it makes good architectural information easier to find and decisions easier to explain. The goal is a connected body of knowledge, not the largest possible form.

The MétiArch perspective

This article explains design principles and lessons from developing architecture tooling. Examples are illustrative. A described design approach does not, by itself, indicate that a feature is enabled or generally available in a deployed product.

← Explore all insights