From my personal experience, I reckon that you might categorise the web site design process into two sections: the structure procedure that doesn't work with a mockups, and also the the one that does. Previously being for both sides of the fence, We've an understanding of the way those two processes work even though designing with out a wireframe works, I'd have to vote in favour of them.
Wireframing, the creation of a "visual blueprint", must not be overly complicated. At most beginner's, I've seen wireframes which might be are simply group of post-it notes using the interface (UI) elements drawn on them. These are then placed onto a small note to demonstrate the structural layout. Match it up with to wireframes produced through design software and you'll see a slightly more refined wireframe over the latter, but regardless how you would like to make your structural model, the result is always precisely the same. The bottomline is, it shows yourself, your customer or any other party where things will be found on the page.
This is sometimes a real-time saver if you are to become a website for the client. Finding comfort my events of standing on "side A" of the fence, when to become 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 after which building your website if the design have been agreed. The major flaw I ran across on this process will be the risk of your client attempting to change the main layout quite considerably. I'd haven't any problem when they just want to tweak things occasionally e.g. colours, make text larger, atart exercising . more images here and there, make video somewhat bigger (the usual stuff); nonetheless it was obviously a whole lot more painful should they then want to move to produce about around the page that directly affected the "page template". Jumping onto "side B" with the fence and producing the wired layout for the site ensures that layout could be agreed beforehand knowing that once the UI design is presented, you may then only have to update the usual stuff.
The need to Spell it for Clients
Regardless if presenting a wireframe with a client though, I have had occasions where they might be hesitant to sign this part off on the grounds it looks very "blocky" and "plain". "Yes it does" can be my immediate response to this because they blocks determines where we're going to put things on your own lovely page so that once you come back to me at a later date once you have reviewed the graphical design, you simply can't then tell me why's the navigation up here and never there? Trust me, I've had clients such as this during the past so even if to become a wireframe, there could be times when you will still need to spell out until this is solely to have the layout correct to begin with, then we'll make use of the pretty tiny bit for it afterwards.
An Arsenal of Design Software
You should not necessarily know the right path around Adobe software as a way to produce some decent wireframes. I personally use a web based tool, Cacoo, to produce mine. This online software lets you drag and drop pre-created elements onto your page. This may save a lot of time in the process.?
As with everything web related, everyone may have their unique opinion about this topic, but my personal preference is by using a wireframe each and every time I'm designing a website. Whether it is for the client or my personal site, it doesn't matter since it means that the UI design is increased because you're effectively working coming from a template.
When you are taking care of a project to get a client, then hoping to have Joe Bloggs sign from the wires before starting on the UI is part of this design method that I'd call important ensuring that you maintain good budget and time management planning with a project.