Great design seems to come either from fits of absolute madness or perfectly clear thinking. When it comes to creating a web application, website, or mobile app for which I am being paid money, I generally prefer the latter. So I believe strongly one should never write a line of code or paint a single pixel without a solid game plan.
Refactoring code can be fun, but when it comes to a large development project, it’s nearly malpractice. Wireframing, therefore, is a crucial process that lets you make mistakes before those mistakes become expensive.
There are a wealth of tools out there for web designers. I happen to hate them all. The web-based tools, created before what I call the “maturity era” of client-side frameworks like EmberJS, feel awful in the browser. The native wireframing apps, on the other hand, can be just as clunky, expensive, or out-dated. And my creativity was quickly sapped by a sea of black and white boxes and Comic Sans headers.
Are you proud showing this to a client? Do you gain a sense and feel for the flow of the project? Does it inspire you to move to the next step? And when the answer to these questions is no, some decide to skip wireframing altogether — an even worse, if understandable, mistake.
So I decided to throw every tool out the window and upend my process. Here’s what I do instead and what you should do, too.
Chris Winn about his process of wireframing a project.
Enjoy the full article over on Chris’s blog chriswinn.com