User-centric Enterprise architecture is about capturing, processing, organizing, and effectively presenting business and technology information to make it valuable and actionable by the organization for planning and governance.
Google is a company that epitomizes this mission.
After reading a recent article in Harvard Business Review, April 2008, I came to really appreciate their amazing business practices and found many connections with User-centric EA.
- Organizing information--Google’s mission [is] ‘to organize the world’s information and make it universally accessible and useful.’” Similarly in User-centric EA, we seek to organize the enterprise’s information and make it useful, usable, easy to understand, and readily accessible to aid decision making.
- Business and technology go hand-in-hand—“Technology and strategy, at Google, are inseparable and mutually permeable—making it hard to say whether technology is the DNA of its strategy or the other way around.” Similarly, EA is the synthesis of business and technology in the organization, where business drives technology, rather than doing technology for technology’s sake.
- Long-term approach—“CEO Eric Schmidt has estimated that it will take 300 years to achieve the mission of organizing the world’s information…it illustrates Google’s long-term approach to building value and capability.” Similarly, EA is a planning and governance function. EA plans span many years, usually at least 5 years, but depending on the mission, as long as 20 years for business/IT projects with long research and development cycles like in military and space domains.
- Architectural control—“Architectural control resides in Google’s ability to track the significance of any new service, its ability to choose to provide or not provide the service, and its role as a key contributor to the service’s functional value.” This is achieved by network infrastructure consisting of approximately one million computers and a target audience of 132 million customers globally on which they can test and launch applications. In EA, control is exercised through a sound governance process that ensures sound IT investments are selected or not.
- Useful and usable—“The emphasis in this process is not on identifying the perfect offering, but rather on creating multiple potential useful offerings and letting the market decide which is best…among the company’s design principles are…usefulness first, usability later.” In User-centric EA, we also focus on the useful and usable products (although not in sequence). The point being that the EA must have clear value to the organization and its decision makers; we shun developing organizational shelfware or conducting ivory tower efforts.
- Data underscores decision making—“A key ingredient of innovation at the company is the extensive, aggressive use of data and testing to support ideas.” EA also relies on data (business and technical) for planning and governance. This is the nature of developing, maintaining, and leveraging use of EA through information products that establish the baseline, target, and transition plan of the organization. A viable plan is not one that is pulled from a hat, but one that is data-driven and vetted with executives, subject matter experts, and other stakeholders. Further, EA provides business intelligence for governance and decision making.
- Human capital—“If a company actually embraced—rather than merely paid lip service to—the idea that its people are its most important asset, it would treat employees much the way Google does.” This concept is embedded User-centric EA, where the architecture is driven by the needs and requirements of the users. Further, Human Capital is a distinct perspective in User-centric EA, where people are viewed as the hub for all business and IT success.
In short, Google is a highly User-centric EA-driven organization and is a model for many of its core tenets.