User stories look clean on the page. “As a [user], I want to [do something], so that [I get value].” They create the sense that the problem is understood. That the user is known. That the work ahead is mostly execution. Then you start building. And somewhere along the way, the story starts to thin out. The “user” turns out to be a composite. The “want” reflects a mix of requests, not a clear job. The “value” is directionally right but not specific enough to guide tradeoffs. W