Design the Value Chain, or Inherit the One Your Tech Strategy Builds For You

The relationship between operations and technology in streaming is changing faster than most organizational charts are catching up to. For most of the last fifteen years, the two functions ran in sequence. Technology strategy set the direction on platforms, encoders, ad servers, and content management systems. Operations built the workflows that ran inside whatever direction technology set. The order was rarely questioned. It is being questioned now, because the gap between when technology strategy gets shaped and when operational consequences arrive has collapsed to near zero. Encoding vendors, metadata architecture, automation philosophy, AI deployment scope: these are strategic technology choices that produce operational reality the same day they ship.

A quick definition first. For the purpose of this article, operations refers to the discipline that oversees the entire content value chain end-to-end: technical operations, team development, vendor relationships, rights translation, metadata governance, and the workflows that connect them. It sits between what the business has committed to deliver and what the systems and people can actually execute. In some organizations it lives under content operations. In others it has been renamed several times. The title has evolved. The work has not.

The rest of this piece is about how three streaming business archetypes arrived at three different relationships between operations and technology, and why all three are converging on the same answer.

Scenario 1: The Hypergrowth Challenger

The Pluto TV model

The hypergrowth mandate is single-purpose. Create value in the market, as much as possible, as quickly as possible. Everything else is downstream of that.

Engineering and infrastructure teams get pointed at the work that produces the most visible value: launching new platform partners, lighting up new channels, shipping the app to new devices. The internal supply chain infrastructure that operations relies on tends to get treated as a commodity priority. The work matters, and it is hard to make a roadmap case for it when the alternative is shipping the next distribution deal.

When I was at Pluto, the supply chain rarely won the argument for a dedicated technology spot on the roadmap. That sounds like a complaint, but it is more of an admitted humblebrag. What we produced was exactly what helped us become successful: a content operation that ran lean by necessity and learned to pivot fast when content strategies changed. Operations built the workflow, used what was available, and moved. What made it work was cross-functional relationships that did not appear on any org chart: data architecture, engineering infrastructure, distribution product. None of it was formally owned. All of it was scalable.

The AI reckoning here arrives as a structural surprise. Hypergrowth challengers have the cultural agility to experiment with AI. The lean operational foundation that made the company fast often lacks the normalized metadata schemas and consistent asset IDs that AI workflows need to scale. Winning the land-grab phase required tolerating imprecision. Scaling AI requires eliminating it. The transition between those disciplines is where most hypergrowth-era companies lose time.

Scenario 2: The Consolidated Entity

The post-merger (PMI) phase

The mandate here is tougher than it looks. The combined company has to produce hypergrowth-level revenue performance while also delivering merger-justifying efficiencies. Margins are thin. Debt loads are heavy. Investors and boards expect the combined entity to be more valuable than the sum of its parts on a defined timeline.

Post-merger integration is a well-governed discipline. There is a substantial playbook industry around it for a reason: it is genuinely complex, and the firms running it bring serious expertise to the work. Back-office foundations usually come first because the combined entity cannot enforce governance, run payroll, or close books until those layers are stable. Revenue strategy moves in parallel. Technology convergence typically follows in the early months as the largest single OPEX line outside of staff, and the place where consolidation savings concentrate. Strategic value chain operations has historically come into the conversation after the major back-office, finance, and technology decisions are in motion.

The structural challenge is what tends to be true about the work that comes later in the sequence: it inherits decisions made before its specific operational requirements were on the table. The unified tech stack gets designed against finance, revenue, and engineering priorities, and the operational shape that emerges from those choices often surprises the operations teams who then have to run inside it.

The AI reckoning for this archetype is compounding. The exact liability networks are now trying to address by deploying AI is often the one created during the merger phase. When two large, partially mismatched catalogs get combined, AI cannot route around the inconsistencies underneath. Vendors brought in to deploy AI capabilities frequently do remediation work before they can do build work. 

The enterprise pays for the merger sequence twice: once when the stack gets built, and again when the stack fails to perform at the operational layer. 

The current sequence is well-governed. It also needs to evolve.

Scenario 3: The Legacy Enterprise Giant

The studio system

