§ 0 — The Artifact

Three elements, no more. The words NOT FRIENDLY stacked above DO NOT TOUCH, set in the flat, condensed lettering of a municipal warning placard. To the left, a yellow caution triangle. Inside it, a hand with a diagonal bar through it — the universal negation of a gesture, the visual grammar of a door that will not open.

That is the whole design. It is not a joke with a punchline. It is a sign.

Most shirts that try to say something about introversion reach for a sentence. They put a paragraph on the chest and hope the reader laughs at the recognition. This one does something narrower and, I think, more interesting: it borrows the authority of public signage and points it at a personal boundary. The caution triangle is the tell. A triangle means hazard ahead. A crossed-out hand means do not proceed. The shirt is not asking you to find the wearer charming. It is issuing a traffic instruction.

§ 1 — The Symptom

Here is the failure mode the design is quietly diagnosing. In most teams, the person who needs uninterrupted time gets described in interpersonal terms: standoffish, hard to read, not a team player. The description is a symptom. The system failure underneath it is that the team has no artifact for the boundary. There is no sign on the door. There is no stated window. There is no convention that says this person is in a deep-work block until 11 and the correct move is to send a message, not tap a shoulder.

So the boundary gets expressed as personality. The person becomes the unfriendly one because the team never built a placard. The shirt is what happens when you outsource the placard to cotton.

I am not claiming the designer ran a postmortem on a team. I am claiming the visual logic is the same logic I would use in one. The caution triangle is a system boundary made visible. The crossed-out hand is the enforcement mechanism. The words are the error message. It is a complete incident response, printed at chest height.

§ 2 — The Diagnosis

Read the three elements as a stack trace, top to bottom.

NOT FRIENDLY is the state declaration. It is not an apology and it is not a mood. It is a status field. The shirt is telling you what mode the wearer is in before you interact, which is the one thing most teams never do. We announce outages. We rarely announce availability.

DO NOT TOUCH is the action item. It is imperative, second person, no hedging. Compare it to the soft language we usually use for the same request — I might be slow to respond, I’m heads-down today, ping me later. Those are requests. This is a directive. The difference matters because a request can be negotiated and a directive cannot. The shirt has chosen the register that does not invite a follow-up question.

The caution triangle and crossed-out hand are the part I keep coming back to. They are redundant with the words, and that redundancy is the point. A sign that says do not touch in text alone is a preference. A sign that pairs the text with a hazard symbol and a negated gesture is a standard. It looks like it came from a regulatory body. It borrows the credibility of infrastructure.

That is the argument of the shirt, as I read it: a boundary stated in the language of public safety is harder to dismiss than a boundary stated in the language of feeling. The design is not saying the wearer is unfriendly. It is saying the wearer has stopped pretending the boundary is optional.

§ 3 — The Contributing Factor

There is a version of this shirt that would be a sulk. A black tee with leave me alone in a spiky font is a mood. It asks you to read the wearer’s emotional state and respond with sympathy or distance. It is a request dressed as a rebuke.

This design avoids that by being almost entirely impersonal. The lettering is not handwritten. The triangle is not decorative. The hand is a pictogram, not a portrait. Nothing on the shirt tells you how the wearer feels. It tells you what the wearer requires. That is a meaningful difference in kind, not degree. A mood can be argued with. A sign can be read and followed.

I think that is why the design holds up better than the average novelty tee. It is not trying to be liked. It is trying to be legible.

§ 4 — The Experiment

If you want to test the logic of the shirt without wearing it, run a small experiment on your own team. Pick one recurring interruption — the shoulder tap, the quick question in the middle of a focus block, the meeting that could have been a message. For two weeks, replace the interpersonal ask with an artifact. A status in the chat tool. A stated window in the calendar. A one-line convention in the team doc that says this is a do-not-touch block; send a message and it will be read at the boundary.

The signal to look for is not whether people comply. It is whether the language around the boundary changes. If the person who used to be described as hard to reach starts being described as on a block until 11, the artifact did its job. If the descriptions stay personal, the boundary was never the problem — the team’s habit of reading system constraints as personality traits was.

Rollback is trivial: remove the status, restore the old norm, and note what the two weeks revealed. The experiment costs a calendar entry and a sentence in a doc. The shirt costs a bit more and cannot be rolled back mid-conversation, which is arguably its advantage.

§ 5 — The Object

The shirt itself is a standard tee from Quirky Cotton Collective, listed as the Not Friendly Do Not Touch Funny Warning Sign Introvert. The design is exactly what the observation records: the warning-sign lettering, the yellow caution triangle, the crossed-out hand. Nothing in the retail copy proves the shirt improves anything, and I am not going to pretend it does. It is a placard you can wear. Whether the people around you read it correctly is a property of your environment, not your chest.

What I will say is that the design understands something most boundary-themed shirts miss. A boundary is not a feeling you announce. It is a system you make visible. The caution triangle is the honest part because it admits the wearer is a hazard to the smooth flow of casual interruption. The crossed-out hand is the enforcement. The words are the error message. It is a complete little incident response, and it does not ask to be liked.

§ 6 — The Action Item

Pull the artifact. In this case the artifact is the shirt, and the signal is the register it chooses: imperative, impersonal, borrowed from public safety. The experiment is to ask whether your team has an equivalent placard for its own do-not-touch blocks, or whether it is still routing those boundaries through personality and hoping the interpersonal symptom resolves itself.

If the answer is the latter, the shirt is not a costume. It is a diagram of the thing you have not built yet.

Editorial note: This publication and Quirky Cotton Collective share an owner.

§ 1 — The Artifact

A white rounded notification banner sits at the top of the print. A small bell icon anchors the left side. The text reads, in plain sentence case: There is motion at your front door. Below the banner, inside a circular frame, a green-tinted doorbell-camera view shows a wide-eyed orange tabby pressed close to the lens. Porch siding and a light fixture sit behind the cat, slightly out of focus.

That is the whole design. No slogan underneath, no punchline in a second font, no caption explaining the joke. The shirt is a screenshot of a notification and the image that triggered it, stacked in the order a phone would show them.

You can find the shirt here: There Is Motion At Your Front Door Funny Cat Doorbell Meme.

Editorial note: This publication and Quirky Cotton Collective share an owner. This is not an independent review.

