Simply put, a user story is a one sentence description on how a user will use use a product. And it starts with “A user must be able to…” For instance, “a user must be able to click the discovery tab to see restaurants around them.” It describes one action – in one flow. Refrain from using “and” inside your one user story. By using “and” you get into too much detail and should probably be separated into another user story. The best approach is to focus on launching a product in the marketplace that has one user story and building more based on that user’s feedback. You can call this frictionless feedback. That’s what I call it anyway. You have to let the end user of your product dictate what you build thereafter – in order to save time and money. When you do that, you’ll build loyalty step by step, story by story.