For many organizations, the enterprise landscape is growing out of control. Simply keeping up with competition and evolving markets means that organizations constantly renew services offered to customers. These new services are supported by new processes, applications and infrastructure that are added to the landscape, making it larger and more complex. Read more
In my previous blog post on Enterprise Architecture at BiZZdesign in 2014, I described how the true value of architecture lies in its relationship with other disciplines within the enterprise.
We recently organized a workshop at BiZZdesign for enterprise architects in healthcare. A mixed group, from hospitals and other healthcare providers. In the workshop, various issues were discussed. We want to highlight some of these topics in this blog.
In previous blogs in this series, we discussed the ‘wastes’ of enterprise architects and enterprise architectures. That may have sounded rather negative, but the main message of course is: EA is no goal in itself, it should support the organization. Regarding Lean we have the same message. Read more
In a previous blog post, I discussed the notion of strategic issues and the need to reconcile them in order to define ones strategy. In this post I will talk about the business model canvas (based on the excellent book by Alexander Osterwalder) as a tool which helps to (a) communicate about strategic choices, (b) analyze ones business model, and (c) consolidate the results of various analyses such as SWOT, value chain analysis, or Blue Ocean analysis.
In my previous blog posts, I discussed the way I see strategy work and the types of models that can be used, and how the business model canvas should be the focal point for architecture work. In this blog post, I will show that enterprise architecture is the tool to go from strategy and business model to execution.
Business models are a helpful way to define a business strategy and steer an organization in the “right” direction. Furthermore, business models foster discussions on the way organizations want to deliver value to their customers. Building business models is fun! Thinking about your organization and its future in an abstract manner is addictive, since there is no chance of failure…
Times are tough: many businesses are struggling to stay afloat in the wild economic currents. Many organizations attempt to find a “blue ocean” of uncontested space, but let’s face it: most of us are stuck in a “red ocean” with a lot of competition, growing power of both suppliers and consumers and increased threat of substitutes. Indeed, one can argue that it is “all hands on deck” for many organizations in their struggle to survive.
In our previous two blogs in this series, we outlined the connections between Lean Management and Enterprise Architecture. The focus of Lean is on taking day-to-day small steps for improvement. The elimination of waste and focus on customer value are central elements in Lean. Enterprise Architecture focuses on longer term results, but as we have seen in the previous blog in this series a Lean perspective is also powerful for Enterprise Architects. Read more
In Lean Management, a lot of time is spent finding and eliminating waste. Our processes and organizations are full of waste. In the Lean philosophy these wastes should not be dealt with as ‘problems’, but as opportunities for improvement.
Over the last two decades, Lean management has proved to be very powerful in improving an organization’s business process performance. During the same time frame, Enterprise Architecture came up as a discipline for controlling the complexity of organizations, their processes, information and IT. At first glance, both approaches appear very different in nature. Read more
One of the most popular topics to debate amongst architects is: what is the proper level of abstraction needed to be applied when creating architectures? Although always a lengthy debate, I don’t ever recall reaching a conclusion that was satisfactory to me. Even worse, at times, my architectural work was discredited by people, claiming “its level of abstraction was too high to be useful.” Read more
Enterprise Architecture supports implementation of change in a coordinated way. Building an Enterprise Architecture Capability is a process of change in itself, and thus can be supported by Enterprise Architecture methods and tools. In this White Paper we described how a high-level approach for the initiation and development of the Enterprise Architecture capability can be derived from TOGAF, and especially its core component the Architecture Development Method (ADM). This high level approach consists of four steps:
Almost every architect has met the following frustrating experience during his career: A proper and well defined business case, architectural advice or Project Start Architecture is not being used by the organization the architect wanted to serve with it. Time and again we see decisions made based on:
In the webinar Business Model Innovation for Architects and their Stakeholders we presented the Business Model Canvas as a relevant tool for Architects in many roles. Changing systems and processes alone is no longer enough in the rapidly changing environment your organization is in today. Designing, innovating and changing business models becomes a discipline that is of increasingly importance for organizations both in profit and non-profit. We explained how this approach fits The Open Group standards TOGAF® and ArchiMate®.
The Decision Model (TDM) is a rapidly growing framework for modeling and executing the business logic behind business decisions. When I first read the book “The Decision Model – A Business Logic Framework Linking Business and Technology” by Larry Goldberg and Barbara von Halle, I was impressed with how TDM models the business logic behind operational business decisions. Read more
The Decision Model (TDM) is a new and rapidly growing methodology and framework for modeling the business logic (business rules) behind business decisions, using a powerful graphical notation, that is easy for both business and IT to understand and implement.