I love user stories.
They’re a great way to communicate requirements. Combined with epics, user stories tell a product narrative so everyone understand the essence of what they are building, yet don’t restrict creativity.
User stories are an outgrowth of agile methodologies, and are used to state requirements without writing endless pages of documentation. Groups of user stories are called “epics”, and if a user story is too big, it can be broken up into smaller stories for the developers to work with.
While they may not replace high-level product requirement documents in all organizations, they can be used to break those requirements into bite-sized pieces that are easier to digest, understand, and build against.