When we think about supporting Business Transformation, we immediately start with the detail. Architects and analysts dive into the nuts and bolts, create some brilliant ‘technical designs’ and models but to non-architects, it often appears as “just boxes and lines”. In this blog I will explain some simple techniques to help bridge the gap.
In a previous blog post I wrote about setting the foundations for data collection and management, ensuring the right metadata is available for effective contributions and reporting activities. In this post, I will describe how, if the information is readily available, can be brought into Enterprise Studio. Read more
The average organization is built on a variety of strategies and motivations, people, processes, applications, technology. An important part to ensure that the right stakeholders are satisfied with being able to contribute, as well as getting targeted reports out to the stakeholders – is metadata. Read more
Few companies have a systematic and reliable way of translating their business strategy into action across all relevant parts of the organization. Research on digital transformations by MIT Sloan  distinguishes between the ‘what’ (what does an organization want to achieve) and the ‘how’ Read more
Since the release of ArchiMate 3.0 last June, my colleagues and I have written a series of blog posts about combining ArchiMate with other standards, methods and modeling techniques. This post summarizes what we have shown you.
In the past, my colleagues and I have written several blogs on the combination of enterprise architecture and agile ways of working (e.g. Enterprise Architecture and Agile Development: Opposites Attract?, Enterprise Architecture and Innovation: A cultural change, Escaping the Jaws of the Project Monster). In this blog, I want to focus in more detail on the use of the ArchiMate language in the context of agile methods, in particular the Scaled Agile Framework (SAFe). Read more
A useful technique for service design and innovation is the Service Blueprint. It is related to customer journey maps (see our previous blog) in its emphasis of customer touchpoints, but focuses more on the realization of services by underlying activities and less on the quality of the customer’s experience. Read more
In several previous blogs, we have outlined how you can use ArchiMate 3 in the context of business architecture and strategy development, such as Capability-Based Planning, and combining it with the Business Motivation Model, the Business Model Canvas and the Balanced Scorecard. In this blog, we continue with the series, looking at how you can describe value chains, value streams, and value networks. Read more
A Customer Journey Map is a useful way to graphically represent the customer experience of an organization. It focuses on the touchpoints that characterize the customers’ interaction with the services of the organization and helps you to optimize this experience.
As we stated in the introduction to this blog series, ArchiMate models can usefully be combined with models in other techniques, in order to zoom in on specific aspects of your enterprise. If these models are tied in to an overall enterprise architecture model in ArchiMate, an integrated model of the enterprise can be constructed that relates (sub)models from formerly separate domains in a meaningful way.
As we have described in our previous blog , the ArchiMate® language is not intended to replace other standards and modeling approaches, but rather to connect them. In this blog, we will focus on relating ArchiMate® to several management-oriented techniques: The Business Motivation Model, Balanced Scorecard, and Business Model Canvas.
The ArchiMate language is not intended to replace other standards and modeling approaches. For many domains, there are languages and techniques available that provide more detailed descriptions. Those languages, such as UML, BPMN and others, have a narrower scope (e.g. UML for specifying software, BPMN for business processes) than ArchiMate, but they lack concepts for relating these to other domains. Read more
In a previous blog on the ‘Digital Customer Intimacy’ strategy of our example insurance company ArchiSurance, we outlined that they intend to use more detailed customer data to improve customer interaction and satisfaction, and to determine customized insurance premiums. To this end, they want to use the Internet of Things, acquiring data from smart, connected devices such as personal fitness trackers, black boxes in vehicles, home automation gateways, fleet management systems, in-store RFID devices, or smart building sensors.
As we have seen in the previous blog, ArchiSurance wants to establish several new capabilities to support its ‘Digital Customer Intimacy’ strategy, such as Digital Customer Management, Data-Driven Insurance, Data Acquisition, and Data Analysis. Positioning these in the context of its current capabilities leads to the following figure, using the ‘highlight’ function of Enterprise Studio to emphasize these new elements. Read more
In our previous blog, we briefly outlined the two strategic options that our example insurance company ArchiSurance is exploring. By analyzing the operational excellence strategy, they have benchmarked their efficiency against the industry average: average capabilities are shown in blue, above-average capabilities in green and below-average capabilities in red (Figure 1). Read more