Common Information Architecture Documents

What’s in a web page design, anyway?  If you abstract away the colors, textures, imagery — all of the elements we call the “look and feel” — what’s left?

• Words
• Links
• Buttons
• Input fields
• Columns
• Boxes
• Scroll bars

Mmm, boring list.  That’s good, though: this should not be the exciting part.  The exciting parts should be the purpose and content of the web site, and the look and feel that give it life — the struggle and the glory of web design. The elements in the list above should be the basic tools, not the wheels you’re going to reinvent in order to make your site the greatest thing ever to happen to the web.

Read the rest of this entry »

Dangerous Phrases: “Wouldn’t it be cool if…”

Now, we at Helen Marie think the web is very cool. That’s why we’re in this business.  We get excited on a daily basis about all manner of new design and interface ideas and technology.  (Personally, I discover a new way to love jQuery almost every day, and that’s exciting.)  It’s this constant fascination that energizes each one of our projects, and that we hope to find reflected in our clients.

Part of our job is to focus this enthusiasm into disciplined decisions about how best to serve a particular client and a particular project.  We have a lot of healthy arguments that start with, “Wouldn’t it be cool if…?”  The question is often followed by, “I agree, but we shouldn’t do that in this case because….”  Or, just as often: “That’s great — but let’s consider that for phase 2.”

We go through this in order to avoid three big pitfalls: building more than the client needs or can immediately use, rejecting new approaches or techniques because we’re unfamiliar, and committing to unreliable approaches or techniques because the coolness factor affects our judgment.  We wrestle with these issues so you don’t have to.

Read the rest of this entry »