“Should we announce this?” is one of the most useful questions in product marketing.
It is also easy to answer badly. Teams either keep everything quiet and wonder why customers miss the work, or turn every small fix into a launch and train people to ignore the announcements.
The hard part is not writing the post. It is deciding how much attention the change deserves.
Use this lightweight scorecard before opening a draft.
Score four things
Give the update a score from zero to two on each dimension. Zero means the signal is weak. Two means it is strong.
1. Customer impact
Does the change improve a task that matters?
- 0: The customer will not notice.
- 1: It removes a small annoyance or helps a narrow group.
- 2: It changes an important workflow, removes a serious pain, or opens a valuable use case.
Customer impact is about the work, not the size of the code change. A two-line fix can matter more than a new settings page.
2. Audience size
How many of the people you want to reach will care?
- 0: One customer, an internal team, or a very unusual setup.
- 1: A defined segment, plan, role, or use case.
- 2: Most active users, a large prospect group, or a market you are trying to reach.
A small audience does not make an update unimportant. It changes where you communicate it. A feature for enterprise admins may deserve a direct message to that group, not a broad social campaign.
3. Strategic importance
Does the update support a product or company direction you want people to understand?
- 0: Useful work with no broader story.
- 1: Reinforces an existing position.
- 2: Introduces a new capability, market, workflow, or reason to choose the product.
This dimension keeps your communication aligned with the product you are trying to become. A small integration may matter because it supports the market you are entering, even if few users need it today.
4. Demonstrability
Can someone understand the value quickly?
- 0: The change is invisible or needs a long technical explanation.
- 1: A short example or screenshot makes it clearer.
- 2: The before and after can be shown in a few seconds.
Demonstrability is not a measure of quality. It is a measure of how easily the benefit can travel through a channel.
Map the score to a communication level
The total score is a guide, not a law. Context still matters.
| Score | Communication level | Typical treatment |
|---|---|---|
| 0 to 2 | Silent | Ship it, record it internally, and move on |
| 3 to 4 | Mention | Add it to a roundup, short update, or concise changelog entry |
| 5 to 6 | Feature | Write a useful release note and use the channels that fit the audience |
| 7 to 8 | Launch | Build a coordinated campaign with a central story, proof, and follow-up |
Use the score to decide how much thinking and preparation the update deserves. Channel selection remains a separate decision.
Try the scorecard on three updates
A dependency update
The product is now running on a newer version of a library. Nothing changes for the customer.
- Customer impact: 0
- Audience size: 0
- Strategic importance: 0
- Demonstrability: 0
This is silent communication. Keep the record for the team and any compliance process. A public campaign would add noise without helping the customer.
A faster import flow
Users can now import a large project in a fraction of the previous steps. A short recording shows the old and new flow.
- Customer impact: 2
- Audience size: 2
- Strategic importance: 1
- Demonstrability: 2
That is a feature announcement, and it might be a launch if faster imports are central to the product’s position. Show the task becoming easier. “Improved import performance” is accurate but weak.
A new GitHub integration
The product can now connect to GitHub and use pull requests as campaign input. The company wants to become the product marketing workspace for software teams.
- Customer impact: 2
- Audience size: 1 or 2, depending on the current customer base
- Strategic importance: 2
- Demonstrability: 2
This deserves a launch. The integration supports a new workflow and a clear market story. It should have a campaign that shows the path from a shipped change to ready-to-review content.
Small updates can make one strong campaign
Use the scorecard for individual updates, but also look for patterns.
Imagine five small changes to onboarding:
- clearer setup instructions
- a better empty state
- a sample project
- fewer required fields
- a checklist for the first task
None may deserve a standalone launch. Together, they tell a stronger story: a new customer can get to the first useful result with less friction.
Bundle changes when they share a customer problem and a believable outcome. A shared calendar week is not enough.
Match the investment to the decision
There are four common mistakes here.
Treating code size as customer importance
A huge refactor may be invisible. A tiny workflow change may save every customer ten minutes a week. Score the result, not the effort.
Treating reach as the goal
More impressions do not make a weak update useful. Start with the people who need the change and the action you want them to take.
Making a launch out of a label
“New AI-powered dashboard” is not a campaign idea. It is a product label. The campaign still needs a problem, an outcome, and proof.
Making every channel mandatory
An update for GitHub-heavy technical teams may need a changelog, a short X post, and a direct email. It may need nothing more. Channel choice is part of the decision.
Use a decision record
Once you choose a level, write down why. One sentence is enough:
We are treating saved reporting views as a feature announcement because weekly report setup affects active marketing teams, and the before-and-after is easy to show.
This helps the next person understand why the update was handled that way. It also keeps you from reopening the same question when the campaign is already in progress.
OpenPMM is being built to carry this decision into the campaign workflow. An agent can start from a GitHub or Linear change, use your brand context and templates, prepare the relevant channel outputs, and leave you with a clear review step. You can choose a direct send for a small update or a full campaign when the change needs more coordination.
The aim is to make that judgment quick, visible, and easy to act on.
Use the scorecard
Announce an update when it has a customer outcome worth sharing, an audience that needs to hear it, a connection to your product direction, or proof that makes the value easy to understand.
Keep it quiet when none of those signals are there. Use a mention when one signal is enough. Build a campaign when several line up.