Understand the characteristics of a Level 2 architecture function

A Level 2 architecture function has moved meaningfully beyond pure documentation and reactive governance into active, proactive advisory engagement. Your architects are present in delivery programs — attending design sessions, reviewing architectural decisions before they are made rather than after, and offering guidance informed by a genuine understanding of each program’s constraints and objectives. This is a real improvement over Level 1 in terms of architectural influence and organizational engagement.

The fundamental structural limitation of Level 2 is that the engagement remains advisory. Your architect recommends; the program team decides. Your architect identifies an architectural risk; the program team chooses whether to mitigate it or accept it. Your architect proposes a design approach; the program team adopts it, adapts it, or ignores it. When delivery pressure intensifies — when timelines compress and the program team is choosing between meeting a commitment and following an architectural recommendation — the recommendation loses. Your architecture function has moved from the periphery to the conversation, but it has not moved from the conversation to the decision.

Influence Without Authority

Level 2 architects frequently describe their operating model as “influencing without authority” — which accurately captures both the positive dimension (genuine influence on a significant proportion of architectural decisions) and the structural limitation (no authority to ensure outcomes). The influence is real when conditions are favorable. It evaporates when conditions become difficult. And when an architectural recommendation is not followed and the predicted consequence materializes — the integration fails, the platform cannot scale, the security gap is exploited — your architecture team was not accountable for the outcome and cannot claim credit for preventing it.