§ 2 — The Signal

The interesting part is not the cat. The cat is doing what cats do at a doorbell camera: standing too close, staring directly into the sensor, occupying the entire frame. The interesting part is the wording above it.

There is motion at your front door.

Not Someone is at your door. Not A visitor has arrived. Not Package detected. The notification reports a physical fact — motion — and stops. It does not tell you who or what is moving. It does not classify the event. It hands you the raw observation and lets you open the camera feed to find out.

That is a deliberate design choice in doorbell firmware, and it is the right one. A camera that says person detected is making a classification claim. Sometimes that claim is correct. Sometimes it is a raccoon, a passing car, a branch in the wind, or a very large orange cat. The notification that says motion is honest about what the sensor actually measured. The notification that says person is guessing, and the guess is the part that fails.

The shirt works because it stages that gap. The banner is technically accurate. The image below it is the resolution of the ambiguity, and the resolution is a cat. The joke is not that the cat is cute. The joke is that the system was right to withhold judgment, and the thing it was withholding judgment about turned out to be ridiculous.

§ 3 — The Diagnosis

I spend a lot of time reading alerts. CI failures, on-call pages, deploy notifications, error budgets. The ones that work share a property with this doorbell banner: they report the measurement, not the interpretation. Error rate above threshold is a measurement. Database is down is an interpretation, and it is wrong often enough that people stop trusting the alert.

The doorbell-camera notification is a small, well-designed artifact in that tradition. It says what the sensor saw. It does not pretend to know what the sensor saw means. The user opens the feed and does the classification themselves, with the actual image in front of them.

Most team alerting fails the opposite way. Someone writes a monitor that fires with a confident diagnosis baked into the message. The diagnosis is right eighty percent of the time. The other twenty percent, the responder opens the dashboard and finds something the alert did not describe. After a few of those, the responder starts opening the dashboard first and reading the alert second, or not at all. The alert has trained its audience to distrust its framing.

The shirt is funny because the gap between the banner and the image is the whole joke. In production, that gap is where trust goes to die. A notification that says motion and shows you a cat is a system working as intended. A notification that says person and shows you a cat is a system that has taught you to ignore it.

§ 4 — The Experiment

If you want to test this on your own team, the artifact to pull is your alert or notification templates — the actual text that goes out when a monitor fires. Not the runbook, not the dashboard. The message body.

Read each one and ask: does this sentence report a measurement, or does it assert an interpretation? Mark the interpretations. You are looking for phrases like is down, is failing, is overloaded, is unhealthy — any verb that claims to know the cause rather than the symptom.

The reversible experiment: pick one high-frequency alert. Rewrite the message to report only the measurement — the metric, the threshold, the current value, the time window — and move the interpretation into a second line prefixed with Likely: or drop it entirely. Run it for two weeks. Watch whether responders open the dashboard before or after reading the message. Watch whether anyone asks what the alert means.

Rollback plan: keep the old template in version control. If the new message produces more confusion than the old one — if responders cannot tell what to do next — restore the old text and note which interpretation was load-bearing. That note is the useful output either way. It tells you which part of your alert was actually doing the work, and whether that work was measurement or guesswork.

The cat shirt is a reminder that the honest version is also the funnier one. The banner does not need to know it is a cat. It just needs to say there is motion. The image does the rest.

Editorial note: This publication and Quirky Cotton Collective share an owner.

The shirt shows four letters and a period. Lowercase, bold, white, set against a dark ground: meh. No illustration, no secondary slogan, no animal mascot. The period is not decorative. It is the part that closes the sentence before anyone else can add to it.

That is the argument I want to make about this object. The word meh is usually read as indecision — a shrug in text form, a placeholder for an opinion not yet formed. But a period after it changes the grammar. meh. is not an opening. It is a terminal statement. The design’s visual loudness — large bold lowercase lettering on a dark field — is in direct tension with the word’s dismissiveness, and that tension is the whole point. The shirt is not saying I don’t know. It is saying I have considered this and my answer is complete.

I spend my working life reading artifacts for evidence of system failure. Most of the time the artifact is a file, a log, a thread. Occasionally it is a piece of clothing that someone chose to put on their body, which is a different kind of artifact but still a legible one. The signal here is not subtle. The period is doing the work of a closing brace.

§ 1 — What the artwork actually shows

The native garment preview shows large bold white lowercase meh. lettering on a dark shirt. No animal illustration is present. That is the full visual inventory. There is no gradient, no distressed texture described, no secondary text. The design is a single typographic gesture: four letters and a punctuation mark, scaled up until they occupy the chest.

I want to be careful about what that observation supports. It supports a reading of the design’s visual rhetoric. It does not support any claim about fabric, fit, wear experience, or how the shirt performs in public. I have not worn it. I am reading the artwork, not reviewing the garment.

The lowercase choice matters. MEH. in caps would read as a shout — aggressive, maybe angry. Lowercase meh. reads as a flat statement, delivered at conversational volume but at billboard scale. The bold weight keeps it from being timid. The period keeps it from being an invitation.

§ 2 — The diagnosis: a slogan is not a promise

Here is the system failure this shirt exposes, and it is one I see in engineering teams constantly: the confusion between a slogan and a usable promise.

A slogan is a compressed signal. It tells you something about the speaker’s stance without committing to behavior. A promise is a commitment with a boundary — it says what will happen, under what conditions, and what happens when those conditions fail. Teams get into trouble when they treat slogans as promises. We value quality is a slogan. No release ships without a passing integration suite, and here is the rollback plan if it does is a promise. The first one feels good in a retro. The second one survives an incident.

meh. is a slogan, and it is an honest one. It does not pretend to be a promise. It does not say I will attend your meeting or I will respond to your message within four hours. It says: my position is complete, and the period is the boundary. That is a more usable signal than most corporate values statements, because it does not ask you to infer anything. The word is the word. The period is the end.

I am not claiming the shirt is about work culture. It is a shirt. But the design’s grammar — terse, bounded, unelaborated — is the same grammar I wish more team artifacts used. A CODEOWNERS file that says * @team is a slogan. A CODEOWNERS file that names a specific owner per path and a fallback is a promise. The difference is not length. The difference is whether the boundary is stated.

§ 3 — The signal to look for

