User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
What is the best way to explain your wireframes to, in my case, overseas clients when you send them via email?
In this scenario my client is the user and I want to help him understand my process so that he is not confused when he sees the design. Would it make sense to explain the wireframes in the email itself or should it be done in a separate document?
Whenever I create a wireframe document, I make enough space on the right for annotations. Annotations are really nice so you can explain what an element is and what it could do in certain scenarios.
Here shows what I did for a document I prepared for a client:
You can also use that right side to show different states of the element (like on hovers, on active, when something happens, etc.)
Just make sure to also meet up with the clients on Skype/phone if you want to elaborate further on anything.
Back in my consulting days, I used this preamble before presenting or sending over any wireframes.
Informs design and guides development by illustrating the navigation, content structure and functionality. Interaction specifications are included to define fundamental user interactions.
Whenever you can, do not send artifacts via email for them to look at without you there. A bit part of your job is presenting the work you create.
So ideally, always show the work to them first during a presentation. That way they're not as likely to jump to all sorts of conclusions prior to your explanations.
