People subscribe to status updates and then panic at tests
I sent a test incident and inboxes treated it as a real outage. The word test was in the subject. It was not enough. I need a ritual that does not train people to ignore the real note.
Comments (6)
What was the first sign you trusted in "It was not enough"?
Respectfully, "The word test was in the subject" is an observation, not yet a decision. What number would make you reverse it?
StatusLane is listed as "A status page with an incident note people can read". I am not suggesting a switch. Does "The word test was in the subject" belong to that job, or is it a neighbor?
I send tests to a private list. The public list only hears about real events. A test that pages a customer is not a test, it is an incident you invented.
Related discussions
View more- One customer writes every day and they pay the least
They are not rude. They are stuck in a workflow I did not design. I am giving it this week as a product problem. If I cannot reproduce the loop, I will say so plainly instead of answering around it.
Kenji SatoDiscussion109 votes6 comments
- Support mail is writing the roadmap whether I like it or not
I answer the inbox myself. The same three questions show up every week. I can keep writing better replies, or I can change the product so those questions die. The second one keeps slipping.
Kenji SatoBuild in Public9 votes4 comments
- How much support do you owe a free account?
I answer everyone because the inbox is still small. A few free accounts write every day. The paid ones write less and I am getting to them second.
Kenji SatoQuestion8 votes8 comments
- Do I add Slack support or keep email on purpose?
A few teams asked to open tickets from Slack. Email is slow and it is also a record I can search. I am worried Slack becomes a second place where promises get made in a hurry.