Diese Frage versucht Christina Wodtke in ihrem Blog zu beantworten. Hier die Punkte, die sie an Wireframes stören:
Firstly, wireframes emasculate the designer. [...] We should ask ourselves how often we need separate roles for interaction and interface design. Then, when we do need the deep knowledge the two specialties provide, we need to ask how can we create a process that allows both to fully utilizes their skills.
Secondly, wireframes create design lockdown too early. [...] The wireframe shouldn’t reflect the final layout of the site. Because there is no color and type treatment, you have to do goofy things to get elements emphasized like put a box around it, or make the type bold. [...] But once you have to show it to your client or your boss, the wireframe has to communicate and without color, image and font it doesn’t.
Lastly, wireframes create a false sense of security about the completeness of the work. Wireframes are not interactive, but they look done. Most engineers are annoyed by wireframes, unless accompanied by usecases because wireframes typically don’t reflect every single state and error case possible. Most would rather just have a prototype.
Es lohnt sich auf jeden Fall den ganzen Artikel zu lesen und mal in die Kommentare zu schauen.
→ Christina Wodtke – What’s Wrong with Wireframes?