Hollywood Doesn't Fear Data. It Fears Who's Reading It.

My friend Tobias Queisser published a guest column in TheWrap this week titled *”Hollywood’s Real Disruption Problem Isn’t Netflix. It’s a Fear of Data.”* If you work anywhere near this industry, read it.

The piece is built around a 2018 conversation Tobias had with the CTO of a major studio. The CTO’s message, paraphrased: transparency creates accountability, and accountability is what people are trying to avoid. So nobody actually wants transparency.

I could have been in that meeting. I’ve been in versions of it for thirty years. The only thing that surprised me is that the CTO said it out loud.

Tobias is making the argument at the development and distribution end — that the same studios that adopt every new camera, lens, and post-production tool the day it ships still evaluate scripts on paper and forecast revenue on whiteboards. He’s right. But the disease isn’t confined to the front office. It runs the whole length of the pipeline. And the middle — production itself — is where the most quantifiable damage is happening every day.

Here’s what I see on every show:

A studio greenlights an $80M production. From day one of prep through wrap, that show generates an extraordinary daily data stream — Daily Production Reports, call sheets, script revisions, setup counts, page counts, footage shot, company moves, pre-calls, forced calls, meal penalty violations, crew sizes, department configurations, weather, sunrise and sunset times, location vs. stage, exteriors vs. interiors. Everything.

Then the show wraps. All of that data — months of meticulously collected, paid-for operational intelligence — gets archived as non-searchable PDFs and never looked at again.

Same studio. Same year. Maybe twenty shows running in parallel. None of them are talking to each other through data. None of them will inform the next twenty.

The CTO’s logic explains why. If you could pattern-match the current production against 200 comparable shoots in week three, you’d know whether the schedule is realistic. You’d know whether the setup-to-page ratio predicts a 12-day overrun. You’d know which department configurations historically deliver on similar genres, locations, and crew sizes. The tools to build that are mature. Azure, AWS, and Google Cloud all sell production-grade analytics platforms off the shelf. [note: this suggests the pattern matching exists, it does in filmIQ not inAzure, AWS, and Google Cloud.]

But once you build it, the daily report becomes a daily verdict. Suddenly there’s a defensible answer to “Is this production really on track?” — and not everyone in the chain wants a defensible answer. Some prefer the ambiguity. Ambiguity is where careers survive contact with reality.

That’s one half of the fear. There’s a second half Tobias’s piece doesn’t quite reach, and pretending it doesn’t exist is how producers lose this argument.

**Data without production literacy is a weapon.**

Here’s how it goes wrong. A studio analyzes its slate and finds that three profitable dramas each shot 100 pages in 25 days. The data is clean. The conclusion drawn from it is broken. A CFO who has never been on a set looks at that pattern and asks, reasonably from their seat: why aren’t we mandating 100-page dramas in 25 days going forward? It sounds rigorous. It is, in fact, rigorous-shaped nonsense. The 100 pages worked because of those scripts, those directors, those casts, those locations — variables the CFO didn’t see and the dataset didn’t capture.

That’s the difference between nuclear power and a nuclear weapon. Same fissile material. Wildly different outcomes depending on who’s holding it and what they intend.

The production-side fear of data isn’t only about transparency. It’s also fear that descriptive patterns will get converted into prescriptive mandates by people who don’t know what they’re looking at. Sometimes from ignorance. Sometimes from a genuine wish to control creative outcomes through the only language they understand. The data graveyard isn’t just lazy archiving. For a lot of producers, it’s defensive — better forgotten than misused.

So this is the same fear Tobias identified, with one wrinkle. On the development side, data threatens accountability. On the production side, it threatens that, plus creative control. Same family of fear. Same defensive instinct. Same wasted intelligence.

The path through is producer-led design. The people who understand what the data is measuring need to be the primary interpreters of it. Not the only ones — finance, analytics, and distribution belong in the room. They don’t get to set the table.

The Netflix comparison Tobias draws is where it gets uncomfortable. A 29.5 percent operating margin in 2025 isn’t only about smarter greenlighting. It’s about a chain that runs on instruments instead of intuition from development to delivery — and instruments operated by people who understand what they’re measuring.

Tobias’s GPS analogy is the right one. Waze didn’t kill driving as a craft. It just gave drivers better information about the road ahead. The same applies to the set: six minutes per shooting day on a 10-episode series converts $40,000 of cost into production value on screen. Six minutes. The data to find those six minutes is sitting in archives the studio already paid to create.

The talent is great. The stories are great. The technology is great. The only thing in the way is the willingness to use the intelligence that’s already in the building — and the discipline to put it in hands that know what it means.

Tobias closes with the line about paper maps — they had their day, but nobody’s switching back. He’s right. The new map is only as good as the navigator reading it. The CTO who told Tobias the truth in 2018 wasn’t wrong about the politics. And the producers who quietly resist data adoption aren’t always wrong about what happens when the wrong people read the dashboard. The answer to both is the same: design the system so the right people are in charge of interpreting it.

I’d love to hear your thoughts.