Visio or Axure are often used by professionals but since most of your clients won’t have either package, it can be a pain if they want to make simple tweaks. You can use any package you like to do a wireframe.
There is some debate about whether wireframes should be done before concept (often creatives feel it is more of a hindrance than a help at this stage) but I’d still do one anyway, just for your own peace of mind. The wireframe should be created before the copy, design and obviously code. A quick drawing and a few questions can really ensure you understand each other. Generally I sketch a wireframe in the first client meeting. Sometimes, especially for forms, the wireframe negates the need for a design at all (much to your designers delight!) When should I create my wireframes? This saves endless revisions to copy decks and PSDs. Your designer has a checklist for each element they must include in the design. Your copywriter will know that they can’t go crazy with long navigation names or big chunks of copy. You can write a 60-page scope document but a wireframe sums it all up in a snap. Wireframes help clients, copywriters and designers (and perhaps even you) understand ho w the site or email will eventually function.
They help you decide just how much content you can squeeze on the page and most importantly they save you time and money. Wireframes help you work out all those niggly bits that you’re just not sure about. In my humble opinion, after a decent sitemap, the most important document when building a website is a wireframe (even more important I’d argue than the budget or the timeline).
0 kommentar(er)