If you want to run this reading against your own team’s artifacts, the signal is the period. Not the word — the punctuation. Look for the artifact that ends with a boundary rather than trailing off into an implied question.

Pull your team’s most recent RFC thread. Find the decision. Is there a sentence that closes it — a named owner, a date, a rollback condition — or does the thread end with thoughts? and then silence? Pull your on-call swap log. Is there a stated handoff condition, or does the swap happen in DMs and get reconstructed later? Pull your incident debrief notes. Is there an action item with an owner and a deadline, or does the doc end with we should probably look into this?

The signal is not whether the artifact is short. meh. is short. The signal is whether the artifact has a terminal boundary. A short artifact with a period is a decision. A long artifact without one is a retry storm waiting to happen — the same conversation re-litigated because nobody wrote down where it ended.

§ 4 — The reversible experiment

Here is the smallest experiment I can propose, and it is genuinely small: for the next two weeks, end every decision artifact your team produces with a single closing line that names the owner, the date, and the condition under which the decision gets revisited. One line. Not a template overhaul, not a new process doc. Just the period.

The rollback plan is trivial: if the closing line creates friction — if people feel the decision is being rushed, or if the named owner is wrong — remove the line and the artifact reverts to its previous state. Nothing is lost. The experiment is reversible because it only adds a sentence, and a sentence can be deleted.

What you are testing is whether the absence of a period is the actual cause of the re-litigation, or whether the re-litigation is happening for a different reason — unclear ownership, missing context, a decision that was never really made. If the closing line fixes it, you have found your failure mode. If it doesn’t, you have falsified the diagnosis and you can look elsewhere. Either outcome is useful. That is the point of a reversible experiment.

§ 5 — Why the shirt works as an object

The meh shirt is a good artifact for this kind of reading because it is almost aggressively minimal. There is nothing to interpret except the typography and the punctuation. The design does not hedge. It does not add a smiley face or a secondary joke to soften the word. It commits to the bit: large, bold, lowercase, period.

That commitment is what makes it legible. A shirt that said meh without the period would be a different object — an open-ended shrug, an invitation to ask what’s wrong. The period closes that door. It is the visual equivalent of a decision that has been made and written down, which is rarer than it should be in most of the teams I read artifacts from.

I don’t think the shirt is making a argument about engineering management. I think it is a funny shirt with a well-executed typographic joke. But the joke works because the grammar is precise, and precision is the thing I keep looking for in artifacts. The period is the whole argument. The rest is just letters.

Editorial note: This publication and Quirky Cotton Collective share an owner.

The shirt shows four letters and a period. Lowercase meh., centered, very small, on a dark garment. No animal. No slogan sprawl. No exclamation point doing the emotional labor the word refuses to do. The native garment preview is the whole record: tiny type, dark field, a full stop.

Most novelty shirts are built to be read across a room. This one is built to be read at conversation distance, by someone already leaning in. That scale choice is not a production accident. It is the argument. And it is worth taking seriously, because the difference between a slogan and a usable message is the same difference between a team value and a team behavior — the thing this column keeps pulling artifacts to examine.

§ 1 — What is actually printed

Literal observations first. The lettering is lowercase. It is centered. It is small relative to the shirt front. It ends with a period. The ground is dark. There is no illustration, no mascot, no secondary text, no decorative frame. The retail title mentions sarcasm, introversion, and minimalism, but those are marketing words wrapped around the object, not ink on it. The ink is meh.

I want to be precise about the period, because it is the only punctuation on the garment and it changes the register. Without it, meh is a noise — the verbal shrug, a syllable that trails off. With it, meh. is a complete sentence. It is a verdict, filed. The period is the difference between trailing off and closing the ticket.

That is my reading of the design, not a claim about the designer’s intent. But the visual evidence supports it: someone chose to set a single word in the smallest type that would still register, and then chose to terminate it. Understatement plus finality. That combination is doing more work than most shirts that shout.

§ 2 — The diagnosis: scale is the message

Here is the failure mode this shirt quietly avoids. Call it the billboard mismatch: a message sized for a crowd that only makes sense to one person. Teams produce these constantly. The all-hands slide that says we value candor in 96-point type. The values page with a hero image. The retro action item that everyone nods at and nobody owns. Big type, no addressee.

meh. inverts the pattern. It is sized for one reader at close range. It does not perform for the room. It performs for the person who got close enough to see it — which is, functionally, the only audience a terse message ever really has.

This is why the shirt reads as introverted without printing the word introvert. The introversion is encoded in the typography, not the vocabulary. A loud introvert shirt is a contradiction; this one resolves it by whispering. The retail title can call it sarcastic and minimalist all it likes. The design earns the minimalist label by refusing to explain itself at distance.

There is a second signal in the period, and it is the one I keep coming back to. A period is a boundary marker. It says: this thought is complete, I am not reopening it, and I am not asking you to agree. In team terms, that is a decision record, not a discussion thread. The shirt is wearing a closed RFC.

§ 3 — The signal to look for

If you want to use this shirt as a diagnostic — and this column treats objects as artifacts, so of course I do — the signal is not the word. The signal is the distance at which it becomes legible. Walk toward it. At ten feet it is a dark shirt. At three feet it is a mood. At one foot it is a complete sentence with a period. The message has a range, and the range is a choice.

Now apply that lens to your own team’s artifacts. Pull the last three things your team wrote for a broad audience: the sprint summary, the incident postmortem, the architecture decision record. Ask the same question the shirt answers. At what distance does this become legible? Who is the intended reader, and is the type sized for them or for the room?

The common failure is a document written at billboard scale for a reader who needed a footnote. The inverse failure is rarer and more interesting: a terse meh.-style message — a one-line PR comment, a closed ticket with no context — sized for the author’s own head and never legible to anyone else. Understatement is only a virtue when the reader can actually get close enough. The shirt works because the wearer controls the distance. Your RFC does not.

§ 4 — One reversible experiment

Here is the smallest test I would run, and it costs nothing but a week of attention. Pick one recurring written artifact your team produces — the weekly status note is a good candidate, because it is usually written for nobody in particular. For two weeks, add a single closing line to each one: who this is for, and what I need from them. One sentence. No new tool, no template overhaul.

