Use Cases
In Saint-Gobain businesses, case examples could include mixed reality on the construction site (e.g. Hyperframe), virtual reality for demos on different solutions and their effects on comfort parameters…
You will find some live examples below.
To get started with your own use case, you will need to identify and define a suitable use case. To help this work, below you will find a list of elements of what a poper use case should and should not include. Defining your use case may seem time consuming at first, but doing it correctly will allow you to learn and progress in a meaningful and structured way and thus tends to pay off as the project goes forward. Don’t forget to check out our Toolkit once you decide to launch your project!
What is a use case?
Included
- Persona - who is using the app, what pains and gains do they have
- What the user wants to do - what are the problems that can be solved?
- The user’s goal - What does the user of the app aim to achieve?
- The steps the user takes to accomplish a particular task - The user journey
- How the app should respond to an action - What happens, when the user clicks, waves or does different actions?
Excluded
- Technical specification for implementation - Technical specs might be necessary but are not part of a use case
- Details about the user interfaces or similar - There may be many ways to to run the use case
