When several products share a release week, it is easy to carry the wrong link, title or availability note into an announcement. Give each update an explicit product before anyone starts writing. A short release record and a final check in the publishing form make that decision easy to verify.
Give each release a product and an owner
Keep one row per planned update in the release list your team already uses. Name the product as it appears in public, identify the person responsible for the announcement, and link to the release notes or documentation that explains the change. Record who can use the change and when it becomes available.
- Product. Public name and product page.
- Change. The workflow, feature or milestone the update covers.
- Availability. The people who can use it and any rollout conditions.
- Release links. The matching documentation and next step for readers.
- Owner and status. Who will check the update and where it is in your process.
Keep the release owner in your own checklist so the team can see who is handling a handoff. On ShipFeed, article access follows membership and permissions for the individual product.
Choose the product when you open the article form
In the ShipFeed workspace, open the product you intend to write about and start a new article from its page. Check the Product field before adding the title and links. The new article form offers approved products you have permission to write for. The product selection determines which product the article belongs to.
When a teammate handles another release, have them check that the intended product appears for their account. If they cannot select it, check the product’s approval and their publishing access with the product owner. The product submission checklist covers the steps for getting a new product ready.
Decide where a shared release belongs
Suppose two fictional apps, MapleTasks and CedarNotes, add a connection in the same week. MapleTasks users can send a task to a CedarNotes document. If the main change is the task action in MapleTasks, publish the update under MapleTasks and explain the CedarNotes connection. A separate CedarNotes update makes sense if its users get a distinct workflow worth explaining, such as a new way to manage incoming tasks.
Use the reader’s task to decide where the announcement belongs. For a separate change in each product, write each update around what that product’s users can do. Link the relevant documentation for both sides where it helps readers use the feature.
Check review and the live destination
Before submitting, compare the product field, title and links with the release record. Check the publishing allowance for the selected product in the workspace and plan for editorial review. Use the product update review guide when preparing the submission or responding to feedback.
Once the update is public, open the article and follow its product link. Confirm that it leads to the intended page and that the links in the update take readers to the right release. Save the public article URL with the release record. Each product page brings together the approved updates for that product, so the same check also protects the history that future readers will find. See how ShipFeed connects products and updates.