How to work with the design team
We're a lean team, but we work across a wide surface: product, marketing, and brand. Design at Resend isn't just about visuals or usability. It's about setting the tone, shaping the experience, influencing the roadmap and making sure everything feels cohesive. Here's how to work with us day-to-day:
What can design help with?
Design can help shape flows, simplify complexity, clarify communication, and align what we build with what users actually need. If something feels confusing, inconsistent, or off-brand, we want to know. No detail is too small and our users deserve the best we can deliver.
How to ask for design support?
Drop a message in #team-design or tag us directly in Linear. Avoid sending DMs as much as possible, we like to work in the open.
For bigger asks, always remember that context is everything. What are you trying to solve? What's not working? How does it affect the user? And be prepared, we're going to ask why. A lot.
What's expected when framing a problem?
Always start with context, not conclusions. We don't expect solutions. Tell us what you're seeing, what's not working, and why it matters. The best prompts include screenshots, user feedback, data, and goals.
How do I give feedback on design?
Start by understanding the design process.
In Discover mode, focus on the big picture. Are we exploring the right problems? Are the alternatives thoughtful? Avoid getting stuck on details too early.
If we're in the Polish phase, then it's time to zoom in. Look at the full flow, edge cases, alignment, copy, and visual precision.
We welcome feedback that's clear, specific, and tied to user goals or outcomes. The most helpful comments focus on clarity, intent, or impact rather than personal taste.
If you're sharing a personal take, that's totally fine. Just frame it as:
"As a developer, this feels..."
"In my opinion, I'd prefer it like this..."
Try to avoid phrases like "users will" or "people prefer" unless there's research or data behind it. The design team works to balance different needs and perspectives, so your experience matters, especially when it's grounded in how you use the product.
Where to leave feedback?
Add comments directly in Figma or reply in Slack threads. Avoid leaving feedback in Loom videos or GitHub issues, since it can be hard to track or easy to miss.
What are our tools?
- Notion: for writing and planning
- Figma: to sketch ideas and compose screens
- Code: as source of truth of all design assets
- Linear: for issue management and user feedback
- Loom: to share explorations and ideas
How does the design team use Figma?
We use Figma to explore ideas, build systems, and collaborate in the open.
Projects are organized by product or domain: Dashboard, Website, Brand, Socials, and so on. Each project contains specic files that usually follow a consistent structure: Checkpoints (CP1, CP2, CP3) to track progress, Playground for explorations, and Backup to document discarded directions.
By following the same structure across files, it’s easier for anyone to navigate our work and know what to expect.
What are our rituals?
Beyond the company rituals the design team has:
- Weekly planning: Every Monday, we have a 30 minutes meeting to we review all the work we did last week and plan what are the goals for the current week.
What are the current challenges at Resend?
Maintaining quality at scale. As a dev tool, design isn't just polish—it's core to the experience and a key differentiator in the industry. We're constantly balancing speed, simplicity, and flexibility across a growing surface. That means pushing past the status quo, advocating for clarity in an complex problem space, and designing for a wide range of use cases without adding friction.
Why is the process important in design?
Process helps us achieve quality at scale. It gives structure without rushing ideas, creating space to explore, align, and refine. Without it, we risk delivering half-baked work instead of thoughtful, durable solutions.