The mandate at this scale is different in kind: protect massive IP libraries, manage global localization, and transition from decades of linear broadcast infrastructure to global direct-to-consumer streaming.

For legacy media enterprises, the relationship between operations and technology is the most fractured of the three archetypes. Built on decades of siloed business units across theatrical, home entertainment, linear broadcast, international syndication, and direct-to-consumer streaming, these organizations possess unparalleled content wealth and deeply fragmented technical infrastructure. I saw this firsthand at TelevisaUnivision, where legacy enterprise complexity compounded the PMI challenge.

Technology and operations have historically run in isolated fiefdoms. Enterprise IT built massive monolithic systems or signed rigid multi-year vendor contracts designed to serve the largest, most visible business lines. Operational teams inside specific business units built parallel shadow workflows using spreadsheets and localized MAM systems to get their daily work done. Each side was reasonable inside its own frame. The problem is they were often never in the same frame.

These giants are constrained by their own scale. A single title might have hundreds of localized video, audio, and subtitle assets scattered across disparate legacy archives. The primary barrier to AI deployment is asset visibility. Before automation can help, the system has to know what it has and where it lives. That sounds basic. At enterprise scale, it is the hardest problem in the building. Enterprise technology leadership coming from an IT or engineering background sometimes underestimates how operations is simultaneously deeply specific in the daily work and broadly overarching across the business. The strategic value of the media supply chain gets underweighted until the technical side starts getting overwhelmed with upstream workflow failures. By then, the gap between where the organization is and where AI deployment requires it to be is measured in years.

The shift this requires

These three scenarios share a common thread. In every archetype, operations waits in line behind technology strategy. Technology strategy is the upstream choice about where the stack is going over the next eighteen to thirty-six months. That sequence no longer holds.

The iterative-build piece matters as much as the strategic alignment piece. Technology lifecycles are short and getting shorter. What is possible in encoding, metadata tooling, and AI-assisted workflow keeps changing on six, twelve, and eighteen month horizons. A strategy designed to be finished in three years will need some reassessment by month nine. The companies that get this right are designing for iteration, with operations and technology shaping the strategy in the same room and adjusting it together as the ground moves.

The relationship between the two functions is a counterbalance. Neither one reports to the other, but they should both report to the same place. They are two disciplines that pressure-test each other at the strategic level, because each one sees failure modes the other one cannot see from where it sits. Technology leadership sees what is possible. Operations leadership sees what is sustainable. The strategy needs both lenses or it produces an expensive surprise.

The core shift is straightforward: design the value chain and the tech strategy together, or accept the value chain the tech strategy builds for you by default. Some companies are staffing for this. Disney has been hiring for workflow orchestration oversight roles, positions whose explicit job is the proactive management of what is being built, how it affects teams, and how to design the media supply chain end-to-end. Those roles did not exist three years ago in most organizations. They are a leading indicator that some leadership teams have figured out the right question and are staffing to answer it.

What readiness actually looks like

A streaming company does not need a futuristic stack to benefit from AI. It needs a disciplined one. The basic requirements are consistent asset IDs, normalized metadata schemas, observable workflows, human review queues, and policy rules expressed in systems rather than managed ad hoc. These are the operational fundamentals that every archetype above either deferred, disrupted, or siloed. The AI era did not create the need for them. The AI era removed the tolerance for their absence. AI cannot perform on dirty data. The technology surfaces the debt.

A new tool inserted into an undisciplined operational structure produces the same output the old tool did, with a more expensive contract attached. Getting the structure right requires leadership to treat operations as a design partner from the strategy phase forward, with a seat in the room where technology direction gets set.

A lot of these dynamics are new, and that is making everyone uncomfortable. Some operational wisdom still applies. If you do not have time to be thoughtful, deliberate, organized, and disciplined as you figure out your joint technology and operational strategy now, think about how little time you will have to do it over again later.

In streaming, the operational value chain is no longer downstream of technology strategy. Increasingly, it is the thing determining whether the strategy succeeds at all.

---

Rebecca Avery is a Senior Streaming Operations Executive, SME of the SVTA Metadata Working Group, and writes about the operational realities of streaming media.