FoundationsBoth sides

What a content "signal" actually is

A signal is an observation that survives being checked. The three tests it has to pass, and why most of what gets called a signal is a coincidence with good PR.

Adam Murray7 August 20268 min read
On this page

"Signal" is the most abused word in content strategy. It usually means "a thing I noticed that supports what I already wanted to do."

That's a shame, because the real concept is useful and fairly precise. A signal is an observation about your content that is stable enough to act on. Not a fact, not a guarantee — an observation that has survived being checked.

This article is about what checking means.

The difference between an observation and a signal

You publish twelve videos. Three of them do noticeably better than the rest. All three happen to have a person's face in the thumbnail.

That's an observation. It's true, and you didn't make it up.

It becomes a signal when it survives three questions:

  1. Is it bigger than the noise?
  2. Is it explained by something other than what I think explains it?
  3. Does it hold when I look at more data?

Most observations fail at least one. The ones that pass all three are worth changing your plan for.

Test 1 · Is it bigger than the noise?

Content performance is extremely variable. Two identical videos published two weeks apart can differ by a factor of three for reasons that have nothing to do with either video — a news cycle, a holiday, an algorithm change, the whim of an early sharer.

So the first question about any difference is: is this difference larger than the difference I'd expect between two things that are actually the same?

You can answer that without any statistics. Look at your existing spread. If your last twenty videos range from 4,000 to 30,000 views, then a video at 26,000 is not remarkable — it's inside the range you already produce. A video at 90,000 is outside it.

This is the whole idea behind treating outliers rather than virality as the unit of analysis. An outlier is defined against your own spread, which is the only benchmark that knows what normal looks like for you.

Test 2 · Is it explained by something else?

This is where most content "learnings" die, and it's the one people skip.

Back to the three thumbnails with faces. Ask what else those three videos have in common:

  • Were they all published on the same day of the week?
  • Were they all on one topic?
  • Were any of them shared by someone with a large following?
  • Were they all longer, or all shorter, than the rest?
  • Were two of them posted in a week when you also ran ads?

If all three face-thumbnail videos were also your only three videos about pricing, you have not learned anything about thumbnails. You have two candidate explanations and no way to separate them.

That isn't a failure — it's a finding that names your next experiment. The correct response is not to pick the more flattering explanation. It's to make one video about pricing without a face, and one about something else with a face, and see which pattern follows.

Test 3 · Does it hold on more data?

Three videos is not enough. It's rarely enough for anything.

The uncomfortable arithmetic: with a small number of pieces, a pattern that looks striking can arise by chance more often than intuition suggests. If you have twelve videos and you check them against ten possible attributes — thumbnail style, length, topic, day, hook type, presence of music, and so on — you are running ten comparisons on a tiny sample. Something will look significant. That's what ten comparisons on twelve items does.

This is the single biggest reason confident content strategies turn out to be wrong.

Two honest ways forward:

Widen the sample. Your own back catalogue, and your competitors' public content. Twelve videos is thin. Twelve videos plus 200 from six competitors in your category is a real dataset — and it's public, which is why competitor research is a methodology tool and not just a spying exercise.

Hold the pattern loosely and test it. Treat it as a hypothesis with a next action attached, which is what running a content experiment is for.

What a signal looks like when it's written down properly

A signal that's been through all three tests is a specific sentence. It has a claim, a magnitude, a scope, and a confidence.

The second one tells you what to do and how much to trust it. That's the whole job.

Notice what it includes: the size of the effect, the sample it came from, one confound explicitly ruled out, and an honest confidence. Notice what it doesn't include: certainty.

Signals versus rules

A signal is local and perishable. A rule is general and stable. Almost everything you'll find is a signal.

"Hooks matter" is closer to a rule — it's about how attention works structurally and it's true across categories.

"Our audience responds to a cold open on the product" is a signal. It's about your audience, this quarter, in this category. It may stop being true. That's not a defect; content strategy is mostly local knowledge, and local knowledge is more actionable than universal advice precisely because it's specific to you.

The mistake is treating a signal like a rule — deciding "we do cold opens now" and never re-checking. Signals decay. Re-derive them.

What isn't a signal

A short list, because naming these saves a lot of arguing:

A single piece's performance. One data point. It could be anything.

Anything from a different platform. Cross-platform comparison is a category error — different denominators, different counting rules.

A number without its denominator. "12,000 views" is meaningless without knowing whether that's three times your normal or a third of it. See measured vs reported.

A pattern you went looking for. If you had the conclusion first and then searched the data, you'll find support. You always will. This is the hardest one to police in yourself, and the reason to write down what you expect before you look.

Someone else's benchmark. Category averages from a report are not your baseline. Your baseline is your content.

Where Acumin fits

The product is essentially an engine for the three tests.

Snapshots establish your own distribution, so "unusual" has a definition. Outlier detection compares each piece against that distribution rather than a flat average. Content analysis groups your work by attribute so a pattern can be checked against the alternative explanations rather than just the flattering one.

And every read carries a confidence band, because the honest answer to "is this real?" is frequently "probably, based on not much." A tool that hides that is making you more confident without making you more right.

The judgement stays yours. What the tooling removes is the tedium that makes people skip tests 2 and 3.

How to use this today

Take the most recent content "learning" your team is acting on. Write it as one sentence.

Then answer, in writing: how many pieces is it based on, what else those pieces had in common, and what you'd expect to see if it were wrong.

If you can't answer the third one, it isn't a signal yet. It's a preference — which is fine, as long as everyone knows that's what it is.


Related: The evidence ladder is how much any given source is worth. Outliers, not virality is the method for finding candidates worth testing in the first place.

Written by
Adam Murray
Founder, Acumin

Adam builds Acumin. He spends his days on the same two problems this library is about: working out what a piece of content is actually worth, and getting a brief through production without it turning into something else.

Want this done on your own channel?

Acumin reads your public content and your category and hands back what to make next — every call with its confidence and the evidence it rests on. The first Snapshot is free.