Five teams. Five countries. One messy chat each.

Launch day. The group chat is doing 40 messages an hour. Somewhere in there, Valeria asked Diego for the final asset pack — and somewhere three screens above that, Diego said yes.

At 16:00 the post goes out with the old price on it. Nobody lied. Diego did say yes — to a version of the ask that changed twice after he stopped reading. The file that shipped was final_final_v3, and the file that was final was v5.

With cami in the chat, the ask became a card while everyone was still typing: one name on it — Diego — one checkpoint, and the v5 link attached to the card instead of drowning eleven messages up. When the price changed, the card changed, and Diego’s own cami told him. Quietly. Once.

Month-end. Jonas needs one approval from Anna to close the books, and Anna approved it — with a thumbs-up, in a DM, nine days ago, somewhere.

Now the auditor is asking who approved the vendor change, and the answer is a screenshot of an emoji. Jonas spends the afternoon scrolling three chats like an archaeologist, and Anna spends it insisting she said yes — which she did. There is just no record that behaves like one.

With cami, Anna’s yes landed on a card: her name, the date, the amount in the brief, the file attached. Month-end stopped being an excavation. When someone asks who approved it, the card answers — and nobody has to defend a thumbs-up in a meeting again.

23:40. Checkout is down. Arjun types “who’s on it?” and gets three thumbs-ups — which is how two people fixed the same bug and nobody restarted the worker.

The postmortem finding was not about code. It was that “who’s on it” got three answers and zero owners, at midnight, in a chat moving too fast to read. Everyone did work. The thing between the work fell on the floor.

With cami, the incident is one card, and the card takes exactly one Accountable. Priya grabbed it, so when Dev jumped in he landed as Responsible with her — not as a second, silent, parallel fix. The worker restart went on the same card as a checkpoint, and it climbed until somebody pressed done.

The packaging supplier said “next week” three weeks ago. Everyone kind of knows. Nobody has said it out loud, because saying it makes it real and the ship date is already ugly.

This is how a factory misses a date: not with a bang, but with a card nobody wants to look at. Rudi raised it in March. It sat there being uncomfortable. Every day it was not handled, it got quietly more expensive.

On cami the card would not sit still. As its checkpoint passed it stopped climbing the queue and did something ruder: it asked Sari to decide. Work it, re-date it, or drop it — in writing, on the board, where the whole team could see the answer. She re-dated it and called a second supplier the same afternoon. Not because anyone nagged. Because the board asked.

Every team already has a cami. Hers is human, her name is Grace, and she is exhausted.

Grace runs ops at a twelve-person agency, which on paper means suppliers and schedules and on reality means being the team’s memory. She sends forty reminders a week. She keeps the real deadline list in her head because the tool nobody updates has the fake one. And she has become — slowly, unfairly — the villain: the one who chases, the one who nags, the reason your Monday starts with three pings.

The dark side of being the reliable one is that the job grows until it is your whole job. cami took the chasing: the board asks now, urgency climbs on its own, and the person who owes an answer hears it from their own assistant — not from Grace. She still runs ops. She just stopped being the alarm clock for eleven other adults.