Hi, > What do you build into your process to prevent this from happening (or at > least to minimize it)?
>From my personal and limited experience there is nothing you can do about it short of dealing with the development yourself. Specs won't do it and there are other surprises that surface during the implementation anyhow. Crucial point is that the specs are never complete and/or unambiguous. If they would be, they'd be so enormous they'd not be fully read or understood (I guess never is a strong word, but...). There is also hardly a way to know all aspects before doing the actual thing unless the thing being done is trivial. Thus, as Adrian wrote already, I think you need to take part in the development phase and be present till the project is "done". That's the only better solution thus far that I've seen to work. Best regards, Janne Kaasalainen ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
