Discovery is a crucial initial phase in any digital service design process. It aims to understand users’ needs, the context of the service, and the problem to be solved. It’s not about creating solutions but about defining the problem. Discovery involves researching, gathering data, and understanding the service’s users, their needs, and the environment in which they operate.
The process is not linear and can be repeated as needed. It includes various activities such as stakeholder interviews, user research, data analysis, and market research. These activities help identify the service’s users, their needs, and how the service can meet those needs.
The discovery phase is not about delivering a finished product. It does not focus on solution design or implementation. Instead, it is about understanding the problem and defining it clearly. The outcome of discovery is a well-defined problem statement, a clear understanding of users and their needs, and a list of potential opportunities for service improvement.
The discovery phase concludes with a decision on whether to proceed with the next phase, alpha. This decision is based on the evidence gathered during discovery and whether it indicates a need for a new or improved service.
It’s vital to remember that the discovery phase is not a one-off process. It can be revisited as needed throughout the service design process to ensure the service continues to meet user needs.
Go to source article: https://ausdto.github.io/discovery-guide/1-introduction/