Working Surfacelink · 29 Sep · 02
02
A client seen from behind, the back of the head showing, sets a toy-sized painted cabinet on a carpenter's workbench, with the small robot that built it standing beside it, while the carpenter, also seen from behind, unrolls a sheet of drawing paper that is still blank, the whole scene drawn with wide empty margins on every side.
The Product Picnic

LLMs are just normal technology. But tech is just a normal medium.

Pavel Samsonov · 27 September 2026

Company story · prototyping · handoff · After the prototype

Read the original
Takeaway

Product writer Pavel Samsonov argues that AI prototypes tempt teams to skip the first step in making a product: deciding what problem it should solve.

Summary

Pavel Samsonov writes The Product Picnic, a newsletter on UX and product management. He argues that AI tools have made it easier than ever to mistake a working prototype for a valuable product. Drawing on the chatbot pioneer Joseph Weizenbaum, he says that making a computer do something is neither the first nor the most important step in creating value.

Key points
  • Samsonov argues that AI models are "just normal technology", and that treating them as special leads teams to lose sight of what people care about.
  • He quotes a comment by Alexis Logsdon: AI models aim first to give the person prompting an answer, however wrong. Logsdon asks whose job it then is to check assumptions.
  • He praises a guide for business people who commission software. It says to define the business rules first, and warns against handing a developer an AI prototype with the words "build this".
  • He recalls many design workshops in which a problem statement beginning "how might we" ended with "using the power of generative AI". He advises cutting that ending, because a solution written into a vision statement never helps.
Implication

A team that prototypes with AI can write down the business rules before it builds the prototype, and hand them to developers with it. The guide Samsonov quotes is for business people who commission software, so applying it to product and design teams is an inference.

Suggested actions
Product

Write down the business rules a piece of software must follow before prototyping it with AI, and give developers those rules along with the prototype.

Design

Remove any named solution, such as generative AI, from a design workshop's problem statements, so that the team does not choose the answer in advance.

Derived by Working Surface from the article. Source line: Baking a solution into your vision statement will never serve you, in the end.

Source issue

29 September 2026: when AI tools do the making, a team has to keep some of the old steps on purpose.