Being able to balance the perfect usability architecture and the most beautiful user experience design is sometimes easier said than done. An architect can design a house, but three different builders can use different quality materials to make the overall structures pale in comparison, even though they used the same blueprints. Only one — or possibly none — of the houses may actually meet what the home owner really wants. But that is also the beauty of design creativity. If you ask three designers to make you a rabbit, you may get one ceramic teapot, one oil painting and one origami Volkswagen Rabbit.

Communication is key. It can be done in a variety of ways, but also has to be tailored from the norm to open up the possibilities for a creative mind to have the latitude to explore the potential artistry of the interface. Some are standard, some new and some forgotten, the following methods are all ways to pull the two together.

Try good old-fashioned talking. In this world of digital, in which I live , I often assume that when I send out flow diagrams and user case scenarios in a pdf, they will magically explain themselves, to the designer on the other end of the Internet. If the designs don’t match what I was thinking, whose fault is that? Take 15 minutes to walk through the design rationale and usability structures with the designers. A few simple words can save a few dozen emails and plenty of un-needed rework.

Get back to the basics. Don’t hold back on information unless necessary; people often forget the standards. Things like user cases, flow diagrams, personas, market research and surveys are all things that architects use when planning their usability architecture, but these things are valuable to the designer as well. The more information you can give a designer about the client, market and goals, the more the creative juices will get flowing for them to build a successful user experience that is honed to the users’ wants and the clients’ business needs.

Give some latitude. Being both designer and architect, I see both worlds through a unique perspective. I understand how people can feel some semblance of disdain about creating in a box when given a wireframe with exactly what you need to design and where it needs to be.

Maybe try this next time: create a list of required elements, not a wireframe. The required elements are things that are base standard in a design, as well as specific things that the client wants or needs for the site to be a success, things like logo, footer navigation links, main Flash animation, header navigation and company message.

Next, give a list of optional pieces. The optional pieces are things that, from a strategic perspective, may be add-ons the client didn’t think of that can create additional value. This is the area that is open for designer exploration. Make sure you prioritize or provide groups of importance. You can list specific items if your strategy team has a defined direction, or list general concepts or goals, and let the designers figure out ways to achieve these goals within their design while also giving them a sense of creative freedom. This method helps keep the wireframe layout from subconsciously affecting the designer while designing.

Finally, continue the discussion. Communication is key through all processes of the design, not only between you and your designers but with the rest of the team. Open the designs and usability up to other team members. You may be surprised at the sometimes unique and informative points of view and direction you receive.

Hopefully, these simple concepts can help your team transform their solid usability architecture into a visual masterpiece.