Do Engineers Understand UX documents? (was "AlanCooper on Software...")
31 Oct 2007 - 5:31pm
6 years ago
I guess I have to respectfully disagree with here.
A fully coded prototype of a highly interactive interface can be
incredibly difficult to deconstruct. If there is some complex business
logic underlying the interaction (especially something that learns from
user behavior), it can be quite laborious to understand the underlying
rules at the level of fidelity necessary for creating shipping code.
There is certainly a place for interactive prototypes, but there is also
a place for the well-written sentence.
My experience with engineers is that are they avoid documents that don't
answer their questions or are difficult to navigate and understand.
If a programmer is unwilling to engage with succinct and clearly
articulated documentation (with good use of text & graphics), my
experience is that they have other problems and are sandbagging.
> David Malouf said: > > I have found that the only true artifact a developer > understands is coded interactive prototype. W/o one there is > always ambiguity left for "cultural" interpretation. >