# Remote teams have no shared past tense > Culture is mostly the memory of things that happened to everyone at once, and a distributed company generates almost none of it by default. What an object is actually doing about that. August 16, 2026 · https://justog.club/stories/remote-team-culture Your company is two years old. Someone asks what it's been like, and you can tell them what you shipped, but you can't point at a day. The Slack archive has four hundred thousand messages in it and not one of them is a memory. You can search it, which is exactly the problem — nobody searches a memory. They just have it, because they were in the room. ## Why does remote culture feel like it isn't happening? Because culture is mostly shared past tense, and remote produces very little of it. The things people mean when they say a company had a culture are almost all *events with dates*. The launch that went wrong. The week everyone was in the same room and something got decided that had been stuck for months. The thing somebody said at the end of a bad quarter that people still repeat. An office manufactures those without anyone trying: proximity plus time, indefinitely. Remote replaces the proximity with a calendar, and a calendar produces meetings. Nobody remembers a meeting. Worth being precise about what this isn't, because the usual diagnosis is wrong. It isn't an engagement problem and the fix isn't more contact — most distributed teams are already over-contacted. What's missing isn't hours together. It's a small number of things that *happened*, that everyone can refer to later without explaining. ## Does swag actually do anything for a remote team? Yes, but not for the reason the industry selling it gives. Search this and you get retention percentages and engagement decks aimed at a people-ops lead at a six-hundred-person company: quarterly kits, vendor catalogues, minimum orders, a budget line. That's a real business and it is not this one. The company reading this is four people, has no people-ops, no budget line, and no use for a branded stress ball. What the object does is give something a date. A box that lands in Denver, Austin and Providence in the same week gets photographed three times in two days, and for about a day the company has a *when*. That's the entire mechanism, and it's the same one an offsite runs on, minus the flights. ### The one number worth keeping The one number the swag industry quotes that's worth keeping is about first days: people who get something physical on day one are close to twice as likely to say they felt like they belonged from the start. Not interesting as an HR metric. Interesting because a first day remote is famously nothing — a laptop shipped from a warehouse and eight intro calls — and a box is the only evidence that you joined something rather than started a subscription. ## What should a remote team actually send? Not a kit. One thing, with a date attached to it. The vendor version is a hoodie, a bottle, socks and a notebook, all carrying the same logo, arriving together. It reads as onboarding paperwork you can wear, and it's interchangeable with the version the company down the street sent — same catalogue, different mark. The version that works is the opposite shape: one garment, one specific thing on it, tied to one specific thing that happened. Then a different one next quarter, because something else happened. ### Which turns the merch into a series That's the part worth planning for. A series is a record. Three years in, someone has five shirts and each one is a year — the launch one, the one from the outage, the one with the customer quote on it, the one nobody outside the company has ever understood. A drawer of those is the closest thing a distributed company has to a wall of photographs. A uniform says where you work. A series says how long you've been here, and what you were there for. Only one of those is worth wearing on a Saturday. ## Do we need someone who can design? No. Say what happened and roughly what it should feel like, and it comes back as several finished directions with a note on how it read you. Nobody on a four-person team has to become a designer for this to exist. What follows is what that expansion is doing on your behalf — worth reading if one of you wants to take the wheel and push a version somewhere specific. ## What makes one look like a company's rather than a vendor's? Mostly restraint about the logo and seriousness about everything else. - **One idea per garment.** The catalogue version stacks a logo, a tagline, a URL and a founding year on one chest because it was priced per print rather than designed. One thing, large or small, is most of the difference in register. - **The specific thing gets drawn as an object**, not described in words. The bug becomes a creature, the codename becomes a crest, the region that went down becomes a map. - **Type is set like a record sleeve rather than a slide.** Naming a genre and a decade moves the result further than any adjective — there's a [whole method for the text side](/stories/text-on-a-shirt-that-works) of this. - **The date is treated as a graphic**, not a footnote. It's the part that makes it a record rather than a slogan. The register to aim at is the one [the founder's shirt](/stories/founders-shirt) uses: quiet, specific, slightly illegible to outsiders. In an office that's a nice-to-have. Remote it's load-bearing, because the shirt is doing the work the hallway used to do. ## When is the right time to send one? When something occurred. That's the whole rule, and it rules out most of the calendar. Shipping the thing that took nine months. A first hire, or a fifth. The week the outage ended. An anniversary of something real rather than of the incorporation date. What doesn't work is sending them *for morale*, on a schedule, with nothing attached — an object arriving for no reason is just laundry, and it teaches people that the next one means nothing either. The one exception is a first day, which is an event by definition, and the one where the box does the most work per dollar. ## How do we actually make them? Design it on [JustOG](/) — upload a mark, or describe the thing that happened and have it drawn. You'll see it on the real garment before ordering, and each piece is made when it's ordered, so five is five and there's no cupboard, no size guessing, and nothing left over from a person who left. Which is also what makes a series possible at all: the second design costs nothing to start, because there was never a first minimum order to earn back. ### One thing to check before planning a drop Check the delivery range against where people actually live. If the plan depends on everyone opening the box in the same week, that's the detail that decides whether it works. Send the first one for something that already happened. There's usually one from this year that nobody has said out loud yet.