It’s outdated to think of designers working in isolation, unveiling their work in a grand presentation to surprised developers. Design should be a collaborative process from the start. Involving developers early brings valuable insights into technical constraints, feasibility, and opportunities. This not only saves time but also builds trust and mutual respect across teams. As a lead designer, it’s your responsibility to ensure your work aligns with the organization’s architecture—if one exists—and integrates seamlessly into the larger system. Great design thrives on alignment, not surprises. When teams collaborate from the start, the result is a smoother process and a stronger product.

Facing resistance from developers and convincing developers of feasibility may be two separate concerns, but assuming developers are non-believers in your design, roll up your sleeves and bang out a proof-of-concept. Be a developer. Lead by example. It doesn't have to be feature complete, just prove the concept that's in question. Stay centered on the user experience and it will be easy to get buy-in from stakeholders. Rationalize your architecture by documenting the considerations clearly. Set clear expectations of timelines for deliverables and be fair and reasonable by listening to those responsible for implementation, even though you aren't letting them hold you back. Most importantly work and communicate as one team together.