Face the difficulties: Why is it difficult to communicate with the development - is it technically difficult to handle, or the development feels that this function is unnecessary, or there is a schedule for development, do not want to do it now, and do it later?
Consider whether my function must be done at the current stage: how important is this function, is it acceptable to remove this function, or accept to do this function in a later version. If it must be done, has the scenario been clearly considered, and can the reasons really convince the developers? If not, can my scenario development email list provide other solutions that the client can accept?
The most important aspect of collaboration is communication. Both sides need to be heart-to-heart. But be careful, don't implement the program according to the development plan without considering the actual function because you think it will be troublesome to develop. The basic product principles should still be preserved.
5. The change of the implementation plan means the change of the prototype, which needs to be adjusted repeatedly
Difficulty: Our company's development process is - product confirmation requirements, flow to the UED team, after the interaction design is completed, the product acceptance is passed to the research and development. Then in the process of research and development, it is inevitable that some functions will be suspended or removed or added to lead to modification of the prototype, and if the product experience is not enough, it may be modified repeatedly.
Facing difficulties head-on: It's the same problem as mentioned above, don't care about other people's opinions, this stage is unavoidable, we need to grow up; everyone has their own responsibilities, and their revisions are inevitable.