Slide 2
Slide 2 text
Maureen describe the painful user experience
• Back in 2013, can you imaging putting in code for a Twitter widget, just to
have that code “eaten” by your CMS? The cost for creating a Twitter
embed widget was estimated at $30K
• Video embeds could only be done in sidebars.
• Your changes were only published 2x/hour, - if you missed the window,
you’d have to wait.
• If you viewed our site on a mobile device, you couldn’t read the tiny text or
use the dropdown menu.
• Staff complained that our site was too busy – they wanted a cleaner,
modern layout.
• The navigation matched our departmental structure – siloed, not user-
friendly.
• You had to remote into our network to make any kind of website update.
• We were constantly getting help desk requests for “how-to” questions
• Oh, and we were still trying to make the site 508
compliant, subject to a consent decree.
2