This tale rings so true. We recently did some layout designs, presented them to the client who liked them and signed them off. We Started to build the site, the said design had differences in IE and Firefox. This caused issues on so many levels from the client thinking we were incapable and deciding to test their site in every conceivable version of IE, FF, Safari & Opera, resulting with us then having to find multiple for different browsers.
If we’d taken the approach Andy describes it would have saved us all a massive headache, we would have been better placed to explain to the client why the site looks different in IE and FF. By presenting a static design we were basically asking for trouble from the off. I think client education from the start rather than letting them make their own assumptions on why things look different is an easier solution for all concerned.
Darren Nicholls
This tale rings so true. We recently did some layout designs, presented them to the client who liked them and signed them off. We Started to build the site, the said design had differences in IE and Firefox. This caused issues on so many levels from the client thinking we were incapable and deciding to test their site in every conceivable version of IE, FF, Safari & Opera, resulting with us then having to find multiple for different browsers.
If we’d taken the approach Andy describes it would have saved us all a massive headache, we would have been better placed to explain to the client why the site looks different in IE and FF. By presenting a static design we were basically asking for trouble from the off. I think client education from the start rather than letting them make their own assumptions on why things look different is an easier solution for all concerned.