Sara Jin
Design & Frontend
The first time someone said BuildFlow felt 'quieter' than the tool they replaced, we knew the design was working. Here are the six rules that make it feel that way.
1. Default to muted
Color is a tool, not a vibe. We reserve our brand indigo for one thing per screen — usually the primary action — and let everything else recede into greys. The eye lands on what matters because there is only one place for it to land.
2. Type does the work
Headlines are tight (-0.02em), bodies have honest line-height (1.6), and we never use more than four weights of Inter on a single screen. Hierarchy through type beats hierarchy through color in 9 out of 10 designs.
3. Motion has a job
Every animation must answer 'what does this teach the user?' Sliding the active tab indicator teaches that tabs moved. Bouncing icons teach nothing. So we don't ship bouncing icons.
4. Notifications are opt-in
Defaults compound. If new users land in a workspace with notifications on for every thread and every reaction, the product feels noisy forever. We default to off, and let users turn things on as they need them.
5. Empty states earn their keep
An empty board is a chance to teach. We use empty states to show one example, one CTA, and zero illustrations of cartoon astronauts. The astronaut doesn't make me create a project.
6. The audit log is part of the UI, not buried
Every page has a small, tasteful link to the relevant slice of the audit log. People who care about it find it. People who don't aren't distracted by it. Both groups stop asking us for change logs.