Updating connected branches in an intelligent way.

  • 1
  • Question
  • Updated 5 years ago
I have a question regarding updates within mind maps. Let's say you have a main topic of "strategy". There you have several branches that make up your strategy. Then you have another main topic being called "execution". There you put all your tasks that you derive from your strategy. What do you do if some part of your strategy changes? Is there a way to connect execution and strategy so you know which tasks in execution that you derived from strategy need to be changed?

Photo of vernehmlassung

vernehmlassung

  • 2 Posts
  • 0 Reply Likes
  • sad

Posted 5 years ago

  • 1
Photo of Ary Velstra, Expert Trainer

Ary Velstra, Expert Trainer

  • 1298 Posts
  • 197 Reply Likes
Have you tried http://www.olympic-limited.co.uk/prod... ?
There is a German version (and a Dutch one coming soon ;-)
Photo of Alex Gooding

Alex Gooding, Champion

  • 872 Posts
  • 220 Reply Likes
Topic Tracker (Ary's recommendation) is a good option but it may be overkill if you are an individual user or if your maps are not very complex

There are some potential alternatives, though a lot depends on the nature of the relationship in your maps between topics under "Strategy" and those under "Execution".

Is there a direct correlation between a strategy topic and discrete execution topics or groups of topics which appear and if so, are they in sequential order (for example strategy A relates to execution topics 1, 2 and 3, strategy B to topics 4 and 5, etc)? Or is the relationship of the execution strategies to the strategy topics non-linear?

Or is the relationship even more fluid, so that for example an execution topic relates to two or more strategy topics, or vice versa? Obviously the first scenario and to a lesser extent the second are the easiest to deal with.

I can think of three options:

1. If the relationship is linear, consider restructuring the map so that instead of one branch for strategy and another for execution, the two are merged and each group of execution topics is linked to the relevant strategy topic.

This approach has the advantage that the relationship of strategy to execution topics is very clear. You can still establish relationships with task dependencies between the execution topics and optionally you can roll-up progress for each group of execution topics to the "parent" strategy topic.

2. If you want to retain the two branch structure you could assign each strategy topic a unique colour. Then code the execution topics relating to that strategy topic with the matching colour. When execution topics need to be updated it then becomes a simple matter to filter for the relevant execution topics by the related strategy topic's colour.

This approach would work with either a linear or non-linear relationship between strategy and execution topics, provided that each execution topic has only one "parent" strategy (though each parent could have several "child" topics). It also has the advantage that each group of related topics will be easy to spot.

3. If however an execution topic relates to more than one strategy topic you would have to consider assigning each strategy topic a unique icon or flag instead of a colour. Untick the Mutually Exclusive option for the group of icons you decide to use so that execution topics can have more than one. Similar to option 2 you can then filter by icon (rather than colour) to find the execution topics you wish to update.
Photo of vernehmlassung

vernehmlassung

  • 2 Posts
  • 0 Reply Likes
Please share a simple mindmap symbolizing what you mean.
Photo of Alex Gooding

Alex Gooding, Champion

  • 872 Posts
  • 220 Reply Likes
OK, I've created maps for each of these options:

Option 1 is restructuring the map to integrate strategies and execution topics:



This is the only option that allows roll-up to individual strategies as well as the central topic.

Option 2 retains the separate strategy and execution branches and uses colours to link them. You can still roll up to the central topic but not to individual strategies:



This image shows the Option 2 map filtered by colour - in this case showing the tasks linked to Strategy C:



Option 3 also retains the strategy and execution branches but uses icons to link them. This approach accommodates task topics that relate to more than one strategy, though it isn't quite as visually effective as Option 2:



The next image shows the Option 3 map filtered by icon - in this case showing tasks linked to Strategy B:



Incidentally with Options B and C topic colours and icons will also be displayed in the Marker Index, as shown in the following image based on Option 3: