Skip the Tools, Make the Outcomes

Designer Luke Wroblewski found that readers of his AI newsroom mostly asked for a report on their question instead of browsing articles, and argues for outcomes before tools.

Software makers have long built tools that people must learn before they get a result. Luke Wroblewski, a product designer, helped build Exposit, a news site whose articles are found, written and edited by AI agents. When Exposit added a feature that compiles a personalised report on any topic a reader asks about, that report quickly became the main way people used the site.

• Wroblewski argues that AI lets a product deliver the result first and offer the tool second, since a tool was only ever a means to an end.
• From the personalised report, Exposit readers could still go deeper into articles, topics and sources.
• On his own website, a feature that answers visitors' questions now also writes a daily summary of his recent thinking. Visitors get something to read without having to ask.
• His test for a team is one question: "are you building another tool, or are you delivering the outcome the tool was supposed to produce?"

A team designing an AI feature can start from the result a user came for and treat the controls that produce it as a second step. Wroblewski's examples are content products, and the wider application is an inference and is not the author's claim.

Derived by Working Surface from the article. Source line: Tool first, outcome second can now (and perhaps should) be flipped on its head.

26 September 2026: when agents can finish whole tasks, teams redesign the work, the checks and the roles around them.