Performance Diagram

Purpose: The purpose of the Performance Diagram is to provide a view over an organization’s performance in reaching their strategic goals.

Core concerns: The Performance Diagram enables you to model Key Performance Indicators – which can be related to strategic goals, derivative Performance Indicators and Derivation Rules. You can create a Performance Diagram as a decomposition of a Key Performance Indicator and model a hierarchy of performance diagrams. The model below shows an overview of an organizations Key Performance Indicators and their status:

In the following model the Key Performance Indicator has been enriched with derivative performance indicators explaining in more details the status of the performance and how it is measured:

The overview of the Key Performance Indicators can also be presented with a simplistic view, highlighting their status using color coded icons:

Relation to other templates: The Performance Diagram is a Strategic template and can be decomposed from Key Performance indicators contained in, for example, a Balanced Scorecard Diagram or Dashboard.

 

Properties and metadata: The Performance Diagram can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Performance Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Product Canvas

Purpose: The purpose of the Product Canvas template is to present the relevant information related to a specific product.

Core concerns: The Product Canvas template enables you to gather relevant Business Charts and model Personae, Product Demands, Markets, Locations and Products. Additionally, you can model a SWOT analysis that details the Strengths, Weaknesses, Opportunities and Threats the product is affected by.

Below, you can see two Product Canvases. The first has its focus on a product within two markets, showing the expectations two different customer segments have to the product.

ProductCanvas_2

The second example shows information related to a specific market, Poland, including product architecture and business assessment:

ProductCanvas_1

Relation to other templates:

The Product Canvas Template is inherently related to the Product Architecture, Product Roadmap and Product Variant Master, in the sense that all these models focus on different aspects of the lifecycle of a product. Furthermore, you can create additional Business Charts for the Product Canvas by using the dedicated template. Another view on projects and initiatives are provided from the Enterprise Investment Portfolio. There, the reasoning behind the investment in the project is visualized by connecting the initiative (in this case a new product) to the specific goals of the enterprise that it contributes to. Another view on how the product meets customer needs can be documented in the Value Proposition Canvas.

Properties and metadata: The Product Canvas can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the canvas
  • Link to the one responsible for the canvas
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Product Canvas where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Product Architecture

Purpose: The purpose of the Product Architecture template is to document the building blocks of a product. Below is an example of a product architecture:

ProductArchitecture_1

Core concerns: The Product Architecture template enables you to model a Product and connect different parts of it with three different connection types: Part of Product, Kind of Product, and Product Interface. See below for an example of a Product Architecture where each Product object is represented graphically:

 ProductArchitecture_2

Relation to other templates: Depending on whether the product is in production or in its development phase, it could be further described in a Product Viewpoint template, have a Product Variant Master, Product Rule Table or be represented in a Product Canvas. It may also be illustrated along with other products in a Product Roadmap, just as its production may be detailed in a Manufacturing Routing Network.

Properties and metadata: The Product Architecture can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the accuracy of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
  • Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below you can see the Product Architecture’s properties dialogue window, where the properties can be viewed and edited:

Enterprise Investment Portfolio

Purpose: The purpose of the Enterprise Investment Portfolio template is to model enterprise goals and investments.

Core concerns: The Enterprise Investment Portfolio template enables you to model Goals, Projects, and Initiatives. The projects and initiatives can be connected to enterprise goals them through Project Contributions, that show the viable minimum and optimistic maximum of the value contribution. Below, you can see an example of an Enterprise Investment Portfolio, where the way goals are realized is visualized:

 

EnterpriseInvestmentPortfolio_1

Other Functionalities: By using the Enterprise Investment Actions tab, you can create, for example, a Portfolio Value matrix, which offers another way to view the same data:

Relation to other templates: The Enterprise Investment Portfolio is a strategic template and is as such related to the enterprise’s Strategy Model, Strategic Roadmap, Business Canvas and Innovation Canvas. The projects contained in the initiatives can also be further described in the Work Model template.

Properties and metadata: The Enterprise Investment Portfolio template can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Enterprise Investment Portfolio template, where you can view and edit the diagram’s Properties in QualiWare Lifecycle Manager.

For more information: This model type is used in the Enterprise Investment Methodology developed by Chris Potts and QualiWare. To learn more about Enterprise Investment, you can about it here:Enterprise Investment.

Dashboard

Purpose: The purpose of the Dashboard template is to publish selections of Business Charts targeting different stakeholders. It should be used to gather a series of relevant or connected Business Charts to provide a dashboard-like overview.

Core concerns: The Dashboard template enables you to gather Business Charts, Key Performance Indicators, Performance Indicators and General Concepts to create stakeholder specific views of analyzed data. For example, an Enterprise Architect could find a Dashboard containing Business Charts relevant to the usage and governance of the Enterprise Architecture useful.

Below, you can see examples of different Dashboards presenting an array of Business Charts:

Dashboard_1

 

Dashboard_2

Relation to other templates: The Dashboard template is closely connected to the Business Chart template, as the Dashboard publishes the charts the Business Chart template generates.

Properties and metadata: The Dashboard can for example retain the following information:

  • A description of the Dashboard
  • Link to the owner of the Dashboard
  • Link to the one responsible for the Dashboard
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Dashboard template where you can view and edit the dashboard’s properties in QualiWare Lifecycle Manager.

Customer Journey Map

Purpose: The Purpose of the Customer Journey Map template is to document the customer’s journey from awareness to the end of their interaction with an organization, covering possible touch points from the customer’s perspective.

Core Concerns: The Customer Journey Map template allows you to model connections between different Personas, Customer Journey Phases, Touch Points, Goals, Roles, Locations, Channels, Technology and the aspects from a SWOT analysis.

You can choose to model both a current state and a desired future state of the customer journey and use the documentation for process improvement. Below is an example of a current state model and a future state model:

