A standing team with named desks
A desk on an org chart isn't real until it has a trigger, a boundary, and a timestamp. Click through four generic desks and see what each one actually shipped last.
A desk on an org chart is a rectangle with a label in it until three more things are true. It fires on something other than a person remembering to click go. It's bounded — a specific list of what it can and can't touch. And it leaves a timestamp: a real, checkable answer to what it did last, without asking the person who set it up. Four generic desks here, kept categorical because the pattern matters more than the project behind it: a watcher checking every thirty seconds, only catching and correcting, never creating; a reviewer that runs before anything merges and can block but not approve its own work; a status board rewriting its own priority table on a timer; an inbox that files and closes but doesn't decide what matters. The desk I trust least is the one whose status a person types by hand — accurate the day it's written, a guess every day after. A board that rewrites its own table is different, not because the information is smarter but because the timestamp means something. Not every desk creates; the watcher's job is noticing another desk's output went missing, fast enough that it doesn't matter, which is why its cadence is the shortest. What none of them can tell you is whether they're still running — a cron job that stops doesn't announce it. A desk is real because it has a schedule, a boundary, and a timestamp that updates without you.