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 WilsonThe 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.
Tushar Deshmukh on why fluent AI is the dangerous kind, and how to design confidence a person can actually calibrate.
Fluency is not understanding. Pavel Bukengolts on a one-page Decision Brief that keeps AI from inflating confidence.
Ben Reason on evolving the service blueprint into a collaboration space for humans and AI, starting with healthcare and B2B.
Tushar Deshmukh opens Designing the Machine: when the interface acts first, interruption is the safety feature, and one mistake can end the relationship.
Roman Yakovlev on mascot systems for TitanApps and Coupler.io—from Jira-inspired character casts to guidelines, AI workflows, and conference swag.
The haircut was the product. The service was the time in the chair, and the day after.