Standardization - Key to success

Week 3
In our book, Enterprise Architecture as Strategy, the author notes that standardization requires defining exactly how processes will be executed. It also usually means replacing good existing systems and process to be replace by those that will provide the new standard. This can be a painful process. However, process standardization delivers efficiency and predictability across the company. 

The BPM Institute has an interesting article on the topic of standardization (http://www.bpminstitute.org/, "Standardization or Flexibility- Partners or Enemies?" 
 vs flexibility. I think the key to remember is that over customization makes it impossible to react with agility to new and changing business environment. I work in finance, so if nothing else, the regulatory environment will force significant change that we must be able to react to quickly. 

Part of what can help to determine where standardization can work and where it can't would be the Common Requirements Vision (CRV) which provides linkages between business strategy and Enterprise Architecture future state requirements. However, often the CRV can be hard for business people to tackle (Gartner, "Building a 'Fast-Path' Common Requirements Vision", 2006). 

The both the full and the fast-path CRV versions recommended by Gartner include the following topics:

1.0       Introduction

2.0       Environmental Trends

3.0       Enterprise Business Strategies (EBSs)

4.0       Environmental Trends/Enterprise Business Strategies Matrix

5.0       Initiatives (full version only)

6.0       Business Change Requirements (BCRs) (full version only)

7.0       Business Information Requirements (BIRs)

8.0       Enterprise Business Strategies/Business Change Requirements Matrix

9.0       Information Technology Requirements (ITRs)

10.0     Information Technology Requirements/Business Information Requirements Matrix

11.0     Information Technology Requirements/Business Change Requirements Matrix (full version only)

12.0     Business Solution Requirements (BSRs) (full version only)

13.0     Future-State Architecture Vision

14.0     Next Steps

The sample Common Requirements Vision Matrix provided by Gartner is interesting, but it is complicated, and I think it would be difficult to get the business to understand it at this point.  Therefore, I think the fast-path method would be helpful. Also, the Business Anchor Model recommended by Gartner seems like an easy to understand document that could help clarify the core value chain business functions. This should be a fairly straight forward document to complete, but would help provide a solid foundation for understanding. 

The point of any of the EA artifacts is to hep both IT and the business define the strategy of the company and understand the impacts for the enterprise. The enterprise focus helps everyone stay out of the minutia, and I believe it will really help our company get clarity on where standardization can be implemented without jeopardizing the overall strategy.