From my personal experience, I assume you could categorise your website design process into two sections: the style process that doesn't use a mockup tools, and the one that does. Previously being on sides of this fence, We have an understanding of the way these two processes work even though designing with out a wireframe does work, I might need to vote to be replaced by them.
Wireframing, the roll-out of a "visual blueprint", doesn't have to be overly complicated. At most elementary, I have come across wireframes which are are simply number of post-it notes with all the gui (UI) elements utilized them. They are then placed onto a piece of paper to show the structural layout. Compare this to wireframes produced through design software and you will go to a better refined wireframe with the latter, but regardless of how you wish to you could make your structural model, it feels right always the identical. To put it simply, it shows yourself, the consumer or another party where things will likely be situated on the page.
This is often a real time saver should you be to become a website to get a client. Returning to my days of due to being on "side A" with the fence, when creating a website for a client Irrrve never utilized to execute any wireframing process back then. The full process was comprised of: gathering requirements, spec'ing the website, creating the graphical UI and after that building the web site if the design had been agreed. The most important flaw I came across within this process would be the potential for the client attempting to affect the main layout quite considerably. I'd haven't any problem whenever they just want to tweak things every now and then e.g. colours, make text larger, start being active . more images occasionally, make the video a little bigger (the typical stuff); nevertheless it would have been a ton more painful if they then want to move a number of things about around the page that directly affected the "page template". Jumping to "side B" from the fence and producing the wired layout for that site implies that layout may be agreed beforehand knowing if the UI design is presented, you could then just need to update the standard stuff.
Being forced to Spell out for Clients
Even though presenting a wireframe with a client though, I've had occasions where they might be not wanting to sign this part off because which it looks very "blocky" and "plain". "Yes it does" will be my immediate reply to this since these blocks determines where we are going to put things on your own lovely page to ensure that whenever you return to me afterwards once you have reviewed the graphical design, you can not then inform me how come the navigation up here rather than there? Keep in mind that, I've had clients similar to this before so even though making a wireframe, there could be occasions when you'll still have to spell it that this is purely to get the layout correct for starters, then we'll make use of the pretty small bit with it afterwards.
An Arsenal of Design Software
You don't have to necessarily know the right path around Adobe software in order to produce some decent wireframes. I use a web based tool, Cacoo, to generate mine. This online software lets you drag and drop pre-created elements on to your page. This could save considerable time during the process.?
As with everything web related, everyone can have their unique opinion with this topic, but my very own preference is to use a wireframe whenever I'm designing a web site. Whether it is for any client or for my personal site, regardless of since it implies that the UI design is sped up because you're effectively working from a template.
If you find yourself taking care of a job for any client, then aiming to have Joe Bloggs sign off of the wires before you begin on the UI is part of this design procedure that I would call important making sure you maintain good budget and personal time management on a project.