explanations of expected behavior and interaction ‣ Leave room for feedback Demos and decomps Pair design and development ‣ Video calls and screen sharing ‣ Use the browser dev tools to tweak and adjust styles Keys and guides ‣ Added layers and artboards to guide and explain the comps Prototypes ‣ Visual: Figma, Keynote, After E ff ects, et al ‣ Code: CodePen, Web fl ow, et al
culture of understanding between your designers and developers. Action Items and Goals ‣ Make a list that is attainable and visible to the whole team. Repeat Back Expectations ‣ Designers repeat back to developers what they understand the devs need and vice versa. Retrospectives ‣ Regular checks for how things are going and what can be improved. Third-Party Helpers ‣ Get help when there are clear communication breakdowns.
team and between designers and developers. Experimentation ‣ Work through di ff erent ideas both in design tools and code editors and iterate on the ideas. Group Improvisation ‣ Work with freedom to try new things and to push limits. ‣ See Ben’s article on The Foundry. Share What You Learn ‣ Team and project demos. ‣ Get feedback and answer questions.