The interaction description document is an important material for the experience designer to connect with the upstream product manager, executive email list and connect with the downstream UI (such as distinguishing between interaction and UI) and development. Generally, teams only need static interaction documentation, and in some scenarios, executive email list operational interaction demos are also required. Specific needs are based on team or functional needs and flexible processing. Therefore, a sufficiently complete and detailed interaction specification document can reduce communication costs and information asymmetry. 1.
Who needs to read the interaction documentation? 1. Product Manager First of all, the output of cooperation between product managers executive email list of different companies and different teams and interaction designers or UE designers is not fixed. In some companies, the product managers output more carefully and will come out together with executive email list prototypes and descriptions. Looking for interactive meetings is more about discovering possible problems from the experience layer; In some cases for various reasons, it may be that one sentence is given to the interaction, and the interaction needs to be carried out from functional planning, information architecture, and prototype description.
There is also a relatively normal process, which is to engage in PRDs for products, and interactively engage in interactive documents, and the logic between executive email list them can be verified with each other. 2. UI Designer Different company teams, different job titles or different responsibilities, may be UI or visual designers who need to output UI interface executive email list drafts. As the downstream of interaction designers, they sometimes need to intervene in demand communication earlier to avoid possible problems in the later stage. 3. Front-end engineer If the front-end team does not read the interactive documentation, it generally needs to focus on the PRD document.