What I learned
Coming to the team at a later stage definitely makes the job more challenging since I have less context about the product history. A big part of what I do at the beginning was just reading through the Github ticket to better understand how decisions were made, since everything, down to every small UI tweaks, are documentated.
Using the same tool helps build deeper empathy between designers and engineers. Prototyping in code brings more credibility to my design decisions.
Open communication becomes especially important when collaborating closely with a engineering team, I've learned to always demonstrate clearly with mockups and prototypes what I am trying to achieve and also gather constant feedbacks from engineers to build consensus. It's also important to document the reason behind every design decision with clarity.
Using the same tool (Github) to design, develop and communicate really helps build deeper empathy between designers and engineers. In a highly iterative environment, opening a pull request also brings more credibility to the design decisions than static images. It allows me to establish trust and introduce systematic changes merely a few months before the launch.
Mapbox Studio is free and in active development. You can learn more about the tool here
and start using it today!