Posts Tagged ‘MindManager’
Using mind mapping in BPM projects and methodology development
In thinking about this topic, it occurred to me that the core issue for me is really the visual representation of influence mapping and the transition from unstructured information to a more structured form. Initial ideas are rarely structured. They are organic, like the way we think. However, structured information, like lists, makes the implementation of those ideas much easier to execute. We use MindManager 8 from Mindjet for our mind mapping tool and to provide the transition to a more structured form for the information. You can check out their website for more information on that tool. You can also look here for more information on mind mapping in general. To make my point I have created an example containing three maps. Each map can represent a project, group activity or a methodology (a collection of methodologies is the case for us).
The solid black lines represent normal hierarchical relationships. The dotted lines represent connections of influence. For example, Topic B3 and Topic C3 both influence Topic A2. In our example, the bolder red dotted line represents more direct influence and the smaller blue dotted line represents less influence. You have to set your own standards, like bolder lines representing more influence or one color representing more influence than another. For StrAIT Advisors, our methodology needed to be influenced by other methodologies. A screen clipping is shown below to illustrate how that actually worked for us.
In our case, the dotted blue lines represent the influence of one methodology on our SLR methodology. Some steps were consolidated while others were not influenced at all. After any fine tuning needed for an individual client, the map is exported to Microsoft Project for project execution. In your case, the influences could represent the relationships between projects being handled by your Project Management Office (PMO). Influences between projects are much easier to show on this type of diagram than on a project plan composed of both projects and subprojects. They are much easier to change as well. In a project plan, the connections between tasks are actual dependencies, not connections of influence. Influence is too subjective and vague of a relationship for a project plan.
The need to capture unstructured ideas in team brainstorming meetings or just a casual meeting between collaborators is a vital part of the genesis of change. The conversion of those unstructured ideas into actionable projects is the next vital step. The use of mind maps periodically during the course of any project can be very useful, even if the ideas captured are just stored for the future. You can update them when ideas for improvement occur to the project team.
My core point for this post is that ideas start as unstructured things but must eventually evolve to structured things. Knowing how that process will happen is a key to being successful and adaptable. Identify your tools of choice before your project begins and make sure your leadership has buy-in into your approach. It will help in building credibility and communicating during the course of your project.
I hope this post has been valuable. Talk to you again later…
