FCCU website, three generations

First Community Credit Union ran a security-first, enterprise-only shop. The CIO's standing mandate was that anything member-facing had to run on enterprise-grade, hard-to-compromise infrastructure, which ruled out the usual consumer platforms entirely. That mandate is the key to this whole story, because it's what forced every rebuild. Across seven years the site went through three full generations serving 150,000+ members and roughly 100,000 monthly visitors across five business lines, and the trigger was the same each time: a platform reached end of life or lost security support and could no longer stay. Rather than treat each forced migration as maintenance, I used it as the moment to also advance what the site could actually do, three times, from three different seats.

Generation One: the security-forced migration onto Kentico (2016, Web Developer). The site I inherited was old, unsupported, and no longer secure. In a shop where the CIO treated security as the first priority, that made replacing it urgent. I led the migration onto Kentico, an enterprise CMS that met the security bar, on roughly a nine-month timeline to get it stood up and running. This first generation was about getting the organization off a liability and onto supported, secure ground.

Generation Two: the ground-up rebuild on Kentico (2018, Senior Multimedia Developer). Two years on, from a more senior seat, I led a ground-up rebuild rather than another patch. I ran discovery across all five business lines to understand what each actually needed, sat on the vendor selection panel, owned the content architecture, and co-wrote the site copy. I partnered with IT and the vendor on Azure server provisioning sized for the site's roughly 100,000 monthly visitors. The result was a faster, cleaner site with clearer conversion pathways than the version it replaced.

Generation Three: the platform migration onto MVC (2021, AVP, Digital Marketing). By 2021 the Kentico version had fallen out of security support, the same trigger as 2016. This time I led the migration onto an MVC platform, and because we were rebuilding anyway, I used the forced move to ship three capabilities the marketing team had never had: dynamic rate insertion so product rates updated automatically across every page, the organization's first landing page infrastructure, and a cookie-based behavioral personalization engine across four product tracks (auto loan, home loan, credit card, CD), triggered by repeat page visits or an email click-through, that adapted homepage banners to what a member had actually been looking at. I reported biweekly to Executive Leadership through the redesign.