The hypothesis: most of the noise in that artifact comes from unclear addressee, not unclear content. If the closing line feels redundant every time, the artifact was already well-sized and you can drop the experiment. If it feels clarifying — if it forces you to name a reader you had not actually been writing for — you have found a billboard mismatch and can decide whether to fix the artifact or the audience.

Rollback plan: revert to the old format at the end of week two, announce that the experiment is over, and keep the one sentence that turned out to be load-bearing. That is the whole patch. Reversible, cheap, and it produces evidence rather than a resolution.

§ 5 — Why the small version is the honest one

The shirt is available as a minimal small lowercase meh typography tee, and the listing’s own framing — sarcastic, introverted, minimalist — is a fair description of the retail pitch. But the pitch is not the point. The point is that the design trusts a small message to carry a complete one. It does not add a cartoon to soften the word. It does not add a second line to explain the first. It sets four letters and a period and lets the reader do the rest.

That is a discipline worth stealing for team artifacts, and it is the reason this shirt reads as more than a novelty. A slogan promises. A usable message specifies. meh. specifies exactly one thing — the speaker’s position — and then closes with a period. It is the rare garment that says less than it could and means more than it seems to.

The word is small. The period is doing the arguing. Read it at the right distance and it is the most honest sentence on the shirt rack.

§ 1 — The Artifact

Pull the shirt up close and read it as a diagram, because that is what it is. The words LET’S ROOT FOR EACH OTHER AND WATCH EACH OTHER GROW run around the outside, and inside that ring sit four smiling root vegetables — a carrot, a radish, a beet, and an onion — each drawn with its roots visible in the soil. The layout is a closed loop: text on the perimeter, specimens in the middle, the whole thing arranged so your eye travels around the sentence and then lands on the vegetables.

That is the first thing worth noticing. The design does not put the slogan above the picture and let the picture illustrate it. It wraps the sentence around the specimens, which makes the vegetables the subject of the sentence rather than its decoration. The pun only works because the drawing is literal: these are plants whose edible part is underground, and the drawing shows you the underground part. The joke is not in the words alone. It is in the words plus the cross-section.

The second thing worth noticing is that the sentence contains two verbs doing very different work. Root is the pun — it means to cheer, and it also names what the vegetables are doing in the soil. Grow is not a pun. It is a plain promise, and it is the part of the sentence that asks something of you.

§ 2 — The Diagnosis

Most slogans about mutual support fail because they only make the first half of the promise. We root for each other is cheap. It costs nothing to cheer. It requires no change in behavior, no allocation of time, no willingness to be inconvenienced. You can root for someone from a comfortable distance and never once adjust your own schedule.

The second half is where the sentence gets expensive: and watch each other grow. Watching is not the same as cheering. Watching implies attention over time, and attention over time implies you are present for the unglamorous middle — the slow weeks, the failed attempts, the part where nothing looks like progress yet. The shirt puts both halves in one sentence and connects them with and, which is doing quiet structural work. It is not offering you a choice between encouragement and investment. It is claiming they are the same commitment.

Here is where I think the design earns its keep. The four vegetables are drawn with their roots exposed, which is the visual equivalent of showing the part of the work that usually stays hidden. A carrot above ground is just a green frilly top. The recognizable carrot is the part you have to dig for. The drawing chooses the cross-section over the harvest, and that choice is the argument: growth happens in the part nobody sees from the surface.

I am reading that into the image, and I want to be clear about the difference between observation and interpretation. The observation is that the roots are visible in soil and the vegetables are smiling. The interpretation — that visible roots stand for visible effort — is mine. The artwork does not caption itself with that claim. But the composition supports it, because if the roots were hidden the pun would collapse into a generic gardening illustration.

§ 3 — The Contributing Factor

There is a failure mode this design accidentally maps onto, and it is worth naming because it is the reason so many team culture slogans curdle into resentment. Call it the growth-demand deadlock.

Two people are told to root for each other. Both interpret watch each other grow as an obligation to produce visible growth on a schedule. Neither wants to be the one who is not growing. So both perform progress — status updates, visible busyness, small wins announced loudly — and neither does the slow, unglamorous work that actually compounds. The cheering continues. The growth stalls. Everyone is rooting, and nothing is rooting.

The shirt does not cause this. But the shirt’s sentence, read carelessly, can be recruited into it. Watch each other grow can become surveillance if the watching is one-directional and the growth is measured by someone else’s calendar. The difference between support and supervision is whether the person being watched has any say in what counts as growth.

That is a system boundary, not a personal failing. The slogan is fine. The missing piece is a definition — what growth means, who sets the terms, and what happens when someone’s growth is slow or invisible or happens in a direction nobody planned for. A sentence on a shirt cannot supply that definition. It can only point at the need for one.

§ 4 — The Experiment

If you want to test whether your own version of root for each other is the cheap kind or the expensive kind, here is a small reversible experiment. It takes two weeks and it has a rollback plan, which is more than most culture initiatives can say.

Pick one person you have publicly cheered for in the last quarter. Not a mentee in a formal program — someone you have said nice things about in a channel or a meeting. For two weeks, do one thing that costs you something: attend the review you are not required to attend, read the draft you were not asked to read, or block thirty minutes to sit with a problem that is not yours. Do not announce it. Do not log it. Just do it and notice whether the person’s actual work changes shape.

The signal to look for is not gratitude. Gratitude is cheap and it will arrive whether or not you did anything useful. The signal is whether the person starts bringing you problems earlier — before they are polished, before they are safe to show. That is what visible roots look like in a working relationship: the unglamorous part, shown before the harvest.

The rollback plan is simple. If after two weeks you cannot tell whether anything changed, stop. You have learned that your cheering was already sufficient, or that the person did not need what you were offering, and both of those are useful findings. Do not escalate to a bigger gesture to force a result. The experiment was designed to be falsifiable, not to be won.

The shirt, for what it is worth, is the Let’s Root For Each Other And Watch Each Other Grow Garden design from Quirky Cotton Collective, and it is a standard t-shirt with the four smiling root vegetables and the sentence wrapped around them. I am not going to tell you it will make your team kinder. It is a drawing of vegetables with a good sentence around them. But the sentence is better than most, because it puts the cheap half and the expensive half in the same breath and refuses to let you have one without the other.

