jen 29 December 2009 This article leaves much to the imagination, because of its story delivery. There’s a great tweet from Eric Meyer that I favorited awhile ago: “What you assume about the motivations of others says a lot more about you than it does about the motivations of others.” I’d apply this to actions, as well. As Andy said, he never did say “design in the browser.” And this is the one of the two more controversial thoughts (it would seem) about this article. So, Andy, if you would, what would be the process for designing a site? Does it vary? Sometimes with ink & paper? Sometimes in Photoshop or Illustrator or Fireworks, or whatnot? Or? Showing the client the design in the browser — that is a really important and useful point. It does alleviate a lot of misperceptions and helps to educate the clients. Everyone keeps learning throughout life, right? About using modern css and not “wasting” time on out-dated browsers, that’s certainly a work environment issue. If you’ve ever worked in an established corporate environment where they are chained to proprietary products, including old out-dated software that is “optimized” (oxymoron) for IE6, and therefore are required to only use IE6 in the workplace (yes, these places do exist), then this idea won’t work. However, it’s a great idea, and eventually IE6 will be gone. It looks like IE9 is rumored to embrace web standards and css3 — and we can all hope that is true. So, Andy, might you show a bit more of the story? Where does this story’s designer begin his creative process?