The Skeptical Architect October 2013

Recent strategic thinking links strategy focusing on competitors, markets and customers served with business models that represent the execution of the business to serve the markets.1 Newth defines the business model as an “internal system that is made up of components, linkages between components, and dynamics.”2 Both perspectives can be represented by architectures, linked together and the impact of changes, structural options and ranking of importance of alternatives assessed using phrase analytics on the architectures.

Earlier this year we wrote about the various types of architectures and in May’s column focused on business change and risk. The focus was on the business analyst’s use of an architecture-based framework to mitigate risk by assessing impact of risk as it cascades through the various architectures. By making explicit the risks associated with the strategic, tactical, and operational alternatives, it provides executives with an enhanced perspective of how architecture can come to the rescue in assessing organizational risk.

The key issue is to show how architecture represents the competitive view and the execution view. Keep in mind that this approach of using architectures includes representing various types of enterprises especially business, governments and other service and product delivery enterprises.

Business architecture provides focus on the opportunity and capabilities of the organization. They are the driving forces behind a business’ strategy to do a merger, acquisition, divestiture, functional alignment like in IT, improve business execution such as process improvement or even engaging in outsourcing activity. Certainly, various architectures are contextually implicit within the business and that of an anticipated strategy. Thus, the families of architectures (Enterprise IT Architecture, Business Architecture, and Strategic Business Architecture) that we discussed in our February column are part of the anticipated strategy articulation and should be made “explicit.”

The contemporary definition of ‘business model’ varies greatly. Making explicit your business model can take on many forms. For example, the Business Model Canvas3 focuses on four (4) major areas for consideration: infrastructure, offering, customers, and finances with nine (9) sub-areas being used in its template. For each sub-area of the template, one describes the specific activities. For infrastructure, key activities (i.e., value chain), key resources and the partner network is described. Likewise, the offering describes the value proposition as proposed by the organization. For the customers, a description of the segments, channels, and type of customer relationship being used. Finally, finances describe the cost structure and revenue stream. All of these elements are part of a business model definition. This ontological framework is quite inclusive of the elements of a business model.

Others have defined business model as simply: Customer Value Proposition, Profit Formula, Key Processes and Resources as four interlocking elements that, taken together, create and deliver value.4 Joan Magretta describes the model as a story that explains how organizations work.5 Of course, most business models have to answer the questions that Peter Drucker cited: “Who is the customer? What does the customer value? How do we make money? and How do we deliver value to the customer at an appropriate cost?” Given these various definitions, no wonder architects find it difficult to position and align their IT enterprise architecture with their business model. Note that all these approaches explain business model as a focus on execution. The architecture approach of phrase models can also do more than the execution of the enterprise. This approach can also define the performance and knowledge architectural perspectives of the enterprise.

In discussing Strategic Business and Enterprise Analysis of a business, we are referring to the content and dimensions of the organization that need to be assessed effectively and efficiently. For example, our experience in doing Enterprise Analysis over the past 25 years covers a wide range of subjects that may be involved doing the analysis. They may include:

Note: A “Yes” indicates that there should be some representation for that category. Not all methodologies include all the components shown here. Over time, the various methodologies should converge on this set of components. Because there are number of different descriptions of business model content, no two approaches are the same. Unfortunately, some of the business model references are implicit and not made explicit. Then, the architect has to make assumptions about the business situation to develop valid business requirements and IT solutions.

At the end of the day the business model for execution is critical for strategic direction success. The architect uses enterprise business analysis methods to identify, rank, assess impact and decide on the execution, knowledge and performance problems management wants solved. This requires a method that articulates the artifacts needed for conclusions, the categories of analysis to use and the traceable linkage between architectures. Given that these are available, phrase analytics coupled with quantitative methods will provide the insight needed for effective restructuring of execution along with the knowledge and performance whether major or minor.

End Notes:

  1. Newth, Francine (2012). Business Models and Strategic Management: A New Integration. Business Expert Press.
  2. Newth, ibid.
  3. Alexander Osterwalder (2004). The Business Model Ontology – A Proposition In A Design Science Approach. PhD thesis, University of Lausanne. 
  4. Johnson, Mark W., Christensen, Clayton M. and Kagermann, Henning. Reinventing Your Business Model, Harvard Business Review, Dec., 2008.
  5. Magretta, Joan. Why Business Models Matter. Harvard Business Review, May, 2002.

Share this post

Gil Laware

Gil Laware

Gil Laware is President/CEO of Information By Design, LLC, a firm who delivers consultative solutions for strategic, tactical, and operational management of organizations. He has over 30 years of consulting and industry experience with Fortune 50 companies He has experience in manufacturing, transportation, government, finance and banking services including business and IT strategic planning; business process management, redesign and improvement; data management; warehousing and business intelligence; enterprise resource planning; project management; manufacturing systems; and customer relationship management. Previously, he was an Associate Professor of Computer and Information Technology in the College of Technology at Purdue University, an Associate Director for Fujitsu Consulting, Manager of Data Services for Whirlpool Corporation, Vice President of Information Services for Franklin Savings Bank, held various managerial and consultative roles with the IBM Corporation, and was President of Management Support Systems. He also provides training internationally. Gil published with TDAN.com and has authored over 30 papers including a NIST chapter that discusses the gaps that exist in the manufacturing systems software development process. He served the DAMA International Education and Research Foundation (DAMAF). He may be contacted by email at gwlaware@ibd-us.com.

scroll to top