What comes first - a blueprint or a concept?
To begin - let’s be clear - we are talking about the development/production tool used to create today’s website the wireframe. As well, most websites today are created using templates. And finally, most websites today, look very similar because there is only so much you can do to a template - no matter how many plugins or code changes you make!
Therefore, within this challenging and sameness environment, for your client, how do you efficiently (both within the given timeframe and the budget), construct a great new website or a refresh for their existing website?
You start by thinking differently, you start by taking out a paper and pencil - for me it’s an unlined paper and fine point marker.( hah, in another post I discuss my ‘issue’ with how lines keep me toooo aligned and therefore not freely inspire-able, and how pencils do not allow for definitive and confident concepting which can build up creative restrictions)
Think about the process - does an architect start by building a structure then coming up with the design after or do they start with sketching designs, agree on one and then go about figuring out how to do it functionally. I think so.
If your client does not have much money or time, then you use wireframes and a template and accept the risk of your solution looking VERY much like everybody else’s. That’s fine and often that’s a good start - but if you can, then I highly recommend taking the extra time at the beginning, concepting - the real competitive world.
hmmm… #1 - “I definitely encourage young ones to deconstruct templates to better understand what's possible. Wireframes are a great learning tool, as are templates!” my web guru - Sarah Moon
I feel that wireframes give the young designers an idea that is the way things are going to ‘be’, but it can cause confusion for understanding the real process. Is this reasonable to say to students and young designers?
hmmm… #2 - - A website wireframe is used to map out the main features and navigation of a new website design. Ah hA! there it is - you have to have figured out what the design looks like, before you start to implement the components necessary to make sure it is easily read and navigated by the user. In my opinion, you start with a potential design direction and ‘test it out - functionally with a user in mind’, before you apply the absolutes of what you can and can not do offered by the restrictions of a wireframe. It gives an idea of the site's functionality before considering visual design elements, like content and color schemes.
hmmm… #3 - There are a few reasons to create a website wireframe, but the most important is that it enables you to identify and take every opportunity to improve your site’s functionality, ease of use, and convenience in order to delight your users. Therefore in my mind it is where within the process to you apply this tool?
hmmm… #4 - A website wireframe provides a practical map of the project for the team to see where everything will go, as they complete the related tasks. To me I interpret this to mean - after the design concept is acknowledged and understood.
It’s up to you, how you proceed, what your process is, but make sure you are clear on the pros and cons of these alternative ways to attack the creation of a successful website - for your product, your client and the user.
— the brand auditor —