IMHO users are more describable than “patchwork,” and allowing yourself to believe this is going to be detrimental to your project. It’s probably better to think of users as a power law distribution, where a majority of users find 3 or 4 aspects of the project most important with the rest of the features in the long tail. This type of user behavior is just about everywhere: buying choices, menu items, website eye maps, etc. It is important to know the most often used aspects of the project and to put these out front and easy to use.
But is the user story format the best way to get those common pain points or behaviours out front and centre?
It’s important to know what they are. But the format you use to describe them can change a lot in how you even understand people and what’s going wrong.
And the why is so important in knowing why someone’s dropping out of a journey, not clicking a thing etc