Do you use User Stories format when appropriate?
Product Backlog Items (PBIs) can be described in the form of a "User Stories" when appropriate. It ensures the developers will know the context for a PBI.
As a [type of User]
I want [some goal]
So that [some reason]
Figure: User Story - template for description
Figure: User Story example in an Azure DevOps PBI
Figure: User Story example in a GitHub Issue
"I want to be able to search for customers."
❌ Figure: Bad example - The user story is too vague and broad in scope
"As a Marketing Manager, I want to be able to search for customers by country and last name, So that I can find their numbers and call customers that are close to me."
✅ Figure: Good example - Clear user story following the [INVEST principle]([https://en.wikipedia.org/wiki/INVEST_(mnemonic)](https://en.wikipedia.org/wiki/INVEST_(mnemonic)))