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?

  • 1
    This question appears to be off-topic because it is about Project Management Communication Issues, rather than UX. Commented Aug 20, 2014 at 11:56
  • 2
    I think this could be UX related actually. Because wire framing is apart of the UX profession, and annotating could be too (at least it was for me for a long time)
    – UXerUIer
    Commented Aug 20, 2014 at 12:26
  • 3
    This is completely UX related question, its just not technical. In this scenario my client is the user and I want to help him understand my process better so that he is not confused when he sees the design.
    – Sokratus
    Commented Aug 20, 2014 at 15:50
  • 1
    Its a good UX question. I've had to do this. And as noted below I did quite a lot of talking it through on the phone as well.
    – PhillipW
    Commented Aug 20, 2014 at 20:26
  • 1
    Having to explain your wireframes with annotations is a funny thing to do as a UX professional. Totally necessary, but it seems like it shouldn't be :). Commented Aug 22, 2014 at 17:56

3 Answers 3


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: enter image description here

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.

  • I feel like this preamble does not help in a significant number of cases. If I didn't know what you are trying to say from the question I would not understand it. May just be me not being a native English speaker through.
    – nwp
    Commented Aug 22, 2014 at 19:47
  • 1
    Disclaimers are good, but clients (like users) don't read. :)
    – DA01
    Commented Aug 22, 2014 at 20:46
  • As I noted, I used this before I presented work as well. So, yes, clients did hear it ;)
    – erik_lev
    Commented Aug 22, 2014 at 20:47

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.

  • You know problem with this I've faced is that client will listen to you, but after the presentation is over they'll tell you that they need to go through it to understand it better. And then they send you a mail asking questions about the exact things you spent 30 minutes explaining and I go like oh "I told you why I did the way it is" and I have to re-explain it to them.
    – Sokratus
    Commented Aug 23, 2014 at 9:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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