
I'm Arjun Dayal, an engineer by training, a designer by practice, a music producer by identity. I believe good design isn't artsy. It's objective. Every decision has a rationale, every pattern has a reason, and when you can explain why something works, engineers, executives, and customer teams can participate in making it better. I lead design at EverCommerce across 20+ products and sample great solutions the way a producer samples great records.
Loose thoughts, theories, and things I'm chewing on — the experiments behind the polished work.
- 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?


