Your website is the frontline when it comes to competing for customers. But what many organizations don’t realize is that it’s also competing for talent to develop and maintain it. An outdated, faulty or slow website can turn away potential talent at first glance. And for those that do bring talent through the door, a site built on legacy infrastructure can be a dealbreaker.
It’s time for businesses to rethink the total cost of legacy CMSes, because these old, clunky tools are driving away the talent essential to driving traffic, converting customers, and delivering digital experiences.
Employees at companies with outdated technology were five times more likely to be frustrated and six times more likely to want to find work elsewhere.
Like software products, websites are built and run by dedicated, cross-functional teams that deliver an ongoing pipeline of updates and new features. While this brings exciting opportunities for content, it also means companies are competing to recruit and retain top talent to build these websites and apps, develop new digital products and expand into more channels and markets.
Technology matters when it comes to talent acquisition and retention. Employees at companies with outdated technology were five times more likely to be frustrated and six times more likely to want to find work elsewhere, compared to employees at companies considered to be technology leaders, according to research from New Digital Workplace Divide.
A CMS impacts most people working on digital products, including the content creators, developers, and digital leaders who direct the development of new products. The technology used to manage content across products can either enable people to do their best work or become a source of frustration. Upgrading content infrastructure is more than a tactical decision — rather, it’s a strategic investment in talent that will drive organizations forward.
Traditional CMSes Frustrate Developers
Developers are arguably the most coveted talent, with job growth projected to be much faster than average for the years 2016-2026, according to the Bureau of Labor Statistics. Developers also have above average turnover rates — as high as 23.3 percent, depending on the type of developer, according to LinkedIn.
Given this, it is critical for companies to address factors that frustrate developers — especially the younger ones. Developers forced to work with tools that were “hot” a decade (or more) ago are likely going to search for opportunities elsewhere.
CMSes, for example, made sense back in the day, but their rigidity has no place in today’s dynamic business environment. Aging CMSes don’t provide development teams with the equipment they need to effectively do their jobs. Outdated CMSes burden developers with environments that introduce redundancy and rigid workflows — whether they make sense for the task at hand or not.
Further, CMSes often tie content management to presentation, requiring developers to hack existing code to create unique pages and digital products. This new code is essentially customization that is prone to breakage, especially when it’s time to update the platform. At best this creates more work for developers; at worst it decreases productivity and increases risk.
Working in an outdated CMS also limits a developer’s ability to write clean code that is future-proof and able to perform well at scale. This ends up being more work for the developer to maintain, and impacts performance for the end user.
Legacy Systems Limit Growth Opportunities for Developers
Developers have a wealth of languages and models to choose from, and modern platforms enable them to choose the right tools for every job. The ability to choose languages, frameworks and technology was the second most important factor for developers assessing new jobs, according to the 2018 Stack Overflow survey. Choice of technology and professional development opportunities were also on Tech Republic’s top 10 list of perks that tech professionals want the most.
It’s no wonder, then, that working with a legacy CMS that dictates the languages that developers must use is something of a development downer. These limitations make it hard for developers to acquire and apply new skills, which in turn mitigates the contributions they can make to the business. A monolithic system crippled with technical debt also forces developers to spend their days creating patches and endless workarounds.
Choosing a Content Infrastructure that Supports Developers
When a CMS holds staff back or forces them into complex workarounds, it’s time to consider a new content infrastructure that:
- Reduces complexity: Start with a content model for your exact needs, and empower developers to choose the best programming languages for each project.
- Reduces silos: Manage a portfolio of digital products with a single, flexible content infrastructure.
- Increases interoperability: Integrate content with, and from, preferred platforms and services without the redundancy of copying and pasting text or manually resizing images.
- Increases reach and relevance: Extend content into new products and geographies, such as multi-channel uses.
- Increases agility: Ship and iterate digital products faster — on websites, apps, and devices.
The cost of turnover is high, so enabling and retaining teams should be a priority. Removing CMS frustrations means valuable, hard-to-replace employees can spend more time celebrating success and less time looking for greener pastures.
Feature image via Pixabay.