{"slug":"exemplar-linear","meta":{"title":"What Linear Figured Out","slug":"exemplar-linear","kind":"exemplar","summary":"That software used all day is a keyboard instrument, and that speed comes from removing round trips rather than from optimising them.","problem":"Tools for daily operational work are usually designed for the first-time user — mouse-driven, dialog-heavy, waiting on the server before showing anything. The people who use them for six hours a day pay that tax on every action.","family":["act","edit","find"],"principles":["friction","orientation"],"status":"stable","visibility":"public","related":[{"title":"Command Palette","url":"/patterns/command-palette","summary":"The pattern their whole interaction model is built around."},{"title":"Optimistic Update","url":"/patterns/optimistic-update","summary":"Why their interface feels instant — no round trip is ever waited on."},{"title":"Master–Detail Drawer","url":"/patterns/master-detail-drawer","summary":"Their issue inspector, and its keyboard-driven ceiling."}]},"body":"## The insight\n\n**For daily software, the bottleneck is not the server, it is the round trip\nthrough the interface.** Click a row, wait, open a menu, find the option, click,\nwait, go back. Each step is fast and the sequence is slow, and it repeats\nhundreds of times a day.\n\nTheir answer is to remove the sequence rather than speed up its parts: the\nkeyboard reaches everything, the interface commits before the server replies,\nand the list never has to be re-found because it never went away.\n\n## What is worth stealing\n\n**The palette is the primary interface, not an accelerator bolted on.** Records\nand actions are in one ranked list, ordered by recency, so \"get to the thing\"\nand \"do the thing\" are a single gesture. The product is genuinely faster to\ndrive from the palette than from its own sidebar.\n\n**Optimistic by default, with a loud failure path.** Nothing waits for\nconfirmation of a change the user already decided. That is only acceptable\nbecause the failure case is visible and local — the aggressiveness and the\nhonesty are one design, not two.\n\n**The drawer keeps the queue.** Issues open beside the list, and the keyboard\nmoves between them, so reviewing twelve issues costs twelve keystrokes rather\nthan twenty-four navigations. Crucially the issue also has a real URL and a real\npage, so the drawer never traps anything.\n\n**Selective inline editing.** Title and properties edit in place; anything that\nnotifies people stays an explicit action. That line — composition is inline,\nconsequences are deliberate — is the judgment most products get wrong in one\ndirection or the other.\n\n**Views are views.** Board and list are two renderings of one dataset, switchable,\nwith the grouping attribute chosen by the reader. The board is never the model.\n\n## Where it does not transfer\n\nLinear is used by people who will invest in learning it. A palette-first,\nkeyboard-first product punishes occasional users, and much internal software is\nused monthly by people who will never learn a shortcut. There, the visible\naffordance matters more than the accelerator.\n\nTheir density and restraint with colour also assume a homogeneous, technical\naudience working in a quiet, dark interface. That is a style, not a rule.\n\n## The extraction\n\n\u003e **Design daily software for the second hour, not the first minute.**\n\nThe first-run experience matters, but it happens once. If people will use this\nevery day, count the round trips in the loop they repeat most, and remove them —\nby keyboard, by staying put, and by not waiting for the server to confirm what\nthe person already decided.\n"}