Wireframes usually come with a disclaimer like ‘not representative of actual design’ – this meaning that it’s an abstract schematic of the content and functions that need to be on the frame. How abstract are they really though? How many times has the final design radically deviated from the wireframe that you’ve seen?
A design process without wireframes is likely to be error-prone and unlikely to be well thought through. I’ve done quite a few wireframes myself over the years and I’m a big fan. However, I’ve also learnt that wireframes can be much more influential on final solutions than they should be, locking down the creative process and fixing a solution that isn’t the best.
My approach: always work on creative concepts before or in parallel to the wireframe. I mean creative design and unfettered ‘what if’ solutioning. Never let the creative be a step after the wireframes unless you’re able and willing to re-architect them as you proceed.
Filed under: creative delivery , information architecture, wireframes
[...] On a related note, don’t get too detailed on your wireframes before you’ve worked on design concepts. [...]