Recognize the signals that indicate a Level 2 posture - Enterprise Architecture Value Model

Recognize the signals that indicate a Level 2 posture

(Chapter 17 of Enterprise Architecture Value Model)

Executive Summary: Chapter Overview

IF4IT

The Bottom Line

This chapter explains how recognize the signals that indicate a level 2 posture reflects the Level 2 advisory posture, where architecture is more actively engaged but still recommends without owning. It helps leaders understand why influence without authority improves engagement but still leaves architecture easy to bypass under delivery pressure.

Core Concepts

Concept	Definition & Strategic Role
Level 2 — Advise	Defines the architecture operating posture in which the function recommends without owning, including its value profile, limitations, and organizational consequences.
Operating Signals	Identifies observable behaviors, deliverables, and leadership evidence that reveal whether the architecture function is operating at this level.
Advancement Requirements	Clarifies the authority, staffing, engagement, delivery accountability, or ownership changes needed to progress to the next level.

Quick Q&A

Question: Why is Level 2 still insufficient?

Answer: Level 2 creates more engagement and influence, but the architecture function still recommends without authority and can be bypassed when delivery pressure increases.

Your architects are actively present in delivery programs but in an advisory capacity — they do not hold formal accountability for delivery outcomes.
Architectural guidance is followed more often than at Level 1 but still inconsistently, particularly when delivery timelines are under pressure.
Your architecture function has strong technical credibility with delivery teams but limited organizational authority with program sponsors and business stakeholders.
When architectural recommendations are overridden by delivery decisions, the recourse is documentation of the override and continued advisory engagement — not a mechanism that produces timely resolution.
Your architecture function is invited to initiative planning and design sessions but not to the executive conversations where initiative priorities and investment decisions are made.
Architecture roadmaps are produced and published, but their execution depends on the cooperation of delivery teams over whom architecture has no authority — making them difficult to maintain and easy to deprioritize.
When asked to account for its contribution to specific delivery outcomes, your architecture function can point to the advice it gave but not to the decisions it made or the outcomes it owned.

How to cite this page

When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.

Example (informal web citation):

The International Foundation for Information Technology (IF4IT), LLC. Recognize the signals that indicate a Level 2 posture | Enterprise Architecture Value Model. https://if4it.org/best-practices/enterprise-architecture-value-model/recognize-the-signals-that-indicate-a-level-2-posture/ (accessed 2026-09-11).

See About Us for content governance and site-wide citation guidance.

Legal Disclaimers