Application Architecture for the Enterprise

Setting Values versus Enforcing Standards

Too many architects fall in to the trap of believing that the distinguishing value they provide to their respective organizations is in the form of defining and enforcing standards. While there is no doubt a role for standards and governance, these architects miss the fact that their most important role is to define the values of their organization.

When overemphasized, standards can become a death spiral... drawn out cycles of identification (by which time they are no longer optimal), blanket application (leading to loss of competitive advantage in cases where they don't apply), and loss of faith in the architecture organization. Standards too often contribute to the cult of ceremonial documentation, rather than the culture of working software. Fanatical standards enforcers also drive the most valuable innovation in organizations to the underground - it is demonized and ignored rather than cultivated and matured.

The differentiating value of an architect should be leadership and influence, not law enforcement. This happens when architects define value statements that are more durable positions than moment-in-time solution statements. Values have deeper meaning, and empower people in the organization to make independent decisions consistent with a larger vision, increasing agility. They allow for individual ownership of a stake in the enterprise architecture - every participant is a stakeholder.

Value statements and the leaders who promote them encourage teams to explore, report, refine, and share their decisions with the whole. Enterprises always have a mixed portfolio to manage - the most valuable mix will at least reflect a set of core architectural values rather than be a poor attempt at homogenization. Review of the portfolio should not be a witch hunt for non-compliant technologies... it should be a gardening effort to ensure the values are represented.

posted by scott @ 10:01 PM