From my own experience, I suppose you can categorise the web site design process into two sections: the look procedure that doesn't make use of a mockups, as well as the the one which does. Being on both sides of the fence, We have an understanding of methods both of these processes work and although designing without a wireframe really does work, I'd personally ought to vote in preference of them.
Wireframing, the roll-out of a "visual blueprint", doesn't need to be overly complicated. At the most elementary, I've seen wireframes that are simply are compilation of post-it notes together with the gui (UI) elements stolen them. They're then placed onto a notepad to exhibit the structural layout. Match it up to wireframes produced through design software and you'll see a slightly more refined wireframe over the latter, but it doesn't matter how you would like to build your structural model, it's wise always exactly the same. To put it simply, it shows yourself, your client or another party where things will likely be found on the page.
This is sometimes a real-time saver if you are producing a website for the client. Rediscovering the reassurance of my times of being on "side A" in the fence, when making a website to get a client I never used to accomplish any wireframing process in the past. The entire process consisted of: gathering requirements, spec'ing your website, allowing the graphical UI then building the web site when the design ended up agreed. The main flaw I found in this process is the prospect of the customer wanting to customize the main layout quite considerably. I'd have zero problem whenever they only want to tweak things in some places e.g. colours, make text larger, add some more images occasionally, increase the risk for video a little bigger (the most common stuff); nevertheless it would be a whole lot more painful should they then wish to move to produce about about the page that directly affected the "page template". Jumping to "side B" in the fence and producing the wired layout for your site implies that layout might be agreed beforehand knowing once the UI design is presented, you could possibly then only have to update the usual stuff.
The need to Spell it for Clients
Even when presenting a wireframe with a client though, I have had occasions where they will be not wanting to sign this part off on the basis which it looks very "blocky" and "plain". "Yes it does" could be my immediate solution to this since these blocks will determine where we are going to put things in your lovely page to ensure whenever you come back to me down the road once you've reviewed the graphical design, you simply can't then tell me why's the navigation up here and never over there? Keep in mind that, I have had clients similar to this previously so regardless if creating a wireframe, there may be occasions when you still must spell it until this is solely to have the layout correct to start with, then we'll apply the pretty small bit to it afterwards.
A collection of Design Software
You don't have to necessarily know on your path around Adobe software to be able to produce some decent wireframes. I prefer a web-based tool, Cacoo, to generate mine. This online software enables you to drag and drop pre-created elements to your page. This could save time and effort in the process.?
As with everything web related, everyone could have their unique opinion with this topic, but my personal preference is by using a wireframe whenever I'm designing an internet site. Whether or not it's for any client and for my very own site, regardless of because it ensures that the UI design is increased because you're effectively working coming from a template.
When you are implementing a project to get a client, then aiming to have Joe Bloggs sign off of the wires before you start about the UI is part of this design procedure that I'd personally call fundamental to making sure that you maintain good budget and personal time management over a project.