From my personal experience, I guess you could categorise the website design process into two sections: the design method that doesn't work with a wireframe software, and the one that does. Having been on sides with this fence, We've an understanding of methods these two processes work and even though designing with no wireframe works, I'd personally ought to vote in preference of them.
Wireframing, the development of a "visual blueprint", needn't be overly complicated. At the most elementary, I have seen wireframes that are simply are series of post-it notes with the user interface (UI) elements drawn on them. These are generally then placed onto a small note to indicate the structural layout. Organic and natural to wireframes produced through design software and you will view a better refined wireframe from the latter, but regardless how you intend to make your structural model, it makes sense always exactly the same. Simply put, it shows yourself, your client and other party where things will likely be found on the page.
This may be a realtime saver if you're creating a website for a client. Going back to my era of due to being on "side A" with the fence, when creating a website for any client I never employed to accomplish any wireframing process in the past. The entire process contained: gathering requirements, spec'ing out the website, allowing the graphical UI then building the site once the design had been agreed. The most important flaw I ran across on this process will be the potential for the client wanting to alter the main layout quite considerably. I'd don't have any problem if they simply want to tweak things every now and then e.g. colours, make text larger, then add more images in some places, make the video a lttle bit bigger (the standard stuff); however it was a ton more painful should they then wish to move a number of things about on 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 in the knowledge that if the UI design is presented, you might then just need to update the standard stuff.
Having to Spell against each other for Clients
Even if presenting a wireframe to a client though, I've had occasions where they would be unwilling to sign this part off because that it looks very "blocky" and "plain". "Yes it does" will be my immediate answer to this because they blocks determines where we're going to put things on your own lovely page so that once you return to me at a later date when you have reviewed the graphical design, you can't then inform me why is the navigation up here instead of over there? Remember that, I have had clients this way previously so even when making a wireframe, there may be occasions when you'll still should spell it 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 don't need to necessarily know your path around Adobe software in order to produce some decent wireframes. I take advantage of an online tool, Cacoo, to make mine. This online software allows you to drag and drop pre-created elements on to your page. This can save lots of time during the process.?
Much like everything web related, everyone will have their particular opinion for this topic, but my very own preference is with a wireframe every time I'm designing an online site. Be it for the client or for my own, 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 implementing a task to get a client, then aiming to have Joe Bloggs sign off of the wires before starting around the UI is part of this design process that I might call fundamental to making certain you maintain good budget and time management techniques on the project.