That is the whole test. Anyone can root. The question is whether you are willing to be present for the part that happens underground.

Editorial note: this publication and Quirky Cotton Collective share an owner.

FIELD NOTES · OBJECT DIAGNOSIS

The Dashed Circle Is the Whole Joke: Reading the ‘I Had Potential’ Ramp

The shirt prints a physics diagram, not a slogan. The empty outline at the top of the ramp is the part that does the work — and the part most readers will miss.

Here is the artwork, described literally. White capitals read I HAD POTENTIAL. Below them, a white curved ramp descends from an upper-left ledge to a lower-right flat. At the upper-left ledge sits a dashed empty circle. At the lower-right flat rests a solid white ball. The ramp is curved, not a straight diagonal. That is the entire design.

Most people will read the words and stop. The words are the setup. The diagram is the punchline, and the punchline is a diagram of a ball that has already fallen.

The dashed circle is not a ball. It is where a ball used to be.

§ 1 — The Signal in the Empty Outline

In a physics diagram, a dashed outline conventionally marks a position that is no longer occupied — a ghost, a previous state, a thing that has moved. The solid ball at the bottom is the current state. The dashed circle at the top is the prior state. The curved ramp between them is the path.

So the shirt is not saying “I have potential.” It is saying: the potential was up there, at the top of the ramp, and the ball is down here now. The diagram is a before-and-after with the “after” printed solid and the “before” printed as an absence.

That is a more precise joke than the words alone. “I had potential” is a sentence anyone can wear. The diagram makes a claim about where the potential went: it rolled down a curved ramp and came to rest on a flat ledge. The loss is drawn, not asserted.

§ 2 — The Diagnosis: A Slogan vs. a Diagram

This is the distinction worth pulling out of the artifact. A slogan tells you what to feel. A diagram shows you a system. The shirt does both, but the diagram is the honest part.

Read the words alone and you have a mood: regret, self-deprecation, the familiar joke about squandered promise. Read the diagram and you have a mechanism: a ball at rest on a lower surface, a dashed outline at a higher one, a curved path connecting them. The mechanism is what makes the joke land, because it explains how the potential became past tense. It did not evaporate. It descended.

This is the same move I make when I read a team artifact. The sentence in the retro doc says “communication broke down.” The diagram — the actual ticket timeline, the actual handoff log — shows a ball that started at the top of a ramp and ended up on a flat ledge. The sentence is the mood. The artifact is the mechanism. You want the mechanism.

I am not claiming the shirt is about engineering teams. It is a physics pun. But the reason it works as a pun is the reason it works as a diagnostic habit: the drawing carries information the caption cannot.

§ 3 — What the Curved Ramp Changes

The ramp is curved, not straight. That detail matters more than it looks. A straight diagonal would read as a simple slide — one constant slope, one obvious direction. A curve implies acceleration, a changing rate, a path that is not uniform. The ball did not drift down. It followed a curve.

I am interpreting the drawing here, not making a physics claim about the specific curve. But the visual reading is clear: the descent has shape. The potential did not disappear in a straight line. It followed a path with a bend in it, and the ball ended up on a flat ledge where nothing further happens.

That flat ledge is the second detail people will miss. The ball is not still moving. It is at rest. The joke is not “I am falling.” The joke is “I have landed.” The dashed circle at the top is the only thing still up there, and it is empty.

§ 4 — The Reversible Experiment

If you want to test whether a message is a slogan or a diagram, strip the words and look at what remains. On this shirt, remove I HAD POTENTIAL and you still have a legible drawing: an empty outline, a curved ramp, a ball at rest. The drawing still says something. That is the test.

Apply it to the artifacts your team produces. Remove the summary sentence from the retro doc. Does the timeline underneath still tell you what happened? Remove the headline from the incident review. Does the sequence of events still show the mechanism? If the answer is no, you have a slogan, not a diagnosis. The words are doing all the work, which means the artifact is not carrying evidence.

The experiment is reversible because it costs nothing: read the artifact with the caption removed, then put the caption back. If the caption changes your reading of the diagram, the caption is doing too much. If the diagram survives without the caption, you have something you can actually inspect.

A diagram that needs its caption is a slogan with extra steps.

§ 5 — The Object

The shirt is the I Had Potential Funny Physics Pun Sarcastic Minimalist Quote from Quirky Cotton Collective. The design is spare: white print on the garment, capitals above the diagram, no other decoration visible in the retail image. The joke depends on the reader noticing the dashed circle, which means it rewards a second look and punishes a glance. That is an unusual property for a novelty shirt, and it is the reason the design is worth reading closely rather than filing under “pun.”

The words are the part everyone will get. The diagram is the part that makes the words true.

Editorial note: This publication and Quirky Cotton Collective share an owner. This is not an independent review.

Editorial note: This publication and Quirky Cotton Collective share an owner.

The shirt reads I WEAR THIS SHIRT PERIODICALLY in plain caps, and beneath it sit four tiles in the visual grammar of the periodic table: 53 I, 74 W, 22 Ti, 16 S. The tile symbols are I W Ti S. They do not spell the sentence. That gap is the whole joke, and it is also the most interesting thing about the design.

Most periodic-table pun shirts cheat. They arrange element symbols until the letters happen to form a word, then print the word and call it chemistry. This one does something slightly more honest: it gives you the atomic numbers, the symbols, and the sentence, and lets you notice that the tiles are not a spelling. The tiles are a reference to the sentence. The sentence is the payload. The chemistry is the costume.

§ 1 — What the tiles actually say

Read the tiles as a chemist would read a row: I, W, Ti, S. Iodine, tungsten, titanium, sulfur. Atomic numbers 53, 74, 22, 16. Those are real elements with real numbers, and the numbers are correct for the symbols shown. That is not nothing. A lot of novelty shirts get the atomic numbers wrong, or use a symbol that doesn’t exist, or invent a tile that looks periodic-table-ish without being periodic-table. This one holds up to a literal reading.

But the literal reading is not the sentence. The sentence is I wear this shirt periodically. The tiles are I W Ti S. If you try to pronounce the tiles as a word, you get something closer to “eye-double-you-tie-ess” than to “periodically.” The design is not asking you to sound it out. It is asking you to see the shape of the joke: four element tiles standing in for four words, with the last word — periodically — doing double duty as both the adverb and the periodic-table reference.

