Two questions that must not be confused

AS-IS asks what is accepted as the current architecture. TO-BE asks what a team proposes to change. The distinction sounds simple until several projects work on the same application, API or capability at once.

Why a status flag is insufficient

Putting 'Proposed' on a shared record can obscure whether the original architecture is still in force. Updating the only copy of an application to describe its intended future can make current-state reporting inaccurate before the change has been reviewed or delivered.

Projects need isolated architectural intent

A practical approach gives delivery projects their own proposed revisions while retaining an authoritative active state. Multiple projects may propose changes to the same element without overwriting each other. An architect should be able to inspect the accepted baseline and each proposal deliberately.

Promotion needs review and reconciliation

Before a proposed revision is activated, it should be reviewed against the latest accepted state. Conflicting changes require explicit reconciliation, not a last-writer-wins overwrite. Activation then becomes a controlled business event with historical traceability.

A model for ongoing change

Architecture is not a sequence of isolated PowerPoint snapshots. It is a history of accepted decisions, proposals and transitions. Treating that history as part of the underlying model creates a more reliable basis for governance and architectural collaboration.

The MétiArch perspective

Explore more MétiArch Insights for practical architecture perspectives.

← Explore all insights