One of the things I am interested as a designer is how we can work better with developers. If you are lucky enough to work as part of an in-house team you probably (hopefully) have a stronger relationship with developers than those of use who only come in as consultants. Often as a consultant, the only contact we have with the development team might be through the project manager or technical lead. So we must rely on our design documents to deliver our message.
Although we would all like our deliverables to be developer-friendly, they don't always turn out that way. Many of the guidelines I've read for creating client deliverables focus on impressing the client and not necessarily getting work done. Sure, they also try to present the information in a way that readers can understand them, but project managers are a much different audience than developers who are actually doing the work. Does anyone know of studies or other research that explicitly looks at how developers are using design deliverables in practice? Particularly integrating things such as wireframes in to functional specifications. Or even if developers "get" the wireframes and mockups we give them. I've found that developers prefer annotated slides or a big numbered list of issues to having to read anything big, but those types of things don't look as nice as a fully written final report for the project manager. Thoughts? ~ Celeste -- Celeste 'seele' Paul www.obso1337.org ________________________________________________________________ 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
