As Forrester’s EA tools analyst specialist, I am regularly receiving inquiries from EA teams that are encountering trouble choosing the "single repository of truth" for the entire enterprise. Generally, they are oscillating between two products after a long decision process, hesitating in many cases because no one product is able to satisfy all the architects: the EAs, the solution architects, and sometimes the business architects. One product satisfies some architects and not the others, and vice versa; in the end, choosing one single product would not satisfy anyone because for each option that will satisfy a few, some will not use it (generally, for good reason), and it will not give others the information they require to do their job. Therefore, for these EA teams, the dream of getting a "single repository of truth" is becoming a nightmare. I encounter this sort of dilemma in half of the inquiries I receive about EA tools and particularly within the largest companies.
My answers are sometimes difficult for these EA teams to hear:
First: Do all team members agree on EA objectives for the next two to three years? Do all architects know and share the same IT objectives and priorities? If EA and IT objectives/priorities are not clear, it is not surprising that they want different tools, because a universal EA tool does not really exist at this time. The recent document I published about the EA management suite as a third generation of EA tools explains how the most recent two generations complement each other.
Broadens the definition of metadata beyond “data on data” to include business rules, process models, application parameters, application rights, and policies.
Provides guidance to help evangelize to the business the importance of metadata, not by talking about metadata but by pointing out the value it provides against risks.
Recommends demonstrating to IT the transversality of metadata to IT internal siloed systems.
Advocates extending data governance to include metadata. The main impact of data governance should be to build the life cycle for metadata, but data governance evangelists reserve little concern for metadata at this point.
I will co-author the next document on metadata with Gene Leganza; this document will develop the next practice metadata architecture based partially but not only on a metadata exchange infrastructure. For a lot of people, metadata architecture is a Holy Grail. The upcoming document will demonstrate that metadata architecture will become an important step to ease the trend called “industrialization of IT,” sometimes also called “ERP for IT” or “Lean IT.”
In preparation for this upcoming document, please share with us your own experiences in bringing more attention to metadata.
My colleagues Ted Schadler and Josh Bernoff are preparing the launch of their coauthored new book, Empowered, after the success of Josh Bernoff’s Groundswell. Basically, Empowered’s message is: "If you want to succeed with empowered customers, you must empower your employees to solve their problems . . . . From working with many, many companies on social technology projects, we've found that the hard part is not just the strategy. The really hard part is running your organization in such a way that empowered employees can actually use technology to solve customer problems.” (Josh Bernoff, Groundswell blog post).
Coupled with Smart Computing — a new cycle of tech innovation and growth within the technology industry that Andrew Bartels described — this movement toward empowered employees represents what I consider to be Web 3.0: the next generation of Internet/intranet/extranet usage that will benefit the enterprise and employees. By adopting “Web 3.0,” enterprises can expect productivity improvements of 5% to 15% as well as improved customer satisfaction.
Enterprises should prepare themselves to benefit from Web 3.0 by: