Mind mapping data visualisations - mindmap visualization

Why does a data bloke love a Mind Map? Me and the Mind Map, we shouldn’t be friends. I like data, and I really like data architecture. This means I spend a lot of time thinking about what goes where. In this a data architect is just like a normal architect: structure matters. Mind maps on the other hand, well, you know, anything goes really; just plonk your idea in the centre of the screen, draw some spokes and go crazy. Never the twain should meet. Right? Wrong! Wrong and thrice wrong. I love mind mapping for exactly this reason. Data architecture is difficult, resistant to change and defines one version of the truth . It makes my left brain hot. Mind maps are simple, fast moving and readily changeable. They fire up my right brain, get me creative. Let me see the whole solution. What does this mean to you, the user? A good data architect should spend a lot of time with the user, taking the requirement, asking questions, probing the solution. This is nothing other than a brainstorm and mind maps are perfect for brainstorming. I see it as the vital first part of taking any user requirement. A step that should happen way before any data architecture. A step that non-data people understand and a step that is all too often neglected. This is a pox on the entire data industry. I use mind mapping to make it right.