Media organizations should be able to pounce on new technologies the way reporters and editors chase a juicy scoop, but there’s often a big barrier: the money they’ve already invested in legacy tools.
According to Deloitte’s 2026 Global Technology Leadership Study, technical debt accounts for 21% to 40% of an organization’s IT spending. That means all the innovative ideas their teams come up with are greeted with a “No,” or at least a “Not right now.”
An editor might come forward with a new approach to digital storytelling that could increase the time audiences spend on a page, for example. It sounds great, but it’s a “No,” because the site’s existing infrastructure won’t easily integrate with the additional tools that would be required. The same goes for a reporter who pitches using AI to help explain the context behind top stories and feature reports.
Elsewhere, an audience development exec could come up with a powerful strategy to attract more subscribers. They get a “Not yet,” though, because the investment they are asking for needs to be allocated towards propping up a database that’s constantly breaking down.
Failing to recognize the problems of legacy technology means publishers risk falling behind competitors, fail to achieve their most important goals, and — most importantly — reduce their ability to innovate in ways that benefit their audiences and advertisers.
This post will:
- Provide a way to better understand legacy technology (or explain it to someone who doesn’t have a lot of technical savvy).
- Define what innovation means in the context of media and publishing.
- Outline the key areas where legacy technology blocks innovation.
- Offer three examples of media organizations that have overcome these challenges and are innovating their way to greater success.
- Suggest an action plan to get innovation back on track.
What is legacy technology?
We all know what politicians and other leaders mean when they talk about the legacy they hope to leave behind. They’re thinking about how they’ll be remembered by those they served, and they’re usually hoping it will be based on achieving a positive, long-lasting impact.
Technology is similar in that the platforms and tools media organizations use can have an extensive track record of delivering on expectations. These are products and solutions that required significant investment, so organizations naturally want to get as much value out of them as possible.
Beyond a certain point, though, this becomes increasingly difficult for a variety of reasons:
- Features become obsolete and/or fail to deliver on user or customer expectations.
- Business conditions evolve, creating needs in performance, scale, and other capabilities that the original products weren’t designed to offer.
- Support options expire.
Market research firm Gartner Inc. defines legacy technology as “an information system that may be based on outdated technologies, but is critical to day-to-day operations.” That explains why, beyond costs, publishers and other organizations hang on to legacy technology so long: they wonder if they can really afford to risk moving to anything else.
On the frontlines, however, AI is creating an increased urgency to modernize. Research from Reuters found 97% of publishers see back-end automation in platforms such as their CMS as important. They’re probably realizing that leaving legacy tech untouched will make it harder and more expensive to use generative and agentic AI in everyday operations.
What innovation in the media sector means
Individual journalists may come up with innovative ways to write a lede, edit a video, or package a collection of stories. What most media organizations are looking for, though, is innovation as it’s understood by other industries: a way of taking new ideas and approaches that lead to new goods and services, or improvements on what they already offer.
Some publishers will be pursuing innovation in specific areas. The Association of Online Publishers’ 2026 survey found “developing new revenue streams through product innovation” ranks first 87%, followed by “growing new audiences” at 82%.
Ultimately, innovation should allow media organizations to do what they do best: nurturing human connection. The stories they tell can help people better understand their government, their communities, and their peers. They can inspire people to work more collaboratively to solve problems.
The greatest publishers simply make us feel less alone, a feat that requires constant innovation as the world becomes more digitally-oriented and technology-driven.
How legacy technology blocks media industry innovation
The longer you hold on to legacy technology, the more likely you’ll be spending time putting out fires instead of looking ahead to your audience’s future needs. This list is by no means exhaustive, but it points out a few of the reasons innovation efforts get put on the back-burner.
1. AI readiness
An outdated CMS can prevent AI platforms and tools from accessing the data they need to help produce content or perform tasks on subscribers’ behalf. This can create extra integration work for already-overworked and often smaller IT teams within publishing companies. It also increases the risk of AI tools causing errors that decrease trust in a media brand, rather than enhance the audience’s experience.
2. Slow workflows
Aging content management systems (CMSes) make editorial teams spend too much time publishing and managing content, even as the volumes they’re expected to produce and the channels they’re using to distribute it are growing. When basic functionality begins failing them, you’re going to see help desk tickets skyrocket.
3. Performance problems
Site and page load speeds matter. They can determine how long and how often audiences engage with your content, and how much they’re consuming. Audiences won’t wait around for long for slow or erratically-performing sites, and will become less likely to return with every bad experience.
4. Point product proliferation
Sometimes it seems easier to apply the tech equivalent of band-aids to legacy technology in the form of additional software and tools. The truth is you’re just going to add more complexity for your IT team to maintain, not to mention a lot of vendor relationships to manage.
5. Lost revenue
Advertisers expect and need to work with publishers who can accommodate specific targeting requirements, provide deep analytics, and ensure brand safety, among other areas. Antiquated systems can limit publishers’ ability to compete and win lucrative campaigns, which could also mean less spending on areas like events.
6. Increased security risks
Cybercriminals are constantly developing more sophisticated techniques to execute attacks and steal data. Even if legacy technology provides basic functionality, it could leave publishers unprotected from a range of threats.
Three media organizations that overcame legacy technology to focus on innovation
It’s easy to be so siloed within your own business that you don’t know how similar firms are grappling with challenges like legacy technology. Here are some examples of how to move modernization forward:
Slate
Slate’s shift from a legacy analytics setup to WordPress VIP and Parse.ly’s modern data infrastructure unlocked a loyalty-first growth model.
By replacing an outdated FTP-based reporting system with real-time APIs, dashboards, and a data pipeline, Slate aligned editorial, product, and analytics teams around “engaged time” as their North Star metric.
This modernization enabled personalized infinite-scroll recommendations, deeper audience insights in Looker, and faster experimentation, driving an 8.5% rise in engaged time and helping Slate Plus reach 35,000 paid members. Success came not from more content, but from moving off legacy tech to a composable, data-driven stack.
The Times
It may be Britain’s oldest daily newspaper, but The Times is taking a forward-looking approach to how it embraces digital-first journalism.
Like many publishers, The Times had been working with a CMS that did one thing well — manage its print operation — but made publishing on digital platforms difficult. This included the need to work across three to seven Google Docs just to publish one article. The team knew they needed something world-class, but there were concerns about compromising their front-end products.
Moving to WordPress VIP has allowed The Times to publish content 34% faster, with 62% fewer clicks. Just as important, The Times has been able to use its CMS as the foundation for a range of innovative digital experiences across its website, tablets, apps, and beyond.
Al Jazeera
Where The Times wasn’t getting what it needed from a single CMS, Al Jazeera was juggling too many. There were half a dozen CMSes that were getting bogged down with security issues which made rolling out new features difficult.
This not only affected day-to-day operations — it meant Al Jazeera couldn’t realize its vision of an innovative digital experience. The plan was to allow people using its app to compare its coverage with those of other outlets, including those coming from international newsrooms and translated from other languages, in order to see the news from multiple perspectives.
By adopting the WordPress VIP headless solution, Al Jazeera can create content once and publish it anywhere, personalize its news feed, and explore integrating user accounts to improve loyalty.
These benefits are on top of lower total cost of ownership (TCO) and improved security. And instead of taking weeks to learn the tools they’re using, Al Jazeera is getting the team up to speed in an hour or two.
Tackle legacy technology with these action items
Getting yourself in a position to innovate doesn’t mean creating your own technology solutions. Publishers should be able to act like media companies, not tech companies.
Instead, use some of the rules of thumb from the case studies referenced above to develop your legacy technology action plan:
1. Audit and assess the extent of legacy technology problems
Go beyond a known-bug list by commissioning a WordPress VIP–led code audit that maps your entire stack, including custom plugins, third‑party integrations, data pipelines, and editorial workflows.
The audit should identify single points of failure, undocumented dependencies, performance bottlenecks, security gaps, and compliance risks, then produce a risk register with severity ratings, effort estimates, and a sequenced remediation plan.
Include a readiness score that benchmarks your current architecture against modern standards for scalability, reliability, and developer velocity.
This pre‑migration assessment surfaces hidden constraints, sets realistic timelines, and prevents costly surprises during cutover so your move off legacy systems is orderly, predictable, and aligned with editorial and product priorities.
It also creates a shared language between engineering, product, and leadership about what must be fixed first, what can be deferred, and where modernization will deliver the biggest ROI in speed, stability, and innovation capacity.
2. Treat procurement like an investigative reporting project
Build a weighted scorecard that reflects your priorities: scalability, security, support SLAs, total cost of ownership, and roadmap fit.
Next, pressure‑test shortlisted platforms with realistic RFP scenarios and proof‑of‑concept briefs. Interview current customers, review competitive analyses, and model performance under peak editorial traffic and breaking‑news spikes before committing.
Demand transparent documentation on uptime history, incident response processes, and upgrade cadences, and validate claims with load tests that mirror your real usage patterns. This rigor prevents vendor lock‑in, ensures the platform can handle your growth and risk profile, and gives you confidence that your chosen architecture will support both today’s workflows and tomorrow’s AI‑driven initiatives.
It also helps you negotiate better terms by understanding where vendors excel and where they cut corners.
3. Try out new platforms and tools as though they were cub reporters
Start with low‑risk pilots — ancillary sites, special projects, or newsletters — to validate workflows, integrations, and performance under real editorial conditions.
Define success metrics such as time to publish, uptime, Core Web Vitals, and editor satisfaction, then document lessons learned and iterate before expanding to flagship properties. Use pilots to test content modeling strategies, permission structures, and editorial review workflows, and to identify any gaps in training or documentation that could slow adoption.
Pilots reduce change‑management friction, surface hidden constraints early, and build internal confidence by proving value on smaller stages before the platform becomes central to your core publishing operations. They also create internal champions who can advocate for the new system and help onboard broader teams once you scale.
4. Augment your talent pool
Fill capability gaps with a blended team: bring in WordPress VIP engineers plus a WordPress VIP Gold or Featured Partner to accelerate migration sprints, performance tuning, and CI/CD setup.
Pair external experts with internal staff to transfer knowledge, codify playbooks, and avoid long‑term dependence on a single vendor while speeding delivery.
You should also invest in structured training programs that upskill existing developers and editors on the new platform’s capabilities, shortcuts, and best practices. This approach ensures you have the right mix of platform expertise, editorial workflow knowledge, and DevOps rigor to execute a smooth transition without overloading your existing team.
Building in lasting in‑house capability lets you continue innovating after the initial migration is complete, rather than relying indefinitely on external consultants.
5. Aim for long-term flexibility and control
Prefer open, composable architectures with clear data ownership, documented APIs, and portability so you can swap components without replatforming.
Negotiate roadmaps, uptime guarantees, and upgrade windows; require audit logs and exportable content/metadata to maintain optionality as your needs evolve.
Design your stack so that critical functions (such as search, personalization, or analytics) can be replaced or upgraded independently, reducing the risk of future lock‑in. The goal is to transcend legacy constraints by giving yourself more choices, whether that’s owning your code, controlling your roadmap, and ensuring your stack can adapt quickly to new formats, channels, and AI workflows as the media landscape shifts.
This flexibility becomes a competitive advantage, allowing you to experiment faster and respond to audience behavior changes without being held back by rigid, monolithic systems.
Media tech modernization as a long-term journey
You probably won’t replace all your legacy applications and infrastructure in one fell swoop. It will take time and care to manage the transition to new technologies in a way that’s secure and successful for employees and audiences alike.
The most important thing is to start the process and commit to ongoing iteration of your tech stack wherever it makes sense. For more on how to think about this, check out WordPress VIP’s CMS Longevity Diagnostic.
