Boxes and Arrows: Comments by Ezra Schwartz

Ezra Schwartz — Fri, 01 Feb 2008 15:27:02 GMT

Patrick, thank you for your feedback.
In the context of the suggested article above…creating and reporting heuristic evaluations typically documents current state of the ui -typically the troubled user interface before the redesign…

As we know, functional requirements will change during the iterative concept development process of the new UI. When I use a simulation tool I notice that stakeholders, especially on the business side, are making meaningful contributions—at sync with progress – because they experience the UI, and how the requirements were articulated. They don’t need to ‘work’ hard at figuring out wireframes, callouts and other stuff that is not user friendly. So there are less surprises (read – cost overruns) when they realize, deep into the process that things are not working as they assumed.

I notice a lot more input at ‘real time and find that capturing change and the possible impact of change on scope can help reduce the cost of such user/stakeholder input. Still, I find it is a real challenge to stay on top of things in a fast paced, simulation based process. Perhaps this should be another article…

Ezra Schwartz — Sat, 23 Feb 2008 15:02:44 GMT

I agree Dana.
BTW, Once one figures out (not that difficult) how to formant a Word template for Axure’s SpecGen utility for generation of specifications, it is possible to provide the team with good-looking, extensive specifications frequently.

Ezra Schwartz — Fri, 07 Mar 2008 16:20:17 GMT

I would highly recommend downloading their evaluation copy and experiments. There are numerous advantages over traditional drawing software you mention and they are not limited just to the heuristic evaluation process. I must stress that I am NOT affiliated with Axure in any way shape or form, and am just a practitioner who is always seeking to improve the value, quality (and yes, as a consultant, also the profitability) of my work. Best Regards – Ezra