The Art of Measurement and Business Architecture

The Art of Measurement and Business Architecture

Original article published here.

Building a Business Architecture model without measuring any of its key elements is a pure waste of time. This article examines the need for strategic and tactical measurements, how to have effective measurements (KPIs) in place, presents various measurement diagram examples, and finally names two sources of KPIs lists for various industries.

The Need of Measurement

Business Architecture will only contribute in driving Information Technology (“IT”) and Business Alignment if key business and IT stakeholders promote a “metrics-driven behavior (devising KPIs and incorporating them into the performance appraisal process).”[i] Failure of Business Architecture initiatives and project is often the fact that C-level management hasn’t taken the time to set the Key Performance Indicators (“KPIs”) properly, as mentioned in Jason Bloomberg’s article[ii].

KPIs can be defined at all levels of a business architecture model, including objectives/strategies, capabilities, value streams, organizations, initiatives, stakeholders, products/services, information, physical and IT assets, requirements and processes and especially all the actions and relationships that link the various parts of a business architecture together.

Some business strategies may truly be ill-advised and extremely risky. Showing the difference between strategies using chosen KPIs is what differentiates the best enterprise/business architects from others. Good business architecture will allow to identify the gaps between the current architecture and future state options by comparing architectures against KPIs and quantify the risks, using impact analyses and decision trees among others, as indicated in an article written by Tim O’Neill.[iii]

Measuring Effectively

The set of possible measurements for Business Architecture is very large since Business Architecture is the link between strategy and execution. Business Architecture measurements can be grouped into strategic, tactical and governance values.

1.     Strategic Values

Business Architecture is the missing link between strategy and execution. KPIs for Strategic Values should stay focus on measuring some cohesive business goals, including business strategy-execution progress measurements, business culture index(es), productivity, business communication effectiveness, business growth opportunities, and cost structure optimization.

2.     Tactical Values

At a tactical level, the purpose of practicing Business Architecture is to improve the efficiency of your organization’s operations. Measurements of efficiency, costs, time will vary based on the nature of your organization’s business.

3.     Governance Values

Governance is the other key area where Business Architecture can deliver value, by determining costs variances, examining detailed impact analyses and establishing balanced score cards associated with risks.

Defining measurements/KPIs can be challenging. Good KPIs must have a target value and a way to be accurately measured and reported. Ideally, good KPIs should include the following characteristics, as mentioned by John Parker[iv]:

·       Aligned with the specific organization’s vision, strategy, and objectives.

·       Optimized—The KPIs should be focused on providing organization-wide strategic value rather than on non-critical local business outcomes. Selection of the wrong KPI can result in counterproductive behavior and sub-optimized results.

·       Measurable—Can be quantified.

·       Realistic—Must be cost effective, coherent with the organization’s culture and constraints and achievable within the given timeframe.

·       Attainable—Requires targets to be set that are observable, achievable, reasonable, and credible under expected conditions as well as independently validated.

·       Clear—Clear and focused to avoid misinterpretation or ambiguity.

·       Understood—business and IT stakeholders and relevant organizational units should know how their behaviors and activities contribute to achieving the KPI.

·       Predictive—The KPI may be compared to historical data over a reasonably long time so that trends can be identified.

·       Agreed—All stakeholders should agree and share responsibility for achieving the KPI target.

·       Reported—Regular reports are made available to all stakeholders and contributors so they know the current state of the business architecture model element and take corrective action if required.

There are numerous ways to design measurement/KPIs diagrams. In this article, you will find 5 diagrams, including the 2-dimensions pie and donut charts, the 2 or 3 dimensions bar chart, the 3 dimensions bubble chart and finally the 4-dimension radar chart.

Sources of KPIs

There are numerous sources of KPIs lists. It’s easy to get lost. In the Business/Enterprise Architecture world, I will limit myself to two. First, there are the KPIs lists for each of the four IT Values Streams[v] defined by the OPEN Group; especially the KPI list regarding the Strategy to Portfolio IT Value Stream[vi]. Second, there is the APQC's Process Classification Framework that contains hundreds of processes[vii], including detailed definitions and thousands of key measures for numerous industries. In particular, the APQC's Process Classification Framework includes a section about developing and managing Business Capabilities Definitions and Key Measures that can be very useful for Business Architecture[viii]. As for the latest version of BIZBOK, surprisingly it mentions often the necessity of measurements/KPIs, but does not elaborate further then that.

Conclusion

This article has examined the need for strategic and tactical measurements, how to have effective measurements (KPIs) in place, presented various measurement diagram examples, and finally named two sources of KPIs lists for various industries.



[i] "Using Business Architecture to Drive IT/Business Alignment" by Roy Hunter published on Oracle’s website on January 2011.

[ii]Enterprise Architecture: Don't Be a Fool with a Tool” by Jason Bloomberg published in Forbes on August 7, 2014

[iii]Six secrets of top enterprise architects” by Tim O'Neill in InfoWorld on Nov. 4, 2015

[iv]Measuring Project Success Using Business KPIs” by John Parker in PM Times on May 4, 2014.

[v] The Open Group’s “IT Value Chain” with its four value streams.

[vi] The Open Group’s “Strategy to Portfolio Value Stream”.

[vii]PCF Version 6.0.0 Process Definitions and Key Measures (Collection)” published by the APQC.

[viii]Develop and Manage Business Capabilities Definitions and Key Measures PCF version 6.0.0” published by the APQC.



Francois Botes

Executive General Manager @ Architects on Demand | Technology Architecture

7y

Another great article. Thanks Daniel Lambert

Daniel Lambert, M.Sc.

Founder and Chairman at Aidon.ai - Partner and Owner of Business Architecture Info

7y

Sunil, If the Business Management and Business Architecture perspectives are not unified, then you're wasting everyone's time trying to implement Business Architecture. In reality, you are limiting your company to only the other more technical 3 dimensions of Enterprise Architecture: Application/Integration, Information/Data and Technical/Infrastructure. Even if these 3 dimensions are planned and executed close to perfection, odds are very high that you will not satisfy the needs of your business stakeholders and that they will do everything to bypass IT with their digital initiatives. I invite you to read this article that I wrote 10 months ago entitled "Make Your CIO More Relevant Using Business Architecture": https://www.linkedin.com/pulse/make-your-cio-more-relevant-using-business-daniel-lambert?trk=mp-author-card .

Sunil Singh

Drive Insurtech and Digital Transformation leveraging changing technology levers

7y

Good points! However, not many organizations practices KPIs as part of Business Architecture. Some effort required to unify the Business Management and Business Architecture perspectives. Without the unification, the debate on "Value of Enterprise/Business Architecture" will continue and things often may get over complicated.

Like
Reply
Michael Poulin

Enterprise/Solution Architect: Integration, Governance, Digital Transformation, Services, Security

7y

1) business architecture (BA) in IT is not an architecture of business because it sees only the implementation side, i.e. the bottom of the body of corporate business. 2) BIZBOK does not go further because measuring BA outside of business context is valueless and this is obvious even for the Guild, but Corp. business doesn't welcome IT BA and doesn't share its context. 3) number of heads/hands and people cannot be a KPI - we are not in the 'business' of creating socialism based on people councils ('soviets'); we need the meetings where only specialists are present while managers, if they are just managers and not specialists in business realms, are not welcome either. 4) a few major KPI for Architects of Business are: cost of reaching corporate goals/objectives, time to market of Corp. (not IT) goals, cost of adoption to market changes, cost of change of just adopted change. Technology innovations disruptive movements have business value only if the help to reduce aforementioned costs.

To view or add a comment, sign in

Insights from the community

Others also viewed

Explore topics