Separate an observation from a remedy
A software idea often arrives as a proposed feature: a dashboard, a shared workspace, an automated reminder. Before considering the feature, it helps to describe the situation that prompted it. What is difficult to do, who encounters the difficulty, and what happens as a result?
An observation and an explanation are different things. A missed handover might be visible; its cause may still be uncertain. Writing them separately leaves room for explanations that a feature list would hide.
Keep the surrounding context
A task rarely exists alone. It may depend on a conversation, an approval, an exception or information held elsewhere. A useful description follows the situation far enough to reveal those dependencies without assuming they all belong in a new application.
Frequency matters as context, too. A rare inconvenience and a repeated obstacle may deserve different responses. This does not require invented measurements. Where frequency is unknown, it is more accurate to say so than to attach a confident estimate.
Leave uncertainty visible
A concise problem statement can include both what seems clear and what still needs checking. The distinction helps prevent a possible explanation from silently becoming a requirement.
Ordinary language is enough: describe the setting, the obstacle and the consequence. A preferred technology can come later, if it becomes relevant.