214
votes
Accepted
Should we kill the features that users are not using frequently, to improve performance?
Beside what was said in the other good answers here, you have a much more basic problem. You are misreading your data.
A heatmap generally sums up all clicks on a pixel, regardless of who made them. ...
- 6,254
86
votes
Should we kill the features that users are not using frequently, to improve performance?
Performance is important, but even more that your goals are achieved.
Consider what kind of users are utilising the sorting feature. Because, for example, it might happen that those users, although ...
- 16.9k
40
votes
Should we kill the features that users are not using frequently, to improve performance?
Do your users know that the columns are sortable?
I ask this, because even though there appears to be a sort indicator on the first column, the users may not realize that they can click the headings.
...
- 801
25
votes
Should we kill the features that users are not using frequently, to improve performance?
This may be a bit off topic as it more sits under the development side of things. As a full stack developer I can say that search functionality can be performance intensive. This all depends on what ...
- 375
11
votes
Should we kill the features that users are not using frequently, to improve performance?
You should always be extremely cautious about removing a feature. Most companies don't have a very good idea of why their customers choose their products over their competitors'. There's always the ...
- 210
10
votes
Should we kill the features that users are not using frequently, to improve performance?
Some good thoughts have already been shared, so I'll just add one thing I didn't see. While the quantitative data around the features use is important, it doesn't reveal why users are or aren't ...
- 101
4
votes
Should we kill the features that users are not using frequently, to improve performance?
To me, the key question when deciding to kill off or redesign an existing feature is simple: what will be the net gain in usability? The general rule of thumb is if you don't see a gain of at least 20%...
- 161
4
votes
Should we kill the features that users are not using frequently, to improve performance?
It seems that if you remove the sorting feature users will have difficulties finding under performing campaigns. This sounds like an important action, if not the primary one, therefore, you should ...
- 11.6k
3
votes
Should we kill the features that users are not using frequently, to improve performance?
Before even considering removing a feature (which took resources to make) think about the following:
Who uses it? Depending on the application sorting might be a feature which only power users use ...
- 555
3
votes
Trying to sort color palette by heat
I'd recommend, if at all possible, to pick only 2 or 3 colors to represent your coldest, (optionally middle), and hottest points in your values, and calculate the gradient between them based on ...
- 19.6k
3
votes
Accepted
What color scale to use for heat map with positive and negative values?
Red and green are well known for positive and negative values. What is your domain?
Question: What do other companies in your domain do, and what are users trained to expect when interpreting these ...
- 25k
2
votes
Should we kill the features that users are not using frequently, to improve performance?
Keep the interface as it is, but ask the developers to move the sorting processing to the client-side.
This will take the strain off the database, and the app will run fast for people who don't sort.
- 121
2
votes
Accepted
Do "rage clicks" on navigation that is supposed to be used repeatedly indicate a problem?
Hopefully, the tool you're using that identifies rage clicks also has session playback. I think your next step is to watch 10-20 playbacks of that particular area and see how quickly the clicks are ...
- 12.9k
1
vote
How to describe two variables in a heatmap?
There are a number of different strategies you can apply, depending on the technical constraints that you have. For example, you can make the table more interactive and allow the cell to show ...
- 27.7k
1
vote
Accepted
Visitor-recording solutions and sensitive data?
I'm the founder of Tamboo (https://gettamboo.com), which is a visitor recording solution much like HotJar or LuckyOrange.
Each type of visitor recording solution addresses privacy and security ...
1
vote
Visual element getting too much attention in heat map
It looks like the element is gaining attraction because users don't know what it is and try to interact with it. So users might be asking themselves "What is this element?" "Am I suppose to interact ...
- 16.9k
1
vote
Should we kill the features that users are not using frequently, to improve performance?
Good answers already, but I can't resist adding my two cents.
The problem is that the percentage of users using a feature is not an accurate metric of the importance or value of a feature.
This ...
- 111
1
vote
Should we kill the features that users are not using frequently, to improve performance?
One, sorting is a feature that users will take for granted. So no user will ever tell you how great that sorting feature is - they will tell you and be very unhappy if that feature is gone.
Two, I'd ...
- 496
1
vote
Should we kill the features that users are not using frequently, to improve performance?
I don't think it is as simple as you should or shouldn't. Is the performance issue perceived or actual? Are you seeing lengthy page load times for search terms that produce a significant amount of ...
- 6,324
1
vote
Should we kill the features that users are not using frequently, to improve performance?
No you should note remove this. Because sorting is the important feature you can use it in future with more refined search criteria..Instead of removing it, make it more detailed probably user not ...
- 724
Only top scored, non community-wiki answers of a minimum length are eligible