Continuing with our example application we can determine the following

[sujonkumar6300]

Below is an example of how we could fill out the form for an inventory control application. I will put one or two values ​​in each field, but in practice more can be put.

Problem Supposed: Users are unable to complete the process of creating a report, due to complicated flow and inconsistent design patterns.

Hard data: 60 monthly support tickets are received requesting help to generate reports.

Outstanding Questions: What specific part of the reporting process are afghanistan consumer email list users having difficulty with?

Ideal scenario
Here we describe what the application and/or product would look like ideally, without taking into account limitations. As designers, we often know the solution to these problems in advance, perhaps not its execution in detail, but we do know how to name the medicine that will cure the known evil.


Ideal Scenario: A user is able to identify movements in their inventory and easily generate a monthly or annual report. They can download the report and/or send it to their supervisor or colleagues.

Elements necessary for this ideal scenario to come true:

Consistent design patterns (styles, icons, components, etc.)