We would very much appreciate your feedback!

Ian

Axure has been my go-to tool for a few years. As you say, it’s not perfect. But once I mastered it and learned to work within the constraints, I found I really could create interactive mockups more rapidly than any other method I’ve tried.

One potential problem with prototypes is the issue of fidelity in interaction design. The best way I can summarize this is to say that “the devil is in the details.” That is, while you can use a tool like Axure to simulate common Web interactions, the nuances aren’t always there. I once found myself in trouble with a client who assumed that my Axure prototype — because it included interactivity — was meant to convey *precisely* how the end product would function. Then when I explained it was “just a prototype”, the client was frustrated because they “thought we were further along” in the product development process.

Of course the real issue there is communication. But my point is that an interactive prototype opens the door to inferences you (as the designer) may not be aware of. Clients may see a clickable prototype and assume that you have created working code, or that you are nearly finished with development — when in fact you are just beginning the collaborative design process!

Just something to be careful of. With great power comes great responsibility! Powerful prototyping tools do not eliminate the need to communicate with stakeholders about design process and intent. Many times, they heighten the need for this kind of communication.

We have to remember that building interactive prototypes can be very time-consuming, so, unless it is absolutely necessary to impress the customer or to figure out difficult interaction case or for usability testing – we have to think twice before decide to do it.