Separating the creative from the technical in web-design.

• Posted: June 24, 2008
• |
• Author: Chris Murphy
• |
• Filed under: Design, Developement, General
• |
• Tags: challenge, Creative, Design, solutions, technical

The first lesson I learned when I started in web-design was that it was extremely difficult to separate the technical from the creative. This is the foundation of my design philosophy and something that comes up now and then in discussions around what it means to "do better work". Over the years, and with the rapid advances in web-technologies, the notion of "extremely difficult" has evolved into "extremely naive".

Web-design in all it myriad forms, can be characterized as the marriage of creative vision and technical implementation. But it is the limitations and resulting solutions for what can be achieved technically that — to me — is the truest definition.

Understandably, this is a touchy standpoint to take depending on who you talk to. From a design and creative perspective, one could argue that it’s all about the ideas; and from a development perspective, one could argue, equally, that the technology drives the creative.

I don’t see that either argument is truly wrong; rather, it has been my experience that creative ideas that steam ahead without regard for the technology required to execute the idea, have typically run amok. This is a lesson that I’m forced to re-iterate whenever I start on a new project.

The road to project hell

When I’m involved in any sort of discussion around creative for online media, one of my first questions is always, “how is it supposed to work?”

Depending on how that question is answered, three typical scenarios arise:

1. People will hedge around the issue of technology and gloss over it with a dismissive, “let’s address that later — this is creative discussion,” response.
2. The “build it and they will come” syndrome rears its ugly head once again (this is, by far, my personal favourite and one that I’d put money on if the occasion presents itself).
3. Technical members of a team are conveniently uninvited from the next few meetings until the concept is baked, and only once it’s ready to go into development are they brought back into the mix.

Follow any of the above scenarios — unimpeded — to their natural conclusion, and the result is an uncomfortable, awkward discussion with the client about how the concept needs to be revisited.

This is the not-so-fun part where I usually get dragged back into the mix to help sort things out. For some reason — and despite my best efforts — the same issues come up time and again.

(At this point I usually excuse myself for a sanity check.)

Seriously, how many awkward client conversations does it take for folks to realize the pattern? How much more of a projects’ profit margin need to be consumed before the red flags start to go up? What about the impact to public/client perception of the creative company as a whole?

Rock the boat

When it comes to online media, it is naive to foster the notion that separating the creative from the technical is sound practice.

If you find yourself in a scenario such as the ones I mentioned earlier, consider the following:

1. Challenge the assumptions and address the issue head-on. There are solid technical solutions to creative challenges, and just because the problem cannot be solved one way does not immediately discount the possibility of it being solved in some other manner. Engage the creative process with a healthy amount of pragmatism.
2. Web-projects need strategy, planning, and enough time to execute effectively. Very few online experiences/applications are instant hits. The rare ones that are (Twitter, FaceBook, BaseCamp, etc), have strategy and planning behind them, each with enough time to evolve. Do not be afraid to play the devil’s advocate and ask the tough questions.
3. Designing and conceptualizing in a silo is rarely ever effective. External input (partial or impartial) can be the difference between having to call a client and tell them you can’t execute on what you proposed, and taking the kernel of an idea and pushing it in a direction previously not considered. Keep your technical team involved as much as possible — they are the last ones who have to execute the concept.

When asked, this is how I consider being able to “do better work”:

If a creative team can accept the notion that separating the creative from the technical is folly, the possibility of conceptualizing better ideas and solutions (stronger creative) is all the more tangible.

Perhaps I am over-simplifying the issue (clients do play a big role in contributing to the issue as well), and there are many other considerations, but all of that aside, at some point common sense needs to prevail.

• (3) Comments
• Permalink
• RSS 2.0
•