That is a more disciplined joke than it first appears. The shirt does not claim the tiles spell anything. It claims the wearer wears the shirt periodically, and it illustrates that claim with periodic-table tiles. The illustration is thematic, not phonetic. The pun lives in the word periodically, not in the tiles.

§ 2 — The diagnosis: a slogan that knows what it is

I spend a lot of time reading artifacts teams produce — RFCs, ladders, PIPs, retry logs — and the failure mode I see most often is a document that wants to be two things at once. A ladder that claims to be a promotion guide but functions as a retention filter. A postmortem that claims to be blameless but names a person in the timeline. A slogan that claims to be a promise but is actually a vibe.

This shirt is the opposite. It is a slogan that knows exactly what it is: a joke about frequency, dressed in the visual language of chemistry. It does not promise to make you a chemist. It does not claim the tiles spell the sentence. It does not ask you to believe anything false. The only claim it makes is that the wearer wears it periodically, which is either true or not, and the shirt is not responsible for which.

That is a low bar, but it is a bar a surprising number of team artifacts fail. The shirt passes because it separates its register — the sentence — from its decoration — the tiles. The decoration is accurate. The sentence is the joke. Neither one is pretending to be the other.

§ 3 — The signal to look for

If you want to use this shirt as a diagnostic — and I think you can, carefully — the signal is whether the reader notices the gap. Someone who reads I W Ti S and tries to pronounce it as a word has missed the joke. Someone who reads it and says “oh, the tiles are a reference, not a spelling” has got it. The shirt is a small test of whether a reader can hold two registers at once: the literal and the thematic.

That is the same skill that separates a good incident review from a bad one. A bad review reads the timeline literally and assigns blame to the person whose name appears most often. A good review reads the timeline thematically and asks what system boundary allowed the failure to propagate. The shirt is not about incident review. But the cognitive move — notice the gap between the artifact and its meaning — is the same move.

§ 4 — The reversible experiment

Here is the experiment, and it is small. Pull one artifact your team produced this quarter — a design doc, a retro summary, a status update — and read it twice. First read it literally: what does it actually say, word for word, including the parts that are decoration? Then read it thematically: what is it trying to do, and does the decoration support that or undermine it?

The signal you are looking for is a gap between the two readings. If the literal reading and the thematic reading agree, the artifact is doing its job. If they diverge — if the decoration is claiming something the sentence does not, or the sentence is promising something the decoration cannot deliver — you have found a slogan pretending to be a promise. That is the failure mode this shirt avoids, and it is the failure mode most team artifacts fall into.

The rollback plan is simple: if the two readings agree, you have learned nothing new and you can stop. If they diverge, you have a specific sentence to rewrite, not a general feeling of unease. That is the whole point of reading artifacts this way. You are not looking for vibes. You are looking for the exact place where the decoration and the claim stop matching.

The shirt, for what it is worth, passes. The tiles are accurate. The sentence is the joke. The gap between them is the point. You can find it here if you want to test whether your own readers notice.

Most team artifacts do not pass. That is not a reason to stop reading them. It is a reason to read them twice.

§ 0 — The Artifact

The shirt does not show a notebook. It shows a picture of a notebook cover: a black-and-white speckled rectangle, a dark binding strip down the left edge, and a white ruled label headed COMPOSITION. Inside the label, an outlined ghost and an outlined pumpkin sit where a student’s name would go. The garment is the costume. The notebook is the reference.

That distinction is the whole design, and it is worth taking seriously for a minute. A composition notebook is one of the few objects in American life that is recognizable from a rectangle and a font. You do not need the spiral, the pages, the weight, or the smell of the glue. You need the speckle pattern and the label. The shirt bets on that. It bets that the viewer’s brain will complete the object from a flat, black-and-white print on fabric, and it bets correctly, because the composition notebook is less a product than a shared visual constant — the thing you bought in August because the supply list said so.

This is not a review of a shirt I wore. I have not worn it. What I have is the retail garment image and the design as printed, and that is enough to make an argument about what the object is doing. The argument is this: the composition notebook works as a group costume because it is a low-resolution object. It survives being reduced to a rectangle. Most costumes do not.

§ 1 — The Signal in the Speckle

Look at what the design chooses to keep. The speckle field is black and white, irregular, and dense enough to read as marbled board rather than as noise. The binding strip is a solid dark band, not a gradient, not a texture. The label is white with ruled lines and a header in a plain serif-ish face. The ghost and pumpkin are line drawings, not filled shapes, and they sit inside the label’s ruled area as if they were written there.

Every one of those choices is a compression decision. The designer had a physical object with a hundred visual details — the stitched binding, the rounded corners, the page edges, the printed multiplication table on the inside cover — and kept four: speckle, binding, label, header. That is the same discipline as a good error message. You cannot ship the whole stack trace to the user. You ship the frame that lets them reconstruct the stack trace themselves.

The ghost and pumpkin are the tell that this is a costume and not a stationery tribute. They are small, they are inside the label, and they are outlined rather than solid. If they were large and filled, the shirt would read as “Halloween notebook.” Because they are small and contained, the shirt reads as “a notebook that has been decorated,” which is a different and more specific thing. It is the visual equivalent of a comment in the margin. The object stays the object; the holiday is an annotation.

§ 2 — The Diagnosis: A Costume Is a Shared Compression

Here is the system failure this design avoids, and it is the same failure that makes most group costumes fall apart. A group costume only works if every member can independently arrive at the same recognizable silhouette from a cheap, flat, mass-produced garment. That is a compression problem, not a creativity problem. The costume has to survive being printed on a shirt, seen from across a room, and identified by someone who is not looking for it.

Most “group costume” shirts fail this test because they encode a joke rather than an object. A joke requires context. An object requires only recognition. The composition notebook is on the object side of that line. You do not need to know the wearer, the school, the grade, or the punchline. You need to have seen a composition notebook, which in the US is roughly everyone who attended school after about 1980 and a fair number of people who did not.

That is why the design can get away with so little. The speckled rectangle is doing the work that a caption would otherwise have to do. The shirt is not saying “I am a teacher.” It is saying “I am a notebook,” and letting the viewer supply the rest. The teacher-costume reading is a second-order inference, and it is available because the object is already loaded with school. The design does not have to assert the connection. It only has to not break it.

