We Are Architects

I like to compare web design and front-end development to architecture. I would argue that we are all truly just architects at heart — re-purposed to build “structures” on the web instead of real physical structures. Architects design buildings for people to use, to live in, to work in, to play in. We do the exact same thing,  just in digital fashion.

Being curious about this ‘web designer equals architect‘ comparison that I’ve come to embrace in my head, I decided to investigate what architects actually do. We all have a vision of what architects do, right? They sit in front of CAD all day drawing walls, doors and toilets on floor plans, right? Some of us (mostly me) just view an architect as Mike Brady sitting at his slanted desk with a pencil and eraser brush, quietly fine tuning a blueprint while Alice chases Bobbie through the house. But after doing some quick online research and reading plenty of articles written by architects on their job duties, I’ve decided that we are in fact architects of the web.

Web Designers are Architects

Finding a little article on About.com that clearly outlines the job duties of an architect, I came across a list titled “A Day in an Architect’s Life” that I found pretty interesting, here it is:

• Discuss the objectives, requirements, and budget of a project
• Provide various pre-design services which may include conducting feasibility and environmental impact studies, selecting a site, or specifying the requirement the design must meet
• Prepare drawings and present ideas for the client to review
• Develop final construction plans that show the building’s appearance as well as details for its construction
• Follow building codes, zoning laws, fire regulations, and other ordinances
• Make necessary changes throughout the planning process

This list could easily be adapted to web design whether you are a freelancer or work for a design firm or corporation. I’ve modified the list and each of these items are really duties we as web designers do on at least a weekly basis. Here is my list:

• Discuss the objectives, requirements, and budget of a web or mobile project
• Provide various pre-design services which may include conducting browser feasibility and device analysis or specifying the requirement the design must meet
• Prepare mockups and present ideas for the client to review
• Develop final development mockups that show the site’s appearance and interactions as well as details for its development
• Follow code specs, web standards, validity regulations, and other web oriented best practices
• Make necessary changes throughout the planning and designing process

Really, web designers and front-end developers are the web’s version of an architect, where as in previous years the web designer was mostly compared to a graphic designer. Today websites are more than advertisements or a place where a person can go to get more information about a commercial they saw.

Sites and apps are really giant media outlets where people now go to watch movies, read a book, play a game, work on a project and interact with others. Just like buildings.

Not Just Graphic Designers

I know what you are thinking right now, “Really? This is an article on a rad web design and development magazine? This isn’t that important.” But if you are a web designer or web developer this is an important piece of your daily job. Assuming you want to create cool, high quality stuff for the web, of course. Web site architecture is a big part of the overall success of your project and understanding the importance of it is kind of a big deal.

We are more than just graphic designers. Graphic design is just one piece of the pie. Just like a building we have to consider larger design elements beyond just the decoration. We have to consider bigger elements if we want the site to withstand the test of time and actually be useful to the client and the user. These larger questions are really what great web architects will ask themselves when designing and developing a site:

• How will the user use the site?
• How will the user interact with each element of the design?
• Will the elements be easy to interact with each other?
• How will the site scale?
• Is the site able to be remodeled or re-skinned?
• Can the site be easily customized?
• Is the design structurally sound?
• What devices will users be using the site on?
• What will users do on and with the site? Read it, watch it, work with it, play with it, etc.

We’ve all either worked on a site that hasn’t been properly architected or we’ve all work with designers and developers who don’t know how to properly architect a site. When designers and developers don’t take these questions seriously or just need to get the job done quickly and dirty, it makes things hard to improve, modify or even update in the future.

The reason this is truly important is that the web is a fluid place; it’s constantly growing, constantly changing, constantly improving itself just as building technologies do. It’s very important to make sure the site structure is solid so that you can continue to build on top of it as well as change it when needed.

Be Better

First, start by asking yourself the questions above when you are working on your next project. Beyond that, I think there are a bunch of other things you can do to start being a better web architect. But in most cases it might just be as simple as adopting a new attitude or philosophy of web design and development.

1. Look at each web project from the project’s best interest, leave your own best interest behind.
2. Be open to learn new tech and new design trends – don’t get left in the dust.
3. Work with really creative and innovative people.
4. Plan ahead and give yourself realistic project time lines.
5. Visualize the finished product and how real people will be using it.
6. Be more patient with the project, your coworkers and even yourself.
7. Fall in love with what you do and work on projects you can be proud of. If you can’t find the passion in your current project, pick out at least one small thing your can improve and make better so that you can get that pride back.
8. Own your work whether it’s good or bad.
9. Be hungry to improve the project and yourself.
10. Try new things all the time even if they aren’t proven techniques yet.

These may sound like something taught at a cheesy self mastery seminar at your local Marriott Hotel convention center. But a great architect is not only concerned with designing a beautiful and pleasing building that will stand the test of time, they are also interested in pushing the boundaries of architecture, designing a great structure for people and leaving a legacy behind.

For web designers, we should try to strive for the same things. We should strive not only to build a site that may have a long and memorable life span on the web (no pun intended). We should strive to innovate where we can and try cutting-edge technologies, fresh design ideas and new usability patterns. We should also want to leave behind a good legacy, even if the only other people that will see or understand it will be the others you work with or for — give them something better to work with.

Don’t Just Write Until it Works

Recently one of my co-workers chatted me a funny comment about how some designers and developers approach their jobs: “Just keep writing until is works“. Needless to say, this type of mentality is not a good practice for web architects. Planning ahead, being patient and thinking about scalability are import keys to being a great architect — but only if you want a great product, I guess.