From my own experience, I assume you might categorise the site design process into two sections: the style procedure that doesn't make use of a mockups, along with the the one that does. Previously being for sides with this fence, We've an understanding of methods both these processes work and although designing with no wireframe works, I'd personally need to vote in preference of them.
Wireframing, the growth of a "visual blueprint", doesn't have to be overly complicated. At the most basic, I have come across wireframes that are simply are number of post-it notes with all the gui (UI) elements drawn on them. These are generally then placed onto a sheet of paper to exhibit the structural layout. Match it up with to wireframes produced through design software and you may visit a slightly more refined wireframe through the latter, but no matter how you intend to build your structural model, the result is always the identical. The bottomline is, it shows yourself, the consumer and other party where things will be on the page.
This is sometimes a real time saver if you're making a website for the client. Returning to my events of being on "side A" from the fence, when making a website for the client I never utilized to accomplish any wireframing process back then. The complete process contains: gathering requirements, spec'ing out the website, creating the graphical UI then building your website once the design ended up agreed. The most important flaw I found within this process is the risk of the customer planning to customize the main layout quite considerably. I'd have no problem when they only want to tweak things occasionally e.g. colours, make text larger, start being active . more images in some places, increase the risk for video somewhat bigger (the most common stuff); but it would be a good deal more painful should they then need to move a number of things about on the page that directly affected the "page template". Jumping to "side B" with the fence and producing the wired layout to the site ensures that layout might be agreed beforehand in the knowledge that when the UI design is presented, you might then only have to update the standard stuff.
Being forced to Spell against each other for Clients
Regardless if presenting a wireframe into a client though, I've had occasions where they will be unwilling to sign this part off on the grounds that it looks very "blocky" and "plain". "Yes it does" would be my immediate answer to this as these blocks will determine where we're going to put things on your lovely page to ensure that whenever you return to me down the road when 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 this is purely to obtain the layout correct to begin with, then we'll apply the pretty little bit to it afterwards.
A collection of Design Software
You should not necessarily know on your path around Adobe software as a way to produce some decent wireframes. I take advantage of a web-based tool, Cacoo, to produce mine. This online software allows you to drag and drop pre-created elements onto your page. This can save time and effort along the route.?
Like with everything web related, everyone could have their particular opinion about this topic, but my own preference is to use a wireframe each time I'm designing an online site. Whether it is to get a client or my own site, regardless of mainly because it signifies that the UI design is increased because you're effectively working from a template.
If you find yourself implementing a job for any client, then aiming to have Joe Bloggs sign off the wires before starting about the UI is a part of this design process that I'd personally call fundamental to making certain you maintain good budget and time management with a project.