NicheSign inStart a trial →
Reference libraryGuideEvergreen● Structurally cited

Guide

Journalists have a word for 'worth covering.' Solo publishers have a feeling.

Newsrooms screen every story against newsworthiness criteria before anyone writes. Solo publishers inherited the cadence and skipped the screen. Here is the filter, and the kill threshold.

The screen newsrooms run before they write, and you don't.

Newsrooms screen every story against newsworthiness criteria before anyone writes. Solo publishers inherited the cadence and skipped the screen. Here is the filter, and the kill threshold.

The story you shipped because it was Thursday

It is Thursday night and the issue is half-written. The topic was not chosen so much as defaulted into: it was Tuesday, the calendar said Friday, and this was the thing you could turn into 1,200 words by deadline. You have done this forty weeks running, and the cadence holds. The open rates do not move. Underneath the small relief of hitting send sits a quieter question you keep not asking. Was this actually worth covering, or was it just available?

Journalists have a word. You have a feeling.

Newsrooms run every potential story through a screen before anyone writes a word. The screen has a name and a fixed set of criteria: timeliness, proximity, impact, conflict, human interest, prominence. A pitch that clears a few of those gets a slot. One that clears none dies in the morning meeting, on purpose, and no one mourns it. Solo publishers inherited the cadence of a newsroom without inheriting its screen. You ship weekly because that is the rhythm, but you choose what to ship the way nobody on a real desk is allowed to: by what is fresh in your open tabs, by what the calendar will accept. Call it the newsworthiness screen, and notice that you almost certainly do not run it.

Consistency advice solved the wrong problem

The whole creator-advice canon is about output. Show up, post daily, never miss a week, build the habit, trust the compounding. Good advice for the muscle, useless for the menu. Consistency disciplines whether you ship. It says nothing about whether the thing you shipped earned its place in front of a reader's limited attention. So the diligent publisher lands in the worst spot of all: hitting cadence reliably with stories that were available rather than worth covering. The thinness people feel in their own issues is rarely a writing problem. It is a selection problem wearing a writing problem's clothes. You can polish a story that should never have run and it still reads thin, because the screen it failed happened upstream of the first sentence.

The six questions a newsroom asks before you do

The criteria are not new and not mine. The study of news values goes back to Galtung and Ruge's 1965 analysis of how events become news (Galtung and Ruge, Journal of Peace Research, 1965), and the working list taught in journalism programs has stayed remarkably stable since. The value of the list for a beat of one is not as a definition to memorize. It is six questions to ask of a candidate before it ever touches your outline.

Run one story through the screen

Say you write a weekly for indie game studios. Two candidates land in your week. The first: a widely used engine changes its pricing model. Timeliness, it broke this week, yes. Proximity, your readers pay that bill, yes. Impact, it changes what they budget and ship on next quarter, yes. Conflict, studios are publicly furious, yes. Prominence, a named engine everyone tracks, yes. Human interest, founders deciding whether to migrate a three-year codebase, yes. That story clears all six and writes itself, because the screen already found the angle. The second candidate: a roundup of your five favorite productivity apps. Timeliness, none. Proximity, weak, it is about you. Impact, nobody changes anything. Conflict, none. Prominence, none. Human interest, none. It fails five of six. The screen is telling you something you already half-knew on Thursday and overrode because the slot was open.

The kill threshold that makes a queue

Here is the rule that turns the screen into a habit instead of a vibe. A story that fails two or more criteria before you outline does not enter the queue. Not next week, not with a better angle, not because it is a slow week and you need something. Two fails and it is out. The discipline is running this at intake, against a list of candidates, not at the blank page on Thursday when sunk cost and deadline are both pushing you to write whatever is in front of you. Do that, and your queue stops being a list of everything you could write. It becomes a short list of things that already cleared a bar. That is the difference between a publisher who feels busy and one whose issues feel like they had to exist.

A screen is only as good as the candidates you run it against

The screen needs something to act on. The reason solo publishers default to what is in their tabs is that assembling a real candidate list across a beat every week is the actual labor, and it is invisible work that never makes it into the issue. This is precisely what a desk does for a reporter: someone watches the beat, surfaces what moved, and brings a stocked list to the morning meeting so the screen has raw material. Niche is built to be that desk for a beat of one. It watches your specific beat's signal, brings you the week's candidates already pegged to what changed, and hands you a stocked queue to run the screen against instead of a blank page to fill. The judgment stays yours. The screen stays yours. What changes is that you are choosing from stories worth covering rather than from whatever you happened to scroll past.

What we're watching

The honest open question is whether a flat two-fail threshold survives contact with every beat. The best beat writers break their own rules a few times a year, on instinct, and they are usually right to. The rule earns those exceptions by holding the other forty-eight weeks. We are tracking where the threshold is too blunt for a given vertical, and whether some beats need a weighted screen, a criterion that counts double, rather than a flat count of six. If your beat has a value that should outweigh the others, that is the kind of thing worth knowing before it becomes a rule.

Frequently asked questions

How do I decide what to write about in my niche each week?

Run candidates through a fixed screen before you outline, the way a newsroom does. Ask of each story: is it timely, does my specific audience have standing to care, does it change what they do next week, is there real conflict, is there a person or decision at the center, and does it involve a name they track. A story that fails two or more of those does not go in the queue.

What actually makes a story worth covering?

Journalism has a stable answer in its news values: timeliness, proximity, impact, conflict, human interest, and prominence. The study of these goes back to Galtung and Ruge's 1965 analysis of how events become news. A story worth covering clears several of them. One that clears none is filler no matter how well it is written.

Isn't newsworthiness different for a niche newsletter than for a newspaper?

The criteria are the same, the weighting shifts. Proximity for a newspaper means geography; for your beat it means your readers' work, tools, and money. Prominence means names your specific audience tracks, not national figures. The screen ports cleanly, you just apply it to your beat instead of a metro area.

What if a story I love fails the screen?

The best beat writers override the rule a few times a year on instinct and are usually right. The threshold exists so those exceptions are deliberate rather than the default. If you are overriding it most weeks, the problem is not the rule, it is that your candidate list is too thin to choose well.

Keep reading

The full reference library lives at /learn.

More on What to write about

What should I write about this week?

Back to the library

Every pillar, all the reference pages

Start using Niche

Three-day, 2,000-credit trial · no card

Install the MCP server

Run the pipeline in your agent