I%u2019m trying to imagine the work scenes that are the context for the widely disparate views expressed in replies above. I think the dimension that segments the responders is the degree to which the people writing the code are separated from decisions about design, in a physical distance, process, or organizational sense.
Where there is no separation, then specs are viewed as unnecessary palabra that require time and energy to produce, and more time to be maintained. Where there is a significant separation, perhaps even different companies doing design and development, or on-shore design and off-shore development, then specs are part of the on-going contract of what needs to be done. Our team always produces functional spec docs for e-commerce sites we design because another company uses them as a starting point for their work, and it%u2019s not at all obvious to them what will happen, from a data modeling and product affiliate logic table perspective, when a given button is clicked. They would have to discover that all over again for themselves, and we prefer to spare them that waste of resources. I think your answer, Siegy, should be based on how much guidance you will be able to give once the ink is dry on your specs. Paul Bryan Usography (http://www.usography.com) Blog: Virtual Floorspace (http://www.virtualfloorspace.com) Linked In: http://www.linkedin.com/in/uxexperts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46833 ________________________________________________________________ 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
