Feature announcement or changelog digest?

A feature announcement answers a focused question such as “How does rescheduling work now?” A digest answers a broader question such as “What changed in how I manage my week?” The first needs enough continuity to explain one change. The second needs selection and grouping more than additional demonstrations.

Avoid naming a sequence a digest simply because three release items exist. If each item needs prerequisites, exceptions and a full walkthrough, a short roundup will probably become a list of claims. Choose a lead story and let the other items remain supporting notes or separate explanations.

The examples below use three fictional changes to a scheduling product: move an existing booking to another open slot; reuse a saved availability block when planning a week; show clearer local-time labels on shared booking details. These are planning assumptions, not current product facts.

All three relate to managing a changing schedule, but they have different explanation needs. Moving a booking involves a consequential action and confirmation. Reusing a block needs a short example. Clearer time labels may be understandable in a single held frame. The two outlines below deliberately give those changes different roles.

This 30-second planning outline spends its attention on one behavior. The other release items are excluded because they do not help the viewer understand the rescheduling decision.

• 0–5 seconds: establish an existing booking and the need to move it. Copy: “Plans changed?”
• 5–11 seconds: show the verified reschedule control and the available destination slots.
• 11–19 seconds: choose one slot and inspect the confirmation details. Keep the original and replacement times distinguishable.
• 19–25 seconds: show the confirmed new booking state and any verified notification behavior. Omit notification claims until supplied by the product owner.
• 25–30 seconds: recap the changed task and name the next action. Put detailed conditions in the accompanying notes without hiding an essential limit.

This alternative 30-second outline provides orientation rather than a complete lesson. Its promise should be “A clearer way to adjust the week,” not “Everything you need to master scheduling.”

• 0–4 seconds: introduce the shared theme, “Adjust the week with clearer context.”
• 4–12 seconds: lead with the booking move, showing the old and new slot plus the confirmed change.
• 12–19 seconds: show a supplied availability block reused in a different week. Avoid implying unverified recurrence behavior.
• 19–25 seconds: hold on a shared booking with the clearer local-time labels and explain what each label refers to.
• 25–30 seconds: show a short recap and direct viewers to the detailed release notes for steps and conditions.

Ask a reviewer to name the question each outline promises to resolve. If the digest leaves them expecting a complete rescheduling tutorial, narrow its title and opening. If the announcement keeps mentioning unrelated improvements, remove those interruptions and retain the coherent action chain.

Use both formats only when they have different jobs. The digest can help existing users identify relevant changes; the focused announcement can then explain the selected task. Repeating the same three-item montage under a new title creates another asset without answering another question.