Is This Actually News? A Practical Decision Before You Draft

“Is this news?” often arrives after a draft already exists. By then, the team is attached to the language and the announcement has acquired momentum of its own. The better moment to ask is before writing. Newsworthiness is not a measure of how proud the team feels. It is a judgment about whether an outside audience has a timely reason to care.

Use the outside-change test

Write one sentence beginning, “For this audience, something changed because…” If the sentence ends with an internal milestone, such as “we completed our roadmap,” the update may belong in a customer email or internal channel. If it ends with a changed capability, access, relationship, or market condition, it may deserve a public treatment.

A redesigned logo is meaningful to the people who made it. A new compliance capability that lets a defined customer group complete a task differently is meaningful outside the company. The distinction is not glamour. It is consequence.

Check timeliness and evidence separately

A real change can still be poorly timed, and a timely conversation can still lack evidence. Ask what makes this relevant now and what a skeptical reader could verify. A partnership signed months ago may need a current activation to be timely. A founder’s observation about a breaking issue needs lived operational context, not a generic reaction.

Use a two-column note. In the first column, list the claim. In the second, list the source: release notes, contract language, approved customer quote, or spokesperson experience. Empty source fields are not a cue to use stronger adjectives. They are a cue to narrow the story.

Choose the right container

There are at least four valid outcomes. A hosted release is useful for a durable, factual company record. A targeted pitch is appropriate when a specific editorial audience has a credible angle. A customer update works when the material matters primarily to existing users. And sometimes the correct answer is to wait.

For example, a new executive can justify a release when their expertise signals a material direction for the company. A routine replacement may be a short customer or LinkedIn update. Deciding not to pitch is not lost ambition. It preserves attention for a stronger moment.

Run the headline test

Draft a plain headline without superlatives. If it sounds like an understandable fact, you have a base to develop. If it depends on “revolutionary,” “leading,” or “game-changing,” return to the change and evidence. Clear language also makes approval easier because stakeholders can debate a specific assertion rather than a mood.

When a release is the right container, guided prompts can turn those verified inputs into a coherent structure, and a hosted microsite can give the final account a dependable home. When outreach is appropriate, matching by beat, outlet, and recent work helps identify people to research, not people to overwhelm.

Make the decision visible

Keep a short log of the outcome and the reason. Over time, it teaches the organization what its strongest moments look like. The goal is not to create more announcements. It is to develop the discipline to make the right one.

Share this decision log with product, sales, and leadership. It gives colleagues a better way to bring forward potential stories: not “can we get press for this?” but “here is what changed, who it affects, and the proof we have.” That change in language improves the raw material before communications is involved. It also helps teams recognize that a strong customer update can be successful without becoming a media pitch. The more consistently an organization distinguishes its audiences and containers, the less likely it is to inflate a routine update or overlook a meaningful one.

For a quick final check, ask a colleague outside the project to read the proposed headline and opening paragraph. Can they repeat the change without using your internal vocabulary? Can they identify the affected person? If not, simplify before selecting a channel. This informal test catches abstraction before it becomes public copy.