When giving on-site feedback, put your model and demo together. The screenshots that appear in the demo must be marked in detail, and where improvements need to be made. Show these to the engineer and

When giving on-site feedback, put your model and demo together. The screenshots that appear in the demo must be marked in detail, and where improvements need to be made. Show these to the engineer and explain them. I often include "before/after" screenshots in my feedback and summarize the improvements that need to be made in a list. In this way, both visual and textual engineers can make improvements quickly and carefully. I do more than that. I also grouped the interaction design improvements into separate categories, because the engineers on your team may be good at this or that area - if you want to categorize them, organizing them will make it easier to spread the work. Overall, engineers responded well to the categorization of improvements so they could systematically work on them and check off them once completed. This is outside of my responsibilities, but it saves me a few trips. 4. Real-life chats are great, but chat records cannot be tracked. Many designers I know like to chat privately with a product manager or engineer about design details. This is great and builds team cohesion, but the downside is that there’s no “paper trail.” Unless your team is just you and the engineer, everything must be documented so that the entire team can understand and feedback. So even if you and your engineers bump up on design improvements in private chats, you still have to come back to the table and summarize them immediately in the form of emails or feedback. This will give the team an opportunity to provide feedback and serve as a record of decisions. At the end when everything gets complicated, every decision that is not documented needs to be noted. 5. Have a beer with your engineers Never underestimate the importance of socializing with your team. Get to know them and let them get to know you. If they feel that you treat them not as a skilled worker completing a design, but as a "person", their trust in you will be enhanced. -------------------------------------------------- -------------------------------------------------- ------------------------------- Dear engineers! You didn't realize that the way out of your predicament was so easy, did you? The above is what designers should do to make your life easier. Accordingly, here's what you should do: 1. Never let "no" slip out of your mouth. When a designer is excitedly talking about an idea with an engineer, the latter tells him not to say it before he can elaborate on it - no Nothing can make a designer more frustrated than this! I find that many engineers (especially those I haven't worked with in years) often shoot down design ideas and innovations. Because they feel that those improvements seem "not that important, but require a lot of work." Trust me, designers know you work hard without even taking a break to make small changes. But that’s exactly why teams need designers and engineers. Our mission is to create intuitive, easy-to-use, and creative products that people want to use and keep coming back. Otherwise, the engineers' hard work would be meaningless. Designers will be excited about interesting or creative ideas, but instead of saying "no" outright, try to take a moment to understand why your designer is so fascinated by the idea. You can talk to the designer or another engineer to see if you can find a way to reduce the engineering cost but achieve the same results. Once your designer sees you as an intellectually curious and open-minded collaborator, you'll be more likely to get the design icon you need at 4 a.m. the night before product launch. 2. Excellence is not extra work. It is very important that different areas specialize in different things. A great designer puts detail and a good user experience above all else. These details are important, and they may not be able to clearly articulate their importance, but details can really influence a user’s knee-jerk reaction to a product or feature. Many errors in details may even create the impression that the product is unprofessional or unreliable.On the contrary, an app that has been improved over time can get a stronger emotional response than an app with no bugs but a poor UI. A designer asks an engineer to move an icon three pixels to the left, or to align text in two areas to the same baseline. These changes may seem unimportant—but the combined changes really make a difference. 3. Conduct a comprehensive product review with the designer before release. If your designer has done a good job in the above items, then don’t release a new product feature without giving the designer a chance to review it—— No matter how small you think the change is. Treat your designers as part of the team: Designers are just as invested in the success of the product as everyone else on the team. Make sure you actually give the designer time to respond and suggest corrections before the product goes to market. If the product is shown to her just for "informational purposes only," that's just as bad as if the designer has never used the product. Hopefully my experience and approach over the past few years will help designers and engineers form a good working relationship. I believe that good cooperation can lead to better products and a better user experience in the end. Tag: Engineer Designer