The Engineering of Intent
Inside the rapid evolution of Anthropic's product philosophy
In the early days of Anthropic, the product team was not a department; it was a handful of engineers trying to make sense of a shifting frontier. Dianne Penn joined when the company was still finding its feet, stepping into a role that required more than just managing features. She had to manage the very nature of intelligence. As the first technical product manager, her task was to bridge the gap between raw research and the tools that people actually use. This wasn't about deciding which button to place where; it was about deciding how a model should behave when it encounters a problem it wasn't specifically trained for. The transition from Claude 2 to the current generation represents a shift from building a chatbot to building an agentic partner.
The Eval-Driven Loop
Development at this scale does not rely on intuition. It relies on 'evals'—rigorous, automated tests that measure how a model performs against specific benchmarks. Penn describes a loop where development is driven by these evaluations. You don't just 'release' a model; you iterate through a cycle of testing, identifying failure modes, and refining the training data. This process is what allowed Claude to develop its specific character. It is an iterative refinement of capability, where the goal is to move the needle on reasoning and tool use without breaking the safety guardrails that define the brand.
The success of a model lies in its willingness to push back when a user's request is illogical or harmful.
One of the most interesting developments is the move toward 'computer use' and tool use. We are seeing a transition where the model is no longer just predicting the next word in a sentence, but predicting the next action in a workflow. This requires a different kind of product thinking. You are no longer designing a conversation; you are designing a capability. When Claude can use a browser or write code to solve a geometry problem, the product is no longer the text it produces, but the work it completes.
- The early research phase with a core engineering team
- The transition to model-driven product development
- The expansion into agentic capabilities like Claude Code
- The integration of tool-use and reasoning as core features
The speed of this evolution creates a permanent state of instability. For a product manager, this means the roadmap is never finished. You are building on shifting sands. The challenge is to maintain a coherent product vision while the underlying technology changes every few months. It requires a focus on the fundamental qualities of the model—its reasoning, its reliability, and its utility—rather than just a list of superficial features.
Product management in AI is the art of managing capabilities rather than just features.