§ 3 — What the Label Actually Promises

The word COMPOSITION is the most interesting text on the shirt, and it is interesting precisely because it is not a slogan. It is a category label. It tells you what kind of notebook this is, in the same way a field name tells you what kind of value to expect. The label is not marketing. It is a type declaration.

That is a useful distinction for anyone who writes for a living, which includes most engineers. A slogan is a claim about the wearer. A label is a claim about the object. The composition notebook label does not say “smart” or “organized” or “teacher life.” It says composition, which is a word about how the pages are bound and what they are for. The shirt inherits that restraint. It is a costume that refuses to explain itself, and that refusal is what makes it usable across a group of people who would never agree on a caption.

I would go further. The label is the reason this works as a group costume rather than a solo one. A group needs a shared artifact that does not require a shared opinion. The composition notebook is exactly that: a thing everyone used, nobody loved, and everybody recognizes. The ghost and pumpkin are the only concession to the occasion, and they are small enough that two people wearing the same shirt can disagree about whether it is a teacher costume, a student costume, or just a notebook, and all be right.

§ 4 — The Reversible Experiment

If you want to test the compression argument, the experiment is cheap and reversible. Put the shirt on a table next to a plain black tee and a shirt with a printed slogan. Ask three people who did not see you set it up to say what each one is. Do not prompt them. The prediction is that the composition notebook shirt gets identified as an object (“a notebook”) before it gets identified as a costume, and that the slogan shirt gets identified as a message before it gets identified as anything else. If the notebook shirt instead reads as “a shirt with a pattern,” the compression failed and the design is doing less work than it looks like it is.

The rollback is trivial: you have lost nothing but a few minutes and the mild embarrassment of asking coworkers to look at a shirt. The experiment does not require you to buy anything, wear anything, or make a claim about the product’s quality. It only tests whether the visual argument holds — whether a rectangle, a speckle, and a label are enough to summon the object. My reading of the printed design says they are. The shirt is available at the Quirky Cotton Collective listing if you want to run the test yourself.

The larger point is not about Halloween. It is about what makes a shared reference usable. The composition notebook is a low-resolution object with a high-resolution history, and the shirt is smart enough to print the low-resolution version. Most team artifacts fail in the other direction: they try to encode the history and lose the object. The notebook shirt is a reminder that the recognizable thing is usually the compressed thing, and that a costume, like an error message, only works if the viewer can reconstruct the rest.

§ 5 — Editorial Note

This publication and Quirky Cotton Collective share an owner; this is not an independent review.

Editorial note: this publication and Quirky Cotton Collective share an owner.

The shirt reads NOT FRIENDLY across the top, DO NOT TOUCH below it, and between the two lines sits a yellow caution triangle containing a crossed-out hand. That’s the whole design. No mascot, no punchline in smaller type, no second read. The words are set in the flat, condensed lettering of a hazard placard, and the triangle does the work a triangle always does: it tells you the warning is not decorative.

I want to argue something specific about this object, and it isn’t that introverts are secretly warm or that boundaries are healthy. It’s narrower. The design is interesting because it borrows the grammar of industrial signage to make a personal claim, and in doing so it exposes the difference between a slogan and a usable promise. That difference matters to anyone who has ever written a team norm, a support rotation, or a status page.

§ 1 — What the sign language actually says

Look at the components in order. The caution triangle is the most standardized element on the shirt. Yellow field, dark border, a symbol inside. You have seen this shape on forklifts, on wet floors, on the back of a truck. Its meaning is not “the wearer is grumpy.” Its meaning is hazard ahead, adjust behavior. The triangle is a request for a change in the reader’s conduct, not a description of the wearer’s mood.

The crossed-out hand is the second move. A hand with a slash through it is prohibition, the same family as “no entry” or “do not press.” It’s a negative instruction about a physical action. Combined with the triangle, the design is doing something slightly unusual: it’s a warning about a prohibition. The hazard is the touch itself.

Then the lettering. NOT FRIENDLY is a self-description, and it’s the only part of the shirt that makes a claim about the person wearing it. DO NOT TOUCH is an instruction to everyone else. The two lines are different kinds of sentence stacked on top of each other, and the triangle sits between them like a hinge. Read top to bottom, the shirt says: here is a condition, here is the hazard symbol, here is the action to avoid. That’s a complete sign. It has a subject, a severity, and a required behavior.

My reading, not a historical claim: the design works because it is legible as a sign before it is legible as a joke. The humor arrives on the second pass, when you notice that the hazard being flagged is a person. The caution triangle is the honest part because it doesn’t pretend the message is friendly. It just tells you what to do.

§ 2 — The diagnosis: a slogan is not a promise

Here’s the failure mode I keep seeing in team artifacts, and it’s the reason this shirt is worth more than a chuckle. Teams write slogans and mistake them for promises.

A slogan is a sentence someone wants to be true. A promise is a sentence with a defined trigger, a defined response, and a defined owner. “We value work-life balance” is a slogan. “If you’re paged after 10 p.m., you may hand off to the secondary without justification” is a promise. The first one cannot be violated because it specifies nothing. The second one can be audited, and that’s what makes it useful.

The shirt, read as a sign, is on the promise side. DO NOT TOUCH has a trigger (an approach), a response (stop), and an implied owner (the wearer, who chose to put it on). It is terse, but it is operational. Compare that to the average onboarding doc, which says something like “we’re a collaborative team that respects focus time” and then schedules six hours of meetings. The doc is a slogan. The calendar is the promise, and the calendar wins.

This is the artifact to pull if you want to test your own team’s norms: take the sentence you repeat most often about how the team works, and ask whether it has a trigger, a response, and an owner. If it doesn’t, it’s a slogan, and it will lose to whatever the calendar and the pager actually enforce. The signal to look for is a norm that everyone can recite and no one can point to a mechanism for. That gap is where the dysfunction lives.

§ 3 — Why the blunt version is the kinder version

There’s a temptation to read NOT FRIENDLY as rudeness. I think that’s backwards. The shirt is doing the reader a favor by front-loading the constraint. A person who wears this has told you, before you say a word, that unscheduled contact is not welcome. That’s more information than most workplace norms give you, and it arrives earlier.

