What a Slow Upload Actually Costs a Newsroom

Every newsroom I have worked with has some version of the same story: the crew gets the shot, and then the shot sits. It sits on a card in a truck, or on a laptop with a bad hotel connection, or in a compression queue that someone built five years ago and nobody has touched since. The story does not fail because the reporting was bad. It fails, or it airs late, or it airs smaller than it should, because the file could not move fast enough to matter.

latakoo's founders, Paul Adrian and Jade Kurian, built the platform out of that exact frustration, because they had lived it as journalists before they built anything. My work there focuses on sales and film partnerships — filmmakers and production teams whose assets are enormous and whose crews are never in one place — and as Scholar-in-Residence, on a slower question underneath the fast one: what does the infrastructure of moving video actually do to the journalism that depends on it?

The honest answer is that infrastructure is not neutral. A newsroom that can move a file from anywhere, on any bandwidth, and hand it automatically into whatever system it already runs, can chase a story a slower newsroom has to let go of. That is not a marginal advantage. Over a year, it is the difference between a beat reporter who can be first from the field and one who is always explaining why the file is still uploading.

I did not expect the research side of this job to matter as much as the sales side, but it has turned out to be the more interesting problem. Workflow decisions get made by whoever is closest to the deadline, almost never by whoever is thinking about what the workflow does to the reporting itself. Somebody should be asking that question on purpose. That is the work I am doing now.