Notes tagged
notifications
8 notes on notifications. All notes.
Follow-up is a schedule, not a feeling
A follow-up that lives in somebody's memory is not a follow-up. Every conversation ends with a dated next action, or the lead closes with a reason.
Demand letters, reminders, and the buyer who says nobody told him
A construction-linked demand is a document plus a delivery. Most collection disputes are about the second half, and the reconciliation is worse than both.
One WhatsApp number, or one per person
Behind every WhatsApp integration is one decision nobody raises in the meeting: does the message come from the company, or from a person who knows them.
Filed as chatter
A document was waiting on one person's signature, and the request reached them as a line in a digest. Not a training gap. A row in a routing table.
Escalation without shame
Most escalation systems require somebody to name a colleague. That is why they go unused, and why problems reach management only after they are unfixable.
A default is a decision somebody made once
Defaults are set in the abstract, by somebody not thinking about your case, and then apply for years without ever looking like a choice again.
An alert that rings for everything is an alert nobody hears
Priority is the wrong axis, because everybody's work is important. Sort by what the message asks the reader to do, and there are only three answers.
One outage should be one ticket
Systems that raise an alert per symptom flood at exactly the moment attention is scarcest, and the flood is usually one cause wearing many names.