Get a Free Deliverable

Organization Mapping in Business Architecture

Organization Mapping is one of the views that a business architect builds to interweave capabilities with the structural and organizational entities of an enterprise.  The business architecture practice of organizational mapping serves many strategic, operational, and technology enablement purposes.  Let us be clear – it is not about a hierarchical representation of the leadership, but a layer underneath representing the structural concepts.

What is Organization Mapping?

Organizational mapping is a business architecture construct of identifying and interweaving the various relationships between the functional and structural elements of an enterprise to analyze the cross dependencies and foster synergy.

What are the components of an Organization? 

In Capstera, the leading business architecture software, Organization concept comprises of several different modules and components:

Organization Mapping – Structure Module:

The structure is a comprehensive view of the organizational elements to gain a perspective of the following Components:

  • Business Units
  • Locations
  • Departments
  • Roles

Now let us briefly review the key aspects of each of the components.

Business Units:

A business unit is a logical grouping of a set of enterprise services.  Typically, business units – some of which are strategic business units – are focused on geography or a portfolio of products/services, or a customer segment.

An example is “Institutional Asset Management” in a typical money manager.  Alternatively, a “Cargo Business Unit” in a large airline. Alternatively, “Aircraft Engines” in a large industrial manufacturer.  These are all examples of a business unit.  If one of them is strategic to the company, then it can be deemed a strategic business unit.

Identifying the business units and capturing essential information will help the business architects in building views and viewpoints.

Organization Mapping - Business Units - Example of a Large Bank

For each business unit, a business architect may capture the following information:

Business Unit Profile:

  • Business Unit ID: Some alpha-numeric identifier
  • Business Unit Name: The common name of the business unit
  • Products/Services: The products and services the business unit focuses on.
  • Customers: The segments of customers served by the business unit.
  • FTEs: Total number full-time Optionally, one may capture the contingent workforce as well.
  • Essential Capabilities: What are the critical capabilities of the business unit?

Locations:

Locations are as the name suggests geographic locations.  The sites are vital to understanding the focus of each site, the types of customer segments the place serves, the products and services the area focuses on, and the capabilities that are vital will help in developing an understanding of the needs and strengths of each site.

For example, a business architect may capture the following information for a Location:

  • Location ID: Some alpha-numeric identifier
  • Location Name: The proper name
  • Category: Type of location such as manufacturing plant, warehouse, retail store, corporate headquarters and the like. Apparently, there can be more than one type of categorization or classification.
  • Number of Employees: The number of employees affiliated with the location
  • Products and Services: What products and services are sold?
  • Customers: Customer segments served. (This is not individual customer names, but the generic segments.)
  • Essential Capabilities: What are the critical capabilities required by this location.

Departments:

The departments are specialized groups units with specific domain skills that serve critical organizational functions.  

For example, Human Resources (or HR) Department is a group of professionals with various HR related functional and domain skills serving the recruit to retire value stream of a company. Similarly, other Departments include “Marketing” or “Accounting and Finance” or “Production” or “Distribution.” 

Organization Mapping - Departments - Example of an Insurance Company

The business architecture practitioners may collect the following information for a specific department:

  • Department ID: Some alpha-numeric identifier
  • Department Name: The proper name of the department
  • Services: The types of services the department is responsible for
  • Number of FTEs: The number of employees affiliated to the Department

Roles: 

A role is a specific type of organizational function where an individual or a group of individuals work on particular responsibilities in pursuit of a business outcome.

For example, in a bank, a “Teller” is a role. Another example is a Pharmacist in a Drug Store. Alternatively, an Anesthesiologist in a Hospital.  It is the not the individual but the position that business architect are interested in.  There may be dozens performing the same job or in large companies hundreds.

Moreover, in a company, there may be dozens or hundreds or even thousands of roles.

A business architect may capture the following information for a specific Role:

Role:

  • Role ID: Some alpha-numeric identifier
  • Role Title: The name of the role.
  • Role Description: A simple explanation of the critical aspects of the role.
  • Number of FTEs: The number of employees is manning this particular role.
  • Additional information may include their assigned business units and

Views and Viewpoints: 

One the business architect has such organization mapping information, he or she can develop the following views: (Note: Not every perspective is essential, and business architects should avoid boiling the ocean and the paralysis by analysis syndrome.)

  • Enterprise Business Units Listing
  • Enterprise to Departments Mapping
  • Capabilities to Business Units Mapping
  • Capabilities to Departments Mapping
  • Business Units to Departments Mapping
  • Capabilities to Roles Mapping
  • Department to Roles Mapping
  • Business Unit to Role Mapping
  • Capabilities to Location Mapping
  • Business Units to Location Mapping
  • Departments to Location Mapping

Of course, you can develop other organization mapping based on what is important to your firm. 

Related Products:

Sign up for Newsletter

[mc4wp_form]