Start with customer handover. The entry pairs “Elena role” with “This week”. That pairing is useful only when it is clear why the context supports the state. A busy team can agree on tasks without agreeing on what matters most. More status messages rarely solve that problem.
Begin with the constraint
Choose a small weekly commitment. Write down the trade-off behind it, then revisit the decision when new information arrives.
Example: Customer handover
The illustrative record contains elena role. Its state is this week. Ask what evidence supports that state, which detail is still uncertain and whether the next person could understand it without reading a separate message thread.
Questions for a working review
- Define the decision the reader needs to make. For customer handover, use “Elena role” as the starting context.
- Find the source behind the example record. For customer handover, use “Elena role” as the starting context.
- Write down the open question before choosing a state. For customer handover, use “Elena role” as the starting context.
A small exercise
Take one recent team operations example from your own process. Write its context without using a status label, then add the label separately. If the two contradict each other, investigate the source before updating the record. Compare the result with “Billing review” in the demonstration to see which distinctions your process needs.
These are planning notes. The specimen is illustrative, and the preview does not process live work.
More practical notes →