Right Tool for the Right Job: Why Overengineering Is the Real Enemy
And while navigating their onboarding, something caught my attention. Not a design pattern, not a component library — a decision
Instead of developing a fully-fledged interactive onboarding system with custom code, data mocks, iframe gymnastics and endless review cycles, they did something radically smarter:
They duplicated their existing Figma UI kit, built a clickable prototype, and used it as their onboarding.
No dev time
No backend
No smoke and mirrors
Just clarity
That’s when Dani Rojas’ wisdom hit me — not about guerilla warfare, but about product reality:
> “Right tool, right job. Everything else is wasted bullets.”
> — *Dani Rojas, Far Cry 6*
Yes, the quote wasn’t originally about software, but damn it fits
In numbers:
🟡 3–4 days to assemble
🔵 0 engineering hours spent on onboarding code
🟢 No CI/CD, no QA cycles, no mocks, no sprint planning
If they had built this onboarding natively, it would require:
Instead:
Figma → Prototype → Link → Done.
The onboarding objective didn’t need a factory
It needed a door
People often confuse tooling with expertise
**Knowing what to use is a skill
Knowing what *not* to use is mastery**
Tools do not create clarity
Decisions do
If the task requires a machete — don’t bring a missile launcher
If the task requires a prototype — don’t hire three developers to build an empire
And for the encore:
**The right tool for the right job isn’t a cliché
It’s the only strategy that scales**
Everything else is ego in technical disguise
