The best time to modernize your newsroom was 5 years ago. The second best time? Right now.

Something rare is happening in broadcasting right now. One of those moments that comes around once every 30 years in our industry where a shift that felt impossible suddenly feels inevitable now actually is within reach. We're talking about replacing your NRCS. Those good old legacy newsroom systems that have been running longer than some of you have been working in broadcast.

I know:
They work.
They've always worked.

That's exactly the problem.

So why change?

Because the talent is walking out the door. The people who set-up these systems and know how to maintain these systems are leaving. They’re either leaving or retiring. This year… Next year... The year after that… And nobody is coming to replace them.

Because the young journalists and producers entering the industry are used to working with Google Docs and collaborative tools that just work. They open a link and start working. No training manual. No proprietary protocol from 1995. Just intuitive interfaces to motivate them and guide them.

You're not going to convince a 22-year-old to learn a closed system when they can go somewhere else and use open tools they already understand. And I get them:
Is it really too much to ask to have a pleasant UX in the tool that you spend 10 hours a day in?

User experience matters.
Design matters.
And taste? It’s not subjective; it exists.

And the biggest problem of all: muscle memory

Broadcast operators built years of muscle memory around these inefficient workarounds. Copying and pasting between systems. Clicking through folders that shouldn't exist. Hours spent on tasks that could be automated. And we know it’s tempting to keep on working with inefficient tools because you don’t want to abandon something you’ve invested so much time in. But it CAN be different.

Modern systems are easier to adopt than legacy systems. When your tools are built around stories, not rundowns, and when automation is visual and no-code, your producers build workflows themselves. What used to take weeks now takes an evening.

Every new integration looks like a 6-month project

Want to add a new camera system? An AI tool? New graphics software? In a legacy environment, that's a 6-month project. It involves custom development. Assistance from a system integrator, maybe even with the vendor on-site. An insanely long approval chain. You know it: it’s the whole shebang.

Legacy systems were built as closed ecosystems. Everything custom, everything locked in.
Modern platforms like Cuez are built the opposite way. Open APIs. MOS integration. Connect any hardware or software through standard protocols. Your old graphics engine connects. Your cameras connect. Your playout servers connect. And if you want to add something new tomorrow, it just works.

Migration is no longer a Big Bang project. It's gradual, on your timeline.

But why now?

Timing is the part that's changing everything. Because AI doesn't plug into a 30-year-old closed system. If you want AI capabilities (and you do), you need modern infrastructure underneath it.

Your data, your networks, your applications all have to be ready. So if you're going to modernize anyway, do it right.

Why 2026 is different

Three things are true right now that weren't true 5 years ago.

Cloud is mature. Not experimental. 90% of IT decision-makers say hybrid and multi-cloud is their ideal model. Staying on-premises is now the risky choice.

Modern systems connect to everything. You don't rip anything out. You carry new tools alongside what you already have. You migrate on your terms.

The window is wide open, but it won't stay open. The organizational momentum, the leadership appetite, the urgency. These things don't last forever. Every month, more legacy expertise walks out the door. Therefore, every month, the migration gets harder.