
A mind map is easier to read than a traditional site map.
There are a few reasons I’ve almost entirely ditched site maps in favor of mind maps. (Mind maps are traditionally considered tools for concept mapping or diagramming complex ideas, not websites.)
First, site maps tend to be better for page-based site diagramming, but as we move toward states and modes, user decisions and flows become more relevant than pages. I find mind maps do a much better job showing routes and decisions that don’t necessarily correlate to a page change.
Second, I find the better mind mapping software to be more intuitive and fast-paced than most site mapping software.

The MindNode UI.
For example, MindNode, an excellent Mac-based mind mapping application, lets you start designing web experiences in seconds. The interface is extremely minimal, and while you can’t customize the look and feel of your work much, the default output is quite elegant and clean. The experience is so easy and fast you actually feel creative again. (MindNode also comes in a touch version for iPhone / iPod / iPad, and it works really well, even on a small screen.)

MindMapper...how very Office-y of you.
But beware. Some mind mapping software leaves a little bit to be desired. For example, MindMapper is feature rich, but I find the interface cluttered and overwhelming. When I want to sketch, I want the UI to disappear. In other words, using software should be as fast if not faster than simply sketching on paper.
Finally, it’s become clear to me after years of experience that most clients just don’t get site maps. They stare blankly, and have little if any feedback. They want to see what the experience will be like for the user. I’ve found mind maps, while still abstract, do a better job conveying what the user experience will actually be like.














