[Sigia-l] Axure

[Ziya Oz]

> I think it would be a tad harsh to an entire product lifecycle team to
> due away with annotations or other documentation at his point in
> digital product design.

In design, the 'ultimate' or the most 'appropriate' time is never around.
Design is a matter of risk management in time. While absolute elimination of
documentation/annotation may not necessarily be the objective, the goal of
rapidly moving in that direction should be.

We don't ship products that *require* copious amounts of documentation,
annotation, help, etc. Why should designers then produce products for their
intended audiences that require them. It's a matter of discipline.

Some of the most difficult aspects of software production are compatibility,
scalability, compliance, latency, performance, resiliency, etc. While these
are supremely important for the final product, they are by and large
irrelevant for the prototype, which is a vehicle for communicating design
intend.

Once you take away the necessity of paying attention to those constraints of
system performance, prototyping becomes much easier. Then you have to figure
out if you want a prototype that shows how the design works or one that
shows how to build that design.

-- 
Ziya

It depends.
If it didn't, you'd be out of a job.