What do you hand the machine so it knows what the work is for? Ben Reason and Lavrans Løvlie on the service blueprint as a flight plan—a compression a human can sign, and a hydration an agent can run.
To me, service blueprint is the flight plan.
—Robb WilsonTushar Deshmukh on why a machine’s mistake costs more trust than the same error from a person, and how to design a way back.
A comic cheat sheet of 12 systems tools. Pavel Bukengolts on mapping the loop before the next fix treats a symptom as the cause.
Roger Forsgren on Fritz Haber: the process that feeds billions, and the weapons that came from the same hands.
ShaoTung Lien on agent memory: a saved note only matters if it changes the next decision.
Tushar Deshmukh on interfaces built to sound caring, and what happens when a user can no longer tell warmth from a performance.
The bill is drift, not speed. Pavel Bukengolts on a System Contract that keeps design intent from leaking into the pull request.
The blueprint as a system prompt: automation can free time, but people still have to decide what that time is for.
The haircut was the product. The service was the time in the chair, and the day after.
Five more realizations from Reason, Løvlie, Godin, and Age of Invisible Machines. Each is trivially true, and each invalidates another category of work.
AI sounds equally confident when it is wrong. Part 2 of Designing the Machine on automation bias, fabricated citations, and designing visible uncertainty.
AI can turn incomplete ideas into polished plans that people accept as finished. Pavel Bukengolts on the Decision Brief: three assumptions, a confidence tag, the strongest counterargument, and the smallest safe test.
Service design is established, and AI is exposing the gaps. Ben Reason asks whether an evidence-based blueprint can help leaders govern complex change.
The haircut was the product. The service was the time in the chair, and the day after.