Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Review the comparison data to identify similarities, differences, and alignments.

  2. Select the specific elements you wish to merge from the source unit into the target unit.

...

Confirm Merge Actions

Review each item carefully before merging to ensure accuracy and alignment with organisational goals. Before completing the merge, you must confirm whether to:

Add

...

Merge

Add an element from the Source to the Target.

  1. Select the Source element and the Target element and click Merge.

  2. Confirm the merge.

...

Overwrite

...

Merge

Overwrite an element from the Source on an element in the Target.

  1. Select the Source element and the Target element and click Merge.

  2. Confirm the merge.

Update

...

Merge

Update an element from the Source with an element in the Target. As an alternative to overwriting, you can choose to update existing elements with new information from the source.

  1. Select the Source element and the Target element and click Merge.

  2. Confirm the merge.

The Source elements will be merged with the Target.

...

  1. The Update merge clarification popup will open when Merge is clicked

Update merge clarification popup

...

Notes on Update Merging

Streamlining dependencies

Description: Streamlining involves simplifying and optimizing the dependencies and processes between two capabilities to eliminate redundancy and inefficiencies. This ensures that only the most essential, efficient, and relevant processes are retained, reducing complexity while enhancing performance and collaboration within the business unit.

Example: For example, if two capabilities in the same business unit use separate tools for similar tasks, streamlining would involve consolidating these tools into one unified system to avoid duplication, reduce costs, and improve workflow efficiency. Similarly, if both capabilities have overlapping processes, these can be combined into a single, more effective process, removing any unnecessary steps.

Discarding redundant processes

Discarding redundant processes means identifying and removing duplicate or unnecessary tasks, workflows, or activities between the two capabilities being merged. This is done to eliminate inefficiencies and ensure that only the most relevant and valuable processes are kept. Redundant processes typically include overlapping steps that do not add value or are already covered by another process in the merged capability.

Example:

For instance, if both capabilities include separate approval processes for similar tasks, discarding the redundant process would involve keeping only one streamlined approval process that covers the necessary functions, thus avoiding duplication and saving time.

...

Unmerge

To unmerge elements from the business architecture domain of one organizational unit from another, follow these steps:

...