In my previous job working for a non-profit (I’ve talked about it before) we used a few different CMS over the years to manage our online fundraising website. One in particular was absolutely awful and caused us major customer-service headaches! Horrible user-interface, bad data management, non-existent reporting capabilities… It was a nightmare.
The following year, we switched to a different CMS and our lives got much easier. 90% of the functionality of this new system was leaps-and-bounds better than the previous year’s. However, one of my coworkers hated the new site. She thought it was ugly, she thought it was primitive. She would see cool flash animations and interactive content on other websites and she wanted to do things like that on ours. But we couldn’t do those things on our site, the new CMS wasn’t configured to handle the type of coding that generates that kind of decorative bling, and so to her it meant that our site didn’t work well enough. She was hung up on looks and blind to essential functionality. She decided that the whole site was deficient just because we couldn’t pretty it up to her standards.
Continue reading “Functionality vs. Style”