Comment by graypegg

> User stories are useful mostly for "flux-based" applications where the user has little freedom.

I'd say basically only useful for those sorts of applications! If you're going by user stories, there should only really be 1 way of solving any 1 issue, and users should get rail-roaded into it. There's always a solution to problems you've closed user stories for, but that's it. Anything outside those is unconsidered and might not even have a "hackable" solution since you're building everything up organically rather than as a designed system.

Great for start ups (saved time and money building the impactful flows, your product only needs to do a few things) but awful for enterprises (users have no freedom to warp your product to their needs, your product needs some predictable structure/rules they can build on... those composable operations you're mentioning.)