We have been running a remote-first design team since before the pandemic, and we recently had the chance to document how we coordinate all of this 👇

I just finished this article on creating better workflows for design and engineering. The principles have formed over years of collaboration with product teams and they're central to our work on improving how we build digital products designsystems.international/…

We're finally ready with the date and early program for @ProcessingOrg Community Day Copenhagen 2023! The event is on November 11th and will, among others, feature @timrodenbroeker as a keynote speaker. More info and registration on pcdcph.com

Pssstttt.... designsystems.international

Thanks Dylan! I'm really interested in this conversation too and appreciate you joining it. I completely agree that a design process based around systems can be very creative and fulfilling. Many of these new Figma features support this, and I think it's a better product for it. I do have this nagging fear that we're building design tools on top of an immature field with workflows that might cause more harm than good ("Ready for Dev" signaling a clear waterfall process that can be really unhealthy, etc). My biggest worry is that designers will now build complex systems that are completely detached from the complex systems that developers build for the end product, which – despite efforts for syncing up these tools – will result in duplicated work and less understanding of what's possible in code. But I can see that @figma has put a lot of thought into preventing these things and I'm also very excited about the possibilities around automation that these new features afford.