Artifact: Release-Slicing Increments — Kestrel Team Messaging

Team messaging sliced into three thin, end-to-end increments -- exercises co-14. Kestrel is a fictional product; every quoted number, question, or finding here is an illustrative, constructed example, not real data or a real transcript.

Increment 1 -- one-way announcements: a manager posts a broadcast message ("early close Friday") that every team member sees in-app; no replies yet. Signal: do managers use it at all, and how often?

Increment 2 -- two-way replies: employees can reply to an announcement in a basic threaded view. Signal: do employees actually engage back, or does the channel stay one-way in practice?

Increment 3 -- shift-specific threads: a message thread attaches directly to a specific published shift (e.g., "who can cover this Saturday close?"). Signal: does shift-attached messaging measurably reduce no-show incidents.