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
If you ship features fast but users don't use them, it's usually one of two reasons:
The feature doesn't solve the core problem yet
Users can't tell how to finish the job with it
Tooltips and guides don't fix either one. They add more for users to read and more for the team to build.
Before you add anything, ask two questions:
What do we want users to do here?
What's stopping them?
Then remove what doesn't help them get there. In a complex workflow, that's usually a step, a field or an option nobody needed.
Remove first. Build only what's still missing. Build less. Get more of it used.
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
Challenges
View all
Related posts
Same data, two different ways to experience it 🤔
I explored two patient list layouts for a mental health platform: a card view and a table view.
Cards feel more visual and personal, but space is limited and adding more information can quickly make them crowded. For complex enterprise products, I often find tables more practical — they’re easier to scan, compare, sort, and can support more columns when users need greater visibility.
For this kind of workflow, I’m leaning toward the table view. Which would you choose — cards or table?
11 voted
55%
9 voted
45%
20 votes
Closed
For a mental-health patient list the choice isn't really card vs table — it's scan-speed vs context. The card wins the first meeting because the photo and name set the clinician's mental model before they touch the row, but the table is what holds up under the daily rhythm of...
Dashboard and MCP request design for sales platform
The goal was the keep the experience simple for the users. Dashboards contain the majority of the information while the MCP request flags what's needed.
Check it out
I love this clean design 😍
