Issue #55

Why Every AI Feature Needs a Named Owner, Not Just a Named Model

sent to 14 subscribers

It's easy to describe an AI feature by which model powers it — "the GPT-based summarizer," "the Claude-powered assistant" — and much rarer for a team to be able to answer, without checking, who actually owns it when something goes wrong. That gap causes more slow-motion damage than most model-quality problems do.

A model name isn't an owner. It doesn't get paged, doesn't decide whether a regression is bad enough to roll back, and doesn't have the context to know whether a weird output is a known limitation or a new failure. When an AI feature ships without a named human owner — not a team name, an actual person whose job includes this feature — the default failure mode is that early warning signs get seen by several people, assumed to be someone else's problem, and never actually investigated until a user complaint forces the issue.

This gets worse, not better, as a feature matures. Early on, the person who built it is still around and still watching it closely out of habit. Six months later, that person has moved to the next project, the feature is "done," and the quiet degradation — a provider's silent model update, a prompt that's drifted out of sync with a UI change, an edge case that's grown from rare to common as usage patterns shifted — has nobody whose job it is to notice.

The fix costs almost nothing and rarely happens anyway: write the owner's name next to the feature in whatever system tracks ownership for everything else your team ships, with the same expectations that come with owning any other piece of production surface — someone to page, someone who reviews the metrics periodically, someone who decides when a change is safe to ship. Treating an AI feature as a special case that doesn't need this, because "it's just a prompt" or "the model handles it," is exactly the reasoning that lets ownership quietly evaporate.

If you can't currently name the person accountable for your most-used AI feature without checking a wiki, that's worth fixing this week, not after the next incident makes the answer obvious the hard way.

← Back to archive