Categories
erwin Expert Blog Enterprise Architecture

Enterprise Architecture: Secrets to Success

For enterprise architecture, success is often contingent on having clearly defined business goals. This is especially true in modern enterprise architecture, where value-adding initiatives are favoured over strictly “foundational,” “keeping the lights on,” type duties.

But what does enterprise architecture success look like?

Enterprise architecture is central to managing change and addressing key issues facing organizations. Today, enterprises are trying to grow and innovate – while cutting costs and managing compliance – in the midst of a global pandemic.

Executives are beginning to turn more to enterprise architects to help quickly answer questions and do proper planning around a number of key issues. The good news is that this is how enterprise architects stay relevant, and why enterprise architect salaries are so competitive.

Here are some of the issues and questions being raised:

  • Growth: How do we define growth strategies (e.g., M&A, new markets, products and businesses)
  • Emerging Markets: What opportunities align to our business (e.g., managing risk vs ROI and emerging countries)?
  • Technology Disruption: How do we focus on innovation while leveraging existing technology, including artificial intelligence, machine learning, cloud and robotics?
  • Customer Engagement: How can we better engage with customers including brand, loyalty, customer acquisition and product strategy?
  • Compliance and Legislation: How do we manage uncertainty around legislative change (e.g., data protection, personal and sensitive data, tax issues and sustainability/carbon emissions)?
  • Data Overload: How do we find and convert the right data to knowledge (e.g., big data, analytics and insights)?
  • Global Operations: How do we make global operations decisions (e.g., operating strategy, global business services and shared services)?
  • Cost Reduction: What can we do to reduce costs while not impacting the business (e.g., balance growth goals with cost reduction, forecast resources needs vs. revenue)?
  • Talent and Human Capital: How do we retain, empower and manage employees and contractors (e.g., learning and development, acquisition and retention, talent development)

Enterprise architecture

Undeniable Enterprise Architecture Truths & the Secrets to Success

As enterprise architects, we need to overcome certain undeniable truths to better serve our organizations:

  1. Management does not always rely on EA to make critical decisions: They often hire consultants to come in for six months to make recommendations.
  2. Today’s enterprises need to be agile to react quickly: Things change fast in our current landscape. Taking months to perform impact analysis and solution design is no longer viable, and data has to be agile.
  3. Enterprise architecture is about more than IT: EA lives within IT and focuses on IT. As a result it loses its business dimension and support.

What can enterprise architects do to be more successful?

First and foremost, we need to build trust in the information we hold within our repositories. That has been challenging because it takes so long to collect and keep relevant and that means our analyses aren’t always accurate and up to date.

With more governance around the information and processes we use to document that information, we can produce more accurate and robust analyses for a true “as-is” view of the entire organization for better decision-making.

Next, we need to close the information gap between enterprise architecture functions that fail to provide real value to their stakeholders. We also need to reduce the cost of curating and governing information within our repositories.

Taking a business-outcome-driven enterprise architecture approach will enhance the value of enterprise architecture. Effective EA is about smarter decision-making, enabling management to make decisions more quickly because they have access to the right information in the right format at the right time.

Taking a business-outcome approach means enterprise architects should:

  • Understand who will benefit the most from enterprise architecture. While many stakeholders sit within the IT organization, business and C-level stakeholders should be able to gain the most.
  • Understand your leadership’s objectives and pain points, and then help them express them in clear business-outcomes. This will take time and skill, as many business users simply ask for system changes without clearly stating their actual objectives.
  • Review your current EA efforts and tooling. Question whether you are providing or managing data the business does not need, whether you are working too deeply in areas that may not be adding value, or whether you have your vital architecture data spread across too many disconnected tools.

Why erwin for Enterprise Architecture?

erwin has a proven track record supporting enterprise architecture initiatives in large, global enterprises in highly regulated environments, such as critical infrastructure, financial services, healthcare, manufacturing and pharmaceuticals.

Whether documenting systems and technology, designing processes and critical value streams, or managing innovation and change, erwin Evolve will help you turn your EA artifacts into insights for better decisions. And the platform also supports business process modeling and analysis. Click here for a free trial of erwin Evolve.

Categories
erwin Expert Blog

Enterprise Architecture vs. Data Architecture vs. Business Process Architecture

Despite the nomenclature, enterprise architecture, data architecture and business process architecture are very different disciplines. Despite this, organizations that combine the disciplines enjoy much greater success in data management.

Both an understanding of the differences between the three and an understanding of how the three work together, has to start with understanding the disciplines individually:

What is Enterprise Architecture?

Enterprise architecture defines the structure and operation of an organization. Its desired outcome is to determine current and future objectives and translate those goals into a blueprint of IT capabilities.

A useful analogy for understanding enterprise architecture is city planning. A city planner devises the blueprint for how a city will come together, and how it will be interacted with. They need to be cognizant of regulations (zoning laws) and understand the current state of city and its infrastructure.

A good city planner means less false starts, less waste and a faster, more efficient carrying out of the project.

In this respect, a good enterprise architect is a lot like a good city planner.

What is Data Architecture?

The Data Management Body of Knowledge (DMBOK), define data architecture as  “specifications used to describe existing state, define data requirements, guide data integration, and control data assets as put forth in a data strategy.”

So data architecture involves models, policy rules or standards that govern what data is collected and how it is stored, arranged, integrated and used within an organization and its various systems. The desired outcome is enabling stakeholders to see business-critical information regardless of its source and relate to it from their unique perspectives.

