Read the annotations to get the best value from wireframes!
Pay attention clients - you need to read those notes! Yeah, you know, those things in tiny writing down the side of your wireframes. They mean something, and they can help you get the best out of your new website.
Not only do they help you understand what’s going on (that’s the idea), but we UX people also tend to use them as a place to flag issues up.
Along with detailing complicated functionality, in a typical wireframe deliverable, you’ll come across important notes, like these from a real project:
"…strongly recommended to include these wherever possible."
"Current POS asset not sufficient, new image needs to be sourced/cropped."
"Exact content awaiting completion of the content audit."
Why should you read them? Aren’t these just all things that we, your agency, should have under control?
Well, yes, perhaps. But if you read them you can then say to your project manager or product owner, “Where is that asset?”, “Who’s job is that?”, “Why has no-one thought of this?” etc. That way you’re going to make the most of the all the resources at your disposal. You’ll know where there may be problems, often before we get into the later design and build stages.
And hence you get more for your money!