Trung Nguyen
← Journal
Tools 12.01.25 4 min read

The case for boring tools in creative work

Every few months a new tool appears that promises to change everything. Usually it doesn’t. The tools I keep coming back to are the ones that stay out of the way.

The novelty trap

There’s a particular pleasure in trying new tools. The fresh interface, the promise of new workflows, the feeling that this time things will be different. I’ve fallen for it more times than I’d like to count.

The cost isn’t just setup time. It’s the cognitive load of learning new patterns, the broken muscle memory, the weeks of suboptimal work while you’re still figuring out where everything lives. And then, six months later, you’re back to the old thing anyway — or on to the next new thing.

What “boring” actually means

Boring tools are tools where the interface has disappeared. You’re not thinking about the software; you’re thinking about the work.

Figma is boring in this sense. Not because it’s simple — it’s genuinely complex — but because after a year of daily use, the gap between intention and execution is nearly zero. I can externalise a thought faster than I can fully form it.

The productivity ceiling

New tools have a low floor and a high ceiling. You can get started quickly, but mastery takes time. Boring tools have a higher floor (onboarding is harder) but the ceiling is also higher, because you’ve invested the time to actually understand them.

The question to ask isn’t “what’s the best tool?” but “what’s the best tool for someone who’s been using it for two years?”

The one exception

The exception is when a new tool collapses a category. Figma didn’t just replace Sketch — it made real-time collaboration in design possible for the first time. That’s not a novelty, it’s a fundamental shift.

When a tool changes what’s possible, not just how you do the same thing, it’s worth the switching cost. When it promises to make the same thing slightly faster or more enjoyable, it probably isn’t.

Discussion

Powered by GitHub Issues. Join the conversation ↗

huy.tran 3 days ago
This resonates a lot. I spent 3 weeks wrestling with a Chakra UI setup before giving up and writing 4 simple components from scratch. Done in an afternoon.
trungnguyen 2 days ago Author
4 components you understand beats 200 you don't.
linh.nguyen 1 day ago
The "rented apartment" analogy is perfect. Sharing this with my team.

To leave a comment, you need a GitHub account.

Comment on GitHub

More from the Journal

Thinking

On writing as a design tool

Read ↗

Product

What makes a product feel intentional

Read ↗

Process

Shipping fast without losing craft

Read ↗