Table of Content
With the help of field observations, context analyses and conversations with clients, a whole lot of information about the use of a product is collected at the beginning of development, which is relevant for the later stages of development.
However, due to the large amount of data and non-standard data formats (e.g., video or audio tape recordings, interview transcripts), it may be difficult to access the data quickly.
Use cases are a method of presenting the collected information in narrative form, making the interaction between the user and the product, as well as the context of use, easily accessible.
How do use cases work?
In most cases, the description of a use case does not exceed the length of a DIN A4 page. For each different target group and for each different goal that the user pursues with the product, a separate use case is developed that describes the special features.
In order not to influence the design solution, the description of the use cases remains on an abstract level, which above all makes clear the goals, the user group and the context of the use and does not contain any details about the technical solution.
The use cases answer these questions
- What features do my users really need?
- Who are the main users of my product and how do they differ?
- Does the design of my interface support the users in their tasks?
How do use cases work with us?
Let’s find out together whether use cases are the right method for your problem and how a collaboration works in detail. You can find our contact details here.
Not the right method for your question?
In our method assistant we have compiled the most important methods for the most typical questions. Try out the method assistant and find exactly the right method for your question: Click here for the method assistant.