Current state model:

CustomerJourneyMap_2

Desired future model:

CustomerJourneyMap_1

Other functionalities: The customer’s touchpoints can be elaborated upon with four scores for Customer Satisfaction, Customer Importance, Customer Effort and Net Promoter Score. Particularly vital touchpoints can be designated as a Moment of Truth.

Relation to other templates: The Customer Journey Map can be used as a groundwork for a strategic change, which for example can be modelled in a Work Model, a Business Capability Model and/or a Strategy Model.

Properties and metadata: The Customer Journey Map can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the accuracy of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
  • Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

The above picture shows the properties dialogue window for the Customer Journey Map, where you can view and edit the diagram’s properties.

For more information: on Customer Journey Mapping, please view our webinar Experience Mapping – Customer Obsession for IT and Digital Professionals with Milan Guenther and Katharina Weber.

 

 

Content Map

Purpose: The purpose of the Content Map template is to describe the Content Items that are produced, exchanged and consumed in the enterprise space.

Core concerns: Consistent content is the basis for all communication, decision-making and collaboration. Creating, managing, and distributing content is subject to Content Strategy work.

The Content Map template enables you to model Content Items, Content Actions and Content Purposes. These elements can be connected by Connections, Association, Aggregations and Flows.

Content elements are assets vital for the organization’s success both internally and externally. An organization should create content that is meaningful and useful to people in touch with the enterprise. Content should be considered a valuable business asset to the enterprise.

Graphical representation of objects:

Below, you can see an example of a Content Map showing the purpose and actions of enterprise- and department strategies:

As you can see, there are flows between the content items, actions and purpose. Because of the nature of strategies, the enterprise strategy and Department strategies are also connected.

Relation to other templates: The Content Map template is based on the Enterprise Design theories and is as such in the same family as the Architecture Overview, Actor Map, Brand Overview, Communication Plan and the  Business Eco System.

Properties and metadata: The Content Map template ­­­­can for example retain the following information:

  • A description of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Content Map template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

For more information: If you want to learn more about Enterprise Design, we have a four-part webinar by Milan Guenther available for viewing. You can also visit Milan’s website, where you can learn more about the Enterprise Design framework.

Business Excellence Diagram

Purpose: The purpose of the Business Excellence Diagram template is to describe a measuring tool based on The European Foundation for Quality Management Excellence Model (EFQM).

Core concerns: The Business Excellence Diagram enables you to model Business Scopes, Criterion and Sub Criterion. These aspects can then be connected by Criterion Influencers.

Below, you can see an example of a Business Excellence Diagram for the Leadership of an organization. The diagram is structured according to the EFQM and shows the overall scores for the leaderships performance:

Other areas covered in the EFQM are Policy & Strategy, People, Partnerships & Resources, Processes, Customer Results, People Results, Society Results and Key Performance Indicators.

Relation to other templates: The Business Excellence Diagram is a strategic template that is complimentary to the Business Capability Model, Stakeholder Model, Business Canvas, and Strategy Model

Properties and metadata: The Business Excellence Diagram ­­­­can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Business Excellence Diagram template, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

For more information: To learn more about the EFQM, please visit their website, where you can also find an overview of the EFQM Excellence Model.

Business Ecosystem

Purpose: The purpose of the Business Ecosystem template is to enable an organization to understand itself from an outside-out perspective by modelling the environment in which the organization is embedded.

Core concerns: The Business Ecosystem supplies five elements to model with: Business, People, Things, Business Interaction and Business Moment. The Business Ecosystem template should primarily be used for modeling entities outside the enterprise to identify new business opportunities in the form of Business Moments.

BusinessEcoSystem

Above you can see a model of a Business Ecosystem. The blue areas are Business Moments, where the interactions between People, Businesses and Things create business opportunities for your enterprise.

Relation to other templates: The Business Ecosystem model is based on the Enterprise Design theories and is as such in the same family as the Architecture Overview, Actor Map, Brand Overview, and the Customer journey map.

The Business Ecosystem is a strategic model and can be used to document a strategic possibility or track along with for example Business Capability Models, Strategy Models, and Work Models.

Properties and metadata: The Business Ecosystem can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the application architecture
  • Link to the one responsible for the application architecture
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
  • Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

For more information: If you want to learn more about Enterprise Design, we have a four-part webinar by Milan Guenther available for viewing. You can also visit Milan’s website, where you can learn more about the Enterprise Design framework.

Business Diagram

Purpose: The purpose of a Business Diagram is to show the functional structure and relationships of the whole or part of an organization.

Core concerns: The Business Diagram template enables you to model Business Functions, Information Systems, Inventory, Business Scope, Lines of Business, Information Flow and Logistical Flow. The diagram’s syntax can be extended to also include strategic elements such as Goals, Objectives, Stakeholders and Performance Indicators.

The Business Diagram should be broken down into several levels of recurring Business Diagram templates. In the model below, you can see an example of a high-level Business Diagram showing Business Functions and their Information Flows and Logistical Flows –  describing the flow of products and services – in this case for a car rental service.

The Business Functions are placed with the operational functions in the bottom together with the Logistical Flow and with management control at the top of the Business Diagram.

On lower levels (decompositions) of Business Diagrams, Information Systems are placed close to the Business Functions that are responsible for or own the Information Systems.

Relation to other templates: The Business Diagram can be used as an addition to a Business Process Network and Strategy Models, giving a practical view of how the organizations functions fit together, illuminating interdependencies.

Properties and metadata: The Business Diagram can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the Diagram
  • Link to the one responsible for the Diagram
  • Indication of the diagram portrays an as-is situation or a to-be situation
  • The Perspective can be defined as either: Holistic, Sub-functional, Process, or IT Focused.
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Business Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.