GregBellDesign

Software that claims to make the documentation process easier always catches my eye. I am a big sucker for it. They make claims such as: time wasted creating boxes and arrows will no longer be, life will be better for everyone, and documentation will be more agile and easy to create and maintain.

Have you ever actually had this experience?

The reason I bring this up is because I tried out the new web app, WriteMaps.

I see what they are trying to do. I understand the push towards tools like this. But, I just don't ever see myself actually using this with a client. How can I create any type of a structure other than a simple hierarchy?

A site map is nothing without notes to go along with it and other types of information to give it context. If I am using cookie cutter software to create my documentation, how do I ever include this necessary information?

I love web based software and simple tools to solve simple problems, but it seems to me that this software could only be used to create the most basic of basic sitemaps.

1. What happens if one of my sections includes a linear flow?
2. What happens if I need to show different uer/system states for different sections?
3. What happens if I need to highlight sections for clients?

I would like to have a tool that was built specifically for Information Architects and Interaction Designers that was web based, but the tool needs to be both specific to the task (sitemaps, flows, wireframes, etc.) as well as open to my documentation process and needs. For now, Visio, Illustrator and InDesign seem to be doing the job just fine.