Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

It's unclear what level of detail and what format should be used to best communicate UX designs to engineering. I am afraid of making it too detailed or not detailed enough.

Format possibilities:

  • Wireframing
  • Storyboards
  • Prototypes
  • Low res (e.g. balsamiq)
  • Text (wiki)

Details:

  • Pixel perfect
  • Business Logic
  • Interaction Design
  • Use Cases
  • Competitive Research
  • Performance requirements

This question isn't meant to boil the ocean, but more of a ballpark answer to lead me in the general direction.

share|improve this question

closed as off topic by ChrisF, Rahul Dec 2 '11 at 10:15

Questions on User Experience Stack Exchange are expected to relate to user experience within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

    
Hi Alien, this question was closed because it's not related to user experience design. Since your question is about both communicating and design, you could consider asking it on Graphic Design, Programmers or Project Management. –  Rahul Dec 2 '11 at 10:17
1  
@Rahul Isn't this question realted to the usability of the artifact that Alien produces to document his design? Of which the developers are the users? –  katDNA Dec 2 '11 at 12:12
    
I think if you rephrased your question to be about what to include in your design documents not how much it would be a much more answerable question. –  Ben Brocka Dec 2 '11 at 14:55
1  
Thats ok I found out this question had already been asked on here a couple times, and didn't get closed. I guess the UX moderators here need to learn that closing new users questions is having a negative impact on their sites UX. –  Alien Dec 2 '11 at 18:19
    
Your question would have been closed for being a repeat, anyway. –  tajmo Dec 2 '11 at 19:24
show 3 more comments

1 Answer 1

I would make a document with a short specification of the functional behavier of the website. Show the page screens with layout guidelines (raster, measures, colors, fonts, images). And maybe descripe the visual conditions of some controls (status for normal, hover, pressed status). In addition label your layers clearly.

I think, this is good basis for communicating with the developer.

share|improve this answer
    
I would add: clickable prototype essential add-on –  colmcq Dec 2 '11 at 12:57
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.