Before you use it
- Use when
- A thread says 'updated requirement' but readers must compare old and new text manually.
Keep this limit in mind
- Keep formal change-control rules where required; a readable delta does not replace approvals or traceability.
Why it matters
State the previous rule, the new rule and why the change matters. For structured data, highlight changed fields rather than resending an unmarked full artifact. Name effective timing and whether previous work must be revised.
Steps
- A reader can identify what changed without diffing two long documents.
An example
'Delivery block: blank → ZM for scope X; effective for Monday load; regenerate batch file only.'
Check your result
A reader can identify what changed without diffing two long documents.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingShow the delta when a requirement changes
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaAttach the source next to the claim it supports
Evidence and sources
CDC clear-communication guidance recommends one obvious main message, placing it early and including a clear action for the audience.
Complex work can require several actions, but the communication still benefits from a dominant purpose.
Description and Examples of Index Items · Core items 1, 2 and 5
CDC guidance recommends lists, chunks and descriptive headings to make information easier to scan and organize.
Very short messages may not need headings; structure should match complexity.
Description and Examples of Index Items · Core items 8 through 10
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.
