You have heard the phrases: 'if we only had a mandate'; 'we need a design authority'; 'the business unit is doing their own thing again.' All these phrases mean the same thing the EA team thinks they own a single decision. The same thing happens every time - what masquerades as target architecture, and the associated specification and standard are doomed to live out their days in bitter, resentful irrelevance.
All because the practitioners failed to act as architects. Architects inform stakeholder of the path that best addresses the set of stakeholder preferences; they ensure all concerns are addressed and then own the stakeholder decision. Poor practitioners believe that their narrow expertise and analysis of a problem space to optimize against a single parochial concern provides some super-power allowing them to see the one right path.
Conexiam’s EA Capability practice sees this trap everywhere. Teams that fall into this trap are on a fast path to the Architecture Graveyard. While EA teams heading on this route are a market opportunity for us, it is a trip you never want to make. The most dangerous part about this trap comes from its behavioral roots. Symptoms include a practitioner trying to use their seniority, status, or perceived expertise of a subject to influence support for an idea instead of providing a crisp traceability the organization's goals, objectives or gaps.
The implications of this behavior are dire. Teams will experience symptoms, such as sensing a loss of credibility, cuts in resources, and increasing bitterness. Typically the symptoms lead to an inability to meet with Stakeholders, and other decision makers, followed by exclusion from decision-making meetings. Meanwhile, the entire enterprise may as well aim a shotgun at its foot.
There is an easy solution to this trap: do architecture and follow the architecture governance process. Not the part where change initiatives are governed, the more important process where the creation of architecture is governed. In Essential EA Governance and the Leader’s Guide, we outlined a simple checklist designed to combat this trap.
This checklist ensures the architect has actually described a target that addresses the preferences of the Stakeholders rather than the parochial interest of subject matter experts or bystanders. Architecture that addresses Stakeholder’s preferences, and willingness to change, is an architecture that gets used.
Most importantly, the checklist highlights that no-one has decision rights other than Stakeholder; not the architect; not a subject matter expert; not an implementer; not the architecture review board. Just the Stakeholders. If you want to own a decision get the right job title.