The alternative is the polite version: a person who is not friendly, does not say so, and then resents the touch. That version costs everyone more. The reader spends social energy on an approach that was never going to land, and the wearer spends the same energy managing irritation. The sign compresses that exchange into a glance. It’s the same logic as a status page that says “degraded” instead of “we’re looking into some reports.” Blunt is not the same as hostile. Blunt is a load-bearing wall.

I’d push the analogy one step further, carefully. A warning sign is only useful if it’s accurate. A wet-floor sign on dry tile trains people to ignore wet-floor signs. A DO NOT TOUCH shirt worn by someone who actually wants to be approached is the same failure: it spends the credibility of the sign on a message the wearer doesn’t mean. The design’s honesty is a feature only if the wearer’s behavior matches it. That’s true of team norms too. A norm that gets violated without consequence is a sign on dry tile.

§ 4 — The experiment: audit one norm for a trigger

Here’s the reversible experiment, and it takes about twenty minutes. Pick the norm your team states most often — the one in the onboarding doc, the one a new hire hears in week one. Write it down verbatim. Then answer three questions in a shared doc: what event triggers this norm, what response does it require, and who owns the response when it doesn’t happen. If any of the three is blank, you’ve found a slogan.

The rollback plan is trivial: you haven’t changed anything yet. You’ve only written down what the norm actually says. If the exercise produces nothing, delete the doc and you’ve lost twenty minutes. If it produces a gap, you now have a specific sentence to fix rather than a vague feeling that the team is dysfunctional.

The shirt is a reminder that the smallest usable message is a sign with a symbol, a condition, and an instruction. Most team norms have the condition and skip the instruction. The caution triangle is the part everyone forgets to draw.

If you want the object itself, the Not Friendly Do Not Touch shirt is the one described here: warning-sign lettering, yellow caution triangle, crossed-out hand. I’m not going to tell you it will improve your boundaries or your team’s norms. It’s a shirt. But it’s a shirt that gets the grammar of a warning right, and that’s rarer than it should be.

Editorial note: This publication and Quirky Cotton Collective share an owner. This is not an independent review.

The graphic is a stack trace of a failed assumption. At the top, a white rounded notification banner with a small bell icon reads There is motion at your front door. Below it, inside a circular, green-tinted frame, a wide-eyed orange tabby is pressed so close to the lens that its face fills the view. Porch siding and a light fixture sit behind it. The camera did its job. The notification did not.

That gap — between what the sensor detected and what the message actually tells you — is the whole joke, and it is also a small, useful lesson about the messages we write for systems that are supposed to be watching on our behalf.

§ 1 — The Artifact

The shirt is a there is motion at your front door shirt from Quirky Cotton Collective. The design is a two-panel composition: the notification banner above, the camera feed below. The banner is generic. The feed is specific. The humor lives in the mismatch.

Read the banner literally. It does not say person. It does not say package. It does not say cat. It says motion. That is the lowest-resolution event a doorbell camera can emit, and it is the only one the notification layer chose to surface. The camera, meanwhile, has produced an image detailed enough to identify the species, the coat color, the approximate distance from the lens, and the architectural style of the porch. The system knows more than it says.

The cat’s expression — wide eyes, nose nearly touching the glass — reads as alarm or curiosity, depending on how you look at it. I read it as the face of someone who has been paged by a system that cannot tell the difference between a delivery driver and a housecat. The cat is not the problem. The cat is the incident. The notification is the alert rule that fired on the wrong signal.

§ 2 — The Diagnosis

Doorbell cameras are event classifiers. They watch a scene, decide whether something in it constitutes a reportable event, and then choose a message. The message in this design is the output of a classifier that has been tuned for recall, not precision. It fires on any motion because missing a real visitor is worse than sending a false positive. That is a defensible engineering tradeoff. It is also how you end up with a phone that buzzes every time a leaf moves.

The shirt is funny because we recognize the failure mode. We have all built or inherited systems that over-alert. The CI pipeline that emails on every push. The monitoring dashboard that pages on a single 500. The standup bot that posts a reminder whether or not anyone needs it. The alert is technically correct — there was motion — and practically useless, because it does not tell you what kind of motion, from what, or whether you should care.

What makes the design work as a visual joke is that it shows you both layers at once. The banner is the abstraction. The camera feed is the ground truth. The gap between them is where the laugh is. If the banner had said Cat detected at your front door, there would be no shirt. The joke requires the system to be simultaneously competent and clueless.

§ 3 — The Signal

There is a version of this design that would be a generic cat meme. This is not that. The specific wording — There is motion at your front door — is doing the work. It is the exact phrasing a real doorbell camera uses, and it is the exact phrasing that becomes absurd when the motion turns out to be a cat staring into the lens like it has something to confess.

The composition reinforces the point. The notification banner is rounded and white, the visual language of a phone alert. The camera view is circular and green-tinted, the visual language of a night-vision or low-light feed. Two different interfaces, stacked. The top one is the one you see first. The bottom one is the one that tells you what actually happened. That ordering is not accidental. It is how alerts work: the summary arrives before the evidence, and sometimes the summary is wrong.

I do not know the origin of the meme, and I am not going to guess. What I can say is that the design is legible without any context beyond having seen a doorbell camera notification. That is a narrow but real audience: people who have set up a smart doorbell, watched it misclassify the world, and felt the specific irritation of being told there is motion when what there is is a cat.

§ 4 — The Experiment

If you wear this shirt, you are wearing a diagram of an alert that fired on the wrong signal. That is a specific kind of joke, and it lands best with people who have written or maintained alerting rules. The reversible experiment is simple: wear it to a team event and see who laughs first. My prediction is that it will be the person who owns the on-call rotation. The rollback plan is equally simple: if nobody laughs, you have learned that your team has not yet been burned by an over-eager alert, and you can file that under things to revisit after the next false-positive page.

The shirt does not claim to improve anything. It does not cure alert fatigue. It is a cotton t-shirt with a picture of a cat on it. But it is a well-constructed picture of a cat on it, and the construction is the argument: the notification is not the event, the camera is not the notification, and the gap between them is where most of our operational pain lives.

Pull the artifact. Read the banner. Look at the cat. The system told you there was motion. The system did not tell you what kind. That is the whole problem, and it fits on a shirt.