The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
I used to think a better product meant adding more features.
Now I think the opposite is often true.
Every new button, setting, and option gives the user one more thing to understand.
Sometimes the best improvement is not adding something new — it’s removing something people don’t really need.
A simple product that solves one problem well is usually more useful than a complicated one that tries to do everything.
What’s harder in your experience: adding features or deciding what to remove?
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
We’re choosing the motion for an AI analytics product demo, and I can’t decide.
Both clips show the same flow. Someone asks a question in plain English. The agent checks permissions, plans the query, runs it past guardrails and builds the dashboard.
1. A walks you through each step as it happens.
2. B skips the steps and drops you straight onto the result.
A shows the work. B shows the speed. For a landing page I keep going back and forth.
Which one would make you trust the product more? Comment A or B, and tell me why.
3 voted
100%
0 voted
0%
3 votes
Closed
I think according to your query the output should consist on a list of clients with late invoices rather then showing charts etc,
Here's the product.
Which one looks better?
Choose any one.
0 voted
1%
0 voted
1%
0 votes
Closed
Which use cases section do you prefer, A or B?
2 voted
67%
1 voted
33%
3 votes
Closed