Every era of computing made something cheap. This one made doing cheap.

Each turn of the machine took a kind of work off a person’s hands and left a different kind on them. Here is the arc, and where we think it goes.

  1. Punch cards

    The first machines counted. A person decided everything and fed the machine one card at a time. Computation was scarce. Judgment was the whole job.

  2. Languages

    Then we learned to write instructions a machine could follow. Intent became something you could write down and run again. The first thing to get cheap was repetition.

  3. The personal computer

    A machine on every desk. Work turned into files: the document, the spreadsheet, the folder. Making got cheap. Knowing which file was the one that mattered stayed with the person.

  4. The network

    Then the machines talked to each other. Distance stopped costing anything. Work turned into messages and pages, and for the first time it lived on somebody else’s machine.

  5. The app

    Every job got its own tool, and the phone put dozens in a pocket. Starting got cheap. Keeping up got expensive: fourteen tools, fourteen partial views, and one person carrying what was decided between them.

  6. The cloud

    The tools moved out of the house and were rented back. Running things got cheap. Owning them quietly stopped being an option, one terms of service at a time.

  7. Intelligent machines

    Now the machine drafts, finishes, and comes back with more. Doing got cheap. What didn’t is a person deciding what’s right, and every one of those tools still sends its output to that person.

  8. What’s next

    our bet

    The next turn puts people back where only people are needed, alone and together. One record that every kind of member writes on. Only the calls that are yours reach you, and a group’s calls are settled by its people, with every machine’s part visible and open to overrule. Every judgment is kept, so a thing decided once is never decided again. That is what we are building.

How we keep our own word

When something nearly goes wrong, we say so here: what it was, how it was caught, and what changed.

A guest nearly answered for the owner.

Some decisions in a workspace can only be settled by its owner. While we were building the check that enforces this, our first version asked the wrong question: it let through anyone who counted as a person, and a guest you invite to one room counts as a person. So a guest could have settled a decision meant only for you. It was caught by the separate check we run on every release before it ships, and that version never reached anyone. The check now asks whether the one answering holds the owner’s authority, not what kind of account they have. The same release also closed a place where that rule had never been checked at all.