What WatchMojo taught me about systems that don't scale emotionally.

There is a version of success in the creator economy that hollows you out. Not through failure, but through scale. Through the slow, almost imperceptible replacement of genuine creative instinct with industrialised systems that work, technically, but that have quietly removed the thing that made them worth building in the first place.

I spent three years at WatchMojo as a writer, voice actor, and eventually Lead Editorial Coordinator. I helped shape editorial direction during a period of significant platform change on YouTube. I contributed to content that generated billions of impressions. And I left with a clearer understanding of the difference between a content machine and a community than I had going in.

This is what I learned.

What WatchMojo actually is

WatchMojo is often mischaracterised. People who haven't worked there tend to assume it's cynical: lists churned out by algorithm, voice acting phoned in, nothing behind it. That's not accurate. The people who work there care about what they make. There are genuinely sharp editorial minds on staff. The production operation is impressive by any measure.

But WatchMojo is, structurally, a content factory. A very large, very efficient one. The pipeline is industrialised in a way that most people who talk about "content strategy" have never actually experienced up close. Topics go through research, writing, editing, approval, thumbnail production, voicing, post-production, and publishing: at volume, at speed, with consistency. The machine runs.

The problem is not that the machine runs. The problem is what happens to creativity, and to audience connection, when it runs for long enough at that scale.

The efficiency trap

When you're producing at industrial volume, you start to optimise. You have to. You learn what performs. You develop formats that work. You notice that certain intros get better retention, that certain thumbnails get more clicks, that certain topic categories reliably draw views. You build systems around those learnings. And then you iterate those systems until they're running almost automatically.

This is rational. It is also where the slow hollowing begins.

The formats that "work" are, almost always, formats that are safe. They're the ones that have already worked. They signal familiarity to the audience rather than surprise. They tell the algorithm: here is predictable content. The algorithm rewards them. And so they get reinforced, and the experimental stuff, the stuff that might build a different kind of audience relationship, gets quietly deprioritised because it's harder to measure.

At the same time, the people making the content start to experience something that I can only describe as creative anaesthesia. You're producing constantly, but you're producing to a brief, to a format, to a template. The decisions that make content feel personal, like the angle you take, the moment you linger on, the line that made you laugh when you wrote it, start to get smoothed out in service of consistency. Consistency is what the machine needs. Personality is harder to systematise.

The audience problem

Here is the structural issue that I don't think WatchMojo ever fully resolved, and that I think most large content organisations don't resolve: the audience is enormous, and entirely anonymous.

When you're reaching tens of millions of people per month, you are not in a relationship with any of them. You are in a distribution arrangement. People find WatchMojo content through YouTube recommendations. They watch it, often passively, often as background. They might subscribe. They almost certainly do not feel any particular attachment to WatchMojo as an entity. They feel attachment to the topic, to the comfort of the familiar format, to the sense of getting information they wanted in a frictionless way.

This is fine as a business model. It is not the same as a community.

I started noticing this gap from the inside. We could see what was performing. We could not easily see why people stayed, or why they left, or whether they cared about WatchMojo specifically versus any other channel that would give them the same content at the same quality. The honest answer, in most cases, was that they didn't care. They were there for the content, not for the brand behind it.

That's a structurally fragile position to be in. If your audience doesn't care whether you specifically make the content, only whether the content exists, then your relationship with them is entirely dependent on continued production and continued algorithmic distribution. The moment either of those wobbles, so does the whole thing.

What I kept trying to change

In my role as editorial coordinator, a significant part of what I was doing was trying to introduce more emotional texture into the content. Not sentimentality, but genuine engagement. Intros that felt like they were written by someone who had a point of view. Scripts that made a case rather than just listing information. Formats that invited the audience into a perspective rather than delivering facts at them.

Some of this worked. Retention went up when the content had more emotional movement. Engagement improved when the voice, my voice or whoever was writing and narrating, felt like a person rather than a format. The numbers supported the approach.

But there's a ceiling to how far you can push this inside a system that is fundamentally built for scale rather than specificity. The more specific you make content, the smaller the potential audience. The more personal the voice, the harder it is to systematise. Every push toward genuine creative distinctiveness ran up against the gravitational pull of the pipeline.

That tension never fully resolved. And eventually I understood that it wouldn't, because the architecture of the organisation wasn't designed to resolve it. It was designed to produce.

The thing that doesn't scale

Belonging doesn't scale. That's the core of it.

You can scale production. You can scale distribution. You can scale reach, impressions, views. You cannot scale the feeling that an audience has of being genuinely connected to the thing they're watching. You cannot systematise the moment where someone feels like the person making the content is speaking directly to them, understands them, is in a real relationship with them. That moment exists. It's what makes the best creators in any medium so powerful. But it requires specificity, presence, and genuine investment that resists industrialisation.

WatchMojo is very good at what it does. What it does is not community. It is reach. And I say that not as a criticism. It's a legitimate and commercially successful thing to build. But it clarified something for me that I've been working from ever since.

When I built NerdyNI, I built it on the opposite principle. Small rooms on purpose. Specific identity on purpose. High emotional texture on purpose. I wanted people to feel like the event was made for them: not because it was optimised for them, but because it actually was. Because I knew the scene. Because I'd been in it for a decade. Because when I was hosting a Pokémon quiz in Belfast and someone showed up in an Ash Ketchum jacket, that wasn't a content metric. That was a person who felt seen.

That doesn't happen at scale. It happens in specific rooms, with specific people, around specific shared enthusiasms. It compounds differently than views do. It builds loyalty that views cannot buy and algorithms cannot manufacture.

What this means practically

If you're building a content strategy, for a brand, for a creator, for a community, the question worth asking is not "how do we scale this?" It's "what are we actually building a relationship with, and who do we want in that relationship?"

Scale and belonging are not incompatible by nature, but they require different architectures. You cannot get to genuine community by treating community as a downstream product of reach. You have to build toward it directly, with different metrics, different timelines, and a different definition of what success looks like.

WatchMojo taught me this by showing me, very clearly, what the alternative looks like at its logical conclusion. I'm grateful for it. The machine ran well. But the machine wasn't the point.