§ 1 — The Artifact
Pull up the garment image and look at the rectangle before you read the title. A black-and-white speckled field, a dark binding strip down the left edge, and a white ruled label headed COMPOSITION. Inside the label, an outlined ghost and a pumpkin. That is the whole design. The shirt is not a notebook; it is a printed picture of one, worn on a body. The costume works because the object is already a costume in the culture: the marble-cover composition book is the most recognizable school supply in the United States, and it carries a specific set of associations — cheap, durable, ruled, handed out in August, filled with things that are not quite right yet.
The retail title calls it a Composition Notebook Costume Teacher Group Halloween. The word costume is doing real work there. A costume is a sign system that depends on the audience already knowing the referent. You do not explain a ghost costume. You do not explain a composition notebook. The design bets that the viewer has held one, written in one, or watched a teacher write on the board with one open on the desk. That bet is the entire mechanism, and it is worth examining because it is the same bet every internal artifact makes: that the reader already knows what the object is for.
§ 2 — The Signal
Here is the observation that matters for anyone who builds things other people have to read: the design does not draw a notebook. It draws the cover of a notebook, cropped to a rectangle, with the label placed where the label actually sits. The speckle is not decorative noise; it is the specific mottled pattern of the marbleized cover stock. The binding strip is on the left, not centered. The label is ruled, not blank. The ghost and pumpkin are inside the label, not floating on the speckle. Every one of those choices is a fidelity claim, and the fidelity is what makes the joke land. If the label were centered, the object would read as a generic school graphic. Because it is offset and ruled and headed with the right word, it reads as that notebook.
This is the difference between a slogan and a usable promise. A slogan says teacher Halloween and stops. A usable promise reproduces enough of the object that the viewer can complete the reference without being told. The design trusts the viewer. That trust is the signal I would look for in any artifact a team produces: does it reproduce the structure of the thing it claims to represent, or does it merely name it? A runbook that says restart the service is a slogan. A runbook that shows the exact command, the expected output, and the failure mode is a composition notebook cover — it gives you enough of the object to recognize it under pressure.
§ 3 — The Diagnosis
The failure mode this design avoids is the one I see most often in internal documentation and team rituals: the artifact assumes the reader is already inside the context, then blames the reader when they are not. The composition notebook cover does the opposite. It assumes the reader has seen the object, and it reproduces the object faithfully enough that the assumption holds. The ghost and pumpkin are the only invented elements, and they are placed inside the label where a student would write their name — which is to say, the design puts the Halloween joke exactly where the personal identification would go. That is a small, precise piece of system thinking. The costume is not the ghost. The costume is the notebook, and the ghost is the name tag.
I am not going to claim this shirt improves anything, cures anything, or demonstrates a software result. It is a printed garment. But the design logic is legible, and the logic is the same one that separates a useful postmortem from a blame document: reproduce the structure, place the annotation where the structure expects it, and trust the reader to complete the reference. The shirt is available as a composition notebook shirt if you want to inspect the artwork yourself; the listing image is the primary evidence, and the rest is my reading of it.
§ 4 — The Experiment
One reversible experiment, and it is not about the shirt. Pick the artifact your team reads most often under time pressure — the on-call runbook, the incident template, the deploy checklist. Compare it to this design. Does it reproduce the structure of the thing it represents, with the annotation placed where the structure expects it? Or does it name the thing and assume the reader already knows the rest? If it names without reproducing, rewrite one section to include the exact command, the expected output, and the failure mode, then watch whether the next reader still asks the question the section was supposed to answer. Rollback plan: keep the old version in git, and if the new section produces more confusion than the old one, revert it and note why in the commit message. The experiment costs an hour and tells you whether your artifact trusts its reader. The composition notebook cover already passed that test. Your runbook has not.
Editorial note: This publication and Quirky Cotton Collective share an owner. This is not an independent review.