The notification banner is white, rounded, and carries a small bell icon. The text inside it reads: There is motion at your front door. Below the banner, inside a circular, green-tinted frame, an orange tabby stares directly into the lens. Its eyes are wide. The porch siding and lights behind it are slightly warped by the camera’s field of view. The cat is close enough that the frame crops its ears.
That is the entire design. A system alert and the event that triggered it.
I have spent a lot of time reading status reports and incident channels, and the thing that strikes me about this shirt is not the cat. It is the sentence. There is motion at your front door. It is grammatically complete, factually neutral, and operationally useless. It tells you that something happened. It does not tell you what to do about it. It does not tell you whether the motion is a delivery, a raccoon, a neighbor, or a person who should not be there. It does not tell you whether you care.
This is the default state of most project notifications. A build fails. A ticket moves to blocked. A dependency publishes a new version. A budget line changes. The system detects motion and reports it. The human on the other end is left to reconstruct the meaning.
The shirt is funny because the cat is funny. But the reason it works as an object — the reason it is worth looking at closely rather than just glancing at — is that it captures a specific failure mode in how technical teams communicate. I call it the motion alert: a notification that reports activity without reporting consequence.
What the artwork actually shows
The design is a composite of two visual languages. The top half is a push notification: white card, rounded corners, bell icon, sentence-case text. The bottom half is a doorbell-camera feed: circular crop, green night-vision tint, wide-angle distortion, a subject pressed close to the lens.
The cat is not doing anything dramatic. It is not knocking. It is not holding a package. It is not wearing a costume. It is simply present, and its presence has triggered the sensor. The joke depends on the mismatch between the gravity of the alert and the ordinariness of the cause. The system says motion. The camera shows a cat.
That mismatch is the whole point. The alert is technically accurate. The cat is technically motion. But the alert has no model of what matters. It cannot distinguish between a cat and a courier. It cannot distinguish between a courier and a person testing the door handle. It reports the lowest-level fact it can detect and leaves the interpretation to you.
I am not making a claim about how doorbell cameras work or what they are designed to do. I am reading the artwork. The artwork presents a notification that is precise about the trigger and silent about the response. That is the visual joke, and it is also a recognizable pattern in project communication.
The motion alert as a project failure mode
I have seen this pattern three times in the last two years, and the shape is always the same. A team sets up a notification — a Slack alert, a dashboard, a weekly status email — that fires whenever something changes. The notification is accurate. It is timely. It is also inert, because it does not encode any decision.
Here is a composite artifact from one of those projects. It is a redacted status line from a daily automated report:
STATUS: Pipeline execution completed. 14 tests passed. 2 tests failed. Artifact published to staging. Deployment to production not attempted.
Every sentence is true. The report is generated automatically. It lands in a channel that forty people are in. And it produces no action, because it does not say whether the two failed tests are new, whether they are known flakes, whether the artifact is safe to promote, or who is expected to do what next. It reports motion. It does not report meaning.
The failure mode is not that the notification exists. The failure mode is that the team treats the notification as communication. They believe that because the information is available, the decision is being made. But the decision is not being made. The information is being transmitted. Those are different things.
I have watched a release manager scan that exact status line, nod, and move on. The two failed tests had been failing for six days. Everyone in the channel had seen the line. No one had asked the question the line was implicitly asking: Are we going to production or not?
Why the cat is the right image for this
The cat in the artwork is not a threat. It is not a warning. It is just a cat, and the camera has done its job by detecting it. The humor comes from the gap between the system’s flat announcement and the viewer’s ability to see what the system cannot: that this is fine, that nothing needs to happen, that the motion is benign.
In project work, the gap runs the other way. The system reports motion, and the humans assume someone else has interpreted it. The alert is not benign. It is a failed test, a slipping dependency, a budget line that moved. But because the notification is framed as a neutral fact, it does not trigger the response it should. It becomes background noise. It becomes the status line everyone scrolls past.
The shirt is a joke about a cat. But it is also a diagram of a communication pattern: a system that detects without judging, and a human who receives without acting. The cat is the event. The banner is the alert. The missing piece is the sentence that should come next: Here is what this means, and here is what you should do.
What I do now
When I set up a notification, I ask three questions before I let it fire:
- What decision does this notification support? If the answer is “none,” it is not a notification. It is a log line. Log lines belong in logs, not in channels where they compete with things that require action.
- What is the threshold for action? A failed test is not a decision. Two failed tests that were passing yesterday is a decision. The notification should encode the threshold, not just the event.
- Who is expected to do what, by when? If the notification does not name an owner and a deadline, it is not a notification. It is a motion alert. It will be read, acknowledged, and ignored.
The shirt is available from Quirky Cotton Collective on Amazon if you want the visual joke on a garment. It is a good joke. But the reason I keep looking at it is not the cat. It is the sentence. There is motion at your front door. It is exactly what most project alerts say, and exactly what most project alerts should not.
Editor’s note: This publication and Quirky Cotton Collective share an owner.