I Learned That Not Every Problem Needs a New Tool
When you build online tools, it’s easy to see problems everywhere.
A slow process.
A confusing task.
Too many steps.
And your first thought can be:
“I should build a tool for this.”
I’ve had that thought many times.
But I’ve learned to pause before opening my editor.
The Builder’s Instinct
Building something feels productive.
You have an idea.
You write some code.
You see something working.
That feels like progress.
But sometimes the problem isn’t big enough for a new tool.
Sometimes people just need a simpler way to do something.
I Used to Build Too Quickly
I would notice a problem and immediately think about the solution.
I rarely stopped to ask how often the problem actually happened.
Or how many people had it.
Or whether something already existed that solved it.
That led to some unnecessary work.
The tool might work perfectly.
But that didn’t mean it needed to exist.
A Better Question
Now I ask:
“Does this problem happen often enough to deserve a solution?”
Then I look at a few things:
- How many people have this problem?
- How often does it happen?
- Is the current solution difficult?
- Can I make the process meaningfully easier?
If the answers aren’t clear, I wait.
Waiting Is Also Research
This was another lesson for me.
Get Bhavin Sheth’s stories in your inbox
Join Medium for free to get updates from this writer.
You don’t always need to build something to learn about it.
Sometimes you can watch.
Read questions.
Talk to people.
Use existing solutions.
See where they struggle.
That can tell you more than immediately writing code.
Not Building Can Save Time
Every tool you create becomes something you need to maintain.
There are bugs.
Updates.
Mobile testing.
Browser differences.
User questions.
Small improvements.
So before creating another tool, I now think about the long-term responsibility too.
The Goal Isn’t More Tools
This might sound strange coming from someone who builds tools.
But I don’t want to build the largest number of tools possible.
I want the tools I build to be useful.
That’s a very different goal.
A smaller collection of genuinely useful tools is better than a huge collection nobody needs.
What I Do Now
When I get a new idea, I write it down.
Then I wait.
If the problem keeps appearing, I investigate it.
If it disappears from my mind, that’s useful information too.
Not every idea needs code.
Sometimes the best solution is realizing you don’t need to build anything.
Final Thought
Building is satisfying.
But solving the right problem is more important than building quickly.
I’ve learned to pause before I create.
Because sometimes the smartest product decision is:
Don’t build it yet.