There is some crossover between enterprise and data architecture. This is because data architecture is inherently an offshoot of enterprise architecture. Where enterprise architects take a holistic, enterprise-wide view in their duties, data architects tasks are much more refined, and focussed. If an enterprise architect is the city planner, then a data architect is an infrastructure specialist – think plumbers, electricians etc.

For a more in depth look into enterprise architecture vs data architecture, see: The Difference Between Data Architecture and Enterprise Architecture

What is Business Process Architecture?

Business process architecture describes an organization’s business model, strategy, goals and performance metrics.

It provides organizations with a method of representing the elements of their business and how they interact with the aim of aligning people, processes, data, technologies and applications to meet organizational objectives. With it, organizations can paint a real-world picture of how they function, including opportunities to create, improve, harmonize or eliminate processes to improve overall performance and profitability.

Enterprise, Data and Business Process Architecture in Action

A successful data-driven business combines enterprise architecture, data architecture and business process architecture. Integrating these disciplines from the ground up ensures a solid digital foundation on which to build. A strong foundation is necessary because of the amount of data businesses already have to manage. In the last two years, more data has been created than in all of humanity’s history.

And it’s still soaring. Analysts predict that by 2020, we’ll create about 1.7 megabytes of new information every second for every human being on the planet.

While it’s a lot to manage, the potential gains of becoming a data-driven enterprise are too high to ignore. Fortune 1000 companies could potentially net an additional $65 million in income with access to just 10 percent more of their data.

To effectively employ enterprise architecture, data architecture and business process architecture, it’s important to know the differences in how they operate and their desired business outcomes.Enterprise Architecture, Data Architecture and Business Process Architecture

Combining Enterprise, Data and Business Process Architecture for Better Data Management

Historically, these three disciplines have been siloed, without an inherent means of sharing information. Therefore, collaboration between the tools and relevant stakeholders has been difficult.

To truly power a data-driven business, removing these silos is paramount, so as not to limit the potential analysis your organization can carry out. Businesses that understand and adopt this approach will benefit from much better data management when it comes to the ‘3 Vs.’

They’ll be better able to cope with the massive volumes of data a data-driven business will introduce; be better equipped to handle increased velocity of data, processing data accurately and quickly in order to keep time to markets low; and be able to effectively manage data from a growing variety of different sources.

In essence, enabling collaboration between enterprise architecture, data architecture and business process architecture helps an organization manage “any data, anywhere” – or Any2. This all-encompassing view provides the potential for deeper data analysis.

However, attempting to manage all your data without all the necessary tools is like trying to read a book without all the chapters. And trying to manage data with a host of uncollaborative, disparate tools is like trying to read a story with chapters from different books. Clearly neither approach is ideal.

Unifying the disciplines as the foundation for data management provides organizations with the whole ‘data story.’

The importance of getting the whole data story should be very clear considering the aforementioned statistic – Fortune 1000 companies could potentially net an additional $65 million in income with access to just 10 percent more of their data.

Download our eBook, Solving the Enterprise Data Dilemma to learn more about data management tools, particularly enterprise architecture, data architecture and business process architecture, working in tandem.

Categories
erwin Expert Blog

Where to begin business process modeling?

Knowing where to begin business process modeling can seem impossible – you have a wealth of information spread out in front of you and no clue where to start. 

Categories
erwin Expert Blog

Business process management’s role in utilizing knowledge

Business process management’s role in utilizing knowledge is, in essence, about alignment, making sure you have the key pieces of knowledge from individual employees, departments and operations. This way, businesses can make better decisions with greater context, based on the full picture.

Categories
erwin Expert Blog

Data Driven Enterprise Architecture for Delivering Better Business Outcomes

Forget everything that you may have heard or read about enterprise architecture.

It does not have to take too long or cost too much. The problems are not with the concept of enterprise architecture, but with how it has been taught, applied and executed. All too often, enterprise architecture has been executed by IT groups for IT groups, and has involved the idea that everything in the current state has to be drawn and modeled before you can start to derive value. This approach has caused wasted effort, taken too long to show results, and provide insufficient added value to the organization.

In short, for many organizations, this has led to erosion in the perceived value of enterprise architecture. For others, it has led to the breakup of enterprise architecture groups, with separate management of the constituent parts– business architecture, information architecture, solutions architecture, technical architecture and in some cases, security architecture.

Data Driven Enterprise Architecture for Business Outcomes

This has led to fragmentation of architecture, duplication, and potential sub-optimization of processes, systems and information. Taking a business outcome driven approach has led to renewed interest in the value enterprise architecture can bring.

But such interest will only remain if enterprise architecture groups remember that effective architecture is about enabling smarter decisions.

Enabling management to make those decisions more quickly, by having access to the right information, in the right format, at the right time.

Of course, focusing on future state first (desired business outcome), helps to reduce the scope of current state analysis and speed up the delivery of value. This increases perceived value, while reducing organizational resistance to architecture.

  • Understand their goals, objectives and pain points, and then help them to express them in clear business outcome related terms. This will take time and skill, as many business users simply asking for system changes without clearly stating their actual objectives.
  • Review your current architecture efforts and tooling. Question whether you are providing or managing data the business does not need, whether you are working too deeply in areas that may not be adding value, or whether you have your vital architecture data spread across too many disconnected tools.

This blog post is an extract taken from Enterprise Architecture and Data Modeling – Practical steps to collect, connect and share your enterprise data for better business outcomes. Download the full ebook, for free, below.