<p>“I part-designed Mike and Sam’s site in Fireworks… Designing using Photoshop, Fireworks, Powerpoint or pencils can be just as important a part of process as HTML and CSS.” </p>
<p>Ahah! That’s how http://forabeautifulweb.com is so beautiful — it isn’t just designing in the browser, and that totally helps with creating more beautiful (and less boring) designs, while still producing live code designs for the client. That’s how I built a particular site that a client loves. Starting off in Illustrator, I had the inspiration, took it to code — showed it as a direction to the client. The client loved it, so I continued the work in the mix of tools, and it worked out. I explained upfront — in the questionnaire and agreement — about older browsers, and the client knew what to expect. I educated the client, who isn’t part of the web tech community, so they could be more informed going forward. This is part of our responsibility. They trust us to know, to inform, to make the best possible decisions for them, with their consideration. It is our responsibility.</p>
<p>“Clients love this process because they feel more a part of it.”</p>
<p>Exactly! </p>
<p>And if you and your environment can’t go this direction — fine. Write an article for 24ways next time… or write it up in your own blog. You’ll have plenty of company.</p>
<p>This is great insight into the methodology of a designer who produces inspiring work. Take from it what you will. If it doesn’t work for you, maybe you can adapt some of it. Even if all you take is making the client part of the process, instead of charging them an arm and a leg to make the design exactly the same in every browser. </p>
<p>Perhaps this discussion will educate some large corporations. I know my friend at “aol.” would love to see the company embrace this way of thinking. </p>
<p>It would save tons of money! That alone should be a great selling point.</p>
jen
<p>“I part-designed Mike and Sam’s site in Fireworks… Designing using Photoshop, Fireworks, Powerpoint or pencils can be just as important a part of process as HTML and CSS.” </p>
<p>Ahah! That’s how http://forabeautifulweb.com is so beautiful — it isn’t just designing in the browser, and that totally helps with creating more beautiful (and less boring) designs, while still producing live code designs for the client. That’s how I built a particular site that a client loves. Starting off in Illustrator, I had the inspiration, took it to code — showed it as a direction to the client. The client loved it, so I continued the work in the mix of tools, and it worked out. I explained upfront — in the questionnaire and agreement — about older browsers, and the client knew what to expect. I educated the client, who isn’t part of the web tech community, so they could be more informed going forward. This is part of our responsibility. They trust us to know, to inform, to make the best possible decisions for them, with their consideration. It is our responsibility.</p>
<p>“Clients love this process because they feel more a part of it.”</p>
<p>Exactly! </p>
<p>And if you and your environment can’t go this direction — fine. Write an article for 24ways next time… or write it up in your own blog. You’ll have plenty of company.</p>
<p>This is great insight into the methodology of a designer who produces inspiring work. Take from it what you will. If it doesn’t work for you, maybe you can adapt some of it. Even if all you take is making the client part of the process, instead of charging them an arm and a leg to make the design exactly the same in every browser. </p>
<p>Perhaps this discussion will educate some large corporations. I know my friend at “aol.” would love to see the company embrace this way of thinking. </p>
<p>It would save tons of money! That alone should be a great selling point.</p>