Enterprise Architecture

It’s time for companies to develop a strategy for knowledge work—one that not only provides a clearer view of the types of information that workers need to do their jobs but also recognizes that the application of technology across the organization must vary considerably, according to the tasks different knowledge workers perform.

Better teamwork requires perpetual mutual helping, within and across hierarchical boundaries

But what I’m talking about is something much more profound and essential: knowing how to work with one another as equal partners in an operational setting.

Because they think that to change culture, you simply introduce a new culture and tell people to follow it. That will never work. Instead, you have to conduct a business analysis around whatever is triggering your perceived need to change the culture. You solve that business problem by introducing new behaviors.

The role of enterprise architect is changing, and sometimes development can be awkward. "Enterprise architects are caught off-guard, and the reason there is that there is this new paradigm," said Wells Fargo's Andrew Guitarte. "In fact, there is a shift in paradigm that business architecture is the new EA, and I am going out beyond my peers here in terms of predicting the future."

need to have a top-down view of how the business actually runs in order to navigate all the complexities and to make fact-based decisions on trade-offs affecting businesses and IT implementation.

The alternative is to build a company-wide rationale for information technology, bringing the internal supply (IT function) and demand (business unit) sides together to focus investment on the few distinctive capabilities that set the company apart. Most top executives understand this reality. They recognize the strategic value of visionary IT leadership, especially in helping their companies understand which strategies are most viable. Some companies have been able to achieve that kind of IT leadership. But many do not know, in practice, how to get there from where they are today.

Corporate capabilities and information technology are intertwined in every company, but the relationship between them is often misunderstood. A capability is the ability to reliably and consistently deliver a specified outcome relevant to your business. This capability is ensured through a combination of processes, tools, knowledge, skills, and organization that are all focused on meeting the desired result.

If you are a CEO, a CFO, or a business leader, you should insist that the IT function develop a complementary road map for its investments. Your business and IT leaders should develop this road map collaboratively. Conversely, if you are a chief information officer seeking to adopt this sort of road map, you may find yourself alone at first. You will need to influence the culture and governance systems of the larger company. You might, for example, seek to include the IT road map process in annual strategic planning exercises, set up joint business–IT governance councils, or establish new metrics for the performance and relevance of IT projects. You will need to insist on broad business participation in high-level IT decisions. Finally, you might seek IT oversight policies such as those imposed at Royal Dutch Shell PLC, where 80 percent of IT spending was dedicated to the 200 most strategically important applications. Now is the time to raise the bar on IT investment planning, to make sure investment capital is used to position the business for success. As a CIO or IT leader, you must focus on enabling the corporate strategy, not fighting about technology standards or managing budgets. As a CEO, a CFO, or a business leader, you must seek to understand how technology can enable your capabilities, instead of simply trying to reduce your unit service cost. The integral role of IT gives you a unique vantage point from which to help the business identify the right capabilities and bring them together across the value chain. With a well-designed road-mapping process, you can give IT the role that it deserves.

Most enterprise architecture (EA) initiatives remain trapped in the IT department, and a new approach – hybrid thinking – is required to break EA out and into the wider organisation, according to Gartner, Inc. Adopting hybrid thinking is an excellent way to meld design thinking, IT thinking and business thinking, and achieve transformative, innovative and strategic changes.