Tuesday, October 07, 2008

 

Renovating the Attic (how is an architect like a web designer?)


When I'm at a party and casually asked the question "What do you do?" (usually posed over a plastic cup of beer at a cookout), I respond with a vague, "I make web sites, you know," and wave my hand in a large circle as though including the entire Internet in my summation. I would never, ever, answer "I'm an information architect." Because that would be embarrassing.


It's hard enough getting someone to grasp the amount and extent of work involved in creating 'what you see' when you're online: the underlying structure, navigation, organization, buttons and bling, etc. My relatives and neighbors can understand the basic idea of making websites – sort of. Thank goodness few of them ever ask a follow-up question...


We've recently begun a home renovation project. After living in the house for two years and coming to a rough idea of what we want to DO with our space, we've hired an architect. His job is to take our grandiose ideas and binder of torn magazine pages, couple them with the existing structure and produce a workable blueprint for crafting the building into something meeting both our dreams and our needs, within physical (and budgetary) limits.


At our first meeting, we asked about the architect's process for tackling a project. It looks something like this: meet with clients, gather ideas, develop a rough approach, meet with clients again and work to refine blueprints, deliver final drawings for the builder to use. Wow. I got it. I understand that process because it's what I use to 'build' online.


I sit down with clients, gather their ideas for a website -- shift through the must-have features and the love-to-do ideas. I dig into the technology to figure out the foundations; develop a sitemap to define the key areas and uses of space and where to put the 'furniture' (content and assets); refine the approach with the client and then deliver a final blueprint for the developers to build or remodel a website.


Of course, problems arise in both realms, and for similar reasons. Our architect went on vacation overseas and neglected to include some of the 'must-haves' when briefing his assistant and the master bath approaches reflected none of our requirements; my client last week neglected to include some of their 'must-haves' during a brainstorming session, and now the sitemap needs tweaking in order to accommodate them.


Finally, I'm beginning to warm up to the title of Information Architect. I'm comfortable defining myself as a virtual architect of online spaces—making the web a better place, one website at a time. I just don't think I'm ready to explain it over a beer just yet, but ask me next summer...




Comments:
I recently started contributing to Mobtown Creative, a blog started up by one of my best friends, photographer Chris Hartlove. In the list of contributors, I was innocently labeled as a Web Designer. I asked Chris to change it. Just lump me in with the other graphic designers. Not because of any sense of embarrassment of my occupation. But because of public mis-perception. Trying to explain what you actually do on a day to day basis with any effectiveness, is in and of itself an artform. especially over a red cup at a cookout.
 
Post a Comment

Links to this post:

Create a Link



<< Home


This page is powered by Blogger. Isn't yours?