Yes! We should have anti-user stories! The only question is; how to index them when writing stories so that they're queried at the right juncture to abandon?
Generally, we accrue these anti-stories as a sort of oral tradition, the classic example of which is "we tried that before, it didn't work." Any [junior] dev worth her salt will, when arriving on a team, start to question all the Chesterton's Fences strewn about the place. That's when we start reciting the anti-epics! Why not codify it?
Admittedly, from my perspective, Chesterton's Fences are technical in nature, but I imagine analogous interactions occur at the product level.
Yep, there's plenty of business process level instances as well. They tend to be in the form of "pointless" meetings or other process steps that people feel are "bureaucratic gatekeeping".
When creating line of business apps these chestertons fences can appear when a product owner does not fully understand the complexity they're supposed to be owning, and they remove / fail to capture critical validation steps in a process for the sake of efficiency.
Generally, we accrue these anti-stories as a sort of oral tradition, the classic example of which is "we tried that before, it didn't work." Any [junior] dev worth her salt will, when arriving on a team, start to question all the Chesterton's Fences strewn about the place. That's when we start reciting the anti-epics! Why not codify it?
Admittedly, from my perspective, Chesterton's Fences are technical in nature, but I imagine analogous interactions occur at the product level.