From my personal experience, I assume you might categorise your website design process into two sections: the design procedure that doesn't utilize a wireframe software, and also the the one that does. Being previously on both sides of this fence, We've a comprehension of precisely how those two processes work even though designing with out a wireframe works, I'd must vote to be replaced by them.
Wireframing, the creation of a "visual blueprint", needn't be overly complicated. At the most basic, I have come across wireframes which might be simply are number of post-it notes with all the graphical user interface (UI) elements stolen them. These are generally then placed onto a notepad to demonstrate the structural layout. Match it up to wireframes produced through design software and you'll see a more refined wireframe from the latter, but regardless how you intend to create your structural model, the result is always precisely the same. In other words, it shows yourself, the consumer 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 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 employed to accomplish any wireframing process in the past. The whole process contains: gathering requirements, spec'ing out your website, creating the graphical UI and then building your website if the design have been agreed. The major flaw I came across within this process would be the risk of your client wanting to customize the main layout quite considerably. I'd haven't any problem when they just want to tweak things every now and then e.g. colours, make text larger, then add more images here and there, make video a little bigger (the usual stuff); nonetheless it would be a whole lot more painful whenever they then wish to move a number of things about for the page that directly affected the "page template". Jumping to "side B" of 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
Regardless if presenting a wireframe with a client though, I have had occasions where they will be reluctant to sign this part off on the grounds which it looks very "blocky" and "plain". "Yes it does" would be my immediate solution to this because these blocks determine where we are going to put things on your lovely page to ensure whenever you revisit me afterwards once you've reviewed the graphical design, you can not then say to me why's the navigation up here and never there? Trust me, I have had clients similar to this in the past so even though producing a wireframe, there can be instances when you still must spell it until this is purely 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 on this topic, but my own, personal preference is to use a wireframe every time I'm designing an online site. Be it for the client or my personal site, it does not matter since it means that the UI design is increased because you're effectively working from a template.
When you're implementing a task for the 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 you maintain good budget and time management on the project.