[IxDA Discuss] Design Deliverables and Developers

[Jason Zietz]

I view design deliverables in the same way as I view whatever it is that 
I'm designing: I'm building something for *someone*, so in order to get 
it right, I must consult with them and understand their needs.  It's 
more important to me that I deliver something that conveys functionality 
and behavior effectively without creating too much noise, i.e., usable 
documentation.

In my most recent project, I communicated with the developer as I worked 
on the documentation, providing him with samples of different options 
(in the context of the project) so he could choose which type of 
documentation best suited him.

Additionally, I'd recommend encouraging communication during the 
development process when possible as things invariably arise that 
weren't covered in the documentation.




> 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.
>