← Back to digest
Commentary

simonw: when do you use Chat, and when do you use Work?

What's this about?

Simon Willison asked ChatGPT iPhone users a plain question: have you worked out when to use Chat and when to use Work? What do you switch to Work for? Have you made Work the default? The question is the item — a widely-shipped product split that experienced users apparently cannot articulate.

What is the Chat/Work split?

Two modes in the same app: one tuned for conversation and quick answers, one for longer, tool-using, document-producing work. The distinction is clear to whoever designed it and, on this evidence, not clear to users — which is a specific and common product failure. The mode you should pick depends on properties of your *task* that you often don't know until you're partway through it.

Why is it worth noticing?

222 likes, and asked by someone who tracks this space closely
  1. When Willison has to ask, it is reasonable to conclude the affordance isn't communicating.
  2. It rhymes with today's routing-gateway thread: both are about who decides which capability handles a request, and both find that the user is a poor place to put that decision.
  3. Mode switches also carry the handoff cost the Handoff Tax paper measures, which is a reason to prefer defaults over choices.
← dotey's earlier finding: the bottleneck was the JSON