We run across a lot of discussion whether the stage of wireframing a website is important or not. Should you avoid the process of wireframing and just dive into design? What is the purpose of wireframes and why many designers and developers implement this stage as part of their planning tool?

Wireframes are an essential tool of communication that provide a rough guide to website structure. Their purpose is to give guidence to general layout, navigational elements, and content structure to designers, developers and clients. The stage of wireframing is achieved after the process of sitemaps has been approved. At this time, you should have in your hands a site structure in a hierarchical style. Here at Imulus, we take time at a wireframe stage in order to run the design and developing stage smoothly. Only an educated client will understand this process if explained. Sure, all clients would like to see their website redesigned in 24 hours…that would require a lot of java. We take time to explain to our clients why this stage is important to us and to them as well. They will understand.

Our designers will work through the wireframe stage to completion and then will sit down with our developers to discuss the many possibilities. This opens different perspectives which are always handy to get everything on track. For example, when it comes to talking about some special functionality feature for the site, it is a good thing that developers know this ahead of time and see what’s expected. They can see what problems they can run into and how to solve them ahead of time. It is too late if this got avoided when the design is already in development. As for the designers, it is easier to have a wireframe in hand. You get the idea where things are supposed to be, and start to visualize the design. Try to have some fun with wireframes. OK, sure, they can get boring sometimes especially when it comes to some revisions but that’s all because you’re anxious to start the designing and developing. Also, you don’t have to adhere strictly to what the wireframe is showing. We have run across many times where the wireframe was showing one thing, but in the design stage we have changed it. It’s all right to change the wireframe in the design stage as long as the purpose and direction is not lost. My advice is to spend whatever time necessary to complete the wireframing stage; it will make your job easier in the design stage, and will save headaches to developers, as well as to clients.

A book recommendation to follow on a wireframing stage: Web Redesign 2.0 | Workflow That Works by Kelly Goto & Emily Cotler

I know that I’m not the only person that has those days where all your ideas just plain suck. Usually my favorite brainstorming technique for my not-so-creative days is to do rapid brainstorming. The key to this type of brainstorming is to set a goal of 100 ideas in 10 minutes and write down literally everything you can think of. Even if your mind starts to drift and you think about a dog that is outside your window, write it down. This way you free your mind from the normal line of thinking; If you write an idea about a dog, it may lead to a great idea - normally you would discount this thought all together.

One of the reasons this technique is my favorite when my brain is feeling “blah” is that it purges out all of those crappy ideas that keep circulating in my head. Typically if I set a goal of 100 ideas and time is winding down, I scrape to come up with new things I haven’t thought of. This way I’m breaking out of my normal train of thought which is key when thinking creatively.