
In the age of web 2.0, life for the web designer has never been better. The once-curious “web log” (remember that word?) is now a robust CMS concept powering the architecture of entire communities. Web-savvy individuals previously kept together by guestbook comments and handmade forums can now seal the relationship with a mutual follow on Twitter. An explanation for that neat CSS fading trick can be found only a few clicks away on a StackOverflow thread, where someone miraculously asked your exact question. All in all, wheel-reinventing has been all but eliminated from the developer’s to-do list.
Since so little from-scratch work is needed anymore, the way we execute websites has changed, in many ways for the better. But the changing execution also changed the design process that comes before it – the phase responsible for answering questions such as “What is this website supposed to do?” “What do we most want the visitor to click on once they’re on the main page?” “How will our brand be embodied in the website, outside the About page?”
Think of it like a chef. A chef must first know the menu, the occasion, the size of the group, what tastes to satisfy and food allergies to consider, and so on. Only then can she go on the hunt for the needed meats, vegetables, spices, and utensils needed to create the dish.
This decision-making process demands a significant time investment, sometimes even more so than the execution. But, especially with the race towards resources-minimizing and compatibility that agencies must strive to win, the question “What does the design need? can easily be stunted to “What do I have to work with?” Continue Reading →







