There are many different forms a user scenario can take, depending on your stage in the design process, the intended audience, team structure, and the individual style of the experience designer.
This is one example of a user scenario, which conforms most closely to what Alan Cooper calls a “context scenario.” In About Face, Cooper’s example of a context scenario is slightly less detailed. He states that “(context scenarios) should not describe product or interaction detail but rather should focus on high-level actions from the user’s perspective.
Of course, in the real world, every project and every team has its own unique identity and needs.
In the case of these user scenarios, a lengthy process of goal setting, persona creation, and ideation had been completed, and the team was looking for a description of the user experience that included some details of the interface itself, in anticipation of the next step in the design process.
This document includes the personas, a summary of each person’s situation, the scenarios, and diagrams of the scenarios. You’ll see that the scenarios have been presented as numbered steps, and each includes a list of the features highlighted in the scenario. This was to make it easier for product managers and developers to discuss the features more easily in meetings.
I consider this example of a user scenario document to be the most detailed format I would use. Any more detail than this, and we’d be in key path scenarios, or even wireframes and use cases.