Earlier this year, I found myself in a very serious room, at a very serious European broadcast technology seminar. Clever slides, impressive demos, serious people 🙂 they made tea look like a recreational activity 🙂

And yet… two moments have stuck with me -not because they were loud, but because they were uncomfortably true.

Cloud: When Sovereignty Meets Reality

““You cannot trust what the Americans tell you !” .”

Cue the awkward silence. A few laptops slowly closed. And, well… he wasn’t entirely wrong.

European broadcasters -and frankly most industries- are caught in a curious bind:

• Strategically dependent on Amazon Web Services, Microsoft Azure, Google Cloud
• Politically aspiring to digital sovereignty

The proposed fixes? Standards. Portability. Reversibility. Kubernetes. “Cloud-agnostic architectures.” Theoretically portable? Theoretically!!!

YouTube: The Reality Check

A colleague from a Nordic broadcaster quietly dropped this bomb:

His son’s YouTube channel outperforms professionally produced broadcast content. Consistently.

Let that sink in: decades of editorial expertise and compliance versus a teenager, a phone, and zero governance.

The knee-jerk reaction is to blame “the algorithm.” But here’s the inconvenient truth:

• People don’t resent curation—they value it.
• The real question isn’t whether algorithmic recommendation is good or bad -it’s: who does it better?

And later, here’s a stat that made the room squirm:

People spend 14 minutes searching for something to watch. Many give up.

We’re building extraordinary content machines, and losing audiences before they even find us.

Technology Isn’t the Problem

Better cloud won’t fix this. AI won’t fix this. Because this isn’t (just) a technology problem -it’s a discovery problem. A product problem. A user experience problem. And yet, we rarely talk about it.

Organisational Design: The Missing Conversation

We discussed everything: AI, immersive media, cloud sovereignty, synthetic content. But one fascinating cultural question arose while talking about the opportunity to have competitive EU hyperscalers:

“How do you convince a German engineer not to fully specify a system before building it?”

(Said with genuine love)

Ah, the real tension:

• Traditional engineering optimises for perfection before release
• Software thrives on iteration, testing, failing, adapting

Broadcast technology? Probably sits somewhere in between.

What really struck me was the room itself: engineers, architects, vendors, technology leaders. People who translate strategy into reality, shape culture, and quietly influence change. Yet one topic was almost absent: organisation.

We didn’t ask:

• How should media tech teams actually be structured?
• Should engineers sit with production or product?
• How do editorial and IT collaborate beyond polite alignment meetings?
• Where does innovation actually happen: in labs, or in corridor conversations between two mildly frustrated teams?

And perhaps the more uncomfortable question:

• Are our traditional vertical structures still fit for purpose?

Media organisations have historically been built around verticals: news, sport, culture -each with their own workflows, priorities, and… technology stacks.

But technology is quietly doing the opposite. It is becoming increasingly horizontal:

• Shared platforms
• Common data models
• Unified distribution channels
• Similar tools across the entire value chain

In other words, while the business remains organised in vertical silos, technology is standardising across them.

And this is where the tension starts to show.

IT teams are expected to support highly specific, vertical needs… using increasingly shared, horizontal platforms. The result?

• Competing priorities
• Fragmented ownership
• Endless alignment meetings (the polite kind)
• And a growing sense that no structure quite fits anymore

Because the real shift is this: everything is becoming IT. And IT systems, in turn, are becoming increasingly similar across the organisation -regardless of whether you produce news, sport, or entertainment.

Which raises a slightly provocative question:

Are “news IT” and “sport IT” still meaningful distinctions -or just organisational habits we haven’t quite let go of?

None of this means verticals disappear. Editorial identity still matters. Deep domain expertise still matters.

But the way we organise technology around them? That might need a rethink.

The slightly uncomfortable truth: technology problems are rarely purely technological. They are… organisational.

The Takeaway

The next competitive advantage won’t come from the right cloud provider or the cleverest AI. It will come from:

• Connecting people, technology, and editorial creativity
• Leaders willing to rethink not just systems —but how their organisations actually function

And preferably, that conversation should happen before the next teenager on YouTube laps us again 🙂