When it comes to design, the first thing that comes to mind is usually the final output: glossy screenshots. However, those screens are the tip of the iceberg.
The real process; It progresses through stakeholder interviews, user research, information architecture, wireframes, prototypes and usability testing. Behind every screen there are dozens of decisions and tried alternatives.
Therefore, the question 'what problem are we solving' is as much a part of the pricing and schedule as the question 'how many screens will be designed'. A beautiful display that doesn't solve the right problem is a failed design.
Frequently asked questions
What are the tasks that are not visible in the design project?
Work such as understanding the need, editing content, creating flow, testing prototypes and evaluating feedback are behind the final visual. Their scope should be visible in the proposal and schedule.
Why is it useful to prepare a flow before starting screen drawing?
It shows which step is required, why, and how to complete the user task. It helps to notice missing or unnecessary steps before detailed visual production.
