This piece sets out what seems to me to be a novel use for mindmapping: Staffing a project, functional unit or department. It is a good illustration of the flexibility of the mindmapping approach. I often use mindmapping in drawing up job specifications and candidate profiles, but not quite in the way described here. I think I'll give it a try.
Here is another slant on getting your writing going -- research and a dash of mindmapping.
There's only a brief mention of mindmapping here, but it's obviously important to the author. Anyway, to me it's a great article on getting moving with writing. I hope you find it so, too.
The key to getting something useful out of this article is to read the author’s title carefully. Mind mapping simplifies the process of project estimating
-- it doesn’t simplify the actual task-time estimation
. Every project manger knows that the work of a project must be broken into separate and manageable units for estimating. To look at a project and think “That’s about a week’s effort” is a recipe for frustration and missed targets. Mindmaps, spider diagrams and bubble charts are excellent for the first phase of breaking a project into manageable parts. For me mindmaps, as strictly defined by Buzan’s rules, are less suitable than spider diagrams for this type of analysis, but we can assume that Dr. Mariaraj is not being too strict in his use of the term below.
I believe these rules are well worth following if you use mindmaps for learning. They are very hard to follow completely and rigidly - and its not worth trying I have found - if you use mindmaps in adult life, in your work or projects.