
I'm Arjun Dayal, an engineer, designer and music producer. I believe good design isn't artsy but objective. Every decision has a rationale and when you can explain why something works, engineers, executives and customer teams can participate and appreciate design. I lead teams at EverCommerce across 20+ products and sample great solutions the way a producer samples great records.
My perspective on design systems, leadership, and the craft behind the work and creativity.
- Process
How I increased my beat-making completion rate by 6x using master components
I spend my days building design systems. Interestingly enough, the same idea (one master component, many instances) is a productive way to finish a beat.
- Design leadership
How do you align a fully-remote team of designers?
How I started breaking down the silos across a 20-person remote design team and why I skipped the rigid design system everyone expects.
- Design systems
Design system foundations
Let's put aside tokens for a second. What does "thinking in systems" really mean?


