When Fun Meets Function: Lessons from Designing a Developer Tool Email

Problem

Is it more important to be interesting or appropriate? Do I prefer what I find interesting, or what meets the actual need?

Beginning of the Story

Shortly after joining the company, I stumbled over a new internal testing toolkit called Tequila . Tequila is a JDC‑incubated UI automation testing package, and I was asked to design a launch email to promote it.

The toolkit had no logo or visual identity—essentially a blank canvas. The email format was unrestricted; it could be formal or casual. Encouraged to be creative, I initially decided to go bold and free.

Rejected Approach

I avoided any framework constraints and tried to break the company’s traditional email style to make it more engaging. I centered the concept around the name “Tequila,” a cocktail, weaving a story about developers drinking tequila for inspiration and creating the tool. The email was written as a developer’s diary, peppered with internet memes and trends.

Reflection on Issues

The result felt off: it resembled a sales pitch for alcohol rather than a developer tool announcement. I realized three key problems:

The playful, gimmicky design clashed with the tool’s need for a clean, professional tone.

Developers, the primary audience, might not appreciate the trendy slang and memes, causing distraction.

In a crowded inbox of internal notices, the email could be mistaken for a promotional message and ignored.

New Approach

After rethinking, I modeled the new design on examples from similar tools’ official sites. This version emphasized the tool’s core attributes—functionality, rigor, and simplicity. I used a straightforward visual of the tool in action as the header image, kept only essential information, and applied a restrained layout. The only nod to the original “Tequila” theme was the color palette, inspired by classic tequila sunrise and margarita drinks, applied to background gradients and accent colors. The revised email passed review.

Conclusion

Returning to the original question—should the focus be on being interesting or appropriate? The answer is that both matter: the email must reflect the tool’s professional nature while still being engaging enough to leave a lasting impression.

Key Insight

The ultimate lesson is to continually ask, “What underlying problem does this design solve?” rather than getting lost in superficial aesthetics.

(PS: In a later meeting, the tool was renamed from Tequila to Tiga.)