Business Outcome Journey Maps are a new technique that help you focus on the key aspects of value creation in your enterprise. Here we show you what they are, why they are useful and how they are supported in BiZZdesign Enterprise Studio.
In recent years, the concept of ‘value stream’ has become increasingly popular. It is a useful element in the toolbox of business architects, and is advocated in, for example, the Open Group Guide to Value Streams and the BIZBOK® from the Business Architecture Guild®. Though ArchiMate® has had a value mapping element since its inception, until now it does not have a value stream element. In this blog we propose to add a value stream element to ArchiMate in a way that supports approaches such as those described in the Value Stream Guide and the BIZBOK, is coherent with the language structure, and minimizes the impact on the rest of the language.
Powerful Analysis Techniques
In the final installment of this blog series, I want to address the domain of risk, security and compliance, an area of increasing importance for architects, process designers and others. As an example, in some previous blogs, I have already outlined the new EU General Data Protection Regulation (GDPR) and its impact. In one of my posts, I used a simple example of data classification and how you can use this to assess your application landscape. Read more
In my previous post, I discussed how you can analyze the business and technical value of your applications, and how architecture models are key in calculating metrics such as the business criticality or strategic value of applications. In this post, I want to focus on financial analysis, and in particular on cost models.
In the previous installment in this blog series, we looked into planning and analyzing change in the enterprise by linking the life cycles of elements such as applications and projects. But how do you decide what to do with, for example, your application landscape? Which applications need to be improved, re-platformed, functionally upgraded, or phased out?
Information Mapping – Business Blueprints are an essential instrument in every business architect’s toolbox. The Guide to the Business Architecture Body of Knowledge (BIZBOK Guide®) defines four core business architecture domains: Value Streams, Capabilities, Organization and Information.
Next to this analysis of the enterprise as it is today, addressed in the previous blog posts, we can also plan, design and analyze change in and of the enterprise. To this end, you can give anything in your architecture model a lifecycle. The specific stages in those lifecycles can be defined depending on the types of objects you model. Read more
As discussed in the introduction of this blog series, the maturation of the business architecture discipline makes the role of model-based support for design, analysis and decision-making increasingly important. Therefore, we introduced you to several useful techniques for business architecture modeling and how they are supported by BiZZdesign Enterprise Studio. In this blog, we will discuss an approach to modeling a blueprint of one of the core domains of business architecture: Organization Mapping.
Dependency Analysis – In my previous blog post, I outlined the value of using analysis techniques to get more business value out of your models. I described one of the most common analysis techniques, impact analysis, and showed how color views and heat maps can be used to depict, for example, the use of applications to support capabilities.
In recent years, we see the audience and attention for business architecture steadily increase. A business architecture provides a business-oriented abstraction of the enterprise in its ecosystem, which helps the organization in decision-making and direction-setting. This maturation of the business architecture discipline makes the role of model-based support for design, analysis and decision-making also increasingly important. In this series of posts we will introduce you to useful techniques for business architecture modeling and how they are supported by BiZZdesign Enterprise Studio. Read more
Strategists, architects, process experts, software developers, data managers and other professionals involved in changing the enterprise often put substantial effort in creating all kinds of useful models of their designs. In many cases, such business models, enterprise architecture models, business process models, software models, data models and more are only used to specify some design, i.e., to describe what should be built. But there is much more value to be had from these models, by using powerful analysis techniques to create new insights. Read more
In my previous blog I wrote about the importance of models to successfully complete a merger, acquisition or divestiture. Of course, one organization’s divestiture may be another one’s acquisition. In this blog post I’ll share one my personal experiences as a consultant, supporting two government agencies that were in the middle of this process.
In my previous blog post, I described the new EU General Data Protection Regulation (GDPR) that will go into effect in May 2018, and I outlined its profound effects on organizations, not just in Europe but around the globe. This regulation, and related EU Directives such as the ePrivacy Directive and the Network and Information System Security (NIS) Directive, force organizations to rethink how they deal with personal, privacy-sensitive data. In this blog, I want to address the steps you can take as an architect to help your organization comply with these regulations.
When I give a presentation to a technical audience showing any kind of picture with an arrow in it (not necessarily an ArchiMate diagram), more often than not, someone will raise their hand and ask: “What does that arrow mean?” When I answer, they will follow up with “Shouldn’t it be the other way round?” Read more
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.