There are many articles about interaction design documents. Many times, reading them may not immediately improve a realm, but we need to continue to practice and summarize and accumulate in combination with projects. Here is a summary based on some design books, design sharing in the industry, and personal experience of doing projects by myself.
1. The Importance of Standardizing Interaction Design Documents
Interaction design document, called DRD (Design Requirement Document).
We know that making a product requires the collaboration of multiple people in the team, and it also has to go through multiple version iterations. In actual work, interaction designers should not only analyze requirements and output interactive drafts, but also cooperate with vision, development, and even testing.
In addition, due to the different rhythm and progress of the project, it is inevitable that the output interactive documents will be different in fineness. Therefore, it is particularly important to output a professional specification and express a clear interaction design document.
What problem does the design specification solve?
Second, the idea of writing interaction design documents
The document cover contains information such as version information and participants.
The purpose of writing interactive documents is to have good upstream and downstream collaboration, so the documents need to be clearly expressed. Documentation includes project background, changelog, design progress, review records, etc. In order to b2b data let the project team know the "historical process" of the design and improve the efficiency of communication.
3.1 Project Background
In the process of version iteration, sometimes human resource allocation (personnel flow or project allocation) will be encountered. If the update log can be recorded in a timely manner and communicated in place, everyone's cooperation will be much smoother.
4. Demand analysis
According to the PRD (Product Requirements Document), the requirements are sorted out, including user research, demand disassembly, competitive product analysis, user experience map, etc. (arranged according to specific projects).
5. Page interaction
Regarding the writing ideas of page interaction prototype documents, common tasks include task flow chart, page flow chart, and information architecture. It needs to be presented in combination with the project scene.
5.1 Task Flow
Before designing, we must first sort out the task flow chart, which is generally the structure of the main process + sub-process, and the drawing software includes Sketch, Axure or other third-party software.