Virtual Relationships and Enterprise Architecture

User-centric EA is based on establishing relationships. There are relationships with stakeholders, which includes understanding their information and governance needs and working to fulfill those. There are also relationships with subject matter experts in both the business and technical areas of the enterprise -- since EA bridges the worlds of mission-business and technology, the chief Enterprise Architect must build relationships in both worlds and facilitate information flow (discovery and exchange) between them and into architecture and planning products for the organization.

EA relationships are real, not virtual

Virtual world online games, such as Second Life, have simulated seemingly all facets of human existence, even relationships. The Wall Street Journal, on August 10, 2007 reports that studies show that "virtual relationships mirror real life...people respond to interactive technology on social and emotional levels much more than we ever thought...on a neurological level, players may not distinguish between virtual and real world relationships studies suggest."

However virtual relationships are not real relationships, which is required for User-centric EA. EA requires building genuine real world relationships, gathering requirements, developing user-centric solutions, and communicating on all levels with stakeholders and partners.

Also, EA is not a game (obviously!). It has real world implications for an organization if done correctly (or not). The results of EA can be the difference between executing on mission and pretending to be fat and happy in Second Life.

How important are relationships to your EA program?

Virtual Relationships and Enterprise Architecture