Re: The Right Shortcuts Lead to Efficient Workflow

LizHunt — Wed, 28 Apr 2010 16:00:07 -0000

This is my first read here, Chris. Thanks for your thoughts!

Having read both Aaron's points and yours, I lean in your direction. With the issue of mediocrity momentarily in the distance, my thoughts are that the practice of pattern-finding should be the vehement pursuit of every modern web designer.

Beyond using wireframes and frameworks in the design process, patterns can be seen and used in both the front and back-end process, and eventually, the client's process.

I argue that using a CMS like Wordpress or Expression Engine is a savvy, even critical way to plan for and execute small web projects. By knowing the end before the beginning, one can better plan for both the functionality and organization of a site, and it's use by the client.

By working creatively within the confines of a well-oiled machine, you're forced to think efficiently and solve problems in a carefully delineated and reasonable way (i.e., "What can I realistically do with the navigation functionality if I'm building it on Wordpress?"). The client reaps the benefits in their process because you're also thinking about their needs: "Will they be able to update this easily?

If you're familiar with it's structure, thoroughly understand it's inner workings, and thoughtfully design for it, using a CMS can ensure that your final result is solid, and therefore, not mediocre.

Re: 20 Steps to Better Wireframing

LizHunt — Thu, 19 Feb 2009 11:34:28 -0000

@123Column - Admittedly, wireframes often fail to help us connect with clients and stakeholders. From a website project perspective, however, this is usually because we do not effectively communicate with them.

Many designers, no matter their role, find themselves educating clients. Wireframing tends to be one of the first processes we have to explain before pushing forward. As suggested in this article, why not really use it as a tool to continue the conversations that began in the project kick-off?

The dreaded 'content delay syndrome', where certain content is promised but never delivered, can hurt us in the visual design phase: creating around 'air' is decoration, not design. This can prove frustrating, and is certainly futile.

Wireframes can, in part, cure this ailment. As a planned deliverable, they can be used as bait, helping catch and reel in precious assets. Even if a client is skeptical about pieces of paper that don't convey visual ideas, they'll certainly warm up to them if they are used to start a dialogue: "The idea in this wireframe is to place content A here, and related content B here. What else would you like to see on this page? Do you have copy or images that might be appropriate? When can we expect to see those?"

Although wireframes are just a stepping stone, they can lay the groundwork for the entire project, and certainly the tone. If you're using them as a communication tool first and foremost, project collaboration can only be more productive.

Disqus - Latest Comments for LizHunt

Re: The Right Shortcuts Lead to Efficient Workflow

Re: 20 Steps to Better Wireframing